Grok Bot Use Cases & Starter Prompts
The best Bot roles own a repeatable outcome, not a loose category of questions. Start each role with read-and-prepare work, review the output, and only then add approved actions or routines.
1. Sales Outbound
Owns account research, ICP scoring, contact prioritization, and review-ready outreach.
“Research the 25 accounts in this CRM view. Score them against our ideal customer profile and recent intent, identify up to three relevant contacts per account, and draft email and LinkedIn outreach in the style examples attached. Skip anyone already in an active sequence. Return a review list; do not send or enroll anyone.”
2. Talent Scout
Owns sourcing, candidate qualification against rubric, and outreach drafts.
“For this role description, find 20 candidates who meet the must-have criteria. Exclude anyone already in our ATS, explain the evidence for each match, and draft personalized outreach in my voice. Do not contact anyone.”
3. Paid Media
Owns campaign performance monitoring, CAC analysis, and budget recommendations.
“Pull current spend and performance by campaign. Compare it with the monthly budget and target customer acquisition cost, then recommend reallocations with the supporting numbers. Draft a Slack update for the growth team. Do not change budgets or send the message.”
4. Expense Manager
Owns weekly expense reconciliation, receipt matching, and policy exception follow-ups.
“Build this week's expense summary from the expense system and the attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner. Return the summary and drafts; do not send messages or change reimbursements.”
5. Product Performance
Owns latency hotspot investigations, trace diagnostics, and incident root cause briefs.
“Investigate the checkout latency increase since yesterday's release. Review dashboards and traces, identify the highest-confidence hotspot, and return a short write-up with screenshots and direct links. Separate facts from hypotheses. Do not change alerts or production settings.”
6. Bug Reproduction
Owns converting issue reports into verified repro packs in staging environments.
“Read this bug report and reproduce it in staging with a fresh test account. Return exact steps, expected and actual behavior, screenshots, browser and OS details, and a minimal test case if possible. Do not use production customer data.”
7. Account Health
Combines telemetry, support escalations, and renewal timing into a churn-risk watch list.
“Review the accounts in this portfolio. Combine recent usage, support escalations, renewal timing, and stakeholder activity into a ranked watch list. For each account, include the evidence, why it matters, and a suggested next step. Do not contact customers or edit the CRM.”
8. Chief of Staff
Generates an actionable morning digest mapped to strategic priorities.
“Review activity since yesterday across my approved channels, inbox, calendar, and meeting notes. Return only items that map to the priorities in this document. For each item, include the source, why it matters, the proposed next step, and whether I owe a decision. Do not send messages or change meetings.”
Turn a Role into a Durable Bot
- Put the job, source systems, output format, and standing boundaries in the Bot's description.
- Run one real task with a safe scope.
- Correct the result until it is reviewable without you.
- Save the working process as a skill and test on a second input.
- Create a routine only after retries and failure cases are defined.
- Keep consequential external actions behind approval.