The Platform PM

Deep dive: voice agents vs people

Field Guide

Voice AI: real-time voice agents

08

Deep dive: voice agents vs people

3 min read · Chapter 8 of 10

Voice agents vs human agents: what's real

My view as of October 2026: a voice agent is cheap and fast enough for most inbound calls, and still fails too many tasks to replace the people behind it. The independent evidence on task success is recent and sobering, deployment numbers are almost all vendor-reported, and the public pull-backs came from quality and measurement more than from regulators.

What the benchmarks say

  • Task success: τ-Voice (278 tasks in airline, retail and telecom service, published in March 2026 and accepted at ICML) tested speech-to-speech agents on clean audio and on realistic audio with noise, 8 kHz phone quality, dropped packets and varied accents. The best completed about 30-50% of tasks on clean audio and 26-38% on realistic audio, against 85% for a text model. No chained stack was tested.
  • Who did best: in the paper, xAI's and OpenAI's agents led (51% and 49% on clean audio) and Google's trailed (31%); in Artificial Analysis's June 2026 index, xAI's Grok scored 52% on the same benchmark and OpenAI's top model at high reasoning 40%. Rankings move with each model version, so I'd test the current ones myself.
  • The vendors' own claims: OpenAI reports GPT-Live-1 at 86% on a benchmark it calls "Tau3 Voice", up from 46% for its previous model, a figure I saw only in press coverage.

What deployments report

  • Utilities: PG&E's line, run by PolyAI, contains 67% of calls, which PolyAI's own page says is 6 points above the old phone menu, and saves 35,000 agent hours.
  • Energy: Parloa says it resolves up to half of E.ON's inbound calls.
  • Customers: Gartner's survey of 5,728 customers found only 14% of service issues fully resolved through self-service, and 64% would prefer companies not use AI for service. Qualtrics found AI customer service fails at almost four times the rate of other AI uses, though neither survey is about voice alone.

Every named deployment figure is the vendor's own, none is audited, and containment, resolution and routing accuracy are different metrics. PG&E's case is the one I'd show a skeptic, because it says what the old phone menu already achieved.

Who pulled back

  • McDonald's ended its IBM drive-thru test in July 2024 after accuracy estimated in the low-to-mid 80s, with accents a reported problem.
  • Taco Bell said in August 2025 that it was rethinking where to use voice AI in its drive-thrus, after prank orders and trouble at peak times.
  • Commonwealth Bank of Australia reversed 45 job cuts in August 2025 when the union showed call volumes were rising.
  • Klarna, in chat, said in May 2025 that its cost focus had produced "lower quality" and began hiring people again.

Gartner predicted in June 2025 that half the companies planning big service headcount cuts because of AI would abandon those plans by 2027. In January 2026 it predicted, in a release I could see only by its title and press coverage, that generative AI's cost per resolution will exceed offshore human agents' by 2030. How a support organization changes around agents, beyond shrinking, is in Becoming AI native.

What containment is worth

The arithmetic in How the money moves makes reliability the bigger lever by roughly five to ten times. Containment also flatters: a caller who hangs up angry counts as contained, and the FTC sued a company in August 2025 for claiming its AI phone agent could replace sales staff. Disclosure cuts the other way on outbound sales, with the 2019 experiment's drop of more than 79.7% in purchases once callers knew. For inbound service, where Maine and the EU now require disclosure, I haven't seen data on its cost.

Questions to ask a vendor

  1. Of the calls your agent handled for customers like us last quarter, what share was resolved, as opposed to merely not transferred, and who checked?
  2. What's the mouth-to-ear turn gap at the 95th percentile on real phone calls, end-of-turn time included?
  3. How do you test with noise, accents, 8 kHz audio and callers who interrupt, and will you run our own scenarios?
  4. When the agent hands off, what does the human see, and what happens if nobody answers?
  5. Do you or your model providers retain or train on our call audio, and can we turn that off in writing?