By Sagar Shankaran, Founder of CallSphere
Real per-minute cost breakdown for ElevenLabs Conversational AI vs OpenAI Realtime in 2026, with the hidden costs most teams miss.
Key takeaways
In production voice-agent deployments in 2026, two stacks dominate: OpenAI Realtime as the speech-to-speech foundation, and ElevenLabs Conversational AI as the cascade-pipeline stack with native function calling. Both ship voice agents end-to-end. Pricing is structured very differently. Choosing one without doing the math costs real money.
This is the cost breakdown updated for 2026 pricing.
flowchart LR
OAI[OpenAI Realtime] --> O1[Per audio input minute]
OAI --> O2[Per audio output minute]
OAI --> O3[Per text token in/out]
EL[ElevenLabs Conv AI] --> E1[Per minute<br/>bundled ASR + TTS + LLM]
EL --> E2[Function call surcharges]
EL --> E3[Voice clone licensing for<br/>premium voices]
OpenAI splits cost across audio in, audio out, and any text token. The new realtime-mini tier introduced in early 2026 dropped audio costs roughly 5x relative to the original GPT-4o-realtime, making audio the smaller line item now and tool-call text the larger one in many agents.
ElevenLabs bundles per-minute, with a base rate that includes ASR, TTS, and a configurable LLM. They charge surcharges when you upgrade the LLM (Claude Sonnet, GPT-5) or use specific premium voices.
Assume a voice agent that:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
For a one-minute average call across 1000 calls per day (16,667 minutes/month):
| Item | OpenAI Realtime (mini) | ElevenLabs (with GPT-5) |
|---|---|---|
| Audio in | ~$160 | bundled |
| Audio out | ~$320 | bundled |
| Text tokens (system + tool I/O) | ~$200 | bundled |
| Per-minute base | — | ~$1500 |
| LLM upgrade fee | — | ~$300 |
| Total per month | ~$680 | ~$1800 |
OpenAI's realtime-mini tier is roughly 2.5x cheaper at this workload shape in 2026. The picture flips for very chatty workloads with heavy tool I/O — ElevenLabs's bundled model becomes more predictable.
flowchart TB
Visible[Visible Cost] --> H1[Provider per-minute or token]
Hidden[Hidden Cost] --> H2[Telephony PSTN]
Hidden --> H3[Egress bandwidth]
Hidden --> H4[Eval and observability]
Hidden --> H5[Recording storage]
Hidden --> H6[Compliance + audit]
Hidden --> H7[Tool-API calls inside agent]
For a typical voice-agent workload in 2026, the LLM/voice provider line is 30-60 percent of total cost. The remaining 40-70 percent is in the items above. Teams that compare only the visible cost are comparing the wrong number.
flowchart TD
Q1{Heavy tool calling<br/>and dynamic logic?} -->|Yes| OAI2[OpenAI Realtime]
Q1 -->|No, brand-voice<br/>matters most| EL2[ElevenLabs]
OAI2 --> R1[Lower variable cost,<br/>faster function calling]
EL2 --> R2[Best voice naturalness,<br/>predictable bundle pricing]
For our healthcare and salon voice agents we run OpenAI Realtime with the mini tier in 2026. For one client where brand voice was the deciding factor (a hotel reservations product) we run ElevenLabs Conversational AI with a custom-cloned voice. The cost difference is real but the brand-voice alignment justified the premium for that customer.
Building on the discussion above in ElevenLabs vs OpenAI Realtime: Per-Minute Cost Analysis 2026, the place this gets non-obvious in production is the latency budget — every leg of the audio loop (capture, ASR, reasoning, TTS, transport) eats into the <1s response window callers expect. 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.
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.
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.
What changes when you move a voice agent the way ElevenLabs vs OpenAI Realtime: Per-Minute Cost Analysis 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.
Where does this break down for 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.
How does the CallSphere healthcare voice agent handle a typical patient intake?
The healthcare stack runs 14 specialist tools against 20+ database tables, captures intent and slots in real time, and produces a post-call sentiment score, lead score, and escalation flag for every conversation — so the front desk inherits a triaged queue, not a stack of voicemails.
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 healthcare voice agent at healthcare.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.
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.
OpenAI Realtime dominates production voice AI in 2026. Claude wins on analytics. Here's a task-by-task decision framework from a real voice agent stack.
Enterprise CIO Guide perspective on ElevenLabs Conversational 2.0 ships native MCP tool use, sub-second turn-taking, and a redesigned dashboard that makes voice agents feel like real software.
Direct OpenAI Realtime + Agents SDK = thinner stack vs Vapi's vendor middleware layer. CallSphere ships voice agents in days, not sprints.
The state of streaming TTS in 2026 — ElevenLabs, OpenAI, Cartesia, Sesame, Deepgram Aura, and Inworld benchmarked on the metrics that matter.
The three production-grade native speech-to-speech LLMs of 2026, side by side. Latency, prosody quality, function calling, and where each one breaks.
© 2026 CallSphere LLC. All rights reserved.
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.