Voice AI platform pricing models in 2026: the enterprise buyer's guide

The five pricing models you'll see in 2026 RFPs

The market has converged on five recognisable structures. Most enterprise quotes are a blend of two of them.

1. Per-minute usage — the legacy default, almost always tiered by committed volume
2. Per-session or per-call — a flat fee per interaction, popular for high-volume, short, transactional triage
3. Per-resolution — outcome-based, charged only when a resolution-definition is met (the definition is the negotiation)
4. Per-seat-equivalent — priced against a notional displaced human agent, charged per concurrent capacity unit
5. Platform plus usage — a fixed annual platform fee for enterprise features (SSO, observability, sandboxes) plus a discounted unit rate

Per-minute pricing: what's actually included

A headline per-minute number is almost always partially unbundled in enterprise quotes. The published rate typically covers a baseline ASR, baseline TTS, and a default LLM. The line items that get added on top are what surprise procurement late in the cycle.

• Premium voices and language packs — frequently a 20–30% surcharge over the baseline TTS
• Higher-capability LLM models for harder reasoning — surcharged per minute or per token
• Prompt-token volume — long retrieval contexts and large knowledge bases meter against a separate token allowance
• Observability and analytics seats — real-time dashboards, conversation review, and QA tooling priced per user
• Telephony — almost never included in the AI rate; either pass-through-at-cost or a markup
• Recording storage and transcription retention — per-GB monthly and per-call retrieval pricing
• Sandbox / UAT environments — many platforms meter non-production usage separately

Per-resolution pricing: the definition is the negotiation

Outcome-based pricing aligns the vendor with the business case, but the word 'resolution' is doing a lot of work in the contract. Four definitions dominate the market, each with its own loophole.

The hidden cost stack

Five line items account for most of the gap between quoted unit rate and realised cost. Together they routinely add 15–25% to the bill.

• Telephony pass-through — PSTN, SIP trunking, and international termination; rarely included in the AI rate
• Recording storage and retention — per-GB monthly plus per-retrieval, multiplied by your compliance retention window
• SSO, SCIM, and audit-log access — frequently behind an 'Enterprise' or 'Pro' tier
• Sandbox, UAT, and dedicated tenant — non-production environments metered separately
• Professional services minimums — implementation, on-going customer-success retainer, and integration hours

Token and model pass-through pricing

Some platforms expose the underlying LLM cost directly and add a platform margin; others absorb it into a bundled per-minute rate. The trade-off is predictability versus exposure.

Pass-through pricing usually quotes lower nominal rates and shifts FX and model-provider rate-card risk to the buyer. If the underlying model provider re-prices or changes its tokenisation, your unit economics move with it. Build a quarterly review and a budget buffer; do not assume the rate at signature is the rate at month nine.

An honest TCO worked example

The same call volume across three pricing structures produces materially different annual bills. The example below uses one million minutes per year, an average call duration of four minutes (250,000 calls), and a 60% resolution rate where relevant.

Contract terms that move the number more than the unit rate

Below the headline rate sit the levers that decide what you actually pay. Negotiate these first; negotiate the unit rate last.

• Volume commits and rollovers — annualised pools beat monthly use-it-or-lose-it by a wide margin
• Ramp curves — committed minimums should scale with your deployment phases, not your contract start date
• Most-Favoured-Nation clauses — material in a market where compute costs are falling year-on-year
• Price-protection windows — cap on annual increases, with a clear basis for any pass-through changes
• Burst overage rates — confirm the per-minute rate that applies above your committed pool
• Exit and data portability — extraction of prompts, voice clones, conversation logs, and tuning data, with timelines and fees defined
• Sub-processor change notification — N days' notice and a right to refuse for material changes

The seven questions that flush out the real number

Send these in the RFP, not in the negotiation. The answers shape the comparison; chasing them late wastes weeks.

1. Is telephony (PSTN / SIP) included, pass-through at cost, or marked up — and at what rate?
2. What is the billing increment — per-second, six-second, or per-minute rounding?
3. Which LLM is included at the quoted rate, and what does upgrading to the higher-capability model cost per minute?
4. How is a resolution defined, and how is a non-resolution recorded — at the contract level, not the marketing level?
5. Is recording storage and transcription retention included for our compliance retention window?
6. What does multi-region or in-country processing add to the unit rate?
7. What are the burst overage and shortfall rates, and what is the annualisation rule?