Back to Blog
GlossaryNovember 4, 20262 min read

Why your Telegram bot cannot see group messages

Everything is configured, the bot is an admin, and nothing happens. The cause is usually a Telegram setting that has nothing to do with your setup.

Why your Telegram bot cannot see group messages

Telegram gives bots a privacy setting that is on by default, and while it is on your bot only receives messages addressed to it: commands and replies. Ordinary group chatter never reaches it, so moderation and analytics have nothing to work with. You turn it off in BotFather for your own bot, and the group starts being visible from that moment.

What the setting does

Every bot has a privacy mode controlled by its owner in BotFather. While it is on, Telegram delivers only messages that concern the bot: commands, replies to it, and mentions. Everything else people say in the group is withheld.

That is a deliberate protection by Telegram rather than a fault. It also means a bot added for moderation sees almost nothing until the setting is changed.

How it looks when it is wrong

The symptoms do not point at the cause, which is why this costs people an evening. Anti-spam never triggers. Analytics shows almost no messages while the group is clearly busy. Word filters pass things they should catch. Everything on your side is configured correctly, and the bot is an admin, so the search goes everywhere except the one place it should.

Changing it

Open BotFather, pick your bot, go to its settings and turn group privacy off. Then remove the bot from the group and add it back, because the permission applies to how messages are delivered from that point on.

If you did not create the bot yourself, only the account that created it can change this, so a bot borrowed from somebody else stays limited until they do it.

What the bot then reads, and what it does not

With privacy off, the bot receives the group's messages so the modules you enabled can act on them: moderation, filters, analytics. It reads them to run those features and nothing else, and the retention window for stored messages still applies. Turn a module off and that reading stops being used for it.

The honest trade-off

A bot that cannot read the group cannot moderate it. If you are not comfortable with that, run the bot with privacy on and use it for commands, welcomes and the shop, which work either way. Picking the limited version deliberately is reasonable; picking it by accident and calling the moderation broken is the thing to avoid.

Frequently asked questions

Where is this setting?

In BotFather, under your bot's settings, as the group privacy option. Only the account that created the bot can change it.

Do I need to re-add the bot afterwards?

Yes. Remove it from the group and add it back, because delivery of messages changes from that point forward.

Will the bot read everything people say?

It receives group messages so the modules you enabled can act on them, such as moderation and analytics, and stored messages are deleted after the retention period.

Can I moderate with privacy left on?

No. Moderation needs to see the messages. Commands, welcomes and the Mini App shop work with privacy on.

Share this article