Telegram chatbot for e-commerce: it isn't a bot, it's an account (and that changes everything)

Almost every guide to "Telegram chatbots" describes the same procedure: open BotFather, copy a token, connect the bot. It works — for bots. For a shop's customer support it usually isn't enough, and the reason has nothing to do with answer quality: on Telegram there are two different ways to be in a chat, and they do different things.

TL;DR

A Bot API bot is a separate identity, with the "bot" label next to its name, and inside groups it sees only the messages that mention it by default.
An assistant connected to the shop's account answers where customers already write, under the identity they already know.
The price of that second route is Telegram's sending limits, which you don't work around: you respect them.
Which is why a serious Telegram assistant doesn't answer instantly — and that isn't a technical limitation, it's the right call.

The two routes, concretely

	Bot (Bot API)	Connected account (MTProto)
How it looks to the customer	A new contact, labelled "bot"	The contact already in their list
Who has to start	The customer must press "Start"	Nobody: the chat already exists
In groups	With privacy on, reads only mentions	Reads the conversation like a member
Earlier history	Starts from nothing	Everything you've already said is there
Limits	Generous, designed for automation	A person's limits, and they must be respected

Neither is "better" in the abstract. A bot is the right choice for broadcast notifications and for commands. For support — where the customer writes "did the medium ever come in?" inside the same conversation as three months ago — the second route is the only one that doesn't ask them to start over somewhere else.

What changes when it's an account

The context is already there

A bot starting from zero doesn't know that this customer wrote to you in March about a return. An assistant on the shop's account reads the conversation as it is, and the answer can take it into account. That's the difference between "good morning, how may I help you?" and "that's the one we ordered for you back in March".

It sees the corrections too

People correct themselves on Telegram. They write "I want the 42", then edit it to "sorry, 43". A system that only listens for new messages answers about the wrong size and comes across as careless. It's worth asking anyone selling you a Telegram assistant whether it handles edited and deleted messages, not just new ones: that question separates those who did the work from those who wired up a library.

It answers the way you would, timing included

A reply that lands in three hundred milliseconds, at any hour, with flawless punctuation, tells the customer exactly one thing: you're a machine. A well-built assistant waits a few seconds before replying and shows "typing" for a time proportional to the message length — not to fake being human, but because those timings are also what Telegram's limits expect. Here the right thing for the customer and the right thing for the platform happen to be the same thing.

The limit you find out about late

Telegram doesn't block you when you cross a threshold: it hands you a mandatory wait, which can be seconds or hours. Anyone who wrote the integration in a hurry handles that case by retrying immediately — which is the fastest way to make the wait longer.

The correct answer is boring: stop for exactly as long as you're told and resume where you left off, without losing the queue. If you're evaluating a vendor, that's the second question to ask. If they can't answer it, the integration has never been under load.

What a Telegram assistant shouldn't do

Answer everything. On anything delicate — a complaint, a refund, an angry customer — it has to hand over to a person, with the conversation already on screen.
Invent availability. If it isn't connected to the catalogue, "yes, we have it" is a sentence that eventually costs you a return.
Message first. An account that sends unsolicited messages is an account with a short life.

What you need to switch it on

The shop account's phone number. Not a personal one: one that belongs to the business, because that account is your support channel.
The verification code Telegram sends, plus your two-factor password if you have one.
The catalogue connected, otherwise the assistant answers in generalities and you may as well have used a bot.
A handover rule, decided before the first angry customer rather than after.

The first point is the one the guides skip, and it's the one you can't go back and fix: connect your personal number and the shop's support lives on your phone forever.

FAQ

Do I need to create a bot with BotFather?

Not for this route. BotFather is for Bot API bots: the right choice for commands and notifications, less so for support, because the customer has to press "Start" and begin from an empty conversation.

Are the answers based on my catalogue?

Only if the store is connected. With Shopify or WooCommerce synced, answers are grounded in real products; without that, an assistant can only speak in general terms — and on products, "general" is a polite word for invented.

Does it work in groups?

Yes, and that's the main difference from a bot: an account reads the conversation like any other member, while a bot with privacy enabled only sees messages that mention it.

How long does it take to reply?

A few seconds, on purpose. See above: it's the choice that holds together credibility with the customer and the platform's limits.

Can I use the same assistant on my site and on WhatsApp?

Yes, if there's a single knowledge base. That's the real advantage of multichannel: not three assistants to keep updated, but one that answers in three places.

ShopBrain connects your site, Telegram and WhatsApp to a single knowledge base, human handover included. If the commercial side interests you more than the technical one, continue with selling at night with AI.