ticket.channel.type: "telegram" in webhooks. Personal Telegram accounts use the separate Telegram Account channel type. Bots are connected and managed in the YoLead UI.
Contacts and sending
Telegram Bot recipients usetelegram_user_id. Starting an outbound conversation requires a user who has previously contacted the connected bot and whom the bot can still reach. A contact identity alone does not grant permission to message that user.
In Embed, replying in an existing chat requires showSendInput. Starting a new conversation requires startOutboundChat, employee access, and the corresponding plan feature. See Embed capabilities.
Messages and attachments
New messages can contain attachment descriptors. Telegram albums appear as separate messages; Public API history can includemediaGroupId to group their items.
Employees can send up to five JPEG/PNG photos or up to five documents in one send. Photos and documents cannot be mixed. The caption limit is 1024 characters. Photos support up to 10 MiB per file and documents up to 20 MiB, subject to lower storage limits and provider restrictions.
Attribution and history
An incoming/start command can supply ticket.attribution.payload when it creates a ticket. See Ticket attribution for capture rules.
History contains messages stored by YoLead. Starting a new outbound bot conversation does not import earlier Telegram correspondence. Ticket history and incoming-message webhooks use the common message contract.