The 1:1 Telegram bot is great for individual customers, but a lot of B2B support happens in shared Telegram groups — one chat with your client's whole team, where several issues run in parallel. The Telegram Group channel is built for exactly that: one bot serves any number of groups, each group becomes a single conversation in your inbox, and the AI automatically splits the traffic into per-topic threads.
Every thread gets its own title, status, priority and assignees, so your team works topic by topic — while the client's team just keeps chatting in their group as usual.
Create the channel
- Go to Projects → your project → Channels and create a new channel of type Telegram Group (multi-thread).
- Paste a bot token from @BotFather. You can create a fresh bot, or reuse the bot that already runs your 1:1 Telegram channel or your helpdesk notifications — when you paste a token Chatonio already knows, it shows which roles that bot is shared with. A bot can only be used within one project.
- Once the token is accepted, the channel page shows a connect command that works for every group you want this bot to serve.
Connect your groups
- Add the bot to the Telegram group as a member.
- Let it read group messages: open @BotFather, run /setprivacy, pick your bot and choose Disable. (Making the bot a group admin works too.)
- Post the connect command from the channel page — /connect followed by your secret — in the group. The bot replies in the group to confirm.
Repeat this for as many groups as you need — the secret is reusable. Everything you've connected appears in the Connected groups list on the channel page.
If you offer Telegram chat in your help center, a client can link a connected group to their account. Everyone in that group then counts as that account, including for tools limited to signed-in customers. See Helpdesk login options, section Telegram chat in the help center.
Auto-accept mode
The How new groups bind setting controls what happens when the bot hears from a group it has never seen:
- Require connect secret (default, recommended) — new groups stay silent until someone posts the /connect command, so you decide which groups get in.
- Auto-accept any group — any group the bot is added to is connected automatically on its first message. Faster onboarding, but anyone who knows the bot's username can start a conversation — keep the username private in this mode.
One note: a bot that has only a 1:1 channel (no group channel) politely explains that it works in direct messages and leaves the group.
How threads work
- Each connected group is one conversation, and every message shows which group member wrote it. A bot command on its own, such as /start, is ignored and doesn't open a thread.
- While the AI is switched on for the project and the channel, it reads the recent chat and files each new customer message by what it is about, not by when it arrived. Everything about one request stays in one thread: the greeting that opened it, order numbers and details sent piece by piece, screenshots, corrections, “any news?” nudges, a colleague adding to the same case, and the thanks at the end. A different subject gets its own thread, even a minute later from the same person. Telegram's reply feature is only a hint: people often reply to the latest message to write about something new.
- The AI gives each thread a short title in the customer's language once the actual request is known. Until then (for example, while a thread holds only a greeting) it shows as Thread #N. A title you give a thread yourself, when you create it or move a message into a new one, is never replaced.
- Threads use the same statuses as conversations — New, Escalating, Processing, Waiting, Resolved, Closed — plus their own priority and assigned operators.
- The AI answers in threads it still owns (New or Escalating). When the last message in the group belongs to another thread, its reply quotes the customer's latest message in its own thread, so the group can see which topic it answers.
Replying as an operator
- Open the conversation: the Threads sidebar lists active threads. Click one to see only its messages, or switch to All messages for the chronological view.
- Replies always belong to a thread, but in the browser you don't have to pick one first. In All messages, your reply goes to the open thread with the latest customer message. To send it elsewhere, click the thread name next to the Chat and Note tabs and choose another open thread or New thread; what you've typed comes along. A customer message that arrives while you type doesn't move your reply. With no open thread, your message starts a new one. When you've opened a single thread, replies go to it; a closed thread can't be replied in. In Telegram, your reply quotes the customer's message by the same rule as the AI's. In the iOS, Android and desktop apps, pick the thread first, then type.
- Claim a thread to take it over: it switches to Processing and the AI goes silent in that thread while it keeps handling the others. Sending a message into an unclaimed thread claims it automatically.
- Set status and priority per thread, and add extra operators when a topic needs more hands.
- An escalated thread is not assigned to anyone automatically, even when an operator is available. Instead, your team is notified through the Needs an operator row, which each operator sets for each project under Account → Notifications. With On shift (the default), the notification goes to whoever is on shift in the project, plus anyone set to Online. In a project with no shifts set, each operator is notified during their own shifts in other projects, or at any time if they have none. Offline counts as off shift. To get these notifications at any time, set Needs an operator to Always. On a phone or in a browser, the notification's title is the thread title followed by the group name; in the desktop app the title is Action needed.
- Resolve a thread when the topic is done. If the client comes back to it later, a fresh thread is created instead of reopening the old one.
Moving a misfiled message
If a message ends up under the wrong topic, open its Move action, pick the destination thread — or choose Create a new thread and give it a title. The same action works for messages left without a thread (Unclassified).
Managing groups and the secret
- Rotate secret — generates a new connect command. The old one stops working immediately; already-connected groups are not affected.
- Stop accepting new groups — clears the secret entirely. Existing groups keep working; rotate the secret later when you want to add more.
- Disconnect a group — removes a single group from the Connected groups list. Conversation history is preserved, but the group has to post /connect again to send new messages. It also removes the group's link to a client's account.
- Remove bot — detaches the bot from the channel entirely.
New to Telegram bots? See Connecting a Telegram bot for the BotFather basics.