-
Tagged @bot on X and Got No Reply? 6 Reasons Your AI Agent Stayed Quiet
You tagged @bot on X, waited, and got nothing back? When @bot says nothing at all, it means your Grok Bot never got the request. The official help page lists six common reasons. Here they are in plain English, with what to try for each one.
Heads up: we couldn’t test this hands-on. This is our own community guide, not an official one.
First, a quick reminder of how it should work
When tagging works, @bot posts a short reply on X saying your request went to your Grok Bot. Your main Bot then does the work, and the results show up in that Bot’s chat in the Grok Bot app, not on X. So a short reply is a good sign. No reply at all is the problem this post is about.
1. Your X account is in a region where tagging isn’t available yet
Tagging @bot works in most countries, but not yet for X accounts based in Australia, the United Kingdom, the European Union, Iceland, Liechtenstein, or Norway. It also doesn’t work if X lists only a broad region for your account, like “South Asia,” or no country at all.
Good to know: what counts is the country X has on record for your account. Where you are right now doesn’t matter, and a VPN won’t change it. If this is your situation, there’s no fix on your side for now. You’ll have to wait until tagging reaches your region.
2. You replied in a thread that has @bot in it, but didn’t tag @bot yourself
Someone else tagging @bot earlier in the thread doesn’t count for you. Try this: post your reply again and type @bot in your own reply.
3. Your post also tags @grok
If the same post tags both @bot and @grok, @bot stays quiet. Try this: post again with only @bot.
4. There’s a video or GIF involved
@bot skips the request if your post, the post you replied to, or a post that either one quotes has a video or a GIF. Still photos are fine, and your Bot can see them. Try this: tag @bot on a post without a video or GIF. Or open the Grok Bot app and ask your Bot about the post there instead.
5. The post didn’t pass X’s internal checks
Posts that don’t pass internal moderation aren’t sent to your Bot. The help page doesn’t say what gets flagged, so there’s no clear fix. If you think a normal post got stopped, try rewording it. If it keeps happening, contact support.
6. Your accounts aren’t linked, or your usage is used up
Two things fall under this one:
-
Grok Bot isn’t linked to your Grok account. Your X account needs to be connected to a Grok account, and that same Grok account needs Grok Bot access. To connect X, go to grok.com, open Settings, then Account, and choose Connect next to the X account option. If your Grok Bot access comes from a SuperGrok subscription, link it using the steps on the Get started help page.
-
Your weekly usage has run out. Tagged requests use your Grok Bot usage, just like chatting in the app. Check how much you have left in the Grok Bot app under Settings, then Usage & Billing. Try again after your weekly usage resets.
Got a reply, but it wasn’t what you expected?
Those aren’t silence, and each one tells you what to do:
-
“Sign up for Grok Bot” with a link means no Grok account is connected to the X account you posted from. Connect your X account on grok.com, set up Grok Bot, and tag @bot again.
-
“Grok Bot isn’t set up yet” means your accounts are connected, but you don’t have a Bot of your own yet. Open Grok Bot, make a Bot, and tag @bot again.
Good to know: you need at least one Bot of your own. Bots that someone else shared with you can’t take tagged requests.
Still nothing?
Go through the six reasons in order. If none of them fit, contact support.
Grok Bot help page:
https://docs.x.ai/grok-bot/tag-on-x
docs.x.ai
Send a post on X to your Grok Bot by tagging @bot, see where tagging is available, and find out why @bot did not reply.
-
Sorry, there were no replies found.
Log in to reply.