Skip to main content
Bring more than one agent into a single session. Agents can hand off the conversation to each other mid-call, each running their own scenario, script, and persona — while sharing the full transcript so far.

When to Use

  • Interview loops — a recruiter agent screens for fit, then hands off to a technical agent for a deep-dive.
  • Sales flows — a discovery agent qualifies, then hands off to a specialist agent for a solution walkthrough.
  • Multi-stage training — one agent runs an onboarding module, then hands off to another for a scenario-based drill.
  • Escalation — a first-line support agent triages, then hands off to a domain expert agent.

Setting Up Handoffs

1

Create each agent's scenario

Build a scenario for every agent in the flow — script, persona, and goals. Each one runs independently once it takes the call.
2

Add a handoff on the source scenario

In the scenario editor, open the Handoffs section and pick the next agent’s scenario. You can add more than one — the agent decides which to hand off to based on the conversation.
3

Describe when to hand off

Add a short instruction for each handoff (e.g. “Hand off to the technical interviewer once the candidate confirms 3+ years of Python”). The source agent uses this to decide when and to whom.
4

Start the meeting

Send or start the meeting from the first scenario. Handoffs happen live — participants stay on the same call while the agent changes.

What Carries Over

When an agent hands off, the next agent receives:
  • The full transcript of the conversation so far
  • The participant’s identity and context (name, memory, uploaded files)
  • The handoff reason the source agent recorded
The new agent then runs its own script and persona from that point forward.

Post-Meeting

The transcript, analysis, and recording cover the entire session across all agents — you get one continuous record, with each turn labeled by which agent was speaking.
Multi-Agent is currently supported on the Gemini Live pipeline only. Scenarios using other pipelines will fall back to single-agent behavior.
Keep each agent’s scope tight and its handoff conditions specific. Overlapping scopes cause agents to hand off too early or loop back and forth.