Skip to content
Chatbotscape
Verified
Telegram bot· Messaging channel
A Telegram bot is a special Telegram account operated by software instead of a person. It needs no phone number: you register it in about a minute by messaging @BotFather, Telegram's official bot for creating bots, and receive an API token that connects the account to your own server or to a no-code chatbot platform. Bots answer private chats, moderate groups, post to broadcast channels, and can host full web applications (Mini Apps) inside the chat. Two facts define the category: the Bot API is free, with no per-message fees, and a bot can never message a user who has not contacted it first — consent is enforced by the platform's architecture rather than by an approval process.
By Chatbotscape Editorial· Methodology· Published 16 July 2026· Updated 16 July 2026

Telegram Bot — Definition, How It Works, and What Makes It Different (2026)

Quick answer: A Telegram bot is an account, not an app. It looks like any other Telegram contact (a name, a profile photo, a chat window), but behind it sits a program responding through Telegram's Bot API. That one design decision explains most of what makes the channel unusual: bots are created by talking to another bot (@BotFather), they cost nothing to run at the channel layer, and they cannot start conversations, so every subscriber is opt-in by physics rather than by paperwork. This entry covers the concept and its mechanics. Market data, platform rankings, and the pricing math live in our Telegram channel guide; the step-by-step build walkthrough is the setup tutorial.

What it is

Telegram's own documentation defines bots as "small applications that run entirely within the Telegram app," and the phrase is more precise than it first sounds. There is no separate bot product, no business app to install, no dashboard on Telegram's side. A bot is a special account — one that needs no phone number and carries a visible "bot" label in the chat — connected over HTTPS to whatever server its owner points it at. Users find it the way they find people: by searching its @username or opening its t.me link.

Creation is famously self-referential. You message @BotFather, Telegram's official bot-management bot, send the /newbot command, and answer two questions: a display name (changeable) and a username (permanent, 5–32 characters, Latin letters, numbers, and underscores, ending in "bot"). BotFather replies with an authentication token. That token is the bot: anyone holding it has full control of the account, which is why every platform that connects to Telegram asks you to paste it exactly once and why it deserves password-grade handling.

The scale of this model is easy to underestimate. Telegram reports more than 10 million bots on its Bot Platform, which it keeps free for both users and developers, a number that makes bots less a feature of the app than a parallel ecosystem inside it.

How it works

Mechanically, a Telegram bot is a message loop. When a user writes to the bot, Telegram's intermediary server records an update; the bot's software collects that update in one of two ways. It can poll (repeatedly ask Telegram "anything new?" via the getUpdates method) or it can register a webhook, an HTTPS address to which Telegram pushes each update the moment it arrives. Polling suits quick experiments; webhooks are how production bots and every no-code chatbot platform operate. The two modes are mutually exclusive — a bot with a webhook set cannot poll.

What the bot sends back is where Telegram's interface toolkit shows up. Beyond plain text and media, bots can present reply keyboards that temporarily replace the user's keyboard with predefined answers, inline keyboards with buttons attached directly to messages (the same design trade-off covered in quick replies vs buttons), slash commands that autocomplete when the user types /, and a persistent menu button. Telegram asks every bot to support three global commands: /start, which begins the conversation, /help, and /settings where applicable. /start doubles as the channel's tracking mechanism — a deep link such as t.me/your_bot?start=summer_promo passes its parameter to the bot on first contact, so one bot can greet visitors from an email footer differently than visitors from a QR code.

At the ambitious end, a bot can stop being a conversation at all: Mini Apps are JavaScript web applications that open inside the chat, with Telegram Stars handling in-app purchases for digital goods. For most SMB deployments these stay optional; the conversational toolkit above covers a working customer service bot.

Where bots live

A Telegram bot operates in four distinct surfaces, and the same account can work all of them at once.

Private chats are the default: one user, one bot, the standard surface for support, FAQ deflection, and lead capture, with human handoff wired in for the conversations automation should not finish.

Groups are where Telegram bots do work that has no equivalent on WhatsApp or Instagram: added as members or administrators, they moderate, welcome newcomers, enforce posting rules, and run commands. By default a bot in a group runs in privacy mode, receiving only messages addressed to it — commands, replies, and mentions — rather than the whole conversation; the /setprivacy toggle in BotFather changes that deliberately.

Channels are one-way broadcast feeds where bots post as administrators, which is how newsletters, alert feeds, and content-distribution schemes run on Telegram. The mechanics of one-to-many messaging on chat apps generally are covered under chatbot broadcast.

Inline mode, enabled per-bot via BotFather, lets users summon the bot from any chat by typing its username and a query (@gif cats mid-conversation) without the bot being present in that chat at all.

What makes it different from other bot channels

