OpenClaw Telegram bot not replying in groups? Go to @BotFather, run /setprivacy, pick your bot, hit Disable, then kick the bot out of the group and re-add it. 30 seconds. Want to skip these Telegram gotchas entirely? Use ZenClaw. The onboarding flow walks you through it. OpenClaw’s source and channel implementation live at github.com/openclaw/openclaw. Here’s the full explanation and fix.
Symptom: DMs work, groups are silent
You just got OpenClaw running, connected a Telegram bot, and DMs work fine. Drop it in a group and it only replies when you type /start or @mention it. That’s Telegram bot privacy mode at work. OpenClaw isn’t broken.
Root cause: Telegram’s bot privacy mode
Telegram Bot API ships with privacy mode on by default. Bots in groups only see these three message types:
- Commands that start with
/ - Messages that explicitly @mention the bot
- Replies to the bot’s own messages
The bot never receives anything else. This isn’t an OpenClaw gap. Telegram’s API filters the messages before they ever reach your instance. For the full OpenClaw Telegram integration flow, see the official docs.
The fix (3 minutes)
Order matters. Step 3 is the one people miss:
- Open Telegram, search
@BotFather, start a chat. (BotFather is Telegram’s official bot-management interface. Details in the Telegram Bot Features docs.) - Send
/setprivacy, pick your bot, selectDisable. - Kick the bot out of existing groups and re-add it. (The setting only applies to groups the bot joins after the change.)
- Test in the group. Send any message. Check the OpenClaw logs to confirm the bot received it.
Why your fix didn’t work
Changed privacy mode but the bot still isn’t replying? The usual culprit is not re-adding the bot to existing groups, or OpenClaw-side filters being too strict. Diagnostic table:
| Symptom | Cause | Fix |
|---|---|---|
| Privacy changed, still silent | Existing groups never re-added the bot | Kick and re-add |
| Bot sees messages but doesn’t reply | OpenClaw-side filter too strict | Check OpenClaw channel config |
| Some groups work, others don’t | Those groups haven’t been re-added | Kick + re-add each one |
/setprivacy command does nothing | Bot not correctly registered | Try /mybots → pick the bot → Bot Settings → Group Privacy |
How ZenClaw handles Telegram onboarding
ZenClaw provides a click-through Telegram bot integration UI. But privacy mode itself is a Telegram-side setting (in @BotFather) — any Telegram bot service requires you to do that step yourself. The flow:
- Sign in to zenclaw.ai, click “Hire AI Employees Now”, create an instance
- In the dashboard, click Connect in the Telegram section
- Follow the on-screen steps: visit @BotFather, run
/setprivacy→ Disable, come back to ZenClaw and paste your token - If you want group support, remember to kick + re-add the bot to each existing group
Hidden settings like this are exactly what trips up non-technical users. ZenClaw turns them into a step-by-step checklist you can follow.
Bottom line
Telegram privacy mode isn’t an OpenClaw bug. It’s Telegram’s default behavior. Fix it manually in 3 minutes, or use ZenClaw and let the flow walk you through it. If you’d rather not keep hitting WhatsApp session loss, LINE pairing errors, or MS Teams webhook failures, ZenClaw saves a lot of pain in one shot.
Hit “Hire AI Employees Now” on the homepage.