Best Grok Bot
Blog

How to Set Up an AI Chief of Staff With Grok Bots

A group of Best Grok Bot mascots standing together on the page's dark background.
TL;DR
  • An AI chief of staff is one front-door Grok Bot that takes all your requests and hands each job to a specialist bot that owns it.
  • You need a plan that includes Grok Bot and one real job you repeat every week. Start with the front door plus one specialist.
  • Write three rules down before you build anything: drafts only, one owner per handoff, and two yeses before anything sends.

Most people use AI one chat at a time. One chat for email, another for a report, another for a follow-up, and you are the one who remembers which is which. An AI chief of staff fixes that by giving you one place to send every request.

I run my business this way, with one front-door "chief of staff" bot plus specialist bots for jobs such as inbox, leads, follow-up, scheduling and reporting. This guide is the setup outline. For how I actually use mine day to day, see The AI Chief of Staff: How I Run My Business With a Team of Grok Bots.

What is an AI chief of staff?

An AI chief of staff is a front-door bot: you give it every request, and it hands the work to the specialist bot that owns that job. You talk to one bot instead of five, and each specialist does one thing well.

In Grok Bot terms, a Bot is an AI teammate with a name, a job and context that builds over time, according to the official Grok Bot overview. Each one works on a cloud computer with a browser, files and a terminal, so it can do work in real tools while your laptop is closed.

The front door does not do every job itself. Its job is routing: deciding which specialist owns a request, passing it on, and keeping track of what came back. The passing-on is called a handoff, which the official chat and collaboration docs describe as one Bot sending a message to another. The receiving Bot wakes up, does the work and can reply later, and you can see the handoff in the conversation.

What do you need before you start?

You need a plan that includes Grok Bot and one real job you repeat every week, which your first specialist will own. Grok Bot is included on the Premium, Super and Ultra plans of The X Subscription, according to the official docs, and not on Free or Plus.

Here is the short checklist:

  1. A plan that includes Grok Bot. Premium, Super or Ultra. See the official Grok Bot plan docs for the current list.
  2. One real repeating job. Something you did more than once last week, with a clear finished state. A morning brief, a client report summary or a list of recurring charges all work.
  3. The apps the job touches. Bots can connect to apps (the docs name Slack, Notion, Drive and Teams) and can also use websites that have no connected app. Know which ones your first job needs.
  4. A place to talk to it. The Grok Bot desktop app runs on macOS, Windows and Linux, and a companion app runs on iOS and Android, according to the official docs.

If you have not picked that first job yet, Start Here: 3 Bots Every Business Owner Should Install is a good place to choose.

A huddle of the Best Grok Bot mascot and five smaller specialist bots on a near-black background.

How do you set up the front-door bot?

Create a Bot, give it the job of front door in plain words, and grant access only as it asks for it. The job description matters more than anything else: it should say what the bot routes, who owns what, and when to stop and ask you.

The setup outline:

  1. Create a new Bot. In the official Create and manage Bots docs, that's New Bot (the + button) at the top of the sidebar, or Cmd/Ctrl+N. On a team, + opens a menu: choose Create a Bot. In Create New Bot, type a name, pick a shape and color for its picture, and choose Create.
  2. Name it for its role. Something like "Chief of Staff" or "Front Desk," so you always know which chat is the door.
  3. Write its job description. Keep it short. At a high level, it should cover:
  • Its role: take every request, decide which specialist owns it, and hand it off.
  • The list of specialists and the one job each owns.
  • What it does itself (quick answers, status checks) and what it never does (send, cancel, delete).
  • When to stop and ask you before acting.
  • Your three standing rules, word for word (see the rules section below).
  1. Grant access as it asks. The docs say a Bot messages you for approval when something needs it, and hands a step back to you when a site blocks automation or needs a human. Give access one request at a time, not all at once.
  2. Run one request through it by hand. Before you add anything automatic, send it one real request and watch where it goes.

How many specialist bots do you need?

Start with one, and add a second only when the first one is reliable and a new job keeps landing on the front door with nowhere to go. I run a front-door chief-of-staff bot that hands work to specialists for writing, building, research, inbox, and site work. I pause bots that are not needed in a given week. I am not publishing a headcount, because that number changes. You do not need a large team to begin.

A specialist owns one job. The templates I built are examples of that shape, and none of them sends on its own:

JobSpecialist templateWhat it never does
---------
Inbox and calendarDaily Email and Calendar BriefReply, RSVP, delete, or send anything to anyone but you
Client reporting and admin (agencies)Agency Reports and Admin HelperSend anything on its own
BillsSubscription and Bill CutterSend a cancellation without a yes on the item and a second yes on the exact text
Follow-up (insurance agents)Insurance Lead Follow-Up WriterSend, schedule, or touch a CRM