Set against the WhatsApp Business API, the contrast is structural rather than incremental, and it runs in both directions.

No fees, no gates. The Bot API charges nothing: no per-message rate, no per-conversation fee, no subscription. There is no business-verification step, no pre-approved template queue, and no marketing-versus-utility category system. A WhatsApp deployment budgets weeks for Meta's approvals; a Telegram bot exists within minutes of messaging BotFather. The only Telegram-side charge appears at extremes — the optional paid-broadcast mode lifts the default ceiling of roughly 30 broadcast messages per second to 1,000 at 0.1 Stars per message, and requires a balance of 100,000 Stars plus 100,000 monthly active users before a bot can even enable it. Ordinary limits (one message per second per chat, 20 per minute per group) are pacing rules, not prices.

Consent by architecture. Telegram's documentation states it plainly: bots cannot start conversations with users. A user must message the bot first or add it to a group. Where Meta enforces opt-in with audits and template review, Telegram enforces it with a capability that simply does not exist — there is no API call that cold-messages a stranger. For operators this reads as a constraint and behaves as a feature: every contact on a Telegram bot's list chose to be there, which is why list-building happens through deep links in bios, QR codes, and channel posts rather than through imports.

The trade-offs. The same architecture withholds things Meta channels provide. There is no verified-business identity program comparable to WhatsApp's, audience reach is concentrated in Telegram-strong markets (CIS, Iran, India, Brazil, Indonesia, Germany) rather than universal, and the hosted Bot API caps bot-sent files at 50 MB (downloads via getFile at 20 MB), well under the multi-gigabyte ceilings Telegram's human users enjoy. Bots also cannot see messages from other bots at all, a loop-prevention rule that occasionally surprises teams wiring two automations into one group. Whether these trade-offs matter is a channel-strategy question that depends on where your customers already are; the decision framework lives in choosing chatbot channels.

Do you build one or connect one?

Telegram's own FAQ is blunt that creating a bot from scratch requires programming. What it does not mention is the ecosystem that grew around that gap: no-code chatbot platforms host the server side for you, so "building a Telegram bot" collapses into pasting a BotFather token into a settings field. SendPulse runs the deepest native Telegram surface among the platforms we have reviewed, Manychat added Telegram alongside its Meta channels, and Botpress treats it as a first-class channel for AI-agent builds. The full comparison table, including which tiers gate Telegram and which platforms reach it only through connectors, sits in the channel guide; the hands-on walkthrough from BotFather to a live flow is the setup tutorial.

  • WhatsApp Business API — the fee-and-approval counterpoint; comparing the two is the fastest way to understand either.
  • Webhook — the delivery mechanism behind every production Telegram bot.
  • Chatbot broadcast — one-to-many messaging mechanics across chat channels.
  • Chatbot channel strategy — deciding whether Telegram belongs in your channel mix at all.
  • Omnichannel chatbot — running Telegram as one surface of a multi-channel deployment.

FAQ

What is a Telegram bot in simple terms?

A Telegram account run by a program instead of a person. It sits in your contact list like anyone else, marked with a "bot" label, and answers automatically: support questions, orders, reminders, group moderation, content feeds. You create one by messaging @BotFather, Telegram's official setup bot, and most businesses connect the result to a no-code chatbot platform rather than writing code.

Are Telegram bots free?

The channel is. Telegram charges no per-message or per-user fees for ordinary bot traffic, and there is no paid API tier for standard use; the only Telegram-side cost is an optional high-volume broadcast mode aimed at bots with over 100,000 monthly active users. What most businesses do pay for is the chatbot platform that hosts the bot's logic, which is a subscription decision, not a Telegram one. The cost math against WhatsApp is worked through in our channel guide.

Can a Telegram bot message someone first?

No, and this is a platform rule rather than a platform setting. A bot can only message users who have already messaged it or added it to a group. That makes cold outreach impossible by design and makes the /start deep link (t.me/your_bot?start=source) the standard way to grow a subscriber list from websites, emails, and QR codes.

Do I need to know how to code to make a Telegram bot?

To build one from raw API calls, yes. In practice, no-code platforms handle the server side: you create the bot identity in @BotFather (a two-minute chat), paste the token into the platform, and design the conversation in a visual builder. The setup tutorial walks the whole sequence.

What is BotFather?

Telegram's official bot for creating and managing bots. It issues the authentication token when you register a new bot and handles configuration afterward: description, profile photo, command list, inline mode, and group privacy settings. Treat the token it gives you like a password — whoever holds it controls the bot.

Is a Telegram bot the same as a Telegram channel?

No. A channel is a one-way broadcast feed run by humans (or by bots posting as admins); a bot is an interactive account that responds to individual users. They combine well: a common pattern is a channel for announcements with a bot handling the questions those announcements generate.

Sources