Skip to main content
Conversations through a connected Facebook Page use ticket.channel.type: "facebook" in webhooks. Contact identities use facebook_user_id. Pages are connected and managed in the YoLead UI.

​
Messages and sending

Employees can reply to existing conversations, including through Embed with showSendInput. Sending requires a usable connection, employee access, and the permissions granted by Meta. Starting a new conversation from a contact identity is unavailable.

​
Attachments and history

Incoming messages can include attachment descriptors in Public API ticket history and message webhooks. Older stored messages are not automatically backfilled with attachment metadata. Outgoing attachment sending is currently unavailable. Messages already stored in YoLead remain readable after disconnection, subject to company access and plan restrictions. File availability follows storage and provider restrictions.

​
Referrals

Supported ad and OPEN_THREAD referrals can supply ref, ad_id, source, and type in ticket.attribution. Standalone referrals and postbacks can also appear as messages in history. Attribution is captured when the ticket is created; later messages preserve it. See Ticket attribution.