The best Grok Bot prompts are a weekday briefing routine, a meeting note-taker, a US restaurant call, a saved weekly skill and a three-Bot group kickoff, and the weekday briefing routine is #1. Each one below uses a feature xAI documents on docs.x.ai/grok-bot, and each one tells the Bot where to stop.
📺 Watch: Grok Bot for Beginners (Set Up Your First Agent Today)
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
That last part matters most. xAI's own guidance says to make the outcome and the decision boundary explicit: what the Bot may change, and where it must stop for you.
Julian Goldie shares new AI systems for small business owners every week inside the AI Profit Boardroom. If you want help picking which of these prompts fits your business first, book a free AI strategy session.
What makes a Grok Bot prompt work
Grok Bot is an agent with its own cloud computer. All your Bots share one persistent computer with a browser, a filesystem and a terminal, and work keeps going when the app is closed.
So a prompt is a job description, not a question. The strong ones carry four parts:
- The result. A summary, a page, a draft, a list.
- The source. A link, a file, a connected app, a channel.
- The timing. Once, or a schedule in plain words for a routine.
- The boundary. What waits for your OK: sending, buying, publishing, deleting.
The skills and routines docs say to require approval for sending, purchasing, deleting, publishing or changing production systems. Every prompt here follows that rule.
The 12 best Grok Bot prompts, ranked
| # | Prompt | Feature it uses | Boundary built in |
|---|---|---|---|
| 1 | Weekday morning briefing | Scheduled routine | Sends nothing |
| 2 | Meeting note-taker | Meetings | Interactivity off |
| 3 | Weekly report skill | Saved skill | Nothing published without OK |
| 4 | Restaurant booking call | Phone calls (US only) | You confirm each call |
| 5 | Three-Bot newsletter | Group chat handoffs | Do not publish |
| 6 | Support repro listener | Slack trigger | No Slack reply without OK |
| 7 | Dashboard export | Vault sign-in | Hands you the computer |
| 8 | Quote comparison page | Pages | Read-only result |
| 9 | Lead form intake | Webhook trigger | Drafts only |
| 10 | Newsletter inbox digest | Bot email address | Claim needs approval |
| 11 | Open issues list | Connectors | Reads only |
| 12 | Thread to Slack | Tag @bot on X | Result stays in the app |
#1 is the weekday briefing because it runs in the cloud with your laptop shut, and it touches nothing outside the chat.
1. The weekday morning briefing
"Every weekday at 7:30 AM, read my new email, today's calendar and any Slack messages that mention me. Post a short briefing in this chat with links. Do not reply to anyone. If one of those sources fails, tell me which one instead of using old data."
The docs say a new routine waits for its next scheduled time. Set it up at 7:35 and the first run is tomorrow. Open the routine, read When to run, and use Test to try it today. There is more on schedules in the Grok Bot routines guide.
2. The meeting note-taker
"Join this Zoom call at 3 PM and take notes. Stay quiet in the meeting chat. When it ends, send me the summary and a list of action items with an owner for each."
A Bot can join Google Meet, Zoom or Microsoft Teams. You paste the link, approve the card, and the host admits the Bot. Meetings are on Team, Enterprise and Ultra plans, per the meetings docs. To keep it listening only, use Disable Interactivity under Meeting actions.
📺 Watch: Grok Bot Can Now Control Apps on Your Phone!
3. The weekly report skill
"Save what we just did as a skill called Monday client report. Include the sources we used, the output format, how to check the numbers, and the rule that nothing goes to a client without my approval."
A skill is a reusable set of instructions available across your Bots. Do the job once by hand, get it right, then save it. Only after that should you put it on a schedule.
4. The restaurant booking call
"Call the Italian place on my saved list and ask for a table for six at 7:30 PM on Saturday. Show me the number before you dial, and tell me what they said."
Phone calls work in the US only, from the desktop and phone apps. The first time, you accept the calling terms. Before each call, the Bot shows who it will call and you choose Call or Cancel. You get a live transcript and can press Take over to join.
5. The three-Bot newsletter
"@Researcher collect this week's AI search news and link every source. @Writer turn it into a newsletter draft. @Checker compare each claim with its link and list only the problems. Nobody publishes anything."
A group chat holds two to six Bots. Give one owner per stage, as the chat and collaboration docs advise. Approval requests and email drafts do not appear in a group, so keep sending in one-to-one chats.
📺 Watch: New Grok Bot Updates are INSANE!
6. The support repro listener
"Set up a routine: when a message in #help-desk includes the words needs repro, open the linked ticket, reproduce it in staging and post the steps here. Never post back to Slack without my approval."
Keep the channel and phrase narrow. The docs warn that a trigger on every message in a busy channel runs often and spends usage.
7. The dashboard export
"Sign in to my analytics account with my saved login, download last month's traffic report and save it to my files. If a passkey or code shows up, hand the computer back to me."
Vault fills logins without the Bot ever seeing the password, per the Vault docs. Never paste a password into the chat. When a site needs single sign-on, a passkey or a CAPTCHA, the Bot asks you to take over.
8. The quote comparison page
"Build a page that compares the three supplier quotes I attached, in one table, with a two-line recommendation at the bottom."
A page lives in the Bot's Library, so you can return to it and share it. Pages is rolling out gradually and is not on Enterprise teams yet.
9. The lead form intake
"Add a webhook trigger to my new-lead routine so each form submission starts a run. Draft a reply for each lead but do not send it. Then show me the POST URL."
On desktop the routine's Webhook section shows the URL, the key and the full header. A 200 response means a run started, not that it finished.
10. The newsletter inbox digest
"Get yourself an email address. Then every Friday at 4 PM, sum up the newsletters that arrived there this week, with one line and a link for each."
You can claim one address at mail.grokbot.com. Nothing is claimed until you approve the card. Email a routine sends always waits as a draft.
11. The open issues list
"Connect Linear, then list every open issue labelled website, with its owner and the date it was opened."
Type @ to attach an app to a task. A Bot can also add an MCP server by URL or command, as the computer and apps docs explain.
12. The thread to Slack
Reply to a post on X with "@bot pull the three main points out of this thread and send them to my Slack."
Your main Bot gets the task and @bot only posts a confirmation. Tagging is not yet available for accounts based in Australia, the UK, the EU, Iceland, Liechtenstein or Norway, and posts with video or GIFs are ignored, per the tag on X docs.
Where these prompts fit in your week
Start with prompts 1 and 2. They save reading time and change nothing outside the chat.
Move to skills and triggers once a job works by hand. Keep anything that sends, pays or publishes behind a card you press yourself.
If you run several agents, the Agent OS guide shows how Julian organises them in one place. To compare the AI models on scored one-shot builds, see the Goldie Bench breakdown. Grok Bot itself picks the model for each task and has no model picker.
Members of the AI Profit Boardroom get step-by-step trainings on agent setups like these. If you would rather map your own first three prompts with Julian's team, grab a free AI strategy session.
FAQ
What makes a good Grok Bot prompt?
Name the result, the source, the timing for a routine, and the approval boundary. xAI's docs ask you to state what the Bot may change and where it must stop.
Why didn't my routine run right away?
A new routine waits for its next scheduled time. Open it and use Test to run it now.
Should I put a password in a prompt?
No. Save the login in Vault or give it through a Secure Form. Values from either are filled into the page without the Bot seeing them.
Can I prompt Grok Bot from X?
Yes, by tagging @bot in a post or reply, where tagging is available for your account's country. The result shows up in your main Bot's chat in the app.
Pick one prompt above, add your own boundary line, and if you want a plan for the rest, book a free AI strategy session and put the best Grok Bot prompts to work.
