Telegram is here

Connect a Telegram bot to your WATeamInbox

WATeamInbox now supports Telegram through the official Bot API. Create a bot with BotFather, connect it, and handle Telegram chats in the same shared inbox as WhatsApp.

Your customers do not all live on one app. Some message you on WhatsApp, others on Telegram. Until now WATeamInbox handled the first group; now it handles both, in the same shared inbox, with the same assignments, notes, and replies your team already uses.

WATeamInbox connects to Telegram through the official Bot API. You create a bot, paste its token into the app, and incoming direct chats land in the inbox next to your WhatsApp conversations.

One thing to know first

A Telegram bot can only reply to people who have started a conversation with it. A customer must open your bot and tap Start before the bot can message them. WATeamInbox cannot use a bot to cold-message an arbitrary Telegram user — that is a Telegram rule, not a WATeamInbox limitation. In practice you share the bot link (or username) wherever you already share your contact details, and conversations begin when customers reach out.

Connect a bot in four steps

  1. Create a bot with BotFather. Open @BotFather in Telegram, run /newbot, choose a name and username, and copy the token it gives you. Treat that token like a password.

  2. Prepare your self-hosted instance. Telegram runs on the channel-neutral side of WATeamInbox, so configure the channel credential keyring, set a public HTTPS APP_URL, reconcile the channel-spine indexes, and enable Telegram for the workspace. The channel-neutral operations guide walks through this, and provisioning fails closed if a prerequisite is missing — so a half-configured instance will refuse to connect rather than silently misbehave.

  3. Open Settings → Connections. Choose Telegram Bot, give the connection a recognizable name, and paste the BotFather token. WATeamInbox validates the bot and registers its webhook for you. The token is stored encrypted and never shown again.

  4. Send a test message. Open the bot in Telegram as if you were a customer, tap Start, and send a low-risk message. It should appear in the shared inbox within moments, where an authorized teammate can assign it and reply.

For the full version with callouts, see the Connect a Telegram bot doc.

Webhook requirements

Telegram delivers messages by calling your application’s HTTPS webhook, so your instance must be reachable from the public internet over HTTPS. For local development, expose the app through a trusted tunnel and keep APP_URL aligned with that origin — otherwise Telegram’s webhook calls will not arrive and conversations will not appear.

It behaves like any other channel

Once connected, a Telegram chat is a first-class conversation. Your team can:

  • Assign it to a teammate and leave internal notes
  • Reply, with the message delivered back through the bot
  • Resolve, reopen, and track it under the same case workflow as WhatsApp

You can run WhatsApp and Telegram side by side in one workspace. When more than one account is connected, WATeamInbox is explicit about which account a conversation belongs to, so a reply never goes out from the wrong place.

If a token leaks

If a bot token is ever exposed, revoke and regenerate it in BotFather, unlink the affected connection in WATeamInbox, and reconnect the bot with the new token. Your existing conversations, assignments, and notes are kept. Never paste tokens into issues, logs, screenshots, or support messages.

Try it

Telegram support ships in the open-source edition today. Self-host WATeamInbox, follow the Telegram connection docs, and give your customers one more way to reach a team that answers from a single, shared inbox.

Questions? Message usWhatsApp · +65 8404 2683