Telegram for customer support: bot, personal account or shared inbox
Telegram is the channel Ukrainian customers trust for anything that matters — and the one businesses most often run from someone’s personal account.
In Ukraine Telegram is not a secondary channel. It is where people read the news, pay, ask and complain. For a support team that means the questions arriving there are rarely trivial — and the way most businesses answer them does not survive growth.
There are three setups in the wild. They are not equally good, but each is right for a certain stage.
Option 1: a personal account
Someone on the team gives out their @username. It works instantly, it feels human, and it is how almost every business starts.
It breaks in three predictable ways: the history belongs to a person and leaves with them; nobody else can cover a sick day; and at some point that person's private life and two hundred customers live in the same app. There is no version of this that scales past one channel and a few messages a day.
Option 2: a bot with a button menu
A bot is free, official and always online. The failure is rarely technical — it is that the bot is built as a menu instead of an answer.
A customer with a real question is offered "1. Delivery 2. Payment 3. Other", presses 3, and gets "Your request has been recorded". Nothing was recorded that a person can act on, and the customer now trusts the channel less than before.
Button menus work for genuinely finite choices — checking an order status, picking a branch, confirming a slot. They fail the moment the customer's question is a sentence rather than a category.
Option 3: a bot connected to a shared inbox
The same Telegram bot, but its messages land in a team inbox rather than in a script. The bot is the transport; the answer comes from a person, or from AI drafting for a person.
This is the setup that holds: history belongs to the company, several people can answer, a question can be assigned, and the customer never sees any of the machinery. They just get an answer from the account they wrote to.
| Personal account | Bot with a menu | Bot + shared inbox | |
|---|---|---|---|
| Time to set up | minutes | a day | an hour |
| History kept by company | no | partly | yes |
| Several people answering | no | n/a | yes |
| Handles a free-form question | yes | no | yes |
| Survives someone leaving | no | yes | yes |
Groups, channels and the questions in the comments
Two Telegram habits catch Ukrainian businesses out.
The first is the group chat: customers are invited into a common group, and support happens in public. It builds community and it makes every unanswered question visible to everyone. If you run one, route it into the same queue as everything else — a group message is a support request with an audience.
The second is comments under channel posts. A post about a new arrival collects fifteen questions about price and delivery, none of which reach your inbox. Treat them like Instagram comments: they are the same questions, and the answer should come from the same knowledge.
Setting it up properly
- Create the bot through @BotFather and give it the business name customers already know, not a technical handle.
- Connect it to your shared inbox. The connection uses the bot token — no personal account, no password.
- Set the greeting to say what the channel is for and when a person is around. Honest hours beat a promise of 24/7 you cannot keep.
- Keep the button menu to at most four genuinely finite actions, and always leave "write your question" as an option that reaches a human queue.
- Feed the twenty most common questions into the knowledge base and turn on AI drafts with sources.
- Add an assignment rule for anything containing a refund, a complaint or an order number.
A bot that says "I do not know, a manager will reply in a few minutes" and then a manager actually replies in a few minutes is better support than a bot that answers everything.
Once Telegram is in a shared queue, the rest of the channels are the same problem with a different logo — that is the argument for one inbox across every messenger.
Frequently asked
Is a Telegram bot free?
Yes. The Bot API is free from Telegram; you pay only for the tool the bot delivers messages into, if you use one.
Can several managers answer from one Telegram bot?
Not from the bot itself — it has no team interface. Connect the bot to a shared inbox and any number of managers can answer from it with assignment and history.
Should we use a bot or Telegram Business?
A bot, for a support queue. Telegram Business features are built around one account holder, while a bot connected to a shared inbox gives the whole team the same thread.