How voice AI agents transfer calls to a human: cold transfer, warm transfer, and conferenced calls. With Telnyx, the AI stays on the line.
AI voice agent handoff to a human is when a voice AI brings another person into a live call. With Telnyx's Multi-Participant Voice AI Calls, an agent can invite a colleague or specialist, introduce them, and stay on the line. It listens quietly while the humans handle the conversation and steps in when one of them asks it to check a calendar, update a record, or schedule a meeting.
AI agent handoff to a human is the moment a voice AI agent transfers a call, in part or in whole, to a human worker. The AI may end its part of the call (cold transfer), brief the human privately and then merge the caller in (private warm transfer), or stay on the line as a third participant after the human joins (conferenced warm transfer).
Handoff matters because the AI agent already has the full conversation context: who the caller is, what they want, what's been tried, what comes next. A handoff that throws away that context forces the human to start over. A handoff that preserves it lets the conversation continue without the caller repeating themselves.
A voice AI agent transfers a call to a human at the moment its job ends and a human's job begins. That moment varies by use case:
Related articles
The shared pattern: the AI owns the front of the call, captures structured context, then transfers to a human at the right moment with that context preserved. Cold transfer breaks the pattern. Warm transfer keeps it intact.
The transfer trigger lives in the assistant's instructions, which decide when based on the conversation. The transfer mechanism handles what happens next.
Three patterns cover most voice AI handoff workflows.
The agent ends its part of the call and routes the caller to a new number or SIP URI. The human picks up cold and asks the caller what they need. This is the default behavior in most voice agent platforms because it maps to standard SIP REFER call control. Useful when context handoff isn't required, such as a generic IVR routing call to the right department.
The agent dials the human first, summarizes the conversation, then bridges the caller in. The human starts the conversation already briefed. This requires the agent to call out, hold the original caller, speak to the new participant, and then merge the call. Few voice agent products ship this as a built-in capability. Telnyx supports it via Voice API call control composition (Dial plus Bridge).
The agent invites the human into the live call as a third participant. All three parties can speak. The agent stays present, defers during human-to-human conversation, and resumes when addressed. The agent continues to use every tool it had configured before the human joined.
Telnyx's Multi-Participant Voice AI Calls feature ships conferenced warm transfer (Pattern C) as a built-in capability. Two tools handle it: Invite and Skip Turn.
The assistant calls the Invite tool during a live conversation, passing the participant's phone number or SIP URI. Telnyx dials the participant and brings them into the existing call as a new party. Once the participant joins, the assistant receives updated conversation context and continues the call with all parties.
Every tool the assistant had configured before the join continues to work. Calendar lookups, CRM updates, custom webhooks, transcription, all of it. There is no separate multi-participant configuration surface. Full setup is in the Multi-Participant Calls dev guide.
For Pattern A (cold transfer), Telnyx exposes the Voice API Transfer command and the SIP REFER command (per SIP REFER RFC 3515). For Pattern B (private warm transfer), the Bridge command handles the merge. These run at the call control layer, separate from the AI Assistant runtime, and require orchestration outside the assistant.
| Pattern | Telnyx mechanism | Where it runs |
|---|---|---|
| Cold transfer | Voice API: Transfer or SIP REFER | Call control layer |
| Private warm transfer | Voice API composition: Dial + Bridge | Call control layer |
| Conferenced warm transfer | AI Assistants: Invite + Skip Turn | AI Assistant runtime |
Most voice AI agents end their part of the call when they transfer. Telnyx voice AI agents can stay on the line if needed.
After the human joins, the assistant can keep working. With the Skip Turn tool, it stays silent during human-to-human conversation. With the Invite tool active, every other configured tool stays available. The result is a multi-party call where the AI listens and acts in the background while the humans handle the conversation in the foreground.
The assistant updates structured systems as the humans agree on next steps. A support specialist confirms a resolution to a customer. The assistant logs the resolution in the CRM, attaches the call transcript, and schedules the follow-up. None of that requires the specialist to break stride.
When either human addresses the assistant directly ("Amber, look up that account again," "Pull up the pricing sheet"), it responds. When humans are talking to each other, it stays out of the way. Skip Turn does not end the call or disable the assistant; it tells the assistant not to speak for that turn.
This turns warm transfer from a one-time handoff into a continuous workflow. The human takes over the conversation. The assistant takes over the systems work.
The strongest voice AI agents for handoff today share three characteristics.
First, they preserve conversation context across the transfer. The human picks up briefed, not cold. Whether through a transcript, a structured summary, or a voice introduction by the AI, the caller does not have to repeat themselves.
Second, they support multiple transfer patterns. A single platform that does only cold transfer (Pattern A) leaves Pattern B and C workflows on the table. Platforms that cover all three patterns can handle a wider range of workflows, even if the mechanism differs per pattern.
Third, they keep the AI useful after the handoff. An AI that drops off the call after transfer is half a worker. An AI that stays on, listens, and continues to update records or take instructions during the human-to-human conversation is a full one.
Telnyx voice AI agents with the Multi-Participant Voice AI Calls feature meet all three criteria. Among major voice AI platforms with public documentation, Telnyx is the only one that ships conferenced warm transfer as a built-in AI Assistant feature, where the AI stays on the line during the human-to-human conversation and continues using its tools.
Vapi, Retell, Bland, and ElevenLabs all support cold transfer through their call control layers, typically via SIP REFER or a transfer-call function. Some handle warm transfer flows through call control orchestration outside the assistant. Conferenced warm transfer with the AI staying on the line as a built-in AI Assistant feature is less commonly available today.
For the technical detail on how the AI stays on the line during multi-party calls (speaker awareness and the Skip Turn tool), see the companion piece, Multi-participant voice AI: speaker awareness on group calls.
Five practices carry across handoff workflows.
Trigger handoff at the right moment. Define the conditions in the assistant instructions. "Hand off when the customer requests a manager," "Hand off when the issue requires policy adjustment," "Hand off when the caller crosses qualification threshold X." Not "Hand off when the AI gets confused."
Pass structured context, not free-form notes. The human picks up a one-line briefing or a structured handoff card with the fields that matter (account ID, request type, what's been tried, customer sentiment). Free-form summaries waste the human's first 30 seconds.
Choose the transfer pattern by use case. Cold transfer for IVR routing or department changes where context isn't critical. Warm transfer with introduction for specialist escalation where the context shapes what the human says. Conferenced warm transfer for workflows where the AI continues to be useful (note-taking, CRM updates, follow-up scheduling).
Use Skip Turn explicitly when the AI stays on the line. Without it, the assistant interrupts the human-to-human conversation. Add Skip Turn to the assistant's tool list and instruct it to defer when participants are addressing each other rather than the AI.
Review handoff calls in conversation history. Multi-participant calls are the hardest to debug. Inspecting the transcript, audio, and tool calls reveals where the assistant interrupted, where it stayed silent when it should have spoken, and where the briefing landed.
Each pattern below assumes the agent owns the front of the call, calls Invite at the right moment, briefs the human, then stays on the line to keep doing systems work while the humans handle the conversation.
A prospect calls in. The agent qualifies against the ICP criteria, captures budget and timeline, and decides whether the lead is sales-qualified.
If yes, it calls Invite with the on-call AE's number. The AE picks up to a one-line briefing ("Series B SaaS, 200 employees, evaluating voice AI vendors, ready to pilot in Q3") and takes the call.
The assistant stays on the line. While the AE leads, the assistant logs qualification fields in Salesforce, books the next meeting on the AE's calendar, and emails a call summary when the call ends.
A customer calls about a billing issue. The agent confirms the account, walks through the standard troubleshooting, and concludes the issue requires a billing specialist.
It calls Invite with the specialist's queue, summarizes the call ("account #12345, three failed charges since Tuesday, customer has confirmed the card is valid, needs manual review"), then stays on.
While the specialist works the case, the assistant updates the ticket in real time, attaches the transcript, and schedules the customer satisfaction survey for the next morning.
A patient calls with symptoms. The agent runs the triage script, captures the chief complaint and any vitals from a connected device, and decides whether the case needs a nurse or a doctor.
It calls Invite with the on-call clinician and briefs them ("48-year-old, history of hypertension, reporting chest tightness for 30 minutes, no prior cardiac history"), then stays on the line.
The assistant takes structured clinical notes during the consultation and pushes the encounter to the EHR when the call ends, saving the clinician documentation time.
A prospect requests an auto insurance quote. The agent collects the required information (vehicle, drivers, current coverage, prior claims) and runs the eligibility check.
If eligible, it calls Invite with the next available licensed agent and hands off the structured lead. Per the NAIC Producer Licensing Model Act, licensed humans must bind policies, so warm transfer is the only legal way to convert these leads in real time.
The assistant stays on, logs the quoted premiums, and triggers the policy-issuance workflow once the licensed agent confirms binding.
An employee calls the helpdesk about a VPN issue. The agent runs the L1 script (restart, credential check, network reachability), determines it's an authentication-server issue, and calls Invite with the L2 on-call.
The L2 picks up to a full transcript pushed into the ticketing system at the same time, plus a one-line spoken briefing.
The assistant stays on the line and updates the ticket with each step the L2 takes, keeping the employee's record current without manual input from L2.
These patterns share a common shape. The agent owns the front of the call, captures structured context, then transfers to a human at the right moment with that context preserved. After the handoff, the agent stays on the line and does the systems work the human would otherwise do manually after the call.
Add an Invite tool to your assistant with the target phone number or SIP URI. Update the assistant instructions to describe when to call Invite, what to say in the introduction, and what to do after the handoff. Add a Skip Turn tool if you want the conferenced pattern (the assistant stays on the line and defers to the human-to-human conversation).
Full setup is in the Multi-Participant Calls dev guide. New to voice AI agents? Start with the Voice Assistant Quickstart.
Most voice AI platforms support some form of cold transfer (the AI ends its part of the call and routes the caller to a new line). Fewer support warm transfer with introduction or conferenced warm transfer where the AI stays on the line. Telnyx ships conferenced warm transfer as a turnkey primitive in its Multi-Participant Voice AI Calls feature.
Yes, on Telnyx. The Invite tool brings the human into the live call as a third participant; the Skip Turn tool keeps the AI silent during human-to-human conversation. The AI listens, defers to the humans, and steps back in when one of them addresses it. It can continue using every tool it had before the handoff.
Cold transfer routes the caller to a new line with no introduction or context. The human picks up cold. Warm transfer keeps context intact: the AI either briefs the human before merging the caller in (private warm transfer) or invites the human into the live call as a third participant (conferenced warm transfer). For voice AI specifically, warm transfer matters because the AI already has full conversation context.
Telnyx supports it via Voice API call control composition: the Dial command originates a new leg, the AI briefs the human on that leg, then the Bridge command merges the caller in. This is achievable but not a single primitive in the AI Assistant runtime. The native turnkey pattern for warm transfer with the AI involved is conferenced warm transfer using Invite plus Skip Turn.
In a conferenced warm transfer (Pattern C), every tool the assistant had configured before the human joined continues to work. Calendar lookups, CRM updates, custom webhooks, transcription, all available. The assistant uses them in the background while the humans handle the conversation in the foreground.
Add an Invite tool with the target phone number or SIP URI. Add a Skip Turn tool if you want the assistant to stay on the line and defer during human-to-human conversation. Update the assistant instructions to describe when to call Invite and what to do after the handoff. Full setup is in the Multi-Participant Calls dev guide.
Add the Invite tool (and optionally Skip Turn) to your assistant in the Telnyx Mission Control Portal, or follow the Multi-Participant Calls developer guide.
Working on an enterprise implementation and need a personal walkthrough? Talk to sales.
