AI Cost CalculatorThe economics of a good AI support handoff
How AI support handoffs affect resolution cost and agent time, with practical ways to measure context transfer and escalation quality.
A support bot can boost its deflection rate just by making it hard to reach a human. The dashboard looks better while customers get more annoyed. Eventually they reach a person anyway - with a longer story, less patience, more frustration, and no faith that anyone's been listening.
Handing off to a person isn't automation failing. It's part of the service, and it has its own economics.
Measure what happens after the handoff
Track how long the agent spends re-asking for information and undoing the bot's wrong guesses. Compare that against tickets that came straight to the team. A handoff with a good summary and verified account details can make the human part faster. A wall of raw chat log can make it slower.
And check whether it's actually sorted on that first human contact. A quick handoff that just leads to another transfer isn't a cheap resolution.
Pass evidence, not a confident guess
The agent picking it up needs the customer's goal, what's already been tried, the relevant account facts, and why the bot gave up. And it should keep what the customer said separate from what the bot guessed - a confident but wrong diagnosis sends the human down the same dead end.
For structured tasks, pass each field with where it came from and how sure the bot is. For open chats, give a short summary plus the full transcript on hand. The agent shouldn't have to read everything, but should be able to check the one detail that matters.
Hand off before the chat gets expensive
Repeated failed answers burn model calls and goodwill at the same time. Set triggers for requests outside policy, shaky lookups, actions the bot can't perform, and clear signs of frustration. One earlier handoff can cost less than four failed attempts to recover.
And be upfront about availability. If the human queue is closed, say what happens next and keep the case. Pretending an instant handoff exists just sets up a second letdown.
Count "contained" and "resolved" separately
A contained chat is one the bot finished without a person. A resolved chat is one where the customer's problem is actually fixed. They overlap, but they're not the same thing. Take a sample of "contained" chats and check for repeat contacts, low ratings, reopened tickets or people who just gave up.
Then work out cost per resolved chat across the whole system - bot-only wins and handoffs together. That keeps you improving the customer's outcome, not one channel's flattering stat.
Let the human improve the next handoff
When a case closes, grab one quick signal from the person who took it over. A one-click rating shows whether the needed details arrived; an optional note catches the odd cases. Over time that quietly exposes missing account data, badly-timed handoffs, vague summaries and gaps in the help docs - without turning every ticket into a survey.
The best handoff saves the customer from repeating their story and saves the agent from piecing it back together. That's worth measuring even when the bot's deflection number doesn't budge an inch.