Call a voice bot and ask it a question. Count the seconds silently while it thinks. If the pause stretches past a couple of seconds, you already feel the awkwardness: real people don't talk like that. A customer on a cold call feels the same thing, and hangs up.
Response speed decides the fate of the conversation. Here's why three seconds is the threshold beyond which a bot stops sounding human.
Where the threshold comes from
A person in conversation replies to the other speaker in two to three seconds. Any longer, and a pause appears that both sides notice. A voice bot has to keep the same rhythm, or the customer understands they're talking to a machine.
Every bot reply is assembled from three steps:
- Recognize the customer's speech and convert it to text.
- Generate a reply.
- Speak it aloud.
The sum of the three steps shouldn't run past about three seconds. If any single step spills over one second, that's our signal to dig into what went wrong.
Our numbers
On one representative call, speaking the reply took 300 milliseconds. For real-time voice, that's a record-setting figure. Speech recognition, together with checking whether the customer had finished their thought, came in at 0.63 seconds.
The gap between one second and three hundred milliseconds looks trivial. In everyday conversation, most people wouldn't even notice it. On a cold call, that gap is the difference that costs you the lead: the customer hears the delay, realizes they're talking to a machine, and hangs up.
The threshold
Three seconds is the line between a live-sounding agent and an obvious machine.
Why we moved to our own servers
Speed comes down to hardware and access to models. As long as recognition, reasoning, and speech synthesis run on someone else's servers on the other side of the world, two problems follow. First, latency: the signal has to travel halfway around the globe and back. Second, reliability: access to external providers hosted abroad can be throttled or cut off without warning, and if that happens mid-call, the bot simply goes silent.
So we moved the entire stack onto our own servers. The models run on our own infrastructure, where we can manage and fine-tune them for the task at hand. Latency drops, and dependence on someone else's limits and policies disappears.
What this means for your business
A fast bot sounds like a live agent and keeps the customer in the conversation. A slow one gives itself away with the very first pause and loses the lead right at the start. Three seconds is the boundary between these two scenarios, and we keep our response inside it.
Hear the pace for yourself
Send over your script and we'll give you a number to call the bot on, so you can time the response speed yourself. Three seconds, and you'll hear the difference.