Independent, unofficial guide written by everyday users · Not part of or affiliated with SpaceXSI (formerly xAI) · New to Grok? Start at GrokExplained.com
GrokBotExplainedPlain-English Bot guides · Unofficial
Beginner guide

See It in Action: One Everyday Grok Bot Setup, Step by Step

Facts last checked October 23, 2026 · About a 7-minute read

GXP, the friendly robot guide for this site, waving hello

Reading about Grok Bot is one thing. Watching someone use it is often when it finally clicks. So let's follow one made-up person through one ordinary week, and show what they type, what each Bot does, and what comes back.

About this page: Pat is an example we made up, not a real customer, and the messages below are our own examples, not screenshots of the app. We drew simple diagrams instead so nobody mistakes this fan site for the real product. Every fact about what Grok Bot can do is linked to an official page.

First, Three Words You'll Hear

Bot
A Bot is an AI helper with a name and one main job. The official docs call it a "durable AI teammate with a name, a job, its own conversation," and memory of how you like things done.[2] You can have more than one, each with its own job.
Chat
A chat is one conversation. Each Bot has its own conversation,[2] so talking to a bills Bot and a calendar Bot means two separate chats. Think of separate text threads with different people: what you say in one thread stays in that thread. You can also start a group chat with two to six Bots in it, like a group text.[1]
Prompt
A prompt is simply the message you type (or say) to a Bot: a question, a request or a job you want done. There's no special wording to learn. Just ask the way you'd ask a helpful friend, and add any details that matter, like "every Monday" or "ask me before you pay anything." Everything Pat types in the examples below is a prompt.
GXP, the friendly robot guide for this site, pointing to the three words
These three words come up a lot.

Meet Pat (Our Example)

Pat has a busy household and a small side business selling handmade candles. Every week there are bills to keep straight, appointments to remember, and a head full of ideas for the business that never quite turn into plans.

Pat used to think of AI as something you chat with or use to look things up. What changed was learning that you can hand a Bot a real job, and that Bots can pass work to each other, so you don't have to be the one keeping track of who does what.[3]

Step 1: One Front-Door Bot, Three Helpers

Pat sets up four Bots. Making a Bot means giving it a short name, one main job, and a description of how it should work.[6] The description is the place for rules that should always stay true, like "never send anything without asking me."[2]

  • Chief of Staff is Pat's "front door." Pat messages this one first. Its job is to pass each request to the right helper and bring the results back in plain words.
  • Bills Helper keeps the household bills in date order and adds them up. It never pays anything.
  • Calendar Helper keeps appointments and reminders straight.
  • Ideas Helper turns business ideas into small, low-cost plans.
Example · Pat's description for the Chief of Staff

Name: Chief of Staff
Job: My front door for the week
Description: When I ask for something, decide which of my helper Bots should handle it, pass it along, and bring the results back to me in short, plain words. Never send, buy, pay for or delete anything without asking me first.

Why separate helpers? The official guide says focused Bots build more useful context than one catch-all Bot.[6]

Step 2: Pat Sends One Message

On Monday morning, Pat opens the Chief of Staff's chat and types one message. You can also speak a message instead of typing it.[1]

Example · What Pat types

This week the electric and phone bills are both due, I have a dentist appointment Thursday at 3, and I want a few ideas for a fall candle sale that won't cost much. Sort it out and tell me what you need from me. Don't send, pay or buy anything.

That's it. Pat doesn't need to remember which Bot handles bills or which one handles the calendar. That's the Chief of Staff's job.

Step 3: The Chief of Staff Passes the Jobs Along

Here is the part that surprises most people: Bots can hand work to each other. The official docs say a Bot can send a message to another Bot, the other Bot "wakes, handles the request, and can reply later," and you can see the handoff in the conversation.[1] So Pat can watch what was passed to whom.

The official docs give one tip that fits here: give each step a single owner, because too many handoffs at once can create duplicate work and noisy updates.[1]

Step 4: Each Helper Does Its Job

Bills Helper

It lists the two bills with their due dates and the total, using the amounts Pat gave it earlier, and makes a simple plan for paying them on time. It doesn't pay anything or give financial advice. Paying stays with Pat.

Calendar Helper

It sets up a reminder for Wednesday evening. A repeating or scheduled job like this is called a routine: it tells a Bot when to do something, and it can run while Pat's laptop is closed.[5] Pat can pause, test, edit or delete a routine later.[5]

Ideas Helper

It writes five sale ideas with the cheapest one first, plus a short note Pat could send to past customers. If Pat has connected an email account, the Bot can show that note as an editable draft. Pat reviews the recipients and the words, then chooses Send or Discard.[1] Nothing goes out on its own.

Step 5: What Comes Back to Pat

The helpers report back to the Chief of Staff, and it pulls everything into one short answer in Pat's chat:

Example · What the Chief of Staff sends back
  1. Bills: the phone bill is due first, then the electric bill. The total and a simple plan are in the Bills Helper chat.
  2. Dentist: a reminder is set for Wednesday at 6 PM.
  3. Sale ideas: five ideas, cheapest first. My favorite: a "bring back your jar" discount.
  4. Needs you: a draft note to past customers is waiting for your review. I haven't sent anything.

Pat spent about two minutes typing. The Bots did the sorting, listing and drafting.

Step 6: Pat Says Yes, No, or Change This

Pat is still the boss. When a Bot wants to do something that needs Pat's OK, it shows what it plans to do, and Pat can choose Allow once, Always allow or Deny.[10] For passwords, two-factor codes and payment confirmations, the Bot hands control to Pat, who does that step personally.[10]

Example · What Pat types back

Make the customer note shorter and friendlier, then show me again. Change the reminder to 7 PM.

