Glossary

Human handoff (AI to human escalation)

Human handoff is the point where an AI agent stops handling a conversation alone and passes it to a person on the support team. A good handoff fires on clear triggers, carries the history and order details with it, and tells the customer what happens next, so they never have to explain the problem twice.

Last updated: 19 November 2026 · By

Fyncall wrote this page. Fyncall details link to our product pages or docs. The claim about WhatsApp links to Meta's developer documentation, checked 19 November 2026.

What is a human handoff?

A human handoff, also called AI to human escalation or live agent transfer, is when an AI agent flags a conversation for a person to take over. The person then decides whether to answer it themselves or let the AI keep handling simple follow-ups.

Handoff design covers three questions:

  • When does the AI hand over?
  • What does the person receive?
  • What does the customer hear while they wait?

It is the counterpart to ticket deflection. An AI agent resolves what it can, and handoff makes sure the rest reaches a person rather than ending in a loop of unhelpful replies.

What triggers a handoff to a human?

A handoff should trigger when carrying on with the AI would cost more trust than it saves time. The usual triggers are a direct request for a person, signs of frustration, repeated failed answers, a high-value customer and a sensitive topic.

Fyncall's AI Escalation settings offer five triggers:

TriggerWhat it detectsSetting
Explicit Human RequestThe customer asks for a personOn or off
Customer Frustration DetectionFrustration, using sentiment analysisThreshold of 2, 3, 4 or 5 negative indicators
Query ComplexityThe AI has failed to resolve the question1 to 5 failed attempts
VIP Customer PrioritizationHigh-value customers, when another trigger firesOn or off
Sensitive Topic DetectionLegal mentions and complaintsOn or off

Escalation rules are included on Fyncall's Free plan, and SLA ticketing is on Pro, as shown on the pricing page. Some situations are not covered by a generic trigger, such as an address change on an order that has already shipped. Write those into the agent's instructions so the AI knows to escalate.

What context should pass to the human agent?

The person picking up a handoff should get enough to reply without asking anything the customer has already answered: the full conversation, a short summary, the customer's order details and what the AI already tried.

In Fyncall, your team gets the conversation with a short summary, as described on the AI support agent page. When the AI creates or enriches a ticket, the tickets docs describe an AI Context card with:

  • Trigger type: what caused the escalation.
  • Detected intent and confidence level: what the customer wanted and how sure the AI is.
  • Sentiment: the customer's mood at the time of escalation.
  • Actions the AI took: the steps it performed before handing off.
  • Suggested resolution: the AI's recommended next step.

Escalated conversations land in the Needs Agent queue, which the inbox overview describes as “conversations waiting for a human agent (AI escalated)”. AI Copilot, which the pricing page lists as Pro only, can draft replies and look up orders for the person who picks it up, as the AI support agent page describes.

What do customers expect during a handoff?

Customers expect to reach a person when they ask for one, to be told honestly that they are waiting, and not to repeat themselves. Silence after “I'll connect you” is an easy way for a handoff to go wrong. The Fyncall settings below are described in the AI Escalation docs.

  • A clear message. Fyncall lets you write a custom escalation message in place of the default. “I've passed this to the team with your order details” sets a better expectation than a generic line.
  • Help while waiting. According to the inbox overview, “even after escalation, the AI keeps helping the customer while waiting for an agent.”
  • A plan if nobody answers. Fyncall's escalation timeout can be 2, 3, 5, 10, 15 or 30 minutes, with up to 5 follow-up messages and an optional offer to create a ticket.
  • Honesty out of hours. With working hours on, you can suggest a ticket, create one automatically, and add an outside hours message saying when the team is back.

Channel rules matter too. On WhatsApp, Meta's Cloud API documentation says a 24-hour customer service window starts when the customer messages or calls you, and that “when the window closes, you can only send pre-approved template messages.” A handoff raised late at night should be first in the morning queue. See the WhatsApp 24-hour window for more.

How do you hand a conversation back to the AI?

Once the issue is settled, the person releases the conversation so the AI can answer the next routine question. Fyncall has three controls, described in the managing conversations docs:

ActionWhat happensDoes the AI reply?
ClaimAssigns the conversation to youYes, the AI keeps responding
Take OverAssigns it to you and moves it to human handling. On web chat, the customer sees that a person has joinedNo, until released
Release to AIRemoves you as the assigned agent. Only the assigned agent or an admin can releaseYes, it resumes

How do you reduce unnecessary handoffs?

Read each week's escalations and sort them: the AI lacked an answer, a trigger fired too early, or the handoff was right. Fill gaps in the knowledge base, loosen one trigger setting at a time, and leave the right handoffs alone.

For a full walkthrough with order situations and a setup checklist, read our post on Shopify AI agent handoff.

Common questions

Is human handoff the same as escalation?

Mostly, yes. Escalation usually means the trigger that flags a conversation, and handoff the whole transfer, including what the person receives and what the customer is told.

Should customers always be able to reach a person?

It is good practice for a direct request to always work. In Fyncall, that is the Explicit Human Request trigger, which you can keep switched on.

Does the AI stop replying after a handoff?

Not by default. In Fyncall the AI keeps helping while the customer waits, and keeps responding if a person claims the conversation. It stops only when someone uses Take Over, until they release it.

Which queue do escalated conversations go to in Fyncall?

They go to the Needs Agent queue, where a teammate can claim them or take them over. You can see how it fits the wider inbox in our shared inbox entry.

Ready to try Fyncall?

Install it tonight, let the AI draft your first replies, and switch it on one channel at a time as you start to trust it.

  • Free plan, no credit card
  • 14-day free trial on Pro
  • Unlimited human replies on every plan