Conversation squads

Conversation squads power live voice workflows. Members hand off mid-call without ending the session. Every member must have the voice capability (chat-only agents cannot continue a mid-call handoff).

Create a conversation squad

Tools per agent

Click a member on the canvas to open agent settings. Attach HTTP tools, MCP, and built-ins on that agent only — the next specialist does not inherit every tool from the previous one unless you attach them there too.

Route traffic to a squad

Instead of binding a single agent, set the voice route to a squad:

• Inbound SIP / phone — choose the squad as the inbound route
• Outbound — start a call with the squad (public API: squad_id on Calls)

The entry member starts the call. Handoffs follow canvas edges at runtime.

Settings shared across the squad

Handoffs work best when every agent runs the same voice pipeline. Under Settings you can pick one agent whose speech-to-text, LLM and voice the whole squad uses, and choose whose storage settings apply to the call. See Squad settings.

Best practices

• One job per agent — 1–3 goals max; only the tools that job needs
• Clear handoff descriptions — exact trigger conditions (“customer asks for pricing”)
• Collect before transfer — use extraction schemas so the next agent receives structured variables
• Limit context growth — use context policy on long calls to avoid token bloat

Next

• Squad settings
• Handoffs & context
• Process squads for unattended API workflows
• Squads API