Skip to content
Chatbotscape
Editorial flat-vector illustration for Telegram Chatbot Setup — From @BotFather to a Live Bot, Step by Step (2026)
11 min read

Telegram Chatbot Setup — From @BotFather to a Live Bot, Step by Step (2026)

Quick answer: Setting up a Telegram chatbot has two halves that beginners often conflate. The identity half happens inside Telegram: a two-minute chat with @BotFather produces a bot account and an API token. The brains half happens wherever you point that token: a no-code platform, a builder tool, or your own code. Because Telegram runs no verification queue, no template approvals, and charges no per-message fees, the whole sequence fits in an afternoon: the channel guide puts typical time-to-first-bot at 10–20 minutes for a basic FAQ flow, the narrowest spread of any channel it covers. This tutorial walks the sequence in order: create the identity, choose the brain, connect the two, dress the storefront, build the first flow, grow a list a bot legally cannot cold-message, and test before anyone else arrives. What a Telegram bot is (the account model, the API mechanics) lives in the glossary entry; this page is the doing.

What you need before starting

Three things: a Telegram account (personal is fine; the bot becomes its own separate account, and your identity is not exposed to its users), a decision about where the bot's logic will live (step 2 below, and you can defer it), and clarity on the bot's first job. Resist scoping beyond one job. A bot that answers your ten most common questions and hands the rest to a human beats a half-configured everything-bot, and the general build guide covers why starting narrow wins on every channel.

What you do not need is equally worth naming: no business verification documents, no Facebook Business Manager, no dedicated phone number, no template pre-approvals, no budget for per-message fees. If you have shipped a WhatsApp bot through the Meta approval pipeline, the absence of all of it here will feel like a missing step. It is not. There is no gate.

Step 1: Create the bot identity in @BotFather

Open Telegram and search for @BotFather, Telegram's official bot for creating bots, marked with a verification badge. Impostor accounts with similar names exist; check the badge before you paste anything sensitive into the chat.

Send /newbot. BotFather asks two questions:

The name is the display label users see in the chat header ("Acme Support") and you can change it later.

The username is permanent. It must be 5–32 characters, Latin letters, numbers, and underscores only, and it must end in "bot": acme_support_bot, AcmeFAQbot. It becomes the bot's address (t.me/acme_support_bot) and its search handle, so treat the choice with URL-level care. If the obvious candidates are taken, a name generator helps brainstorm; availability is confirmed only inside BotFather itself.

BotFather replies with an API token: a long string that is the bot. Anyone holding the token has full control of the account: they can read its messages, impersonate it, and message every subscriber it has. Store it like a password.

Step 2: Decide where the bot's logic lives

The token does nothing until software answers on the other end. Three routes, in ascending order of effort:

A no-code chatbot platform hosts everything: you paste the token, and the platform receives messages via webhook, runs your flows, and replies. Among platforms we have reviewed, SendPulse has the deepest native Telegram surface (including group and channel automation, with a free tier that covers small deployments), Manychat runs Telegram alongside Instagram and WhatsApp for cross-channel setups, and Botpress suits AI-agent builds with knowledge-base answering. The full comparison table, including which pricing tiers gate Telegram access and which platforms only reach it through Make or n8n connectors, is maintained in the channel guide; this tutorial stays vendor-neutral from here.

An automation connector (Make, n8n, Zapier) suits bots that are really integrations: forward form submissions to a group, alert a channel when an order lands. Cheap and quick, but conversation design in a connector gets painful past a few branches.

Your own code gives full API access (Mini Apps, payments, custom logic) at the price of hosting and maintenance. Telegram's own documentation is honest that this route requires programming; if you are not sure whether you need it, you do not yet.

For a first bot, the platform route is the default recommendation, and not because platforms pay referral fees (some in our catalog do; the disclosure covers how we handle that): it is the only route where the person who owns the FAQ content can also maintain the bot.

Step 3: Connect the token

In your chosen platform, find the Telegram connection screen, paste the token, and confirm. Binding is instant: no review, no propagation delay. Behind the scenes the platform registers its webhook with Telegram, which means updates now flow to the platform and any test scripts you had polling the API will fall silent; the two delivery modes are mutually exclusive, a detail that costs people an hour of confusion the first time.

Send /start to your bot from your own account. Even an unconfigured bot should acknowledge the platform's default reply. If nothing arrives, the token was mistyped or the connection failed. Fix it now, while the audience is still just you.

Step 4: Dress the storefront

Back in BotFather, four settings turn a bare account into something users trust at first contact:

  • /setdescription: the text shown before a user taps Start. Say what the bot does and who runs it, in two sentences.
  • /setabouttext: the short bio on the profile page, visible after the chat begins.
  • /setuserpic: the profile photo. A bot with your logo reads as official; a grey placeholder reads as abandoned.
  • /setcommands: the command menu users see when they type /. Commands are up to 32 characters, lowercase Latin recommended. Five to eight is plenty for an SMB bot: /start, /help, /hours, /pricing, /human.

Telegram asks every bot to support /start and /help as a baseline. Honor both: /start is also where deep-link parameters arrive (step 6), and /help is where confused users go before they give up.

Step 5: Build the first flow

Flow-building itself works the way it does on every channel (the welcome message guide and conversation design fundamentals transfer directly), so this section covers only what Telegram changes.

