Text hides a lot of sins. On chat, a half-second of extra latency is invisible and a slightly awkward phrasing just sits there quietly. On a live phone call, both are brutal. Voice is the channel that punishes every shortcut, and shipping it taught us where the real engineering is.
Latency is a feature, not a metric
On a call, silence is a signal. Wait too long to respond and the caller assumes the line dropped, or that they weren't understood, and they start repeating themselves — which now collides with the agent finally answering. The entire conversation degrades from a single second of delay.
So latency isn't a number you report; it's a feature you design around. That means streaming everything, starting to speak before the full response is computed, and keeping the reasoning-to-speech path short. We go deeper on the budget in voice AI latency. The target isn't "fast enough on average." It's fast enough that the caller never wonders whether anyone's there.
Interruptions are normal — handle them like a person
People interrupt. They cut in with "no, the other account," or start their next question before you've finished. A voice agent that plows through its scripted sentence while the caller is talking feels deaf and disrespectful.
Real conversations require barge-in: the moment the caller starts speaking, the agent stops, listens, and re-plans from what it just heard. Getting this right is mostly about being willing to throw away work — the half-spoken response the agent was in the middle of — instantly and gracefully, the way a person trails off mid-sentence when you jump in.
Confirmation without an undo button
Chat has an implicit undo: the customer can see what happened and say "wait, that's wrong." A phone call has none. Once the agent says "done, I've moved your reservation to Friday," the caller acts on that.
So high-stakes actions on voice get an explicit verbal confirmation before they commit — "I'm going to move your reservation to Friday the 12th, is that right?" — and only then does the tool fire. It's the voice equivalent of a confirmation dialog, and skipping it is how you turn a helpful agent into an expensive mistake.
Handoffs have to be warm
When a call needs a human, the worst thing you can do is dump the caller into a queue to start over. By the time a person picks up, the agent should have handed them the whole context. That's a warm handoff, and on a phone line it's the difference between continuity and starting over.
The through-line
None of these are AI problems, exactly. They're conversation problems — timing, attention, confirmation, continuity — that text let us ignore. Voice makes them unavoidable, and getting them right is what separates an agent that sounds like a person from one that sounds like a phone tree with a better voice. Hear it on the voice page.