Telegram

Telegram is a first-class channel in Lane.Chat. A Telegram bot can act as a full customer-support endpoint: visitors DM your bot, messages land in the same inbox as web chats, AI and Flows run the same way, and agents reply from the dashboard.

How it works

1. You create a bot with @BotFather and get its token.
2. You connect the bot to your application in the Lane.Chat dashboard (paste the token; Lane.Chat registers the webhook for you).
3. Telegram delivers updates to Lane.Chat's webhook. Inbound messages are normalized and routed through the same visitor-message pipeline as every other channel; outbound agent/AI/Flow messages are translated back to Telegram's native format.

Connecting the bot

Paste your bot token into the application's Telegram settings in the dashboard. Lane.Chat calls Telegram's setWebhook for you and starts receiving updates — there is no endpoint for you to host or configure.

Message translation

Outbound rich messages degrade gracefully to Telegram:

• Buttons and card buttons become inline keyboard buttons; button clicks come back as callback queries and are routed into your Flows.
• Carousels are sent as a sequence of cards.
• Markdown and link messages render as formatted text.
• Media (images, stickers, GIFs, voice) maps to the closest native Telegram type, with a text fallback where there is no equivalent.

Inbound Telegram messages (text, media, stickers, replies, button callbacks) are normalized to Lane.Chat's internal message shape before they hit your Flows, AI, or webhooks.

Binding a visitor to Telegram

A web visitor can link their Telegram account so replies reach them there. The widget requests a one-time binding code via POST /v1/binding/telegram/generate; the visitor sends it to the bot to complete the link.

Deep links

Your application's connected bot username is returned to the widget in the session appConfig as telegram_bot_username, so you can build https://t.me/<bot> deep links in your own UI.