Grok Bot on X: Why @bot Does Not Respond

Independent guide, not official support. Checked against xAI's public documentation on October 14, 2026. We did not test a reader's account or send a live request. Follow the official app for account-specific availability.

Start with the actual outcome

On X, tagging @bot hands a post to your main Grok Bot. The public @bot response is only a confirmation; the work and its result appear in the Bot's conversation in Grok Bot. A confirmation is therefore not a promise that the task will be answered publicly.

If there is no @bot reply, xAI says your Bot did not receive that request. Before resetting anything, use this decision path.

Six checks in order

1. Did you personally tag @bot?

A reply in a thread that already mentions @bot is not sufficient. Your own post or reply must include @bot. If the same post also tags @grok, remove the second mention for this test. Both are documented reasons for silence.

2. Is there video or GIF content in the thread?

The post you send, the post it replies to, or a quoted post can prevent handoff when it contains video or GIF media. Still images are supported. For diagnosis, choose a public, text-only post that does not quote a media-heavy thread.

3. Is the correct X account connected?

Open grok.com → Settings → Account and check the X Account connection. It must be the same X account you are posting from, linked to the same Grok account with Grok Bot access. Complete any authentication on official sites only.

If @bot responds with a sign-up link, xAI says it cannot find a linked Grok account for that X identity. Link the account first; do not keep reposting.

4. Do you own at least one Bot?

A Bot shared with you by another person cannot receive your tagged requests. You need a Bot you created. If @bot says Grok Bot is not set up, xAI says the accounts are connected but an owned Bot is missing.

5. Is your X account region eligible?

According to xAI, tagging is not yet available for accounts based in Australia, the UK, the EU, Iceland, Liechtenstein, or Norway. An X account with only a broad region or no country recorded may also be ineligible. Eligibility uses the country X has on record, not your physical location. Do not assume a network change alters this setting.

6. Are usage or moderation blocking the handoff?

xAI also lists exhausted weekly Grok Bot usage and internal moderation among possible causes. Check your current account usage and the content of the public post. There is no universal reset time or request allowance promised by these sources. A single silent post is not proof of an outage or an account ban.

Read the response correctly

One safe diagnostic and when to stop

Try one public, text-only request about non-sensitive material. Do not post private files, customer information, credentials, or payment data. If you get a confirmation, inspect the Bot conversation instead of posting repeated requests. If not, note which prerequisite failed and consult official help.

When contacting support, keep the app version, approximate time and time zone, the visible reply (or lack of one), and a redacted description of the account-link state. Never share passwords, one-time codes, cookies, or private conversations.

Official evidence and limitations

The xAI guide to tagging @bot (updated October 7, 2026) provides the eligibility rules and response meanings. Grok Bot troubleshooting explains how to diagnose account and task issues without destructive resets. The official changelog documents product changes; X search by a Bot and X @bot tagging are separate features, so search access does not prove tagging eligibility.