Resolution, not deflection: rethinking the support metric that matters
Most support automation is measured by containment — the share of conversations that never reach a human. It's an easy number to move and a dangerous one to chase. A chatbot that stonewalls a frustrated customer until they give up "contains" the ticket just as well as one that actually solves the problem. The metric can't tell the difference.
We built Symphia around a different question: did the customer's problem get resolved?
Why containment misleads
Containment optimizes for absence — the absence of a human, the absence of a follow-up. But absence isn't success. When you reward a system for deflection, you get a system that's very good at ending conversations and very bad at ending problems. The costs show up later and off-dashboard: repeat contacts, churn, one-star reviews, and the slow erosion of trust that no containment chart will ever surface.
The deeper issue is that deflection and resolution look identical in the short term. Both close the ticket. Only one of them keeps the customer.
What we measure instead
Symphia optimizes for resolution rate — the share of conversations where the customer's underlying goal was actually accomplished. That's a harder thing to measure, and the difficulty is the point. It forces three things to be true:
- The agent has to understand the goal, not just match an intent.
- The agent has to be able to take an action — issue the refund, change the booking, update the address — not just describe how.
- You have to be able to tell afterward whether it worked.
That last requirement is why resolution and observability are the same project. If you can't see what happened, you can't claim it resolved.
How agents should behave when they can't resolve
An honest resolution metric changes agent behavior at the edges. When Symphia can't resolve something — missing permission, ambiguous request, a genuinely human judgment call — the right move is a warm handoff, with full context, not a dead end. A handoff isn't a failure of the metric; a silent handoff is. The worst outcome is the customer repeating themselves to a human who has none of the history.
The operating loop
Optimizing for resolution turns support into a feedback loop instead of a cost center:
- The agent attempts a resolution and takes real actions.
- Every conversation is graded — resolved, partially resolved, escalated.
- The failures cluster. Those clusters are your roadmap.
Deflection hides that roadmap. Resolution hands it to you.
If you're evaluating agent platforms, ask the vendor how they measure success. If the answer is containment, you're buying a system optimized to make customers go away. Ask for resolution instead — and ask how you'd know. That's the bar we hold the platform to.