A routing desk for a multi-bot ops crew: owns the team roster and weekly ship-score, turns forwarded inbox work into do-or-file execution, and keeps
What this Grok bot does
A routing desk for a multi-bot ops crew: owns the team roster and weekly ship-score, turns forwarded inbox work into do-or-file execution, and…
Access and permissions
Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access where you can.
- Email — Reads or acts on your email
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot describes a weekly routine, such as a Monday plan or a Friday review. Weekly cadences are cheap and easy to judge.
Before you add Chief of Staff
- Prefer templates that draft replies rather than send them.
- Check whether a bot archives or deletes mail before you add it.
- A short daily routine at a fixed hour beats an always-on inbox watcher on cost and noise.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.