By Sagar Shankaran, Founder of CallSphere
WebRTC's getStats() returns 50+ metrics. Five of them tell you whether your AI voice agent will sound great or stutter. Here is the production cheat sheet.
Key takeaways
getStats() is the most underused API in WebRTC. Five metrics polled every 2 s will tell you exactly when a customer is about to hate your AI voice agent — before they hang up.
flowchart LR
Mobile[iOS / Android SDK] --> WHIP[WHIP ingest]
WHIP --> Mux[Mux / LiveKit]
Mux --> Brain[AI brain]
Brain --> WHEP[WHEP egress]
WHEP --> Web[Web viewer]`RTCPeerConnection.getStats()` returns a dictionary of RTC objects: codec info, transport info, inbound RTP, outbound RTP, candidate pair, and more. The W3C spec is at `webrtc-stats` and Chrome's `chrome://webrtc-internals` is the visual companion. By 2026 every serious voice-AI vendor wires getStats into their analytics — because LLM and TTS quality complaints almost always trace back to network, not model.
The five metrics that matter for voice:
Sample these every 1–5 seconds, diff with the previous report, and you have a real-time QoS dashboard.
CallSphere runs a getStats poller in every browser session that opens our /demo page and every customer-facing voice flow. The metrics ship to our internal analytics over a fetch beacon every 5 s. We aggregate by vertical (Real Estate OneRoof, Healthcare, etc.) and alert when any vertical's p95 RTT crosses 280 ms. With 37 agents and 6 verticals, this is the only way we catch regional ISP issues before they become support tickets.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
The same poller also drives our SLA dashboard. Customers on the $499 and $1499 tiers see real-time loss/jitter/RTT for their fleet — proof of HIPAA/SOC 2-grade observability beyond just LLM token counts.
```ts function startQosPoll(pc: RTCPeerConnection, onSample: (s: any) => void) { let prevLost = 0, prevPkts = 0; return setInterval(async () => { const report = await pc.getStats(); let inbound: any, remoteInbound: any, outbound: any; report.forEach((r) => { if (r.type === "inbound-rtp" && r.kind === "audio") inbound = r; if (r.type === "remote-inbound-rtp" && r.kind === "audio") remoteInbound = r; if (r.type === "outbound-rtp" && r.kind === "audio") outbound = r; }); const dPkts = (inbound?.packetsReceived ?? 0) - prevPkts; const dLost = (inbound?.packetsLost ?? 0) - prevLost; prevPkts = inbound?.packetsReceived ?? 0; prevLost = inbound?.packetsLost ?? 0; onSample({ lossRate: dPkts > 0 ? dLost / dPkts : 0, jitter: inbound?.jitter ?? 0, rtt: remoteInbound?.roundTripTime ?? 0, qLimit: outbound?.qualityLimitationReason ?? "none", }); }, 2000); } ```
Does Safari support getStats? Yes; minor naming variance — wrap with feature checks. Are these metrics privacy-sensitive? No personally identifiable information; just network-level counters. How heavy is polling? Sub-millisecond per call; do not poll faster than 1 Hz. Can I correlate to STT word error rate? Yes — log loss + jitter alongside the STT confidence per turn. What about server-side stats? SFUs (LiveKit, mediasoup, Pion) export their own; combine both for full visibility.
Customer dashboards include this telemetry on every plan — see /pricing. Or watch the live poller on /demo.
WebRTC getStats() for Voice AI: The QoS Telemetry That Actually Matters in 2026 is also a cost-per-conversation problem hiding in plain sight. Once you instrument tokens-in, tokens-out, tool calls, ASR seconds, and TTS seconds against booked-revenue per call, the right tradeoff between Realtime API and an async ASR + LLM + TTS pipeline becomes obvious — and it's almost never the same answer for healthcare as it is for salons.
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.
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.
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.
How does this apply to a CallSphere pilot specifically? Setup runs 3–5 business days, the trial is 14 days with no credit card, and pricing tiers are $149, $499, and $1,499 — so a vertical-specific pilot is a same-week decision, not a quarterly project. For a topic like "WebRTC getStats() for Voice AI: The QoS Telemetry That Actually Matters in 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 does the typical first-week implementation look like? 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.
Where does this break down at scale? 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 escalation.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.
A founder's guide to texto a voz (text-to-speech in Spanish): LATAM vs Castilian voices, free options, and how CallSphere ships Spanish agents.
A founder's guide to the female voice generator landscape: AI female voices, Japanese voices, robot voices, and how CallSphere ships 57+ voices live.
A founder's guide to the Siri voice generator landscape: how AI voice cloning works, what is legal, and how CallSphere uses 57+ voices in production.
A founder's guide to AI voice assistants for ecommerce: customer service, order lookup, and how CallSphere fits in versus virtual receptionists.
Robot text to speech in 2026: how I pick TTS APIs, when robotic voices help, and how CallSphere ships 57+ language voice agents. Hands-on guide.
The customer support specialist role in 2026 is half human, half AI. Here is what the job looks like, the AI tools that pair with it, and how we ship it.
© 2026 CallSphere LLC. All rights reserved.
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.