Voice AI is changing the customer service conversation, but enterprises still need to be careful about how they measure success.
Contact centers have long used deflection as a simple way to understand the value of automation. If fewer calls reach human agents, the logic goes, the operation becomes more efficient as costs fall and queues shrink.
That logic is understandable, but it is also incomplete.
According to Dmitry Timofeev, Director of Product at Parloa, deflection became popular because customer service has often been viewed through a cost lens, an “attractive trap” for leaders.
“It became a very common measure of success because historically customer service contact centers have been a cost center, and they've been treated as a cost center. Deflection directly maps to cost savings.”
The danger in this approach is that the contact center optimizes for the wrong thing. A voice AI agent might answer instantly and reduce the number of calls that reach live agents. But none of that proves the customer’s issue has been resolved.
Why Deflection Is Too Narrow for Voice AI
In voice channels, customers often call because they have a specific, urgent, or complex issue. If the AI agent only blocks the path to a human agent, or repeats basic information without resolving the problem, the experience can deteriorate quickly.
“The best way to ensure a hundred percent deflection is to simply hang up on a call without solving the customer problem. Then every single call will be deflected, but what you will have is a lot of angry customers who want to have nothing to do with your company anymore.”
Deflection only tells part of the story. It does not show whether the customer received the right answer, understood the next step, avoided repetition, or reached a human agent with enough context for the issue to move forward.
Timofeev argued that success needs to be defined from the customer’s perspective.
“Every time we talk about customer support, what good looks like, you need to define it from the consumer perspective. Ideally, the person who is calling wants to get their problem solved painlessly and quickly, and that is more than just a deflected call.”
This is why voice AI should be measured by resolution, Timofeev explained.
“Companies who are incentivized on deflection will optimize for deflection at the expense of everything else, including at the expense of the customer experience, which is what you actually want to drive.”
That point is becoming more important as voice AI adoption accelerates.
The Real Test Is Resolution
Customers are beginning to experience AI agents that connect quickly and manage more useful conversations than older IVR systems. That raises expectations across other brands and service environments.
Timofeev argued that this presents an opportunity, rather than simply a cost to be reduced.
“Every customer problem is an opportunity to invest into a customer relationship and make it better.”
That shifts the role of voice AI. Rather than acting as a barrier between the customer and the contact center, voice AI should help move the customer towards a useful outcome. It should identify intent, manage the right journeys, complete suitable tasks, and escalate when the situation requires human support.
Service teams should aim “to get customers instantly connected with an AI agent instead of hanging in the queue for a long time,” Timofeev explained. “And they want to make sure that the AI agent is able to solve as many problems as possible, starting from the simpler ones and highest volume ones, but then going further up and up and up into complexity.”
Escalation Quality Matters
This is where measurement needs to evolve. Deflection can still have a place, but it should not sit alone. Voice AI should also be judged by resolution rate, escalation quality, customer effort, sentiment, repetition, and the impact on human agents.
AI agents will not solve every issue. Some conversations need a human agent because the case is sensitive, complex, unusual, or outside the AI agent’s configured scope.
“AI agents generally can only resolve the issues that they are configured for,” Timofeev said. “So, there will always be room for bringing a human agent into the conversation.”
A handover is not a failure in itself, but the problem comes when the handover is poor.