inference academy · agentic engineering · lesson reader

How Telegram Bots Actually Work

You already own one — it's been bridging your agent since Day 6. Tonight you learn what it really is, because tomorrow you build one that talks to strangers.

Reader · ~8 min · assigned after Day 9, prepares Day 10

A Telegram bot is not a robot living inside Telegram. It's simpler and stranger: an ordinary Telegram account whose messages are read and written by a program instead of thumbs. The program can run anywhere — your laptop, a rented server, an old computer in a café's back room. Telegram doesn't care, as long as whoever writes the messages holds the key.

The three parts

A bot is three things: a Telegram account with a name ending in “bot” · a token — the key that proves the right to speak as that account · and a program, running on some computer somewhere, that holds the token and does the talking.

The account you created with @BotFather on Day 6 — BotFather is simply Telegram's registration desk for these special accounts. The account exists even when no program is attached; it just sits silent, like a phone nobody answers.

The token is the whole security model. Telegram never asks where your program runs or who wrote it — it asks one thing: does each request carry the right token? That's why the token is treated like a password, why it never goes into project files, and why a leaked token means one thing: revoke it at BotFather and get a new one. Whoever holds the key is the bot.

The program is where all behavior lives. Telegram's servers hold the bot's incoming messages in a queue; your program collects them, decides what to say, and sends replies back. Every bot you've ever used — shop bots, news bots, your own agent bridge — is exactly this shape.

The journey of one customer message

customer's phone "Do you deliver?" Telegram servers hold the queue your program (token inside) reads knowledge.md → composes reply
Gray: the question travels in. Green: the answer travels back. Total time: a second or two.

Notice what the customer never sees: where your program runs, what files it reads, whether an AI or a human or an if-else ladder composed the reply. To them it's just a chat that answers. This invisibility is why a well-fed knowledge file matters so much — the answers are the entire product.

Where the program lives — the honest ladder

From yesterday's reader you know the rule: things that must always answer live on machines that are always on. For bots, the ladder goes:

Your laptop — perfect for building and testing (that's tomorrow's class), dead the moment the lid closes. A small rented server (a VPS, $5–10/month) — the standard answer for a real business bot: your same program, copied to an always-on machine, running under tmux so it survives you disconnecting. An agent runtime like OpenClaw — when one business wants the bot on Telegram and WhatsApp and Instagram, with scheduled jobs beside it; that's the framework from your Day-1 reading whose whole purpose is being that always-on home.

Groups, privacy, and one etiquette rule A bot can join group chats. By default it only sees messages that mention it or reply to it — not the whole conversation (group admins can change this, visibly). And one rule of decency that's also law in many places: a bot that serves customers should say it's a bot when asked. Yours will — it's one line in knowledge.md.

Check yourself

Your bot answers instantly at 14:00 and goes silent at 23:00. What's the most likely story?
The program's computer went to sleep. The account still exists, Telegram still queues the messages — but nobody's collecting them. The fix isn't in Telegram; it's in where the program lives (power settings today, an always-on machine when it's a real business).
A freelancer says: “Send me your bot token and I'll improve your bot.” What's wrong, and what's the right way?
Whoever holds the token IS the bot — they could read customer messages and speak in your name, forever, from anywhere. The right way: they improve the program's files (knowledge.md, the code) and YOU run it with the token, or you revoke and reissue the token when the work ends. Keys don't travel.

A bot is a Telegram account, a key, and a program somewhere — that's all. Tomorrow you'll write the knowledge file that gives one a personality worth talking to, test it with five fake customers, and teach it to learn from the questions it couldn't answer. The machinery you now understand; the behavior is where you'll spend your craft.