'Can I talk to a person?' — handled, every time.
The moment a caller asks for a human, the agent stops selling and starts handing over. Staff available? Warm transfer with the context attached. Nobody around? The agent takes the caller's email, confirms it back, and emails the team a full brief.
The handoff is the make-or-break moment of any AI phone agent. A caller who has to repeat themselves — or worse, lands back in a menu — will not call back. This demo shows the two exit paths we wire for every voice deployment: the warm transfer and the email-capture fallback.
Every step is sample data — the in-browser sandbox below is offline and produces no real calls or emails. Wiring the live workflow needs telephony, an on-call rota and consent records configured up-front.
What triggers this workflow
Mid-call, the caller says something like 'speak to a person', 'can I talk to someone?', or the agent detects frustration — the handoff workflow takes over from there.
Source: Twilio voice stream / live call
Workflow steps
- Twilio voice + n8nAnswer & listenThe AI voice agent answers on the first ring and follows the approved call script.
- n8n workflowDetect handoffThe request-for-human phrase (or frustration signal) is detected and the automation pauses.
- Twenty CRM + ChatwootCheck who's onThe on-call rota is checked for an available team member right now.
- Twilio voiceWarm transferAvailable: the agent briefs the team member first — caller name, number, intent, what was already tried — then bridges the call.
- Twilio voiceEmail-capture fallbackNobody available: the agent asks for the caller's email, reads it back to confirm, and promises a same-day reply.
- Listmonk + ChatwootNotify the teamAn internal email with the call summary lands in the team's inbox, and a callback task is created.
- Twenty CRMLog the callThe contact, call outcome and handoff reason are written back to the CRM.
Tools used
Human handoff
Handoff is the feature, not the failure
Asking for a person is a success signal for the workflow, not a breakdown. The agent never argues, never hides the option, and never leaves the caller stranded — it transfers, captures, or books a callback, and the human picks up with full context.
- Caller explicitly asks to speak with a person at any point
- Frustration or repeated 'I don't understand' detected in the caller's tone
- Topic is outside the approved script (complaints, legal, medical advice)
- Two consecutive failed attempts to answer the caller's question
- Caller mentions an emergency — routed straight to the on-call line, no email loop
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Handoff detected mid-call
Caller Helen Marsh triggered handoff ("Speaks to a human"). Automation paused — the agent's only job now is a clean handover.
- Caller
- Helen Marsh
- Handoff reason
- Speaks to a human
- On-call check
- Yes — Sam is on call
- Call summary
- Asked about a quote for a full exterior repaint of a weatherboard house in Bentleigh.
- Logged
- Fri, 2 Oct, 2:44 am
2. Branch handling
Warm transfer: the agent briefed the team member BEFORE bridging the call, so the caller never repeats themselves.
Warm-transfer brief — caller: Helen Marsh. Reason: Speaks to a human. Summary: Asked about a quote for a full exterior repaint of a weatherboard house in Bentleigh. AI-generated interpretations in this brief are labelled; please confirm facts with the caller.
Agent (to team): "Helen Marsh is on the line, asking for a person — reason: speaks to a human. Summary: Asked about a quote for a full exterior repaint of a weatherboard house in Bentleigh. Bridging now."
Call bridged. Transcript and outcome write back to the CRM when the call ends.
3. Call log
Call closed. Caller: Helen Marsh. Outcome: warm-transfer. Reason: Speaks to a human. Summary and transcript archived against the contact record.
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
n8n workflow template
n8n template — LGM 09 Live-Call Human Handoff (SIMULATED, inactive). Ships with active: false — no live integrations are wired. See the setup section below for the wiring checklist, and download the JSON to inspect or import it.
Setup for production
Wiring it for production
Live deployment needs telephony, an on-call rota, and the handoff rules agreed in writing before any real call is answered.
- Provision a Twilio number with voice and call-transfer (conference or <Dial>) capability in the business's Australian region.
- Write the approved call script — including the exact phrases that trigger handoff and the topics that always escalate.
- Maintain the on-call rota in Twenty CRM (or your CRM of choice) so the agent knows who to try first, second, and last.
- Connect Listmonk (or your email provider) for the internal notification, and Chatwoot for the callback task.
- Record the caller's consent for AI-handled calls in the opening message, per Australian telemarketing and consent guidance.
- Test all four branches — transfer, email capture, callback, frustration — with real phones before going live.
Production prerequisites
- Twilio number with voice + transfer enabled (AU)
- On-call rota maintained somewhere the workflow can read it
- Handoff rules agreed in writing (triggers, order of escalation, emergency path)
- Caller consent wording approved before the first live call
- A human in the loop — no live call ships without a named person on the rota
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
What if nobody is available when the caller asks for a person?
The agent falls back to email capture: it asks for the caller's email, reads it back to confirm the spelling, then emails the team a full brief — caller name, number, what the call was about — and opens a callback task. The caller is never sent back to a menu.
Does the team member get any context on a transferred call?
Yes — that's the point of a warm transfer. Before bridging, the agent sends the team member the caller's name, number, intent, and what was already tried, so the caller never has to repeat themselves. AI-generated interpretations are labelled as such, not presented as caller-confirmed facts.
Can the agent refuse to hand off and keep trying to handle the call?
No. The handoff triggers are hard rules, not suggestions. Once a caller asks for a person (or the frustration threshold trips), the automation pauses and the human path takes over — the agent's job from that point is a clean handover, not a save.
More demos you can run in your browser
Live-Call Human Handoff across the platform
Want this live-call human handoff workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.