By the Onsites AI team · Last updated · 5-minute read
Telegram is where a surprising number of customers already live — fast, informal chat that feels like messaging a friend rather than filing a request — and it takes minutes to turn that traffic into a proper support channel. Setup is two steps: create the bot with Telegram's own @BotFather, then connect it to your desk in Settings → Channels. From that point, every message a customer sends your bot becomes a conversation in the same shared queue as your email and website chat, with the full team behind it. This guide covers both steps plus the operating habits: who answers, how fast, with what saved replies.
For many markets — Eastern Europe, Central Asia, Southeast Asia, large parts of the Middle East — Telegram is not a messaging app so much as the internet's inbox: people run their commerce, their communities, and their customer relationships inside it. A buyer who found your site from a Telegram group will ask their first question in Telegram, not in your contact form. Giving them a channel that answers with full context — their account, their previous conversations — rather than asking them to "please email support" is the entire difference between a chat that converts and a chat that evaporates.
For the team, the math is just as good. Telegram conversations arrive in the same queue as everything else: claimable, taggable, SLA-tracked, with private notes for internal context and the customer history attached if the person has contacted you before. One bot, one queue, no new logins for anyone — and the bot identity stays stable across employee changes, which is exactly what a personal Telegram account used for support cannot promise.
Telegram's bot platform needs no code. In Telegram, talk to @BotFather, send /newbot, choose a display name and a username (this becomes the public handle — yourcompany_support_bot reads better than bot547821_bot). BotFather replies with a token; keep it, because the channel setup in your workspace asks for it. Two settings in the same conversation are worth doing while you are there: a description line that says what the bot is for ("Support for Acme Trading — replies from the team, weekdays 9-18") and the bot's about text. Both show up in the bot's profile and set expectations honestly.
One decision to make consciously: the bot username is forever, and customers will type it. Support-flavored names ("..._support") signal that a team — not a marketing funnel — is on the other end.
In Settings → Channels → Telegram, paste the token from BotFather and save. That is the entire integration: messages sent to your bot now arrive as threads in the shared queue, replies your team sends go back into the customer's Telegram chat, and the message history stays attached to the conversation. If your customers arrive from a website too, the same customer contacting you on both channels unifies under one record — the omnichannel guide explains how one queue behind several channels changes team behavior; the mechanics here are identical.
The greeting. First message a stranger sends the bot should get a reply that states who answers, from where, and when: "You've reached Acme support — replies from the team, weekdays 9–18, usually within the hour." Save it as a canned response; the template library guide has the twenty worth saving.
The timezone promise. Telegram is global and your working hours are not — state them in the greeting, and set the hours in Settings so the queue escalates honestly when volume outruns staff. The SLA guide covers how the escalation actually triggers.
Tag vocabulary for messaging traffic. Telegram questions cluster ("shipping", "orders", "quote-request") and they deserve the same tags as the rest of the desk — with one channel-specific addition worth considering: "from-tg", so you can later see what this channel brings in before deciding to advertise it more.
Team norms. Whoever sees a Telegram thread claims it in the queue exactly like email — first-touch at this size, with round-robin once you outgrow it, as covered in the assignment guide. Nothing about messaging channels requires re-learning the desk; one queue, same rules.
Match the register. Telegram reads casual — short sentences, no letterhead, first names. The customer who writes "hey, quick one" will find a 400-word formal letter alien; the same customer on email expects it. Keep two registers in your reply style, and let saved replies be written once per register rather than shared.
Attach things. Telegram handles photos, PDFs and documents natively, and customers use that freely — a photo of a damaged carton is better evidence than a paragraph. Those attachments land in the thread like any other message and count toward storage like everything else; text is tiny, so conversations rarely dent the free 100 MB — the storage guide has the honest math when documents pile up.
Handle the out-of-hours expectation. Telegram's always-on feel makes an unanswered 23:00 message feel like neglect by default. The greeting stating hours — plus the desk's honest response habits — turn that expectation from a failure mode into a stated policy.
Two patterns show up within a month of turning the channel on. First, the group carryover: businesses with a Telegram community watch the same questions repeat — price, availability, shipping — and the queue's tag report makes that visible in two weeks, which is the moment to publish an explainer and let saved replies carry it. Second, the identity effect: customers who chat on Telegram then visit the website arrive pre-identified, and the widget conversation attaches to the same record — one relationship, several channels, none of them losing history. That is what a support channel is for; the bot token is just the handshake at the door.
Start here if Telegram is where your customers already are: no per-message costs, three seats free, the bot identity stays yours for as long as you want it — and if the day comes when the queue must live inside your own network, the whole channel set runs self-hosted without rewiring the bot.
How do I create a Telegram support bot?
Open a chat with @BotFather in Telegram, send /newbot, pick a display name and a public username, and you receive a bot token. Paste that token into Settings → Channels → Telegram in your help desk and messages to the bot start arriving in your shared queue.
Does Telegram support work with the rest of my help desk?
Yes — Telegram messages flow into the same queue as website widget chat and email, claimable by the team, with private notes, tags, SLAs and the customer context panel. Replies you send from the queue arrive in the customer's Telegram chat.
Is there a cost per Telegram message?
No. The Telegram channel is part of the complete software included in the free plan — three seats and 100 MB storage, no per-message or per-conversation fees. Costs only start when you add a fourth seat ($15/month) or buy AI credits.
What should I configure on the Telegram bot on day one?
A greeting that identifies the team and states response hours, working-hours settings so the queue escalates honestly, and a small tag vocabulary for messaging topics. The greeting is a saved reply — edit the hours line if your policy changes.
Can customers send files and photos over Telegram support?
Yes — Telegram's native attachments (photos, PDFs, documents) arrive in the thread like any other message. Text conversation is tiny; document volume is what counts against the 100 MB free storage, beyond which packs cost $1/GB per month.