Customer Support AI Pricing: Examples & Companies

What is it

Customer Support AI Pricing is the pricing for AI products that automate customer service — chatbots, ticket triage, and autonomous resolution agents.

Customer support is the use case where outcome-based pricing took hold first, and the reason is structural: a resolved support ticket is a clean, measurable, attributable outcome. Unlike a “completed” coding task or research job — where defining the unit is genuinely hard — a support resolution can be defined precisely enough that buyer and seller (mostly) agree on what to bill for. That clarity is why Intercom’s Fin at $0.99 per resolution became the canonical example and dragged the rest of the category toward the same model.

30 of the in-corpus companies serve the customer-support use case, and they split into three camps. The chat/email resolution agents price per resolved ticket — Intercom, Intercom Fin, Gorgias, Decagon, Sierra, Forethought, Maven AGI, Yellow.ai, Ada, Lorikeet, and Kustomer. The voice agents meter minutes instead — Bland AI, Synthflow AI, PolyAI, Parloa, ElevenLabs, and Cartesia. The seat-priced adjacencies — Zendesk AI, Cresta, Observe.AI, Uniphore, Fathom, Krisp, and Unbabel — layer AI onto a per-agent license.

The dividing line is what the vendor sells: a finished outcome (per resolution), a metered interaction (per minute), or a tool a human operates (per seat). The category is now the bellwether for outcome-based pricing across software — the proof case people reach for when they argue about whether you can charge per business result. The shared unit underneath the resolution camp is per-resolution pricing.

How it works

Support AI pricing has three building blocks: a platform fee (per seat or per ticket), an outcome/usage meter (per resolution, per engaged conversation, or per minute), and channel surcharges (voice costs more than text). Vendors mix these differently, but the meter is increasingly the dominant line item.

The worked math is what separates the camps. Take a busy ecommerce brand on Gorgias’ Pro plan: a $360 base (2,000 tickets), $360 in ticket overage (1,000 extra at $36/100), and $1,350 in AI Agent resolutions (1,500 at $0.90) totals $2,070 — where the per-resolution charge alone is nearly 4x the subscription. The outcome meter, not the seat count, becomes the bill. The same pattern appears on Yellow.ai: the free tier’s 500 sessions are a rounding error against a mid-volume brand doing 5,000 resolutions/month, which lands at ~$4,455 (4,500 billable × $0.99) — again the meter dwarfs the (zero) platform fee.

Voice math runs on a different clock. On Bland AI, 10,000 outbound calls averaging 3 minutes is 30,000 minutes at $0.14 = $4,200/month plus $0.015 per dial attempt — and crucially, a long unresolved call still bills, because minutes accrue regardless of outcome. That’s the structural gap between the voice camp (handle time) and the resolution camp (clean outcomes). Buyers modeling spend should estimate cost per solved ticket by channel, not a blended per-seat figure. Our guide to choosing the right usage metric walks through picking a value metric like this, and the breakdown of usage-based pricing models covers how these meters combine.

Companies using this

Thirty companies in the current corpus serve the customer-support use case, spanning three pricing shapes: the chat/email resolution agents (Intercom, Gorgias, Decagon, Sierra, Forethought, Yellow.ai, Ada, Lorikeet, Kustomer, Maven AGI), the per-minute voice agents (Bland AI, Synthflow AI, PolyAI, Parloa, ElevenLabs, Cartesia), and the seat-priced adjacencies and CX platforms (Zendesk AI, Cresta, Observe.AI, Uniphore, Gladly, Fathom, Krisp, Unbabel). The healthcare patient-facing agents (Hippocratic AI, Nabla, Suki AI, Ambience Healthcare) round out the set. The table lists each company’s full pricing structure.

Patterns observed

• Per-resolution is the chat/email default, and the rates have converged. Intercom Fin ($0.99), Gorgias ($0.90), and Yellow.ai ($0.99) all price the resolved ticket within a dime of a dollar. The headline numbers cluster tightly — see per-resolution pricing for the underlying billing mechanics. This is remarkable price alignment for a category where the underlying model cost varies enormously by vendor.

• The outcome meter outgrows the platform fee. Across Gorgias, Yellow.ai, and Zendesk AI, worked bills show resolutions and consumption charges exceeding the seat/ticket subscription several times over at moderate automation volumes. The seat is becoming an entry ticket; the resolution is the revenue. Zendesk is the clearest bridge case — it kept its per-agent Suite plans ($19/$55/$115) intact and bolted automated-resolution consumption on top rather than replacing seats.

• Voice prices minutes, not outcomes — a hard split inside one use case. Bland AI ($0.14/min), Synthflow AI (~$0.11–$0.24/min historically), and PolyAI (per-minute, quote-only) all bill handle time. A voice call that fails to resolve still bills, so the voice camp cannot reuse the chat camp’s deflection economics. Parloa and ElevenLabs sit here too, metering voice/chat minutes rather than closed tickets.

