Telegram

To connect Telegram, open the in-app Connections settings.

Telegram is a chat-style channel for prompting Dispatch from your phone. You message Dispatch's Telegram bot the same way you would chat with a person; the agent runs your prompt and sends the response back as a Telegram message.

How the connection works

Telegram is set up by starting a chat with Dispatch's bot and linking your Dispatch account. Once linked, messages you send to the bot create chat-origin agent runs in your account.

Read capabilities

• Receive text messages addressed to the Dispatch bot in linked chats.
• Non-text updates (photos, files, voice notes) are ignored by the webhook in this release; only text is read.

Write capabilities

Telegram sends take one of two paths:

• Chat reply to your prompt. When you message the bot, the agent's streamed text is delivered back to the chat by the Telegram channel sink (telegramChannelSinkCreate). The channel sink is the response-delivery transport for a chat-origin run; it is not a tool call and not routed through the permission gate.
• Additional sends via the telegram_send_message tool. When the agent decides to send a separate message (a scheduled brief, an automation-originated post, or an extra reply alongside the streamed response), it calls telegram_send_message. That tool carries the external-write risk annotation and routes through the permission gate. The gate consults your policy on every call once the permissionAgent enforcement flag is on for your org; while the flag is off the gate emits telemetry and lets the send through.

What automations can use

• Scheduled actions that post to a linked chat are supported.
• Trigger automations that fire on incoming Telegram messages are not currently exposed; chat is the standard interaction model.

Limits and behavior

• One linked chat per account. A Dispatch account is linked to one Telegram chat at a time; the user can re-link to a different chat if needed.
• Tool-driven sends are gated. When the agent calls telegram_send_message — for scheduled briefs, automation-originated posts, or additional messages alongside a chat reply — the call routes through the permission gate (validator consultation requires the permissionAgent flag to be on). Chat replies delivered by the channel sink are not gated. The policy file controls cadence and content rules for the gated tool path.
• No group chats. Dispatch operates against a one-to-one chat with the bot; it does not act inside Telegram groups.

Related

• Permission gate
• Automations: scheduled messages to Telegram are a common pattern.
• Cookbook: VIP alerts for getting pinged on Telegram when a top contact reaches out.