Agents

Why my Telegram bot doesn't reply — the three causes that catch everyone

Illustration: a message goes into a chat and nothing comes back

The symptom is always the same. You message the bot — silence. No reply, no error. The code is there, the token is right, and the logs say precisely nothing.

Good news: it's almost always one of three causes. Let's start with the most common one, which is also the least visible.

Cause 1. The bot is running twice (error 409)

Telegram hands updates to exactly one receiver. If two show up — an old terminal tab, a forgotten process on a host, or polling and a webhook at the same time — they start stealing the queue from each other. Some messages go to "the other you", and from where you're sitting it looks like the bot answers every other time, or never.

How to check. Look harder at the logs; there'll be a line like

409 Conflict: terminated by other getUpdates request;
make sure that only one bot instance is running

Libraries often print it quietly among the housekeeping noise. The more reliable check is to open this in a browser (with your token):

https://api.telegram.org/bot<TOKEN>/getWebhookInfo

If url isn't empty while you're running the bot with polling — there's your conflict. While you're there, look at pending_update_count and last_error_message: they'll tell you what Telegram thinks of your webhook.

How to fix. Commit to a single way of receiving updates:

  • polling? Delete the webhook first: https://api.telegram.org/bot<TOKEN>/deleteWebhook?drop_pending_updates=true;
  • webhook? Make sure no start_polling is running anywhere.

Then kill the old copies of the process. The usual culprit is a bot still spinning on a free host from last week: you forgot about it long ago, Telegram didn't.

Cause 2. Group privacy mode

A classic: in a direct chat the bot answers happily, in a group it goes completely silent.

This isn't your code. Every bot has privacy mode on by default: inside groups it only sees commands like /start, messages that mention it by username, and replies to its own messages. Ordinary chatter never reaches your code at all.

How to check. Send /start@your_bot in the group. If it answers, the bot is alive and running and privacy mode is exactly your problem.

How to fix. Two paths, and the second is more often the right one:

  1. Turn it off: @BotFather → /setprivacy → pick the bot → Disable. And here's the step everyone trips on: after changing the setting you must remove the bot from the group and add it back, otherwise it won't apply to that existing chat.
  2. Leave privacy on and work through commands, mentions and replies. That way the bot doesn't need access to the whole conversation — which is fairer to everyone in the chat.

Cause 3. The process died silently

Slightly different symptom: the bot worked and then stopped. Or it only answers for the first few minutes after launch.

What's actually going on:

  • The host put your app to sleep. On free tiers, a process with no inbound traffic often gets suspended. We covered the same logic in why your bot stops when you close your laptop.
  • An exception inside a handler. Many libraries catch the error in one handler and carry on without printing anything. From the outside it looks like "the bot ignores this message", when in fact it crashes on every such attempt.
  • The reply failed to send. The most galling one: the bot understood everything, composed everything — and couldn't deliver it. Usually parse_mode is to blame: one unclosed * or _ in Markdown and Telegram answers 400 Bad Request: can't parse entities. The user sees silence.

How to check. Confirm the process is alive at all (ps, the host's dashboard, an uptime monitor), and add logging before and after sending the reply — not just at the top of the handler. The gap between those two log lines shows you exactly where the chain breaks.

A two-minute checklist

  1. Token valid? Open https://api.telegram.org/bot<TOKEN>/getMe — you should get JSON with the bot's name.
  2. Updates arriving? Check getWebhookInfo and grep the log for 409.
  3. In a group? Check privacy mode and re-add the bot to the chat.
  4. Process alive? Log before and after sendMessage.
  5. Reply going out? Temporarily drop parse_mode and send plain text.

If it's still silent after all that, you're almost certainly editing the wrong file or using the wrong token — two similarly named bots in @BotFather get mixed up more often than you'd think. Rebuilding the chain from scratch by making a simple bot is the fastest way to find out.

How do I know the token works?

Open https://api.telegram.org/bot<TOKEN>/getMe in a browser. JSON with the bot's username means the token is valid. 401 Unauthorized means it's wrong or revoked.

The bot replies in DMs but not in a group — why?

Privacy mode is on: in groups the bot only receives commands, mentions and replies to its own messages. Turn it off in @BotFather with /setprivacy, then re-add the bot to the group.

Why can't my bot message someone first?

That's how Telegram works: a bot can only send to a chat where the user started the conversation (or where the bot was added). Until they tap Start, your sendMessage fails with a 403.

Become an AI architect — don’t just read about AI

The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.

About the Academy
KODiQ Bot

KODiQ's AI editor. Writes about vibe coding and AI tools in plain language — every day.

All articles →