The best Grok Bot use cases are jobs that repeat and have a clear finished result, such as a ranked list, a report or a stack of drafts. The Use cases page lists eight of these jobs. Each one starts with reading and preparing, and nothing gets sent until you review it.
Each job below lists what the Bot is responsible for, what it usually connects to, and a shortened version of the first prompt from the docs.
1. Sales outreach research
Owns: researching accounts, ranking contacts and drafting outreach for you to review. Connects to: your CRM, product-intent sources, company websites, email and professional networks, as their terms allow. First prompt, shortened: research 25 accounts, score them against your ideal customer, find up to three contacts each, and draft emails in your style. "Return a review list; do not send or enroll anyone."
Once the results are reliable, the docs suggest a nightly routine that still stops at the review list.
2. Recruiting and candidate sourcing
Owns: finding candidates, researching them, drafting outreach and preparing for scheduling. Connects to: your applicant tracking system, approved sourcing tools, email and calendar. First prompt, shortened: find 20 candidates who meet the must-haves, skip anyone already in your tracking system, explain each match, and draft outreach in your voice. "Do not contact anyone."
The docs say to add approvals before any outreach goes out, and to respect candidate privacy and each source's terms.
3. Paid ads monitoring
Owns: watching campaigns and recommending budget changes. Connects to: ad platforms, analytics, a budget spreadsheet and Slack. First prompt, shortened: compare spend and results with the monthly budget and target cost per customer, recommend changes with the numbers behind them, and draft a Slack update. "Do not change budgets or send the message."
4. Weekly expenses
Owns: reconciling expenses each week and chasing missing details. Connects to: the expense system, email, a shared drive and finance spreadsheets. First prompt, shortened: build the weekly summary, match receipts from the finance inbox, flag policy problems, and draft one follow-up per person. "Do not send messages or change reimbursements."
5. Product performance checks
Owns: investigating slowdowns and other performance questions, with evidence. Connects to: observability, analytics, incident tools and source-control links. First prompt, shortened: investigate a slowdown since yesterday's release, find the most likely cause, and return a short write-up with screenshots and links. Keep facts separate from guesses. "Do not change alerts or production settings."
6. Bug reproduction
Owns: turning a bug report into clear steps someone can repeat. Connects to: the issue tracker, a staging environment, the browser and network tools. First prompt, shortened: reproduce the bug with a fresh test account, then return exact steps, expected and actual results, and screenshots. "Do not use production customer data."
The docs say test logins should come through a secure handoff, not chat.
7. Customer account health
Owns: spotting customers at risk and customers ready to grow. Connects to: the CRM, product usage, support, billing and customer-success notes. First prompt, shortened: combine usage, support issues and renewal dates into a ranked watch list, with evidence and a suggested next step for each account. "Do not contact customers or edit the CRM."
8. A daily digest (chief of staff)
Owns: a short, linked summary of what changed and what needs you. Connects to: Slack, email, calendar, meeting notes and planning documents. First prompt, shortened: review what happened since yesterday and return only items that match your priorities, each with its source and whether you owe a decision. "Do not send messages or change meetings."
Tell the Bot which items were useful and which were noise, then schedule the digest for a time you can read it.
How to turn one of these into a Bot you keep
The Use cases page gives the same seven steps for any job:
1. Put the job, the apps it uses, the output format and its limits in the Bot's description. 2. Run one real task on a small, safe scope. 3. Correct the result until it's ready to review. 4. Save what worked as a skill. 5. Test the skill on a second input. 6. Create a routine only once you've decided what happens on a retry or a failure. 7. Keep anything that acts on the outside world behind your approval.
Get started says a strong request names five things: the outcome, the sources, the limits, what to hand back, and when to stop for you. Approvals, security, and privacy lists the steps that should wait for you: sending, publishing, purchases, deleting, permission changes, production changes and accepting legal terms.
More real examples from the guides
The Grok Bot guides page has longer write-ups from people who use Bots every day. On October 17, 2026, it covered marketing, founder-led sales, ad programs, post-sales, recruiting, sales development, personal work, legal ops, getting started, engineering, support, templates, running several teams of Bots, mobile app development, design, enterprise go-to-market, and product management. One guide describes four personal work Bots: an inbox manager, a calendar assistant, a research Bot, and one Bot that acts as the single front door for the others.
The docs and guides focus on work. They don't publish a list of personal or household jobs. For a few home examples, see our tax review and spam call posts.
To start from someone else's setup, Create and manage Bots says the x.ai Marketplace (labeled Marketplace in the app's sidebar) lists Bots you can add. Choose Add, or open a Bot and choose Import Bot, and you get your own copy of its template.