Raised in Slack. Answered on the go.

Route Slack tickets into Telegram

Slack
Telegram

Slack is a desk tool. The moment your team steps away - on call, on the road, between offices - it goes quiet, and so does anything raised in it. Telegram, with over a billion monthly users, is already on the phone in everyone's pocket. Routing Slack tickets into Telegram means a request raised at the desk can still get answered from anywhere, by whoever's reachable.

Why this pairing

Why teams send Slack to Telegram

Slack is where work is raised during the day; Telegram is where your team stays reachable after it. Pairing them keeps tickets moving around the clock - raised at a desk, answered from a phone, returned to Slack as if nothing unusual happened.

  • Keep responding to Slack tickets when nobody's at a laptop - the answer comes from a phone.
  • Each ticket opens as its own Telegram forum topic, so on-call chaos stays organized.
  • Great for night shifts and distributed teams: Slack stays staffed after the desks empty.
  • Replies return to the original Slack thread, so the requester sees a normal Slack answer.

How it works

One thread, both ends

Someone in a connected Slack workspace runs /ticket. InboxBarn listens over Socket Mode, captures the thread, and routes it onward without anyone touching a help-desk portal.

InboxBarn routes that conversation into Telegram as a forum topic per conversation inside a Telegram supergroup. Your team reads it and answers it right there, in the tool they already have open - no portal to log into, no queue to refresh.

The reply always goes back on the channel the customer used.
Whether your agent types in Telegram, the dashboard, or somewhere else entirely, the answer is delivered to the same Slack thread they started. The customer sees one continuous conversation in the tool they chose - they never know, or need to know, where the work actually happened.

Setup

Set it up in three steps

  1. 1

    Connect Slack over Socket Mode

    Install the InboxBarn Slack app, switch on Socket Mode, and the /ticket command is live for everyone in the workspace - no public webhook to host.

  2. 2

    Connect your Telegram bot

    Paste a bot token from @BotFather and point it at a forum supergroup where the bot is an admin with the Manage Topics permission. Each conversation opens as its own topic.

  3. 3

    Pick a category and go live

    Map the source to a routing category (general, billing, VIP, sales) and point your destination at it. Send a test message - it should appear on the other side in seconds, and your reply should land right back where it started.

1 billion+

monthly active users on Telegram. Telegram is already open on the screens of the people who answer your customers - routing to it just meets them there.

Source: Telegram founder Pavel Durov, March 2025

Questions

Frequently asked

Does the Slack user need Telegram?

No. They raise and receive everything in Slack. Telegram is only where the on-call responder reads and replies.

How are tickets kept separate in Telegram?

Each one becomes its own forum topic in a supergroup, so concurrent tickets don't blur together.

What's required to connect Telegram?

A bot token from @BotFather and a forum supergroup where the bot is an admin with Manage Topics.

Where does the reply go?

Back to the original Slack thread, even though it was typed in Telegram from a phone.

Connect Slack to Telegram today.

Every channel is included on every plan - no per-channel taxes. Wire up the bridge in a few minutes and answer your customers from the tool your team already lives in.