Start with a chief of staff Bot

How this helps you

You only have to talk to one Bot. It works out which of your other Bots should do the job, so you are not juggling chats.

You are my chief of staff. When I ask for something, decide which of my Bots should do it, hand it over, and give me one short summary when it is done.

What they did

Several top YouTube creators (Nate B Jones, Matthew Berman, Alex Finn) set up a chief of staff Bot first. They talk mostly to it, and it passes jobs like calendar or email work to the right specialist Bot.

Who it's for: Anyone with two or more Bots who is tired of switching between chats.

How to try it

1. Create one Bot whose description says it coordinates your other Bots and is the one you talk to.
2. Add specialist Bots one at a time (email, calendar, research), each with one job.
3. Ask the chief to hand work over and report back with one summary, instead of you messaging each Bot.
4. Keep the team small. @unicodef1wn's article says 'you don't need 45 bots'.

What to expect

You send one request; the chief tells you which Bot took it and comes back with a single summary.

Common mistakes

• Starting with many Bots at once. Add a specialist only when a job keeps coming up.
• Putting every Bot in one group chat. In a group chat every Bot answers, which uses more usage.

Related tips

• One job per Bot: Give each Bot one job and a list of things it never does.
• Pick a main Bot so it can see and delegate across your team: A main Bot gets wider visibility into your other Bots, messages you first, and hands work out.
• Use a group thread to watch Bots work together: Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
• Make an executive assistant your first Bot: Charlie Chang's beginner setup: one general helper Bot first, told plainly what it owns, before any specialists.
• Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
• Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
• Keep an attention list instead of a priority list: An hourly routine reads your email, Slack, meetings and calendar and keeps a short list of what you are actually working on. Other Bots use it as a filter.
• A manager Bot that never does the work itself: Give a lead Bot one job: break work down, hand it to worker Bots, and check results against the goal. Big projects then run as a chain you only talk to at the top.
• Plan every Bot job with four blocks: Corey Ganim runs 6 Bots and 14 weekly routines across 11 apps. Each job is built from the same four blocks: Bot, routine, skill and connector.
• Run a daily standup with your Bots in a group chat: Put your main Bots in one group chat and have your primary Bot ask each morning what everyone is doing today, so nothing slips.
• Three questions before you create another Bot: Only make a new Bot if the job needs its own memory, different permissions or its own schedule. Otherwise give it to your chief of staff.
• Route every meeting transcript to the right Bot with a webhook: When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.
• A people Bot that remembers everyone you meet: Tell one Bot about people as you meet them, with exact spellings, and ask it later who someone was in one line.

Worth knowingThe Grok Bot team said in Lenny's Podcast that early users mostly talked to a chief of staff that fanned out tasks. Multi-bot chats use more weekly usage, so keep the team small.

Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips