The voice agent stack, explained: STT, LLM, TTS and telephony

Every voice agent is the same loop: hear the caller, decide what to say, say it, and do it fast enough that the pause feels human. The interesting choices are which layers you buy as a bundle and which you assemble yourself.

Updated 2026-10-29

1. Transport: phone lines or WebRTC

Phone agents need numbers and SIP trunking from a carrier-grade provider. Browser and app agents usually run over WebRTC. Pick this first — it decides latency budget and which orchestration options fit.

2. Speech-to-text

Streaming STT with good endpointing (knowing when the caller has finished) matters more than raw accuracy benchmarks. Test on your own audio: accents, background noise, phone-quality 8 kHz.

3. The model

The LLM decides what to say and which tools to call. Speech-to-speech models such as OpenAI Realtime collapse STT, LLM and TTS into one hop, trading control for latency.

4. Text-to-speech

Time-to-first-audio and how natural the voice sounds over a phone line are the two things callers notice. Most TTS vendors stream; check voice cloning terms if you need a custom voice.

5. Orchestration

Something has to manage turn-taking, interruptions (barge-in), tool calls and state. Hosted platforms do this for you; open-source frameworks give you the pipeline to run yourself.

6. Testing and observability

Voice agents fail in ways text chat doesn't — talking over the caller, long silences, mis-heard numbers. Budget for simulated-call testing and per-turn tracing before you scale traffic.

Comparisons

Browse the categories

Building one of these tools? Submit it free, or get featured in front of builders reading this.