By Sagar Shankaran, Founder of CallSphere
Endpointing decides the exact moment to send the transcript to the LLM. VAD-only is naive; semantic endpointing uses context. We compare both, with model-based turn detection benchmarks for 2026.
Key takeaways
TL;DR — VAD-only endpointing fires on silence and ignores meaning. Model-based endpointing reads the transcript and decides if the user is done — cutting endpoint latency by 200-400ms on natural pauses. LiveKit, Pipecat, and OpenAI Realtime all ship semantic turn detection in 2026.
Endpointing is "did the user stop?". VAD answers "is there silence?". They are not the same. A caller saying "I'd like to book... an appointment for... Tuesday" has 600ms of silence inside a single utterance. VAD would fire after the first ... and you'd send a half-formed query to the LLM.
Three endpointing strategies:
flowchart LR
AUDIO[Audio] --> VAD[VAD silence]
AUDIO --> ASR[ASR partial]
VAD --> TURN[Turn detector<br/>model]
ASR --> TURN
TURN --> DECIDE{User done?}
DECIDE -->|Yes| LLM[Send to LLM]
DECIDE -->|No| WAIT[Keep listening]
WAIT --> AUDIO
CallSphere uses model-based endpointing for Healthcare (Realtime's native turn detector) and hybrid VAD + punctuation for Salon, Behavioral Health, Restaurants, Real Estate, and Legal. The FastAPI :8084 gateway records per-turn endpointing decisions for replay and tuning. 37 agents, 90+ tools, 115+ DB tables, 6 verticals, $149/$499/$1,499, 14-day trial, 22% affiliate.
Try a vertical or start a trial.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Q: Is model-based endpointing always better? For natural conversation, yes. For touch-tone-style "yes/no" flows, VAD-only is fine.
Q: How big should the turn-detection model be? LiveKit's open turn detector is ~135M params, runs in 30-50ms on CPU.
Q: Does Realtime API ship semantic turn detection? Yes — server-VAD and semantic-VAD modes since late 2025.
Q: What's the false-cut rate to target? < 1% on production traffic. Above that, callers complain.
Q: Does CallSphere expose endpoint config? Yes — per-agent override for Growth and Scale tier customers.
Endpointing: When Should an AI Voice Agent Stop Listening? (2026) usually starts as an architecture diagram, then collides with reality the first week of pilot. You discover that vector store choice (ChromaDB vs. Postgres pgvector vs. managed) is not really a vector store choice — it's a latency, freshness, and ops choice. Picking wrong forces a re-platform six months in, exactly when you have customers depending on 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.
Production AI agents live or die on three loops: evals, retries, and handoff state. CallSphere runs 37 agents across 6 verticals, each with its own eval suite — synthetic call transcripts replayed nightly with assertion checks on extracted entities (date, time, party size, insurance, address). Without that loop, prompt regressions ship silently and you only find out when bookings drop.
Structured tools beat free-form text every time. Our 90+ function tools all enforce JSON schemas validated server-side; if the model hallucinates an integer where a string is required, we retry with a corrective system message before falling back to a deterministic path. For long-running flows, we treat agent handoffs as a state machine — booking → confirmation → SMS — so context survives turn boundaries.
The Realtime API vs. async decision usually comes down to "is the user holding the phone right now?" If yes, Realtime; if no (callback queue, after-hours voicemail), async wins on cost-per-conversation, which we track per agent in 115+ database tables spanning all 6 verticals.
Why does endpointing: when should an ai voice agent stop listening? (2026) matter for revenue, not just engineering?
The healthcare stack is a concrete example: FastAPI + OpenAI Realtime API + NestJS + Prisma + Postgres healthcare_voice schema + Twilio voice + AWS SES + JWT auth, all SOC 2 / HIPAA aligned. For a topic like "Endpointing: When Should an AI Voice Agent Stop Listening? (2026)", that means you're not starting from scratch — you're configuring an agent template that's already been hardened across thousands of conversations.
What are the most common mistakes teams make on day one? Day one is integration mapping (scheduler, CRM, messaging) and prompt tuning against your top 20 real call transcripts. Day two through five is shadow-mode running, where the agent transcribes and recommends but a human still answers, so you can compare side-by-side. Go-live is the moment your eval pass-rate clears your internal bar.
How does CallSphere's stack handle this differently than a generic chatbot? The honest answer: it scales until your tool catalog gets stale. The agent is only as good as the integrations it can actually call, so the operational discipline is keeping schemas, webhooks, and fallback paths green. The platform handles the rest — observability, retries, multi-region routing — without your team owning the GPU layer.
Want to see how this maps to your stack? Book a live walkthrough at calendly.com/sagar-callsphere/new-meeting, or try the vertical-specific demo at realestate.callsphere.tech. 14-day trial, no credit card, pilot live in 3–5 business days.
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.
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.
On May 4 2026 OpenAI published its Realtime stack rebuild — split-relay plus transceiver edge. Here is what changed and what it means for production voice agents.
© 2026 CallSphere LLC. All rights reserved.