Ask for a Page that charts how your Bots talk

How this helps you

You see duplicate Bots and messy handoffs on one Page before usage or quality problems pile up.

Create a Page called Bot org chart. List every Bot you can see on my account. For each one show: job in one line, who it messages, whether it can send/spend/post, and any overlapping duties. Draw the handoffs as a simple hierarchy or flow. Flag duplicates and Bots with no clear owner job. Do not change any Bot until I approve.

What they did

In Q&A #1 someone asked for an organization chart view of their Bots. Matt liked the idea and shared that before public launch there was an internal organization button showing Bot hierarchy and how messages flowed. It did not ship, but he said you can prompt your Bot to generate that map, and suggested a Page as a good home for it. Pair that with what Eric said about memory: each Bot has its own memory, plus a small shared user memory, and skills act like user-encoded memory. The chart makes handoffs and duplicate Bots visible before you add another specialist.

Who it's for: Anyone with more than three Bots who cannot remember who owns what.

Before you start

• At least a few Bots already created
• Pages available on your plan

How to try it

1. Ask your Chief of Staff to list every Bot it can see, who they message, and which jobs overlap.
2. Tell it to create a Page titled Bot org chart with boxes for each Bot, arrows for handoffs, and notes for shared skills or routines.
3. Review the Page: merge duplicates, mark who may send or spend, and who is read-only.
4. Pin or bookmark the Page and refresh it after you add or retire a Bot.
5. Optional: add a weekly routine that updates the Page when the roster changes.

What to expect

You get a shareable Page that shows Chief of Staff at the top, specialists underneath, and arrows for research-to-writer style handoffs.

Common mistakes

• Treating the chart as permission control; approvals still live in each Bot's rules.
• Never refreshing it after you add Bots.
• Hiding send/spend Bots in a pretty diagram without marking them.

Related tips

• Organise your Bots: sections, pins, names and colours: Group Bots into sidebar sections, pin the ones you use most, give them short clear names and let your main Bot recolour them by area.
• Turn data your Bot already has into an interactive Page: Matt Palmer of the Grok Bot team asks for Pages that teach a concept or chart his own data: training logs he keeps in chat and his X posting patterns pulled through a connector.
• Build a three-Bot starter team: Scout, Shopper and Desk: One Bot researches and checks sources, one shops and stops before checkout, one learns a weekly task by watching you once.
• 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.

Worth knowingFrom Matt Palmer, Grok Bot Q&A #1 (6 Nov 2026), around 27:50. The shipped product may not restore the old internal org button; the Page prompt is the supported workaround he described.

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot pages & dashboards tips