A Telegram bot that earns its keep

A Telegram bot is one of the cheapest pieces of software a business can put in front of customers. It needs no app store review, no install, no login screen and no design system. A person taps a link, presses Start, and they are talking to your business inside the app they already have open forty times a day. That low friction is exactly why so many bots get built — and why so many of them are quietly abandoned within a month.

The bots that survive have something in common. They are not clever. They do one job that a person would otherwise have to do by hand, they do it at the moment the customer needs it, and they never surprise anyone. This note walks through what that looks like in practice: what a bot can and cannot do on Telegram, the handful of jobs that reliably pay for themselves, and the design decisions that separate a bot people use from one they mute.

Start from what Telegram actually allows

Most disappointing bot projects begin with an assumption that turns out to be false. The platform has firm rules, and they are worth knowing before anyone writes a line of code or pays for a build.

The first rule is the one that surprises people most: a bot cannot start a conversation. It can only message someone who has pressed Start on it (or otherwise contacted it) first. There is no way around this, no paid tier that lifts it, and no list of phone numbers you can upload. Anyone who promises to "DM all your channel subscribers" is either misunderstanding the platform or selling something that will get an account banned.

The second rule is about groups. By default, a bot added to a group runs in privacy mode: it only sees messages that are commands aimed at it, replies to its own messages, and a few service events. If the bot needs to read ordinary conversation — to answer a question, catch a spam link or count entries in a giveaway — privacy mode has to be off, or the bot has to be an administrator. This is a deliberate protection for group members, and it is why a well-behaved bot asks only for the rights it needs.

The third rule concerns channels. A bot in a channel is only useful as an administrator with the specific right it needs, usually Post Messages. It never sees a list of subscribers, because Telegram does not give that list to anyone, bots included. What it can do is publish, edit and delete its own posts on schedule, and read the channel's own posts if it has been made an admin.

Finally, there are pace limits. Telegram's own bot FAQ describes a ceiling of roughly thirty messages per second for broadcasts, with much tighter limits inside a single group. Those are ceilings, not targets. Bots that run near them tend to collect errors and, eventually, restrictions. Anything that sends to a lot of people should be spread out over time and should stop cleanly when someone asks it to.

None of this is bad news. These limits are the reason Telegram inboxes are still pleasant, and a pleasant inbox is the whole commercial value of the channel. A bot designed around the rules keeps that value; a bot designed to evade them spends it.

The five jobs that reliably pay for themselves

After watching a lot of channel operators and small businesses run bots, the useful ones fall into a short list. Almost every successful bot is one of these, or two of them stitched together.

1. Answering the same ten questions

Every channel with a few thousand subscribers gets the same questions over and over: delivery times, opening hours, how to pay, whether the drop is sold out, where to find the menu. An FAQ bot that recognises those questions in a group and answers them instantly does two things. It saves the owner an hour a day, and it makes the group feel attended to at three in the morning.

The trick is restraint. A good FAQ responder has a short list of question-and-answer pairs written by a human, matched on clear keywords, and it stays silent when it is not sure. A bot that answers every message with a guess is worse than no bot at all, because members learn to ignore it — and then they ignore the correct answers too.

2. Greeting new members properly

The first minute after someone joins a group decides whether they stay. A welcome message that tells them what the group is for, what the rules are and what to do first (read the pinned post, introduce yourself, claim the newcomer discount) turns a silent lurker into a participant. It also sets expectations early, which cuts moderation work later.

Keep it short. Three lines and one button beat a wall of rules. If there is a single action you want a newcomer to take, make it the only button.

3. Taking structured requests

Wholesale enquiries, booking requests, custom orders, job applications, support tickets: anything where you currently ask people to "DM us with the details" and then spend three messages extracting the details. A bot that asks the questions in order — name, quantity, date, city — and hands you a complete, tidy request saves a surprising amount of back-and-forth.

This is the job where inline buttons matter most. Letting someone tap "10 kg" or "Next week" is faster and less error-prone than asking them to type. Validate as you go, confirm the summary at the end, and tell the person when they will hear back.

4. Keeping the room clean

Spam in Telegram groups is relentless: fake giveaways, fake job offers, link drops from accounts created an hour ago. A moderation bot that removes messages containing links from brand-new members, blocks forwarded promotions and warns before it bans protects the thing that makes the group worth joining. Moderation is also the bot job where mistakes are most visible, so it pays to start conservative — delete and warn, rather than ban — and to log every action somewhere an admin can review it.

5. Running a moment

Giveaways, launch countdowns, limited drops, polls that decide the next product. These are short-lived but high-attention, and a bot handles the mechanics — collecting entries, enforcing one entry per person, drawing a winner fairly and announcing it — so the owner can focus on the conversation around it. The fairness part is not decoration. Members notice when the same handful of people win, and a transparent draw is cheap trust.

Deep links: the most underused feature on the platform

Every bot has a link of the form t.me/yourbot, and that link can carry a short payload: t.me/yourbot?start=spring-flyer. When someone opens it and presses Start, the bot receives the payload along with the first message.

That single mechanism does a lot of work for a business:

• Attribution: give every placement its own payload — the Instagram bio, the printed flyer, the partner channel's post — and you know exactly where each conversation came from.
• Context: a link from a product post can open the bot already on that product, so the first thing the person sees is relevant.
• Consent: pressing Start through a link on your channel is a clear, deliberate opt-in, which is precisely what a DM list should be built on.

The payload is limited to a short string of letters, digits, underscores and hyphens, so keep a small table that maps codes to meanings rather than trying to pack data into the link itself.

Design decisions that decide whether people keep using it

A bot is an interface with almost no chrome. That makes the few decisions you do make very visible.

Say what it does in the first message

When someone presses Start, the first reply should say in one or two sentences what the bot is for and offer the two or three most likely next actions as buttons. "Hi! I take wholesale orders for Northline Coffee and answer delivery questions" is infinitely better than "Welcome! Use /help to see commands."

Prefer buttons to commands

Slash commands are a developer's idea of a menu. Most people never type them. Inline keyboards under a message, and a persistent menu button, cover nearly every case and remove the guesswork. Reserve commands for power users and admins.

Edit, don't spam

Telegram lets a bot edit its own messages. A multi-step flow that edits a single message as the person moves through it — rather than sending a new message for every step — keeps the chat readable and makes the bot feel like an app instead of a chatterbox.

Fail out loud, and kindly

When something goes wrong — a payment did not go through, a request could not be saved, the bot lost a permission in a group — say so plainly and say what happens next. Silent failure is the fastest way to lose trust, because the person assumes they were ignored. A bot that says "I couldn't save that, please try again in a minute — nothing was charged" keeps the relationship intact.

Let people leave

Every bot that messages people should honour /stop and should stop immediately and permanently. Users who block the bot should be skipped, not retried. This is not only courtesy. A bot that keeps messaging people who have left it collects reports, and reports are what turn a working bot into a restricted one.

Ready-made or custom?

For the common jobs — FAQ answers, welcome messages, giveaways — a well-built template is almost always the right starting point. It costs little, it is running in minutes, and it has already met the edge cases that a fresh build will discover the hard way: the member who joins and leaves in the same second, the question phrased in a way no one anticipated, the giveaway entrant with three accounts.

A custom build earns its price when the bot touches something specific to your business: your stock levels, your booking calendar, your CRM, your delivery zones, your pricing rules. The moment the bot needs to read or write your own data, a template stops fitting.

When you do commission one, write the brief as a list of conversations rather than a list of features. "A café owner messages us at 7am asking whether 20 kg of the Brazil roast can be delivered to Leeds on Thursday — the bot should check stock, check the delivery zone and either confirm with a price or offer the next available day" tells a builder far more than "stock integration, delivery checking, order capture." Conversations expose the edge cases; feature lists hide them.

Ask three questions of anyone quoting a custom bot:

• What happens when Telegram is slow or returns an error? A serious answer mentions retries, queues and what the user sees in the meantime.
• Who holds the bot token, and where is it stored? You should be able to get it back, and it should never sit in a shared chat or a spreadsheet.
• How will you know it is working next month? Logs, alerts and a simple health check are part of the build, not an extra.

Measuring whether it earns its keep

A bot is worth keeping if it saves more time or makes more money than it costs, and both are easy to measure if you decide upfront what to count.

For an FAQ responder, count the questions it answered that a human would otherwise have answered, and multiply by a realistic two minutes each. For a request-taking bot, count completed requests and compare the conversion from "started" to "submitted" with what you saw when people had to DM you. For a welcome flow, compare how many new members post in their first week before and after. For moderation, count removed spam and — just as important — false positives that an admin had to undo.

If a number is not moving after a month, the problem is usually not the code. It is the first message, the button labels or the moment the bot appears. Those are cheap to change, so change them one at a time and watch the number again.

A realistic first bot

If you run a channel or a community and have never deployed a bot, the most reliable path looks like this. Start with a welcome message and an FAQ responder in your group, because they are low-risk and immediately useful. Add a deep link to your channel's pinned post so that interested subscribers can opt in to direct messages. Watch what people ask for over the next few weeks — the questions the FAQ cannot answer, the requests people keep making in DMs. That list is the brief for whatever you build next.

A bot does not need to be impressive. It needs to be there at the right moment, do its one job without fuss, and get out of the way. Built like that, it becomes the member of staff who never sleeps, never gets short with a customer and never forgets to reply — which, for a business living inside Telegram, is about as good a hire as it gets.