How to add a bot to a Telegram group (and a channel)

TL;DR. Group: info page → Add members → search the bot’s exact @username → confirm, then promote to admin if it moderates. Channel: bots enter only as administrators — info → Administrators → Add administrator. The part most guides skip: a non-admin bot in default privacy mode sees only commands addressed to it, an admin bot sees everything except other bots; grant rights minimally; and bots are capped at 20 messages per minute per group, which explains most “my bot stopped responding” mysteries.

Adding the bot is the easy 5% — three taps and a username. The other 95% of problems come from what happens after: rights, visibility, and limits. All of it below, in order of when you’ll hit it.

Adding a bot to a group

1. Open the group and tap its name — the info page opens.
2. Add members (on some clients: Add under the members list).
3. Search the bot’s exact username — it always ends in bot. Search by the handle, not the display name: impostor bots ride on look-alike names, and the handle is the only unique identifier.
4. Confirm. The bot appears in the members list like any participant.

If it should do anything beyond answering commands — delete spam, greet newcomers, filter comments — continue straight to promotion:

5. Info page → Administrators → Add administrator → pick the bot.
6. Grant rights minimally: a moderation bot needs Delete messages and Ban users; it does not need Change group info or Add new admins. Every box you don’t tick is attack surface you don’t carry.

Adding a bot to a channel

Channels don’t have a members list a bot could sit in — a bot joins a channel only as an administrator:

1. Channel info page → Administrators → Add administrator.
2. Search the bot’s username, set rights, confirm.

A posting bot needs Post messages; an editing bot additionally Edit messages of others if it manages posts it didn’t create. Comment moderation happens in the linked discussion group, so a bot that guards comments is added to that group — the channel-side admin seat alone doesn’t cover it. The full setup for that split is in Telegram comment moderation.

Privacy mode: why the bot “doesn’t see” the chat

The most common post-install confusion has a one-paragraph answer.

By default, every bot runs in privacy mode: inside a group it receives only commands addressed to it (/command@your_bot), replies to its own messages, and a few service events. It does not read the conversation. That’s a feature — members shouldn’t assume an invisible reader — but it means a spam filter installed as a plain member filters nothing.

Two ways out:

• Promote the bot to admin. Admin bots receive everything except messages from other bots. For moderation, this is the intended state.
• The developer disables privacy mode in BotFather. Works for bots that must read without moderating — but the admin route is more transparent to your members, because the admin list is public.

Corollary worth knowing: no bot, ever, reads a group it isn’t a member of. The scary version of “bots read your chats” is not how the platform works.

The limits that masquerade as bugs

• 20 messages per minute per group. A bot that welcomes members, answers commands and posts digests shares one 20-message budget. Under load it queues — from outside, that looks like “stopped working, then caught up.”
• ~1 message per second in private chats, which is why a broadcast to your members trickles rather than detonates.
• A cap on bots per group. If adding fails with everything else correct, remove bots nobody used since last year and retry.

Choosing what to add: one bot or a stack

The classic setup is a stack: one bot greets, one filters spam, one handles comment moderation, one posts. Each is a separate admin seat, a separate operator to trust, and a separate slice of the 20-messages budget.

The consolidated alternative is a single bot that carries moderation and protection, welcome flows, and AI answers to member questions as one admin seat with one rights grant. Fewer seats to audit is a security argument, not just a convenience one. If you’d rather build your own, creating a bot without code covers the BotFather side.

Safety checklist before granting admin

• Identify the operator. A bot is a program run by someone; that someone will receive your group’s messages once the bot is admin. No identifiable developer — no admin seat.
• Minimal rights, reviewed quarterly. The Administrators list is your audit surface; prune bots that no longer earn their seat.
• Watch for name imposters. Verify the exact handle against the developer’s site or channel, not against search results.
• Removing is instant and total. Demote or remove the bot and its access ends that second — nothing lingers.

---

Platform behavior cited here — privacy-mode visibility rules, admin bots receiving all messages except other bots’, and the 20 messages-per-minute group limit — is from Telegram’s Bot FAQ.