u/ord_phreaker

We just shipped an upgrade to Ultra Voices on Telnyx.

The big thing: the voices sound more natural now, especially in the parts where TTS usually breaks down.

Pauses feel less awkward.

Delivery is less flat.

The voice handles longer sentences better.

And the timing feels closer to an actual phone conversation.

This matters a lot for voice agents because the voice is usually the first thing users judge.

You can have solid STT, good routing, clean prompts, and fast tool calls, but if the voice sounds robotic or weirdly paced, the whole experience feels off.

We put together a quick before and after video using the same voice so the difference is easier to hear.

The improved Ultra Voices are live now on Telnyx.

Give it a shot in the Telnyx portal

We just shipped an upgrade to Ultra Voices on Telnyx.

The big thing: the voices sound more natural now, especially in the parts where TTS usually breaks down.

Pauses feel less awkward.

Delivery is less flat.

The voice handles longer sentences better.

And the timing feels closer to an actual phone conversation.

This matters a lot for voice agents because the voice is usually the first thing users judge.

You can have solid STT, good routing, clean prompts, and fast tool calls, but if the voice sounds robotic or weirdly paced, the whole experience feels off.

We put together a quick before and after video using the same voice so the difference is easier to hear.

The improved Ultra Voices are live now on Telnyx.

I’ve been spending a lot of time around production voice AI deployments, and the same patterns keep showing up.

The hard parts usually aren’t the voice model by itself. They’re the system around it.

A few lessons that seem to matter most:

1. Start with one call type. General support agents usually become vague fast.
2. Measure resolved calls, not answered calls.
3. Track time to first audio and full turn latency separately.
4. Test on real phone audio, not only browser audio.
5. Word error rate is an incomplete metric. Entity capture matters more.
6. Let callers interrupt. Turn-taking is where a lot of “AI feel” breaks.
7. Keep tool responses short and structured.
8. Confirm before write actions.
9. Build eval sets from real calls.
10. Treat handoff as part of the product, not a failure path.
11. Separate model failures from workflow failures.
12. Review failed calls every week.

The biggest shift for me is that voice agents are judged inside a live interaction. A caller notices latency, repetition, awkward pauses, bad escalation, and missing context immediately.

So the production question becomes less “can this agent talk?” and more:

• Can it complete the workflow?
• Can it recover from messy audio?
• Can it use the right tools?
• Can it hand off cleanly?
• Can the team improve it every week?

For teams building voice agents right now, what has been harder than expected?

I’ve been spending a lot of time around production voice AI deployments, and the same patterns keep showing up.

The hard parts usually aren’t the voice model by itself. They’re the system around it.

A few lessons that seem to matter most:

1. Start with one call type. General support agents usually become vague fast.
2. Measure resolved calls, not answered calls.
3. Track time to first audio and full turn latency separately.
4. Test on real phone audio, not only browser audio.
5. Word error rate is an incomplete metric. Entity capture matters more.
6. Let callers interrupt. Turn-taking is where a lot of “AI feel” breaks.
7. Keep tool responses short and structured.
8. Confirm before write actions.
9. Build eval sets from real calls.
10. Treat handoff as part of the product, not a failure path.
11. Separate model failures from workflow failures.
12. Review failed calls every week.

The biggest shift for me is that voice agents are judged inside a live interaction. A caller notices latency, repetition, awkward pauses, bad escalation, and missing context immediately.

So the production question becomes less “can this agent talk?” and more:

• Can it complete the workflow?
• Can it recover from messy audio?
• Can it use the right tools?
• Can it hand off cleanly?
• Can the team improve it every week?

For teams building voice agents right now, what has been harder than expected?

I’ve been spending a lot of time around production voice AI deployments, and the same patterns keep showing up.

The hard parts usually aren’t the voice model by itself. They’re the system around it.

A few lessons that seem to matter most:

1. Start with one call type. General support agents usually become vague fast.
2. Measure resolved calls, not answered calls.
3. Track time to first audio and full turn latency separately.
4. Test on real phone audio, not only browser audio.
5. Word error rate is an incomplete metric. Entity capture matters more.
6. Let callers interrupt. Turn-taking is where a lot of “AI feel” breaks.
7. Keep tool responses short and structured.
8. Confirm before write actions.
9. Build eval sets from real calls.
10. Treat handoff as part of the product, not a failure path.
11. Separate model failures from workflow failures.
12. Review failed calls every week.

The biggest shift for me is that voice agents are judged inside a live interaction. A caller notices latency, repetition, awkward pauses, bad escalation, and missing context immediately.

So the production question becomes less “can this agent talk?” and more:

• Can it complete the workflow?
• Can it recover from messy audio?
• Can it use the right tools?
• Can it hand off cleanly?
• Can the team improve it every week?

For teams building voice agents right now, what has been harder than expected?

I’ve been spending a lot of time around production voice AI deployments, and the same patterns keep showing up.

The hard parts usually aren’t the voice model by itself. They’re the system around it.

A few lessons that seem to matter most:

1. Start with one call type. General support agents usually become vague fast.
2. Measure resolved calls, not answered calls.
3. Track time to first audio and full turn latency separately.
4. Test on real phone audio, not only browser audio.
5. Word error rate is an incomplete metric. Entity capture matters more.
6. Let callers interrupt. Turn-taking is where a lot of “AI feel” breaks.
7. Keep tool responses short and structured.
8. Confirm before write actions.
9. Build eval sets from real calls.
10. Treat handoff as part of the product, not a failure path.
11. Separate model failures from workflow failures.
12. Review failed calls every week.

The biggest shift for me is that voice agents are judged inside a live interaction. A caller notices latency, repetition, awkward pauses, bad escalation, and missing context immediately.

So the production question becomes less “can this agent talk?” and more:

• Can it complete the workflow?
• Can it recover from messy audio?
• Can it use the right tools?
• Can it hand off cleanly?
• Can the team improve it every week?

For teams building voice agents right now, what has been harder than expected?

I’ve been spending a lot of time around production voice AI deployments, and the same patterns keep showing up.

The hard parts usually aren’t the voice model by itself. They’re the system around it.

A few lessons that seem to matter most:

1. Start with one call type. General support agents usually become vague fast.

2. Measure resolved calls, not answered calls.

3. Track time to first audio and full turn latency separately.

4. Test on real phone audio, not only browser audio.

5. Word error rate is an incomplete metric. Entity capture matters more.

6. Let callers interrupt. Turn-taking is where a lot of “AI feel” breaks.

7. Keep tool responses short and structured.

8. Confirm before write actions.

9. Build eval sets from real calls.

10. Treat handoff as part of the product, not a failure path.

11. Separate model failures from workflow failures.

12. Review failed calls every week.

The biggest shift for me is that voice agents are judged inside a live interaction. A caller notices latency, repetition, awkward pauses, bad escalation, and missing context immediately.

So the production question becomes less “can this agent talk?” and more:

• Can it complete the workflow?
• Can it recover from messy audio?
• Can it use the right tools?
• Can it hand off cleanly?
• Can the team improve it every week?

For teams building voice agents right now, what has been harder than expected?