• Definition is the real differentiator, not price. Intercom and Gorgias bill only on full, escalation-free resolution; Decagon explicitly states “you don’t pay if the AI fails and the case is passed to a human”; Kustomer bills $0.60 per engaged conversation, which can include unresolved contacts. A lower headline rate on a looser definition can cost more per solved ticket.

• Enterprise players gate the rate entirely. Ada, Sierra, Maven AGI, Parloa, Observe.AI, and Uniphore publish no self-serve price. Third parties fill the gap: ~$69/agent/mo and a ~100-seat minimum for Observe.AI, ~$150K/yr for PolyAI, and six-figure floors reported for the largest voice deployments. This is the sales-led end of the category, where opacity cedes the pricing narrative to teardown sites.

• Outcome pricing bleeds into labor substitution. Hippocratic AI prices patient-facing agents as staffing at ~$9/agent-hour, explicitly benchmarked against ~$39/hr for a nurse. It’s the far edge of the outcome logic: instead of pricing a resolution, price the hour of the human you replace. The healthcare scribes (Nabla at ~$119/mo/provider, Suki AI quoted per clinician) stay per-seat because they assist rather than resolve.

Counterexamples & variants

The clearest counterexamples are the seat-priced adjacencies. Fathom and Krisp touch customer support — Krisp powers call-center voice AI and noise cancellation, Fathom transcribes support calls — but both bill per user, not per outcome, because they sell a tool a human operates rather than a finished resolution. Unbabel is similar: its LangOps translation supports multilingual service desks but prices on words and documents (or a self-serve freemium tier for Widn.ai), since the “outcome” of a translation is harder to define than a closed ticket. Cresta and Observe.AI coach and QA human agents, so they price per agent-seat (~$69/agent/mo reported for Observe.AI) even though the whole product is AI. When the AI assists a human rather than replacing the human’s action, per-resolution pricing doesn’t apply — and these companies prove it.

The voice-minute meter is the most consequential variant within the use case. Bland AI, Synthflow AI, PolyAI, and Parloa can’t clean up their unit into “resolution” because a phone call’s value is fuzzier than a chat’s — did a 6-minute call that ended in a callback “resolve”? So they meter minutes, which bills whether or not the issue closed. This is the opposite trade from the chat camp: worse outcome alignment, but far simpler and non-gameable metering. Synthflow shows the pressure this creates — it removed self-serve per-minute pricing entirely in mid-2026 and went Enterprise-only at a $30,000/year floor, a reminder that usage transparency and enterprise sales motions pull in opposite directions.

Two further variants are worth flagging. Engaged-conversation metering at Kustomer ($0.60) and assisted-conversation metering at Gladly ($0.60 for Sidekick) both look cheaper than Intercom’s $0.99 but bill on a looser event than a strict resolution — a case where the model is easy to misapply, since the sticker undersells the effective cost per solved ticket. And credit-pool resolution pricing at Lorikeet prices in credits with different draw rates per channel (0.95 text vs 1.50 voice) inside an annual pool, keeping outcome alignment while letting the effective rate fall as customers scale and giving the vendor room to reprice channels without renegotiating contracts.

What this means for buyers vs vendors

For buyers

Budget per solved ticket (or per handled minute for voice), not per seat — and read the resolution definition before the price. A $0.60 engaged-conversation rate (Kustomer) can cost more per actually-resolved issue than a $0.99 strict-resolution rate (Intercom) if a chunk of your conversations escalate. If your volume is voice-heavy, model minutes, not resolutions: a long unresolved call on Bland AI ($0.14/min) still bills, so handle time — not deflection rate — drives your invoice. Watch for the meter overtaking the subscription at scale, as the Gorgias worked example shows (resolutions ~4x the base). When a vendor like Ada, Sierra, PolyAI, or Observe.AI gates the rate, third-party purchase data (Vendr, AWS Marketplace, teardown sites) is your benchmark before the sales call — the ~$69/agent/mo and ~$150K/yr figures those sources publish are your negotiation floor. Start with our introduction to usage-based pricing, and estimate a specific bill with the Intercom pricing calculator.

For vendors

Outcome pricing aligns your revenue with deflection, but it lives or dies on the definition of the billable event — define “resolution” precisely and publish it, because the resolution-vs-conversation ambiguity is the single biggest source of buyer distrust in this category. Decagon’s explicit “you don’t pay if the AI fails” copy is the gold standard; Kustomer’s looser engaged-conversation meter invites scrutiny. Decide where to put the platform fee: a low seat or ticket floor plus a dominant resolution meter (Intercom, Gorgias, Zendesk AI) maximizes value capture from heavy users, while a free-tier-plus-overage entry (Yellow.ai at 500 free sessions) removes adoption friction for self-serve. If you sell voice, accept that minutes — not resolutions — are the honest unit, but surface the difference so voice-heavy bills don’t surprise customers. And if you gate the rate (Ada, Sierra, Uniphore), remember that opacity cedes the pricing narrative to third parties who already publish your numbers.

Explore this theme in the knowledge graph →