“We need a bot” almost always means one of two projects, and confusing them costs a month of work. One bot faces your customers: it takes orders, answers “how much does it cost” at midnight, books a haircut. The other faces you: it pings when a post fails to publish, gives your client an approve button, and lets you schedule a post from the back of a taxi.
Both run on the same Bot API, but they are built differently, cost different money and break in different places. Here’s what a bot can actually do in 2026, the hard limits nobody puts in a proposal, how to turn Telegram into a control panel for your social media, and the cases where a bot is a liability with three subscribers.
Two “business bots” people keep mixing up
| Customer bot | Control panel | |
|---|---|---|
| Talks to | Your customers | You and your team |
| Jobs | Leads, FAQ, booking, catalog, payments | Alerts, post approvals, publishing, stats |
| Who builds it | No-code builder or a developer | Usually built into a tool you already pay for |
| Success metric | Qualified leads, DMs you no longer answer | Hours saved, posts that go out on time |
| Typical failure | A 12-button menu instead of an answer | Notifications everyone muted in week two |
Both are worth having, just not at the same time. Start with the one that fixes today’s pain: drowning in identical DMs means a customer bot; posts going out late and unapproved means a control panel.
What the Bot API can and can’t do
The limits matter more than the feature list, because that’s what proposals leave out.
- A bot can’t message first. Until a person taps Start, you cannot send them anything. A phone list exported from your CRM is useless for Telegram — you have to bring people into the bot first.
- Broadcasts are not instant. The platform’s guidance is roughly 30 messages per second across chats and about 20 per minute into a single chat or channel. A 10,000-person list takes minutes to deliver. Any vendor promising “instant to everyone” is just hiding the queue from you.
- Blocked users return an error. If someone blocked the bot, the API answers 403. Clean those out, or your “10,000 delivered” is a number that means nothing.
- In groups the bot is blind by default. Privacy mode limits it to commands. If you want keyword moderation, you turn privacy off in @BotFather — a deliberate decision, not a checkbox.
- There is no “send later” in the API. Every bot scheduler stores the queue on its own server, not inside Telegram. What follows from that, we unpacked in the comparison of scheduler bots and services.
- File limits: a bot downloads up to 20 MB and sends up to 50 MB. Long videos need compression or a link.
What bots do well — and what teams forget to use:
- Deep links as free UTM tags.
t.me/yourbot?start=ig_biotells you where every subscriber came from in their very first event. Different tags in the Instagram bio, the Reels caption and your email signature, and a month later you have honest channel attribution without paying for analytics. - Payments inside the chat. Digital goods go through Telegram Stars; physical orders go through the Payments API with a provider such as Stripe. Nobody leaves the conversation, and chat-to-payment converts far better than “email us for a quote”.
- Mini Apps instead of a website. Catalog, cart and booking open as a normal web app inside Telegram. For a local business that is often cheaper and faster than a responsive site.
- Telegram Business. You can connect a bot to your personal account: greeting messages, quick replies, away replies and AI drafts right inside your DMs, without losing the human account customers already write to.
The control panel: running social media from Telegram
The idea is simple — move the three actions you open a laptop for into a chat.
- Alerts worth not muting. Not “post published” thirty times a day. Two events: publishing failed (Instagram token expired, media rejected) and a one-line daily summary. Everything else is noise.
- One-tap approval. The draft arrives with a preview and two buttons, Publish and Send back. A manager or a client answers in 20 seconds from a phone, and approval stops being a two-day bottleneck.
- Capturing ideas on the move. A voice note or a forwarded competitor post lands in the bot and becomes a draft in the calendar. “We should write about the new labeling rules” no longer dies in your notes app.
- Publishing from chat. Text, image, pick the accounts, and the post goes into the queue for the next good slot.
In Repost21 that is Luna’s job: the AI assistant lives both in the app and in a Telegram bot — ask for a post, send a voice note, approve with one tap. Everything lands in the same content calendar instead of a parallel queue nobody tracks.
What it costs to build
- No-code builders (Manybot-style tools, SendPulse, Chatfuel and similar): free tiers with subscriber caps, paid plans roughly $10 to $40 a month. A “greeting → menu → lead to a manager” flow is an evening of work.
- Custom development: from a few hundred dollars for one clear scenario to several thousand for a Mini App with payments and CRM sync. Add a $5 VPS for hosting.
- A bot built into your existing tool: zero, if you already pay for the tool. The control panel above is almost always cheaper this way than as a side project.
Honest rule: below 200–300 active subscribers, custom development doesn’t pay back. Ship an MVP in a builder, watch which buttons people actually press, rewrite later.
Scenarios that work
| Niche | What the bot does | First step |
|---|---|---|
| Café, delivery | Menu, order, status, repeat-order nudge | QR code on tables with a tagged link |
| Salon, clinic | Booking, 24-hour reminder, reschedule | ”Book now” button in the Instagram bio |
| Online course | Delivers materials, homework, payment follow-up | Lead magnet in exchange for a bot start |
| Store | Mini App catalog, payment, tracking number | Link in the Reels caption |
| B2B services | Qualifies a lead in four questions, hands off to sales | Link in the LinkedIn signature and site footer |
The common thread: each bot closes one specific action instead of explaining the whole company. How to bring people in from a channel is in the Telegram channel growth playbook; connection details live in the docs.
When a bot will NOT work
- Your audience isn’t on Telegram. In most of Western Europe, Latin America and the US, customers are on WhatsApp, Instagram DMs or email. Check where your inquiries come from today, not where the developer is comfortable.
- Nobody handles escalations. A bot clears routine questions, but roughly every tenth conversation needs a human. Without someone on duty, “a human replies in 5 minutes” quietly becomes “we’ll get back to you tomorrow”.
- Long, complex sales. A $20,000 project is not sold through buttons. The bot’s ceiling here is booking a call.
- Cold outreach plans. Telegram is not email: you cannot message people who never started the bot, and aggressive blasts earn blocks and spam reports fast.
- As a substitute for content. A bot processes demand; it does not create it. If your channel is quiet, start with regular posts — what to automate and what to keep human is covered in the SMM automation guide.
If the control panel is the bot you need first, check the pricing: Luna in Telegram and alerts come with Starter, post approvals with PRO, and the calendar plus idea feed are testable on the free plan — signing up takes a minute.