Repository Public
1<!-- source: https://docs.x.ai/grok-bot/use-cases (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Start34# Use cases56The best Grok Bot roles own a repeatable outcome, not a loose category of7questions. Start with read-and-prepare work, review the result, then add8approved actions or a routine.910## Sales Outbound1112**Owns:** account research, contact prioritization, and review-ready outreach.1314**Connect:** customer relationship management (CRM), product-intent sources,15company websites, email, and professional networks as permitted by their terms.1617**Start with:**1819> Research the 25 accounts in this CRM view. Score them against our ideal20> customer profile (ICP) and recent intent, identify up to three relevant21> contacts per account, and draft email and LinkedIn outreach in the style22> examples attached. Skip anyone already in an active sequence. Return a review23> list; do not send or enroll anyone.2425After the output is reliable, create a nightly research routine that stops at26the review list.2728## Talent Scout2930**Owns:** sourcing, candidate research, outreach drafts, and scheduling31preparation.3233**Connect:** applicant tracking system (ATS), approved sourcing tools, email,34and calendar.3536**Start with:**3738> For this role description, find 20 potential candidates who meet the must-have39> criteria. Exclude anyone already in our ATS, explain the evidence for each40> match, and draft personalized outreach in my voice. Do not contact anyone.4142Add approvals before external outreach, and have the Bot respect candidate43privacy, regional requirements, and source terms.4445## Paid Media4647**Owns:** campaign monitoring and budget recommendations.4849**Connect:** advertising platforms, analytics, budget spreadsheet, and Slack.5051**Start with:**5253> Pull current spend and performance by campaign. Compare it with the monthly54> budget and target customer acquisition cost (CAC), then recommend55> reallocations with the supporting56> numbers. Draft a Slack update for the growth team. Do not change budgets or57> send the message.5859Keep campaign changes behind approval even after the analysis becomes a60routine.6162## Expense Manager6364**Owns:** weekly expense reconciliation and missing-information follow-up.6566**Connect:** expense system, email, shared drive, and finance spreadsheets.6768**Start with:**6970> Build this week's expense summary from the expense system and attached71> policy. Match receipts from the finance inbox, flag missing categories or72> policy exceptions, and draft one follow-up per owner. Return the summary and73> drafts; do not send messages or change reimbursements.7475Ask for policy citations on every exception and totals that reconcile back to76the source.7778## Product Performance7980**Owns:** targeted performance investigations with evidence.8182**Connect:** observability, analytics, incident tooling, and source-control83links.8485**Start with:**8687> Investigate the checkout latency increase since yesterday's release. Review88> dashboards, traces, and flamegraphs; identify the highest-confidence hotspot;89> and return a short write-up with screenshots and direct links. Separate facts90> from hypotheses. Do not change alerts or production settings.9192Use a routine for a recurring health report, not for unsupervised production93changes.9495## Bug Reproduction9697**Owns:** turning reports into reliable reproduction packs.9899**Connect:** issue tracker, staging environment, browser, and network tools.100101**Start with:**102103> Read this bug report and reproduce it in staging using a fresh test account.104> Return exact steps, expected and actual behavior, screenshots, browser and OS105> details, relevant console or network notes, and a minimal test case if106> possible. Do not use production customer data.107108Provide approved test credentials through a secure handoff, not chat.109110## Account Health111112**Owns:** risk and expansion signals across a customer portfolio.113114**Connect:** CRM, product usage, support, billing, and customer-success notes.115116**Start with:**117118> Review the accounts in this portfolio. Combine recent usage, support119> escalations, renewal timing, and stakeholder activity into a ranked watch120> list. For each account, include the evidence, why it matters, and a suggested121> next step. Do not contact customers or edit the CRM.122123Define risk thresholds in the Bot description so the weekly result stays124consistent.125126## Chief of Staff127128**Owns:** a source-linked digest of what changed and what needs attention.129130**Connect:** Slack, email, calendar, meeting notes, and planning documents.131132**Start with:**133134> Review activity since yesterday across my approved channels, inbox, calendar,135> and meeting notes. Return only items that map to the priorities in this136> document. For each item, include the source, why it matters, the proposed next137> step, and whether I owe a decision. Do not send messages or change meetings.138139Tune the Bot by marking what was useful and what was noise. Then schedule the140digest for a time you can review it.141142## Turn an example into a durable Bot143144For any role:1451461. Put the job, source systems, output format, and standing boundaries in the147 Bot description.1482. Run one real task with a safe scope.1493. Correct the result until it is reviewable.1504. Save the successful process as a skill.1515. Test it on a second input.1526. Create a routine only when retries and failure cases are defined.1537. Keep consequential external actions behind approval.154155Continue with [Get started](/grok-bot/get-started), then review156[files and results](/grok-bot/files-and-results) and157[approval boundaries](/grok-bot/approvals-security-and-privacy).158