Back to VAmoS Pro Bench
November 5, 2026

Voice agents can't spell your name

Joshua Meyer

Let's imagine that your name is Camila Kowalski and you have to call customer support. The person who answers isn't sure whether your name starts with a C or a K, and so they ask you to spell it before they type it into their computer. Anybody working in customer support will do this; it's not in the training manual, it's just common sense.

We expect voice agents to be able to do it too, but we found out that they don't. This blog post talks about the problem and also how the newest VAmoS candidate - Dialt - does on it.

Putting voice agents to the test

We ran nineteen voice agents through VAmoS Pro Bench, our benchmark of simulated customer calls to a utility company. Every agent gets the same calls, from the same simulated callers. Before the agent can open account info, it has to verify the caller with (among other things) the customer's name.

All of the agents had access to the same traditional disambiguator for names: Soundex, an old phonetic code that ignores vowels and doubled letters, so “Hadad” passes for Haddad. But it keeps the first letter as written, so “Kamila” does not pass for Camila. Nevertheless, agents still manage to get your name wrong more often than you'd expect:

0% 5% 10% 15% 20% openai realtime 2.1: 0.9% of 218 callsopenai realtime 2.11% dialt smart: 2.2% of 225 callsdialt smart2% dialt fast: 2.7% of 222 callsdialt fast3% eleven realtime mini: 2.7% of 222 callseleven realtime mini3% elevenlabs: 3.2% of 225 callselevenlabs3% openai realtime: 4.5% of 225 callsopenai realtime5% gpt-live 1: 4.8% of 225 callsgpt-live 15% phonic: 5.0% of 221 callsphonic5% vapi: 5.5% of 222 callsvapi6% grok voice: 6.7% of 225 callsgrok voice7% deepgram: 8.0% of 213 callsdeepgram8% mistral: 8.0% of 163 callsmistral8% livekit: 9.5% of 225 callslivekit10% gemini 3.1 live: 10.3% of 224 callsgemini 3.1 live10% gemini 3.8 live: 10.4% of 222 callsgemini 3.8 live10% hugging face: 14.6% of 169 callshugging face15% smallest ai: 14.6% of 225 callssmallest ai15% pipecat: 15.7% of 225 callspipecat16% gradium: 16.6% of 225 callsgradium17%

Share of calls where the first name the agent sent to the account check did not match the account, on calls without a TV in the room.

The first problem: speech-to-text

All of these voice agents, at some point in this task, need to convert speech-to-text. Cascaded agents always do it with a native speech-to-text model, but even speech-to-speech models need to type text into their tools. So long as databases expect text and human speech is audio, the problem is not going away.

Here is how often native speech-to-text got the name right in cascaded stacks.

0% 25% 50% 75% 100% elevenlabs: 218 of 225 callselevenlabs97% vapi: 209 of 222 callsvapi94% dialt fast: 208 of 222 callsdialt fast94% dialt smart: 205 of 225 callsdialt smart91% deepgram: 188 of 213 callsdeepgram88% mistral: 143 of 163 callsmistral88% livekit: 196 of 225 callslivekit87% gradium: 184 of 221 callsgradium83% hugging face: 133 of 161 callshugging face83% smallest ai: 175 of 217 callssmallest ai81% pipecat: 152 of 225 callspipecat68%

Cascaded agents only: the share of calls where speech-to-text wrote down the caller's name well enough to pass the check, the first time the caller said it.

When the name came through wrong, it was usually something plausible: “Alice Chaudhary” for Elise Choudhury, “Farrakowski” for Farah Kowalski, “Elise had that” for Elise Haddad.

The second problem: trusting speech-to-text

Next, the agent has to decide whether to trust the speech-to-text or not. Humans do this all the time. When we hear somebody say their name, we know how confident we are in our spelling. And even if a human only saw the name spelled out and entered it into their system, when the system rejected it, they would know some names are more likely to get misspelled, so they'd ask again.