Approval requests and email drafts show up in a Bot's own one-to-one chat, not in a group chat,[1] which is one more reason it helps to know what a chat is.

GXP, the friendly robot guide for this site, holding up one hand to say stop
Stop: nothing happens until Pat says yes.

Step 7: Next Week, It Starts on Its Own

After a few weeks of this, Pat asks the Chief of Staff for a routine: every Monday at 8 AM, look over the week and send a short list of what needs attention. "Chief of Staff" is one of the official example jobs, built around exactly this kind of digest of what changed and what needs you.[4] The official advice is to make a task reliable first, and only then put it on a schedule.[5]

Example · What Pat types

Every Monday at 8 AM, send me a short list of what's coming up this week: bills due, appointments, and anything waiting on me. Don't send or pay anything.

What's Official and What's Just One Way to Do It

  • Official: Bots can message each other and hand work off,[1] and the overview says Bots coordinate "so you aren't the router between tools."[3] You can put two to six Bots in a group chat, and they can pass work among themselves.[1] The docs' own team example has a coordinator Bot that "can assign work."[2]
  • Official: "Chief of Staff" is a listed example job, focused on a daily digest.[4][7]
  • One way to do it: using a chief of staff Bot as the single "front door" that sends every request to the right helper is a way some users like to organize their Bots. It isn't an official feature name, and you don't have to do it this way.
GXP, the friendly robot guide for this site, giving a thumbs up
Start small. Add helpers later.

Do You Need All This on Day One?

No. One Bot is plenty for many people. The official advice is to start with the smallest useful team and add another Bot only when a job has a steady role of its own.[2] A good path:

  1. Start with one Bot and one job. Our guide Which Grok Bot Job Should You Start With? helps you pick.
  2. When a second kind of job keeps coming up, add a second Bot. See After Week One: Running More Than One Bot.
  3. Only then, if it helps, make one of them your front door.
One safety note: all of your Bots share one cloud computer, including its files and website logins, so separate Bots aren't a security wall.[9][10] Keep anything that sends, buys, pays or deletes behind your approval. See Keeping Your Bot Safe.

What About Cost?

Grok Bot needs a paid plan, and Bot work draws from your plan's weekly usage pool.[8] More Bots and more routines mean more work, so they use more of that pool. No actual usage amount is published for any plan, so we can't tell you how many Bots or handoffs a plan covers. The honest way to find out is to watch your own usage for a week or two. See Which Plans Include Grok Bot? for current plans.

Words to Know

Plain-English definitions in our own words, with official facts linked.

Bot
An AI helper with a name, one main job and its own conversation.[2]
Chat
One conversation. Each Bot has its own, like a separate text thread with one person.[2] A group chat has two to six Bots in it, like a group text.[1]
Prompt
The message you type or say to a Bot: a question, a request or a job. Plain everyday words work fine.
Chief of staff Bot
A Bot whose job is keeping track of the big picture for you. Officially, "Chief of Staff" is an example job built around a daily digest of what needs your attention.[4] Some people also make it their "front door" Bot that passes jobs to helper Bots.
Helper Bot
Our name, not an official one, for a Bot with one narrow job, like bills or reminders, that the front-door Bot passes work to.
Handoff
When one Bot sends a job to another Bot. You can see handoffs in the conversation.[1]
Routine
Tells a Bot when to do a job, such as every Monday at 8 AM.[5]

Common Questions

What is a “chat” in Grok Bot?

A chat is one conversation. Each Bot has its own conversation, so talking to two different Bots means two separate chats, a lot like separate text threads with two different people. You can also start a group chat with two to six Bots in it.

Can Grok Bots hand work to each other?

Yes. The official docs say a Bot can send a message to another Bot, the other Bot handles the request and can reply later, and you can see the handoff in the conversation. Bots in a group chat can also pass work among themselves.

What is a chief of staff Bot?

Chief of Staff is one of the official example jobs, built around a daily digest of what changed and what needs your attention. Some people also use a chief of staff Bot as their “front door”: the one Bot they message first, which passes each job to the right helper Bot. That second idea is a way some users organize their Bots, not an official feature name.

Do I need several Bots to start?

No. One Bot is plenty for many people. The official advice is to start with the smallest useful roster and add a Bot only when the work has a steady job of its own.

How much does it cost to run several Bots?

Grok Bot needs a paid plan, and Bot work draws from your plan's weekly usage. No actual usage amount is published for any plan, so the honest way to find out is to watch your own usage for a week or two.

What to Read Next

Sources

Facts on this page come from these official pages, checked on October 23, 2026. Pat, the story and the example messages are our own illustration, not official examples. Grok Bot changes often, so if something looks different on your screen, the official page wins.

  1. Message and collaborate, official Grok Bot docs: https://docs.x.ai/grok-bot/chat-and-collaboration
  2. Create and manage Bots, official Grok Bot docs: https://docs.x.ai/grok-bot/bots
  3. Grok Bot overview, official docs: https://docs.x.ai/grok-bot/overview
  4. Use cases, official Grok Bot docs: https://docs.x.ai/grok-bot/use-cases
  5. Skills and routines, official Grok Bot docs: https://docs.x.ai/grok-bot/skills-routines-and-automations
  6. Get Started, official Grok Bot docs: https://docs.x.ai/grok-bot/get-started
  7. Grok Bot product page: https://x.ai/bot
  8. Grok Bot on The X Subscription, official docs: https://docs.x.ai/x-subscription/grok-bot
  9. Frequently asked questions, official Grok Bot docs: https://docs.x.ai/grok-bot/faq
  10. Approvals, Security, and Privacy, official Grok Bot docs: https://docs.x.ai/grok-bot/approvals-security-and-privacy