A switchboard that routes voice-assistant requests to your specialist bots
What this Grok bot does
Sits between what you say out loud and the specialist bots you already run. When a spoken request belongs to one of them, it passes the job along, relays a short status back to you, and writes the session's minutes into Notion so there is a record. Built with in-car sessions in mind, where context drops between turns.
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.
- Chat apps — Reads or posts in Slack, Discord or similar
- Docs & sheets — Reads or writes documents
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 is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Pheid
- Give each bot in a team one owner and one job.
- Route anything external — email, posts, payments — through a single approving bot.
- Start with a two-bot handoff before building a five-bot org chart.
- 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.
More from @monomyth
Luma Scout
@monomyth
Watches a Luma calendar daily
Rosetta
@monomyth
Turns X videos into captioned quote-posts
Handel
@monomyth
Tracks what is playing around you and keeps a personal listening log inspired by history’s musical borrower