Voice agents mostly just trust it. When the text held a wrong name, the agent sent it to the check 85% of the time:

0% 25% 50% 75% 100% elevenlabs: 6 of 6 misheard nameselevenlabs100% gradium: 29 of 29 misheard namesgradium100% hugging face: 13 of 13 misheard nameshugging face100% mistral: 12 of 12 misheard namesmistral100% livekit: 17 of 18 misheard nameslivekit94% smallest ai: 29 of 31 misheard namessmallest ai94% vapi: 10 of 12 misheard namesvapi83% deepgram: 14 of 17 misheard namesdeepgram82% pipecat: 12 of 15 misheard namespipecat80% dialt fast: 5 of 7 misheard namesdialt fast71% dialt smart: 2 of 15 misheard namesdialt smart13%

When the agent had a wrong version of the name, how often did they try to enter it in the computer?

dialt smart is the exception. It almost never sent a misheard name. Its replies suggest it gets more than one version of what the caller said, and asks when they disagree:

“I heard two versions of the first name: Zamina, with Z as in Zebra, or Amina, with A as in Alpha. Which is on the account?”

“I heard the name as ‘Farrakowski,’ but it also came through as ‘Kowalski.’ Could you repeat the full name on the account?”

This clearly paid off.

Agent asks again, but hears the same thing

A rejection from the computer is the clearest signal that the spelling was wrong. Most agents ask the caller to say their name again, but it rarely helps. Ask a caller to say “Camila” again, and the speech-to-text returns “Kamila” again.

The speech-to-speech models do this too. gpt-live 1 asked its callers to try again, heard the same thing, and sent “Kamila Kowalski,” “Kamila Kowalski,” “Kamila Kowalski.” After three failures the agent has to stop.

Which agents ask to spell

Half the stacks never asked anyone to spell their name, including both Gemini Live models, grok voice and both OpenAI Realtime models. dialt smart asked far more than anyone else:

0% 2% 4% 6% 8% 10% dialt smart: 19 of 248 callsdialt smart8% deepgram: 3 of 285 callsdeepgram1% phonic: 3 of 296 callsphonic1% pipecat: 3 of 300 callspipecat1% dialt fast: 2 of 262 callsdialt fast0.8% vapi: 2 of 297 callsvapi0.7% gradium: 2 of 300 callsgradium0.7% hugging face: 1 of 240 callshugging face0.4% gpt-live 1: 1 of 299 callsgpt-live 10.3% livekit: 1 of 300 callslivekit0.3% elevenlabs: 0 of 292 callselevenlabs0% eleven realtime mini: 0 of 290 callseleven realtime mini0% gemini 3.1 live: 0 of 298 callsgemini 3.1 live0% gemini 3.8 live: 0 of 295 callsgemini 3.8 live0% grok voice: 0 of 300 callsgrok voice0% mistral: 0 of 217 callsmistral0% openai realtime: 0 of 287 callsopenai realtime0% openai realtime 2.1: 0 of 290 callsopenai realtime 2.10% smallest ai: 0 of 298 callssmallest ai0%

Share of calls in which the agent explicitly double-checked the spelling.

“Is your first name spelled Farrah with two R's, or Farah with one?”

dialt fast asked less often, but after a rejection it produced the most human line we found. Its recognizer had transcribed the name as “Kovalski”, but the computer rejected it. So dialt asked whether the V should really be a W:

“Sorry about that — I just want to get the spelling right. Is it Kovalski, or Kowalski with a W?”

The caller spelled it out, and the next try went through.

If you're building a voice agent, keep these things in mind. The agent shouldn't trust a name just because the speech-to-text produced it. And when in doubt, it should just ask the human to spell it.

Test it before your callers do

A new speech recognizer, voice platform or prompt can change how every call goes. Veris runs it against simulated callers and twins of your systems, and grades what the agent did.

Book a demo