It's a fair question to ask before adopting any AI system that talks to your customers: what happens the moment it hits something it genuinely can't handle? A vague answer here — "don't worry, it's smart enough" — should make you more skeptical, not less. Here's the specific, honest version for AIVA.
The short answer
It hands off to a person, and it takes the conversation with it. The customer doesn't get dropped, doesn't get a dead transfer, and doesn't have to start over and explain their situation from scratch to whoever picks up next. That last part is the one buyers should actually pressure-test in a demo, because it's the difference between a real handoff and a system just giving up.
What actually triggers a handoff
Three categories, consistently: genuine emotional distress — a customer who's frustrated or upset, not just asking a hard question; anything involving compliance, legal, billing disputes, or account security, where a documented human decision matters; and, most simply, a customer explicitly asking for a person. Any of these routes to a human immediately, regardless of whether the underlying question was technically something the system could have answered. We've written separately about the fuller logic behind these specific triggers, if you want the deeper reasoning — this piece stays focused on what it means for you as a buyer deciding whether to trust it.
What a bad handoff looks like, versus a real one
It's worth being concrete about this, because "handoff" gets used loosely across the category and the gap between a good one and a bad one is enormous in practice. A bad handoff sounds like a dead transfer — dial tone, then a generic "please hold," then a human who opens with "hi, how can I help you today?" as if the previous three minutes never happened. The customer has to explain their entire situation a second time, often while already annoyed that they needed a person in the first place. A real handoff sounds different: the person picking up already knows the caller was asking about a delayed refund, has already read what was tried, and opens with something closer to "I see you're asking about the refund on order 4521 — let me take it from here." Same underlying event. Completely different experience for the customer standing on the other end of it.
Why a bad handoff is worse than no handoff at all
There's a reason this deserves real scrutiny before you buy rather than after: a customer who reaches a dead-end bot at least knows immediately that they're talking to a machine, and can hang up and call again asking for a person directly. A customer funneled through a "handoff" that drops all context and dumps them on a human who has to ask "sorry, what's this regarding?" has now had two bad experiences back to back — the failed automated attempt, and then a human interaction that felt exactly as disconnected as the automated one. A handoff done badly doesn't just fail to fix the original problem; it actively makes the customer's opinion of your business worse than if the call had simply rung through to a person from the start. This isn't just a hunch — widely cited customer-loyalty research has found that how much effort a customer has to spend getting an issue resolved, including repeating themselves to someone new, predicts whether they come back far more reliably than how impressed they were by any single interaction.
What "full context" actually means
This phrase gets used loosely across the category, so it's worth being specific. It doesn't mean the human just sees that a call is being transferred. It means they get the conversation so far — what the customer asked, what's already been tried or answered, and why the handoff happened. The practical effect: the person picking up starts from where the conversation already is, not from "hi, how can I help," which for a customer who's already explained their issue once is often the single most frustrating phrase they can hear.
Who actually receives the call
A detail worth stating plainly because it's easy to assume otherwise: the person who picks up is on your own team, not a call center AIVA operates on your behalf. That matters for a buyer for a simple reason — the escalation only works if the person receiving it can actually do something about the issue, which means it needs to reach someone who works for your business and knows it, not a generic third-party agent reading from a script of their own.
What this looks like across channels
On a phone call, the conversation routes to a person on your team, carrying the context of the call so far. In web chat, the same handoff logic applies — the visitor doesn't need to retype what they've already said. Over SMS, a conversation that needs a person gets flagged and routed the same way, since SMS threads are just as visible to your team as any other channel. The mechanism is consistent across all three; what differs is just the shape of the channel itself.
When you're evaluating any AI receptionist, ask to see an actual handoff happen in the demo — not hear it described. Ask specifically what the human receiving it sees. That single test tells you more than a features page will.
Can you tune how quickly it escalates?
Yes, and it's worth asking any vendor whether that's actually configurable or fixed at one setting. A lending platform and a salon have very different thresholds for what counts as urgent enough to need a person immediately, and escalation sensitivity should match your specific business rather than ship as one setting applied identically to every account. If a vendor's answer to "can we adjust this" is no, that's a real limitation worth knowing before you commit, not after your first difficult call shows you the gap.
The honest gap worth asking about directly
Here's a question worth putting to any vendor, including us, before you sign anything: what happens to an escalated call outside your team's working hours, if nobody's actually available to pick it up? This isn't a hypothetical edge case — a customer with an urgent, genuinely distressing issue doesn't necessarily call during business hours, and a vague answer to this specific question is worth noticing. It's exactly the kind of detail that separates a vendor being straightforward with you from one hoping you don't ask.
Why this matters more than resolution rate alone
It's tempting to judge a system purely by how much it resolves without a human — and resolution rate is a real, useful number, visible in real time on AIVA's dashboard and running 82–96% across customers depending on the business. But it's an incomplete picture on its own. A system that hits a high resolution number by refusing to escalate genuinely difficult calls isn't actually better — it's just quietly failing the customers who needed a person most, in a way that doesn't show up in the metric. The number worth asking about alongside resolution rate is what happens on the calls that don't resolve automatically.
If you want to see the reasoning in more depth
We've written in detail elsewhere about one specific call that reshaped how we think about escalation — a case where nothing on paper looked wrong, and a human reviewer caught something a transcript alone couldn't show. It's worth reading if you want to understand the philosophy behind the trigger list, beyond just the buyer-facing summary here.
What to ask before you buy
Ask any vendor, AIVA included: what specifically triggers a handoff, what does the receiving human actually see, who is that human, what happens outside business hours, and can you watch a handoff happen live rather than take it on description. If the answers are vague, that's the answer. See how escalation actually works, compare it against the broader list of questions worth asking any AI receptionist vendor, or book a demo and test a handoff yourself, or start free with ₹500 in credit and try it on your own number before you commit to anything.