Let Grok Bots hand work off asynchronously

A Bot can send an asynchronous message to another Bot. The receiving Bot wakes, handles the request, and can reply later. You see the handoff in the conversation. Official steps: Message and collaborate → Let Bots hand work off. Overview: Grok Bot.

When handoffs help

• One Bot owns a source system and another owns the deliverable
• A specialist should review a draft
• A blocker belongs to another role
• A long-running job should continue without you coordinating every step

Ask for a clean handoff

1. Name one owner for the current stage.
2. State the outcome, the source of truth, and what requires your approval.
3. Tell the owning Bot which teammate should wake next (and what that teammate must return).
4. Watch the transcript for the handoff message and the receiving Bot’s reply.

Example pattern:

@Researcher gather the sources and link every claim, then hand off to @Writer. @Writer produce the draft and stop. Do not publish.

Group chat vs direct handoff

• Group chat: several Bots share one outcome and visible handoffs (Start a Grok Bot group chat). Bot-to-group handoff messages are currently text-only.
• Direct handoff: one Bot messages another asynchronously; useful when an image or file must go Bot-to-Bot for inspection (send the image directly to that Bot).

Pitfalls

• Too many parallel handoffs create duplicate work and noisy updates — keep a single owner at each stage.
• Bot-to-group messages cannot carry attachments today; send images direct Bot-to-Bot when a teammate must inspect them.
• Multi-Bot review loops can burn weekly usage — stop with Stop now and a single owner (Redirect or stop work in progress; Stop multi-Bot review loops).