By Sagar Shankaran, Founder of CallSphere
Human turn gaps run 200-300ms. Most agents hit 800-1500ms. We unpack VAD vs semantic turn detection, duplex audio pipelines, and CallSphere's per-vertical barge-in thresholds.
Key takeaways
TL;DR — Humans take turns at 200-300 ms gaps; most voice agents lag at 800-1500 ms because they wait for VAD silence. Semantic turn detection (audio + text) closes the gap to ~300 ms without cutting users off mid-thought.
Pure VAD turn detection has two failure modes:
Sub-100 ms barge-in (caller interrupts the agent's TTS) is the other hard problem. Without duplex audio, the agent keeps talking for 200-400 ms after the caller starts speaking — exactly the moment the caller most wants control.
Semantic turn detection — combine VAD with a lightweight text classifier on the partial transcript. "I'd like to schedule for the..." (incomplete) gets a longer wait; "next Tuesday at 3" (complete) cuts to 200 ms.
Duplex audio pipeline — STT and TTS run on separate streams; the moment STT detects voice the TTS pauses (ducking) and the agent can decide whether to yield.
Barge-in confidence — distinguish a real interruption from a backchannel ("uh huh", "yeah ok"). Backchannels keep the agent talking; new content yields the floor.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Per-vertical thresholds — tune the budget by call type. Spelled numbers need longer pauses than yes/no flows.
flowchart TD
USER[User speaks] --> VAD{VAD detects voice}
VAD -->|Yes - agent speaking| DUCK[TTS duck audio]
DUCK --> CLASS{Backchannel or content?}
CLASS -->|Backchannel| KEEP[Agent keeps speaking]
CLASS -->|Content| YIELD[Stop TTS, listen]
VAD -->|Silence > threshold| SEM{Semantic complete?}
SEM -->|Yes| RESPOND[Generate response]
SEM -->|No| WAIT[Extend wait]
CallSphere ships per-vertical turn budgets across all 37 specialized agents and 6 verticals, with detailed metrics in the 115+ DB tables:
Latency targets: VAD ≤ 250 ms · STT ≤ 300 ms · TTFT ≤ 600 ms · TTS first audio ≤ 200 ms · network ≤ 150 ms. Hear the difference on a demo. Trial free for 14 days.
| Dimension | Pass | Fail |
|---|---|---|
| End-to-end latency | < 800 ms | > 1500 ms |
| Mid-turn cut-off rate | < 2% | > 8% |
| Barge-in latency | < 200 ms | > 500 ms |
| Backchannel false yield | < 1% | > 5% |
| Caller-rated naturalness | ≥ 4.2 / 5 | < 3.5 / 5 |
Q: Should every utterance use semantic turn detection? Yes for production. Pure VAD is fine in prototypes but fails on spelling, addresses, and dollar amounts.
Q: How do I handle two callers on speakerphone? Speaker diarization at the SIP edge; treat each voice as a separate VAD stream. AssemblyAI and Deepgram both support it.
Q: Does ducking annoy callers? Less than the alternative (agent keeps talking over them). Set ducking gain to -24 dB, not full mute.
Q: What about the agent's own TTS bleeding into the mic? Echo cancellation (AEC) is mandatory on speakerphone calls; built into LiveKit and most SIP gateways.
One layer below what Voice Agent Turn-Taking & Barge-In Tuning (2026) covers, the practical question every team hits is multi-turn handoffs between specialist agents without losing slot state, sentiment, or escalation context. Treat this as a voice-first system from the first prompt: the agent's persona, its tool surface, and its escalation rules all flow from that single decision. Teams that ship fast tend to instrument the loop end-to-end before they tune any single component, because the bottleneck is rarely where intuition puts it.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
A production-grade voice stack at CallSphere stitches Twilio Programmable Voice (PSTN ingress, TwiML, bidirectional Media Streams) to a realtime reasoning layer — typically OpenAI Realtime or ElevenLabs Conversational AI — with sub-second response as a hard SLO. Anything north of one second of perceived silence and callers either repeat themselves or hang up; that single number drives the whole architecture. Server-side VAD with proper barge-in support is non-negotiable, otherwise the agent talks over the caller and the conversation collapses. Streaming TTS with phoneme-aligned interruption keeps the cadence natural even when the user changes their mind mid-sentence. Post-call, every transcript is run through a structured pipeline: sentiment, intent classification, lead score, escalation flag, and a normalized slot extraction (name, callback number, reason, urgency). For healthcare workloads, the BAA-covered storage path, audit logs, encryption-at-rest, and PHI-safe transcript redaction are wired in from day one, not bolted on at compliance review. The end state is a system where every call produces a row of structured data, not just a recording.
How do you actually ship a voice agent the way Voice Agent Turn-Taking & Barge-In Tuning (2026) describes?
Treat the architecture in this post as a starting point and instrument it before you tune it. The metrics that matter most early on are end-to-end latency (target < 1s for voice, < 3s for chat), barge-in correctness, tool-call success rate, and post-conversation lead score distribution. Optimize whatever the data flags as the bottleneck, not whatever feels slowest in your head.
What are the failure modes of voice agent deployments at scale?
The two failure modes that bite hardest are silent context loss across multi-turn handoffs and tool calls that succeed in dev but get rate-limited in production. Both are solvable with a proper agent backplane that pins state to a session ID, retries with backoff, and writes every tool invocation to an audit log you can replay.
What does the CallSphere outbound sales calling product do that a regular dialer does not?
It uses the ElevenLabs "Sarah" voice, runs up to 5 concurrent outbound calls per operator, and ships with a browser-based dialer that transfers warm calls back to a human in one click. Dispositions, transcripts, and lead scores write back to the CRM automatically.
Book a 30-minute working session at calendly.com/sagar-callsphere/new-meeting and bring a real call flow — we will walk it through the live outbound sales dialer at sales.callsphere.tech and show you exactly where the production wiring sits.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
96% of well-designed agents close calls politely; the rest leave callers with the robotic-hangup feeling that undermines the whole flow. We map endCallPhrase tuning, silence-timeout policies, and CallSphere's vertical farewell library.
WebTransport is Baseline as of March 2026. Media Over QUIC ships in production within the year. Here is what changes for AI voice agents — and what stays the same.
Every 100ms of latency costs you. So does every cent per minute. Here is the decision matrix we use across 6 verticals to pick where to spend and where to save on voice AI infrastructure.
Vapi 465ms optimal, Retell 580-620ms, Bland ~800ms, ElevenLabs 400-600ms — but those are best-case. We design a fair benchmark harness, P95 measurement, and a reproducible methodology for 2026.
How to stream tokens, tool-call deltas, and intermediate steps from an agent — with code for both the OpenAI Agents SDK and LangChain — and the gotchas that bite in production.
Streaming changes the eval game — final-answer correctness isn't enough when users perceive the answer one token at a time. Here's the metric set that matters.
© 2026 CallSphere LLC. All rights reserved.