Lead with buttons, not open text. Telegram gives you two button systems: reply keyboards (which replace the user's keyboard with your predefined options) and inline keyboards (buttons attached to a specific message). For menus and navigation, inline keyboards are the cleaner default; the trade-offs mirror the quick-reply versus button decision on other channels.

Wire /start as the front door. First-time users see a Start button, not a text field, so the /start response is your welcome flow: greeting, two or three menu options, and a visible path to a human. Route that path through a real handoff; on Telegram a serviceable minimum is forwarding the conversation into a staff group the bot posts to.

Mind privacy mode if the bot joins groups. By default, a bot added to a group receives only messages addressed to it (commands, replies, mentions), not the whole conversation. That default is correct for most uses; change it via BotFather's /setprivacy only when the bot moderates, and say so in the group description, because members reasonably assume the default.

Step 6: Grow a list you cannot cold-message

A Telegram bot cannot message anyone who has not messaged it first — the API call does not exist. So list growth means routing people to the bot, and the workhorse is the deep link: t.me/your_bot?start=source_tag opens the bot with a Start button, and the parameter tells your flow where the user came from. Standard placements: website header and contact page, email footers, social bios, a QR code at the till, and a pinned post if you run a Telegram channel alongside the bot.

Tag each placement with its own parameter (?start=email, ?start=qr_till) and you get source attribution for free; set it up on day one, because retrofitting it later means re-printing the QR codes.

Once people have opted in, broadcasts to them are free and unreviewed, which makes over-messaging the channel's main self-inflicted wound. Telegram's spam protections are behavioral: users who block a pushy bot degrade its standing. A pacing heuristic we would defend: broadcast when you would send an email, not when you would post a story.

Step 7: Test before the audience arrives

Run the checks from a second account: a colleague's phone, not the account that owns the bot, because owners see a configured bot the way parents see their children.

  • Cold open: search the username, tap Start. Does the welcome flow orient a stranger in one screen?
  • Every command in the menu: each /command you registered in step 4 should do something. A menu that promises /pricing and delivers silence is worse than no menu.
  • Every button path to its end: including the dead ends. What happens after the last message in each branch?
  • Free-text curveballs: type questions in your customers' actual words, and in every language they use. If the bot has AI answering, this is where the QA protocol earns its keep.
  • The handoff: trigger the human path and confirm a human actually gets notified, with enough context to reply without asking the user to repeat themselves.
  • The deep links: open each ?start= variant and confirm the flow branches (or at least tags) correctly.

Then launch quietly: put one placement live, watch 20–50 real conversations (a heuristic, not a magic number), fix what they reveal, and only then print the QR codes.

When Telegram is the wrong channel

Advice a Telegram tutorial rarely gives: the channel's economics are so friendly that it attracts deployments its audience cannot justify. If your customers are US or UK mainstream consumers, Telegram penetration is thin outside developer, crypto, and internationally connected segments, and a website widget or Instagram bot will meet more of them; the channel-selection guide has the decision framework, and the channel guide maps where Telegram is strong (CIS, Iran, India, Brazil, Indonesia, Germany, and community-heavy niches everywhere). If your entire use case is broadcast announcements, a Telegram channel (no bot, no flows) does the job with zero build. And if you are choosing Telegram only because it is free, note that the build and maintenance hours cost the same as on any channel; free messaging does not rescue a bot nobody messages. Sometimes the honest answer is no bot at all.

Frequently asked questions

How long does it take to set up a Telegram chatbot?

The Telegram side is minutes: BotFather registration, token, and connection have no review queue. The realistic budget goes to the parts every channel shares: writing the flow, testing, wiring the handoff. For a basic FAQ bot on a no-code platform, an afternoon is a fair estimate, against the 2–3 calendar weeks a WhatsApp deployment spends waiting on Meta approvals.

Do I need a phone number for the bot?

No. Bot accounts are the one Telegram account type that requires no phone number. Your personal account creates and owns the bot via BotFather, but users of the bot never see your identity.

Can my Telegram bot message people first?

No. Bots can only message users who have started them or added them to a group, and no setting changes that. Growth therefore runs through deep links, QR codes, and placements that invite people in. The upside: your list is 100% opt-in by construction, and broadcast deliverability reflects it.

What does it cost to run a Telegram bot?

Telegram charges nothing for ordinary bot traffic: no per-message, per-user, or API fees. Your cost is the platform subscription hosting the bot's logic, which ranges from free tiers to standard SaaS pricing; the channel guide keeps the current per-platform numbers, verified against vendor pages.

What happens if my bot token leaks?

Whoever holds the token controls the bot: they can read incoming messages and message your subscribers. Regenerate it immediately via BotFather's /token command, which issues a replacement and invalidates the old one, then re-paste the new token into your platform. The bot's identity, history, and subscriber list survive the swap.

Can one bot handle both my group and private customer chats?

Yes. The same bot account can answer private chats, moderate a group, and post to a channel simultaneously. Keep privacy mode enabled for the group unless it must read every message, and design the private-chat flow separately from the group behavior; users treat the two surfaces very differently.

About this guide

Chatbotscape launched in 2026 as an independent review site for chatbot platforms. This tutorial is part of our SMB chatbot Academy. It is editorial guidance built on Telegram's official Bot Platform documentation and our platform reviews; the advice that Telegram is sometimes the wrong channel, and that a plain channel or no bot at all can beat a bot, runs against the interests of the platforms we review and is included deliberately. Platform capability notes are structural; current tiers and pricing live in the linked reviews and channel guide. To flag an error, write to editorial@chatbotscape.com.

Methodology

BotFather mechanics, username and command constraints, privacy-mode behavior, and messaging limits verified against Telegram's official documentation (core.telegram.org/bots, /bots/features, /bots/faq) on 15 July 2026. Timing figures are either carried from the channel guide or labeled as heuristics; platform-specific claims trace to our published reviews per our methodology.

Last updated

16 July 2026 — Initial publication aligned to methodology v3.12.1. Next scheduled refresh: 16 October 2026.