Diagnose a Silent OpenClaw Telegram Bot
When an OpenClaw Telegram bot goes quiet, send the same simple prompt through the OpenClaw Control UI and a private Telegram chat. Use the two results to decide whether to repair the Gateway, approve the sender, or investigate the Telegram connection.
Establish a working baseline
On the OpenClaw host, run openclaw gateway status. Then open the Control UI with openclaw dashboard and send a prompt that needs no tools, such as Reply with CHECK-21. Record whether the Gateway reports that it is listening and whether the chat returns CHECK-21. The reply is the stronger test because it exercises the path from the Control UI through the Gateway to the model.
If the Gateway is down, restore it through the controls for your deployment and repeat the test. If it is listening but the Control UI chat fails, use that failure to investigate the agent or model before editing Telegram settings. If the Control UI replies, take the same prompt to Telegram so you can compare the two paths.
Establish a control-platform reply first so a silent Telegram test can be compared with a working model route.
Getting started - OpenClawRead the first private message result
Open the intended bot's private Telegram chat, press Start if Telegram offers it, and send the probe yourself. OpenClaw's default Telegram DM policy is pairing. If the bot returns a pairing prompt, verify that it came from the chat and sender you intended to enroll, then approve the request through the OpenClaw pairing procedure for your installation. Send a fresh probe after approval and look for the requested reply.
If the bot is completely silent, check whether Telegram was actually configured on the running Gateway. Confirm that its configured token belongs to the bot you opened and that the installation is using the replacement token if one was issued. Change one setting at a time and repeat the private probe after each change.
A missing reply receipt can follow a successful incoming update. Keep inbound transport, access policy and the visible reply as separate observations.
Telegram - OpenClawUse delay and group silence as separate clues
If Telegram DMs reply but a group stays silent, keep the working token in place. OpenClaw documents group allowlists and mention gating. In the intended group, send one prompt that explicitly mentions the bot, then inspect the group policy if it stays silent. If the mentioned prompt works and plain messages are ignored, verify whether mention gating is the intended behavior before changing it.
If replies are slow even in a private chat, send one probe at a time and record when each message and reply appears. Check which service reported any rate-limit error before deciding how to retry. Keep long polling, the default transport, while diagnosing an intermittent delay unless you have evidence that the transport itself is failing. Changing to a webhook adds another path to verify.
Telegram - OpenClaw