For the inbox job, see the Inbox & Email page. For follow-up, see the Follow-Up page.

If you install one of these as a template, know what comes with it. The official templates guide says a template copies a bot's instructions, relevant memories, skills and specific plugins into a new bot in your account. It does not copy custom code or scripts, secrets, private skills, or non-standard plugins such as MCP servers, and the new bot has to reinstall its plugins.

When to use a group chat. The docs allow group chats of two to six Bots, with a stated shared outcome and a named owner for the next step. That cap is a useful ceiling for a small team. But approval requests, requests for secrets or logins, and email or Slack drafts do not show up in a group, so anything that needs your sign-off stays in each bot's own chat.

To see how a front door and its specialists fit together in a real business, read The AI Chief of Staff: How I Run My Business With a Team of Grok Bots.

How should bots hand work to each other?

Every handoff should have one owner, a clear deliverable and a named next step. The official docs advise one owner at each stage and warn that "parallel handoffs create duplicate work and noisy updates." If two bots both think a task is theirs, you get two half-done versions.

A good handoff from the front door says three things:

  1. Who owns it. One specialist, by name.
  2. What done looks like. "A draft reply to this email," not "handle this."
  3. What happens next. Return the draft to the front door, which brings it to you.

Two more points from the docs:

  • There is no off switch for bot-to-bot messages. If you want a bot to check with you before messaging another Bot, tell it in plain words and ask it to remember that.
  • Make it work by hand before you automate it. The skills and routines docs advise starting with a one-time task, making it reliable, saving the method as a skill (a reusable set of instructions), and only then putting it on a routine (a rule that tells one bot when to run a job, on a schedule or when something happens). When you do create a routine, the docs say to confirm the owning bot, the schedule and time zone, the input source, the expected result, the point where the bot must ask you, and what happens if a source is missing.

What rules should you write down first?

Write down three rules before you build any bot, and paste them into every bot's job description: mine are drafts only, one owner per handoff, and two yeses before anything sends. They keep a team of bots from acting on your behalf in ways you did not approve.

Rules to write down first

  1. Drafts only. A bot that touches the outside world writes drafts. A person approves and sends.
  2. One owner per handoff. Every task has exactly one bot responsible at each stage.
  3. Two yeses before anything sends. For anything that sends or cancels: one yes on the item, then a second yes on the exact text and recipient.

The second yes is the one that catches a wrong recipient or a cancellation you did not mean.

My team also follows handoff rules and usage rules I wrote. If you want a set of ready-to-install bots, in order, that look for money before they ask you to spend more of it, see The Payback Roadmap.

How do you know it is working?

Run a few checks after the first week instead of trusting a feeling. If requests reach the right specialist, drafts come back to you before anything goes out and no task has two owners, the setup is doing its job; if not, fix the front door's job description first.

Checks you can run yourself:

  • Routing check. Send the front door five real requests. Did each one go to the specialist that owns that job?
  • Owner check. Look at the handoffs in the conversation. Did any task get passed to two bots at once?
  • Approval check. Did every send or cancel come to you for a yes before it happened?
  • Stall check. Did any bot hand a step back because a site blocked automation? Those are jobs to do yourself or rethink.
  • Usefulness check. Did you open fewer separate chats this week than last?

None of these promise a result. They tell you whether the structure works, so you can decide whether to add the next specialist.

FAQ

Do I need a separate plan for each bot?

Grok Bot is included on the Premium, Super and Ultra plans, according to the official Grok Bot plan docs. The official Grok Bot FAQ and plan pages do not state a limit on the number of Bots you can create. Check those pages for current usage rules before you add more bots, because usage comes from a shared weekly pool.

Can the front-door bot send emails for me?

My rule is that it does not. Bots that touch the outside world write drafts, and anything that sends or cancels needs a yes on the item and a second yes on the exact text and recipient.

Will my bots keep working when my laptop is closed?

Yes. The official overview says each Bot works on a cloud computer and keeps going while your laptop is closed, and routines run in the cloud too. You still get approval requests when a bot needs you.

Can I keep one bot away from my logins?

No. The official Grok Bot FAQ says all of one user's Bots share one cloud computer, including browser sessions and logins, and that separate Bots are not a security boundary. Connect only the accounts you are comfortable with any of your bots reaching.

Can I talk to my chief of staff from my phone or Slack?

The official docs say a companion app runs on iOS and Android, and you can talk to a Team Bot in Slack. Chatting with Bots in X Chat is also rolling out gradually.

This bot is one piece of a full AI team. See how I run my business with a team of Grok bots. The AI Chief of Staff: How I Run My Business With a Team of Grok Bots

Last checked: Nov 17, 2026, ET. This page needs a refresh if the official docs change how Bots are created, how handoffs or group chats work, which plans include Grok Bot, or what a template copies.