Orchestration lets one agent (a supervisor) bring in other agents (specialists) when a question falls outside its lane. Instead of asking every agent to do everything, you build a small team — one front desk, a few specialists — and let them cooperate.
Find these settings under Settings → Orchestration on any agent.
Set up a supervisor
To make an agent a specialist of another agent:
- Open the specialist's settings.
- Set Supervisor agent to the agent that should route to it.
- Optionally add Specialization domains (e.g. "billing", "vision", "scheduling") so the supervisor knows what this specialist is best at.
From the supervisor's side, pick an Orchestration pattern. Two patterns are available today:
Handoff
With Handoff, the supervisor decides when to transfer the conversation to a specialist. After the handoff, every following message in that conversation is answered by the specialist — its prompt, model, tools, and memory — until you start a new conversation.
Use handoff when:
- A question needs deep specialist knowledge for several turns (not just one lookup).
- You want the customer to clearly feel they've been "transferred to billing" — like a real call centre.
The supervisor announces the transfer to the customer before it happens, so it never feels abrupt.
Sequential
With Sequential, the supervisor stays in charge. When it needs a specialist's input, it consults them privately, receives their reply, and folds it into its own answer. The customer only ever talks to the supervisor.
Use sequential when:
- You need a one-off lookup ("what's our refund policy?") rather than a full transfer.
- The supervisor has the customer context and the specialist provides a single fact.
Specialist calls have a depth limit of three, so a misconfigured chain can't recurse forever.
Specialisation domains
Each specialist can declare what it's good at — "vision", "reasoning", "extraction", "translation", and so on. The supervisor sees this list in its prompt and uses it to decide who to call.
Pick domains that describe the specialist's skill, not the product area. "Billing" is fine if the agent's whole purpose is billing; "extraction" is better when the specialist's job is pulling structured data out of messages.
What about concurrent or group-chat patterns?
Two other patterns — concurrent (run specialists in parallel) and group chat (specialists deliberate together) — are not yet available and are hidden from the picker. They need a different execution model and will be added in a future release.