The packaging, the receipt and the Instagram bio all say: “Questions? Message @anna_support on Telegram.” It works until Anna goes on vacation, changes her number or quits, and three hundred customer conversations leave with her. The opposite failure is just as common: a bot with ten buttons where you can’t simply type “you sent the wrong size” and reach a person.
If your customers live on Telegram (Eastern Europe, Central Asia, the Middle East, plus crypto, gaming and developer communities everywhere), support there needs a system, not somebody’s handle. There are three setups: a company account with Telegram Business, a support bot and a group chat. Here’s how to set up each, how to combine them, and when Telegram is the wrong channel altogether.
Three setups and where each one breaks
| Account + Telegram Business | Support bot | Group chat | |
|---|---|---|---|
| Best for | 1–2 agents, up to 30–40 chats a day | Repeat questions, several agents, night messages | Products with a community: SaaS, courses, hardware |
| Strength | Feels like chatting with a person | Works 24/7, not tied to one employee | Customers answer each other |
| Where it breaks | Two people in one account answer the same customer twice | Users must tap Start; menus instead of answers annoy | Public complaints, spam, needs a moderator |
| Cost | Telegram Premium subscription | Free builders up to custom development | Free, but eats moderator time |
The quick rule: varied questions that need a human, start with the account. Half the questions are identical or arrive at night, add a bot. People ask about the product rather than their order, open a group. Most growing businesses end up running two of the three.
Setup 1: a company account with Telegram Business
Telegram Business is a set of features for a regular account that comes with Telegram Premium. What matters for support:
- Opening hours and location on the profile, visible before anyone writes.
- Greeting message for new customers or people who haven’t written in a while.
- Away message outside hours, with a real time: “We’ll reply tomorrow from 9 am. Shipping info is pinned in our channel.”
- Quick replies typed with ”/”: /shipping, /payment, /returns.
- Chat links with pre-filled text: the customer lands in a chat with “I’d like to check my order” already typed. Put one on your site and in your bio.
- A connected bot that replies on the account’s behalf in chosen chats while you can step in anytime.
The rule that saves the most pain: the account belongs to the company, not the employee. A company-owned SIM, a cloud password for two-step verification, a manager with access. When an agent leaves, the history stays and customers keep writing to the same @username.
The hard limit: you can’t assign a chat to a specific person. Two agents in one account will eventually both answer the same customer, differently. More than two agents means it’s time for a bot or a helpdesk.
Setup 2: a support bot as the first line
A bot answers repeat questions without a human and collects details before an agent joins. Two flavours:
- Feedback bot. The customer’s message is forwarded to you, you reply to it, and the customer gets your answer from the bot. Livegram works this way; most builders have a similar module.
- Menu bot. Buttons for common questions plus “Talk to a person”. No-code builders such as SendPulse handle it without a developer.
A start screen that doesn’t annoy:
Hi! This is the Northwind Home support bot. Our team replies 9 am to 9 pm; leave a question anytime.
📦 Where’s my order · 💳 Payment & shipping · ↩️ Returns · 👤 Talk to a person
Each button gives one short answer and a next step. “Where’s my order” asks for the order number and shows the status if the bot is connected to your store, or passes it to an agent. “Returns” explains your 30-day policy in three lines and asks for a photo and the receipt.
Setup in one evening:
- Create the bot in @BotFather with /newbot. The username must end in “bot”.
- Write the description with /setdescription (up to 512 characters). It shows in the empty chat before Start: say what the bot does and when a human takes over.
- List the questions from your last 50 conversations. Build buttons for the 4–5 most common topics, not your org chart.
- Route “Talk to a person” to a shared agents’ group rather than the owner’s DMs.
- Test from a second account: voice note, photo, sticker, typo, a message at 11 pm.
- Add tracked links:
t.me/northwind_help_bot?start=ig_bioin your bio,?start=boxon the QR code in the package. The parameter (up to 64 characters) shows where each chat came from.
Bot API limits still apply: a bot can’t message anyone who hasn’t tapped Start, and broadcasts are rate-limited. More in our post on Telegram bots for business.
Setup 3: a group chat where customers help each other
A public chat works when a question is useful to many: configuring the device, finding a feature, submitting a course assignment. Experienced users answer newcomers, and one reply is seen by hundreds. For orders and complaints it’s the wrong place: phone numbers and addresses don’t belong in public.
Keeping it usable:
- Topics: Questions, Bugs, News, Off-topic.
- Slow mode: a 10-second to 1-hour pause between one member’s messages blunts spam waves.
- A pinned rule: “Order numbers and addresses go to @northwind_help_bot only.”
- A moderator with a standard: no question waits more than 2–4 business hours.
Comments under channel posts are support too: route them into the same queue as DMs.
The combo: bot at the door, humans on the hard stuff
For most stores and services with 30+ requests a day:
| Question | Who answers |
|---|---|
| Hours, shipping, payment | Bot, instantly |
| Order status | Bot by order number, or a human without store integration |
| Message at night | Bot takes it and says when a person will reply |
| Complaint, refund, unusual request | Human; the bot collects the order number and photos |
| Product how-to | Group chat |
The bot hands off when the customer taps “Talk to a person” or types “agent”, fails to understand twice, writes something clearly angry (“refund”, “scam”) or sends a photo of a damaged item. The agent sees what the bot collected, so nobody repeats their order number. After handoff, aim for 15–60 minutes during business hours. Reply templates are in our guide to customer service on social media.
AI in the bot resolves more than buttons do if it answers only from your documents, never promises discounts or refunds, and says it’s a bot. Read 20 random conversations weekly; one invented price means narrowing the sources.
At 50–100 requests a day or three agents, get a helpdesk. Zendesk, Crisp and open-source Chatwoot connect a Telegram bot and add what Telegram lacks: assignment, statuses and one customer history across channels.
Four metrics to check weekly
- Time to a human reply after handoff, as a median.
- Share of chats the bot resolves. Under a third means the buttons answer the wrong questions; rename them in your customers’ words.
- Tapped Start, then silence. Many of these means an unclear start screen.
- Bot blocks. A spike after broadcasts means the support bot is being used for promos, and a customer who blocks it won’t see the reply about their order either.
When Telegram is the wrong support channel
- Your customers aren’t there. Count last month’s requests by channel. In the US and much of Western Europe, most people may prefer WhatsApp, email or phone.
- Sensitive data. Regular chats and bots aren’t end-to-end encrypted, and builders store conversations on their servers. If you serve EU customers, GDPR covers whatever the bot collects: check where the vendor keeps data and sign a data processing agreement.
- Contractual B2B support needs ticket history and response-time reports. Telegram can be the entry point; the work happens in a ticketing system.
- A bot instead of people. If nobody is behind “Talk to a person” until Monday, say so on the start screen.
Repost21 won’t replace a support bot and has no shared inbox. It covers the neighbouring job: answers to common questions become Telegram channel posts on the content calendar, and Luna drafts them from the prices and policies in your brand knowledge base. The more answers sit pinned in your channel, the fewer repeat questions reach support. Try it free.