Scenario Practice: Choose Your Route
💡 Goal: In about 15 minutes of reading this overview, you'll pick the Grok Bot scenario route that suits you and walk away with two things—a starting plan for that route (an official starter prompt, or a combination of verified features like X search and Pages), and the six-step implementation method for turning a role into a persistent Bot. This is the fourth stop of this Grok Bot tutorial: Efficient Workflows answered "how to lock in your work," and this stop answers "what to use it for."
🎯 Stage Goals
- Be able to state the official definition of a "good role"—it has a repeatable output, not a pile of scattered questions—and use it to judge whether the work at hand is suitable for turning into a Bot
- Be able to start with a starter prompt, and know why it stops where it does: every official prompt deliberately stops at the review point, leaving sending, publishing, purchasing, and production changes behind approval
- Be able to run a role as a persistent Bot following the official six steps: write responsibilities into the description → run once within the safety scope → refine until reviewable → save as a skill → only define a routine after retries → keep external actions behind approval
⏳ Estimated Time
- This overview: about 15 minutes
- Taking just one route: Route A (Workplace) has 5 lessons at about 54 minutes, Route B (Programmers) has 3 lessons at about 34 minutes, Route C (Creators) has 3 lessons at about 34 minutes (including a ±30% margin: about 38–70 / 24–44 / 24–44 minutes)
- Taking all three routes: 11 lessons totaling about 122 minutes (about 85–159 minutes)—read routes on demand; there's no need to cover everything
🚀 Before You Start
- You've completed the Efficient Workflows stage—the scenario pages assume you already know the main line of "do it once → save as a skill → build a routine"
- Know how to save skills before coming here: every lesson in Routes A and B requires saving the working method as a skill; if you haven't read 3.2 Skills and Demonstration, catch up first
- Most scenarios require connecting apps (CRM, email, Slack, issue tracking…): see the 5-step connection method in 2.5 Connecting Apps
- Think of a piece of work you repeat every week—the judging criteria are below; one-off questions aren't suitable for turning into a Bot
- A cup of coffee ☕—the highlight of this stage is reusable starter prompts and a few comparison tables, so the hands-on workload is light
📚 Choose Your Route
The official use-cases page provides 8 roles with starter prompts. At this stage, they are regrouped by audience into three routes: 5 for the workplace, 2 for programmers; the creator route is built from three verified features: X search, Pages, and a Bot-specific mailbox. 11 lessons in total.
The basis for choosing a route isn't your job title, but "who keeps assigning you repetitive work."
Route A: Workplace—Watch the Information Flow for You (5 lessons, about 54 minutes)
Who it's for: people who spend every day being chased by Slack, email, calendars, and reports. All 5 roles come from the official use-cases page, each with a ready-made starter prompt.
| Scenario | Output the Bot Delivers | What to Connect | Duration |
|---|---|---|---|
| A1 Daily Briefing | A change summary with source links, flagging what awaits your decision | Slack, email, calendar, planning docs | 12 minutes |
| A2 Expense Reconciliation | Weekly reconciliation summary + one follow-up draft per person with missing items | Expense system, email, finance sheets | 10 minutes |
| A3 Sales Outreach | Account research, contact ranking, reviewable outreach drafts | CRM, intent sources, email | 12 minutes |
| A4 Talent Sourcing | Candidate sourcing and research, personalized outreach drafts | ATS, sourcing tools, email, calendar | 10 minutes |
| A5 Account Health | A ranked list of risk and expansion signals | CRM, usage, support, billing | 10 minutes |
The official page also has an 8th role, "Paid Media": monitoring campaigns and suggesting budget adjustments, connected to ad platforms, analytics, budget sheets, and Slack. This tutorial doesn't yet have a dedicated page for it; see the official use-cases page for the starter prompt (docs.x.ai/grok-bot/use-cases).
Route B: Programmers — Bringing the Bot into the engineering workflow (3 lessons, about 34 minutes)
Who it's for: people who write code, watch alerts, and get chased by issues. The first two lessons come from official roles, and the third uses the cloud computer itself as a development environment.
| Scenario | Output the Bot Delivers | What to Connect | Duration |
|---|---|---|---|
| B1 Bug reproduction | From bug report to reproduction package: steps, screenshots, minimal test case | Issue tracking, staging environment | 12 minutes |
| B2 Performance investigation | Targeted troubleshooting backed by evidence, keeping facts and hypotheses separate | Observability, profiling, incident tools | 12 minutes |
| B3 Cloud computer as a development environment | Persistent /workspace: run scripts, install dependencies, verify the environment | The cloud computer has a built-in terminal and browser — no connected apps needed | 10 minutes |
Remember two official details first: B1's test credentials must go through a secure handover (Take over) — never send them in chat; B2's routine is only for periodic health reports, not for unattended production changes.
Route C: Creators — from topic selection to delivery to subscription (3 lessons, about 34 minutes)
Who it's for: people who make content and need to deliver on a regular schedule. This route isn't a copy of official roles — it's a production line built from three verified features: X search to find trending topics → Pages for delivery → a dedicated mailbox to send subscriptions.
| Scenario | What you do | Which feature it relies on | Duration |
|---|---|---|---|
| C1 Topic research | Search public posts, read web pages, and follow trends for topic research | X search (no connection needed, read-only) | 10 minutes |
| C2 Deliver with Pages | Turn reports and dashboards into shareable pages | Pages (stored in the Bot's Library) | 12 minutes |
| C3 Email newsletter | Send newsletters to readers from the Bot's dedicated mailbox | mail.grokbot.com mailbox + routine | 12 minutes |
C3 builds on 2.6 the Bot's dedicated mailbox — emails sent by a routine always go to drafts and wait for you to click Send, and this rule sets the newsletter's sending cadence.
After choosing: the official six steps to turn a role into a persistent Bot
Whichever route you choose, the implementation path is the same — the six steps given on the official use-cases page:
| Step | What you do | Corresponding tutorial |
|---|---|---|
| 1 | Write the responsibilities, data sources, output format, and standing boundaries into the Bot's description | 1.5 Your first Bot |
| 2 | Run one real task within a safe scope | — |
| 3 | Refine the results until they can be reviewed without you watching | — |
| 4 | Save the proven method as a skill and test it with a second input | 3.2 Skills |
| 5 | Only create a routine after defining retry and failure handling | 3.3 Routines |
| 6 | External actions with consequences always stay behind approval | 3.1 Approvals |
The first 3 steps all stay within the safe zone of "reading and preparing" — every official starter prompt deliberately stops at a review point: get reviewable results first; sending, publishing, purchasing, and production changes always stay behind approval.
Why can't the order be reversed? A routine runs "the method that works when you're not there" — if the process isn't reliable before you schedule it, errors will show up for work right on time too.
🎒 What you'll gain
- A map of Grok Bot scenarios organized by audience: of the 11 lessons, 7 map directly to official roles (workplace 5, programmers 2), and the other 4 lessons turn the cloud computer, X search, Pages, and the dedicated mailbox into development and creation tools
- An official yardstick for "what's worth turning into a Bot": what a role owns is repeatable output, not a pile of scattered questions
- A six-step implementation method: from writing responsibilities to creating a routine, every key step has a corresponding tutorial as backup
- A safety line shared by all scenarios: the starter prompt stops at a review point — review first, delegate later, and external actions always go through approval
The scenarios are the shell; the method is the core: all three routes use the same "get it right first, then solidify it, then automate it" approach. After finishing any route, you can move on to the advanced handbook for cloud computer maintenance, Vault, and team management, turning a single Bot into a team's infrastructure.
Ready? Start lesson one: the daily briefing →
Not taking the workplace route? Go straight to your starting point: Bug reproduction (programmers) · Topic research (creators)