Phase 0: Voice AI Fundamentals & Architecture · 45 min · Python · OpenAI SDK
What Voice AI Agents Are and How They Differ from Text AI and IVR
Voice AI is not ChatGPT with a microphone — it's a fundamentally different engineering discipline.
Hiring signal: Understanding what voice AI is and how it differs from text AI appears in every voice AI interview screening.
What you will learn
- Explain what voice AI agents are and how they differ from text-based AI and traditional IVR systems
- Articulate why real-time constraints make voice AI fundamentally different from text AI
- Map the voice AI market landscape: key companies, use cases, and growth trajectory
- Identify the core engineering challenges unique to voice AI: latency, turn-taking, interruptions, telephony
The Problem
Text AI is forgiving. You send a request, wait 2 seconds, get a response. If the user types slowly, no problem. If the model takes 5 seconds, the user waits. Voice AI has no such luxury. When a human speaks, they expect a response in under 500 milliseconds. Beyond 800ms, the conversation feels broken. Beyond 1200ms, the caller hangs up.
Traditional IVR systems ("press 1 for sales, press 2 for support") don't have this problem — they don't converse. They present menus and wait for DTMF tones. But they also can't handle natural language, follow-ups, or context. Voice AI agents occupy the gap between IVR rigidity and human flexibility, with the real-time constraints of neither.
This lesson establishes the mental models every voice AI engineer needs before writing a single line of audio code.
The Concept
What a Voice AI Agent Is
A voice AI agent is a real-time system that:
- Listens to human speech via streaming audio
- Understands spoken language using ASR + LLM
- Responds with synthesized speech
- Manages conversation — turn-taking, interruptions, context
- Acts — makes API calls, queries databases, schedules appointments
The critical word is real-time. Every component operates on streaming audio, not batch requests.
Voice AI vs Text AI
| Dimension | Text AI | Voice AI |
|---|
| Latency budget | 2-5s acceptable | 300-500ms required |
| Input format | Text (discrete tokens) | Audio (continuous stream) |
| Output format | Text (can format/iterate) | Audio (must be natural first try) |
| Turn-taking | User sends, waits for response | Continuous — both parties can speak |
| Interruptions | N/A — user stops typing | User can barge in mid-sentence |
| Error recovery | User re-types | User repeats or rephrases — costs latency |
| Context | Full text history | Must manage conversation state across turns |
| Streaming | Token-by-token text | Chunk-by-chunk audio (20ms frames) |
Why can't you just wrap a text chatbot with ASR and TTS and call it a voice agent?
A text chatbot wrapped with ASR+TTS introduces 2-5s latency (batch ASR → LLM → batch TTS), has no streaming, no interruption handling, and no turn-taking detection. Real voice agents stream audio in 20ms chunks, overlap ASR/LLM/TTS processing, detect when the user finishes speaking, and handle barge-in — all within a 500ms budget.
Voice AI vs Traditional IVR
| Dimension | IVR | Voice AI |
|---|
| Input | DTMF tones (press 1) | Natural speech |
| Flexibility | Fixed menu trees | Open-ended conversation |
| Context | None | Multi-turn context, follow-ups |
| Personalization | Account number lookup | Voice biometrics, conversation history |
| Error handling | "Invalid input" | "I didn't catch that, could you repeat?" |
| Cost | $0.001/min | $0.10-$0.20/min |
| Setup | Weeks of menu design | Prompt engineering + API integration |
The Core Engineering Challenges
- Latency — 500ms glass-to-glass budget. Every millisecond matters.
- Turn-taking — Knowing when the user has finished speaking (not just paused).
- Interruptions — Handling barge-in when the user speaks over the agent.
- Streaming — Processing audio in 20ms chunks, not batch requests.
- Telephony — Bridging PSTN/SIP to web audio (WebRTC, WebSocket).
- Cost — $0.10-$0.20/min vs $0.001/min for IVR. Must justify ROI.
- Accuracy — ASR errors propagate through the pipeline. 95% WER means 1 in 20 words wrong.
Unlock the full lesson
You've read the first 2 sections. The rest of this lesson covers Build It, Use It, Ship It, Evaluation, Key Terms, Common Pitfalls, Interview Framing — plus a hands-on lab, quiz, and project artifact.
Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.
Browse all courses · View pricing · DeVenture Academy