Menu

Grok Bot Guides: xAI's Official Playbooks, Sorted by Job

Updated 2026-10-12

xAI publishes a free library of Grok Bot Guides on its own site. Each one is written by someone at the company who uses Grok Bot for their actual job, and walks through the bots they set up, the tools those bots connect to, and where a human still signs off. We counted 17 when we checked in October 2026.

They’re good reading, but they’re written by power users for power users. This page sorts them by job, says in a sentence or two what each one is about, and gives you a small first step to try. Every title links to xAI’s original. We wrote the summaries ourselves. If you’re new to Grok Bot, start with our Grok vs Grok Bot explainer and our Grok Bot 101 walkthrough.

One pattern runs through all of them: the bot researches and drafts, and a person approves anything that spends money, sends a message, or changes a live system. Copy that habit and you’ll avoid most beginner mistakes.

Start here

Grok Bot 101. What a “bot” really is (instructions plus its own cloud computer), how to set one up, how routines and multi-bot chains work, and a few personal workflows. Who it’s for: everyone. Try this first: read our step-by-step walkthrough, then build one small bot for a weekly chore.

Grok Bot for Work. Four everyday helpers: an inbox manager, a calendar assistant, a research scout, and one “front door” bot that sends requests to the others. Who it’s for: anyone who loses hours to email and scheduling. Try this first: have a bot sort your inbox and draft replies, and don’t let it send anything yet.

Templates for Grok Bot. How to package a bot so someone else can install it as a starting recipe, and how to install one yourself. Who it’s for: teams that want to reuse a setup that already works. Try this first: install a template, then rewrite its instructions to fit how you work.

How I run multiple teams of Grok Bots. An experimental way to run several projects: each one gets its own channel, list of bots, and task board. Who it’s for: intermediate users already running a few bots. Try this first: put two bots in one project chat before you build a bigger setup.

Sales and go-to-market

Grok Bot for Founder-Led Sales. Early-stage selling: defining your ideal customer, finding design partners, preparing for calls, building a repeatable playbook, and forecasting. Who it’s for: founders closing their first customers. Try this first: ask a bot to write a one-page ideal customer profile and a 20-account target list for you to review.

Grok Bot for SDRs. Outbound prospecting: research packets on each account, a quick check that sorts leads into clear-to-contact or needs-a-look, and outreach that’s drafted for you but sent by a person. Who it’s for: sales development reps. Try this first: get research packets for five accounts and compare them with what you’d have found yourself.

Grok Bot for GTM. Enterprise go-to-market with a “chief of staff” bot, prompts for prospecting and account research, and slide decks that update themselves. Who it’s for: account executives and GTM leads at larger companies. Try this first: ask for an account brief before your next big meeting.

Grok Bot for Post-Sales. Looking after existing customers: a coordinating bot, a specialist bot per account, and routines that prepare calls and keep track of what you promised. Who it’s for: customer success and account managers. Try this first: set up a routine that lists every open promise you made a customer and when it’s due.

Marketing

Grok Bot for Marketing. Six bots that take work from competitor research to positioning documents, Google Ads campaign drafts, landing pages, and performance reports. Who it’s for: small marketing teams and solo marketers. Try this first: have a bot compare your product page with three competitors’ and point out the gaps.

Grok Bot for Performance Marketing. Running an entire paid ad program with a team of bots, and the parts the team still handles itself. Who it’s for: anyone who manages ad spend. Try this first: ask for a weekly spend-vs-budget report with suggestions, and keep budget changes in your own hands.

Support

Grok Bot for Support. Working a support queue: connecting your tools, five jobs to hand off (bug reproduction, churn analysis, refunds against your written policy, and custom reporting among them), and turning them into routines. Who it’s for: support leads and founders who answer tickets themselves. Try this first: give a bot your refund policy and ten past requests, and see whether its decisions match yours.

Product, engineering and design

Grok Bot for PMs. A product manager with a team of bots: attention lists, help shipping software, and the specific bots the author runs. Who it’s for: product managers. Try this first: ask for a daily list of the threads and tickets that need your decision.

Grok Bot for Engineering. Engineer bots that manage coding agents in the cloud, keep a feedback loop going, and handle the rest of a small team’s work. Who it’s for: developers and engineering leads. Try this first: have a bot gather the context on one bug and write a clear task, then hand that task to your coding tool.

Grok Bot for mobile app development. A case study of six bots that build, ship, and improve one mobile game. Who it’s for: indie app makers. Try this first: set up one bot that sums up app store reviews every week.

Designing Grok Bot with Grok Bot. How a designer uses always-on bots to explore more ideas and work with real production assets while keeping the creative calls. Who it’s for: designers. Try this first: ask for several rough versions of one screen and judge them yourself.

Grok Bot for Recruiting. Interview prep, scorecards, sourcing candidates, and analyzing interview rounds across your applicant tracking system. Who it’s for: recruiters and hiring managers. Try this first: have a bot write a prep sheet for one interview loop.

Grok Bot for Legal Ops. Prep for one-on-ones with counsel, Slack triage, contract workflows, and a strict rule that bots draft and a human sends. Who it’s for: legal operations teams. Try this first: have a bot sort a week of legal requests by urgency, and let it draft only, never send.

A few honest caveats