The headline number, the per-resolution rate or the monthly fee, is rarely the one that decides what you actually pay. AI customer service pricing comes in at least five shapes in 2026, and the shape you sign up for changes your bill more than any single rate does.
Pick a model that charges per seat, and your costs stay flat while the AI quietly does more of the work, which means you stop capturing the savings. Pick one that charges per resolution, and the bill tracks the value the system actually delivers. Same vendor, same quality, very different economics over a year.
This is the hub for how that pricing works. We walk through the models you will see, what drives the bill under each one, the costs vendors tend to bury, and a simple way to estimate your own number before a single sales call.
The pricing models you will actually see
There are five common ways AI support gets billed, and a given vendor usually blends one or two of them.
| Model | How you're billed | Best for | Watch out for |
|---|---|---|---|
| Per-seat / per-agent | A license fee per human agent | Small, stable teams | You pay the same as the AI takes over more work |
| Per-resolution (outcome) | A fee each time the AI resolves a ticket | Teams automating real volume | How the vendor defines a "resolution" |
| Per-conversation / message | A fee per thread or per message sent | Predictable, low-complexity chat | Costs track chatter rather than value |
| Per-minute (voice) | Metered by call time | Phone-heavy support | Carrier costs and idle time |
| Hybrid | A base subscription plus usage or outcome overage | Teams wanting predictability plus upside | The overage rate and where it kicks in |
The market has been moving away from seats. Bessemer's AI pricing playbook documents the shift, with pricing migrating off per-seat licenses toward usage, outcome, and hybrid models. The logic is simple. When one AI agent can handle the volume of ten people, a per-seat fee stops describing the value being delivered.
Per-resolution pricing, and why outcome billing is winning
Outcome-based pricing charges you when the AI resolves a customer's issue. Intercom's Fin lists $0.99 per outcome. Zendesk announced its own move to per-resolution billing at its Relate 2025 event, with mid-market deals landing around $1 to $2 per resolution, negotiated rather than published. Across the category, outcome pricing is becoming the default for support.
The appeal is alignment. You pay when a ticket gets handled, so the vendor only makes money when the product works. That is also the catch worth reading closely: every vendor defines "resolution" differently. Fin counts a conversation that reaches a natural close, whether the customer confirms the answer or simply stops replying. Zendesk counts a request the AI closes without escalating to a human. Those definitions decide your invoice, so check them before you compare rates.
One definition detail matters more than the rest: what happens when the AI hands a ticket to a person. Some vendors still bill that interaction. Others treat a human escalation as free, since the AI did not resolve anything. Open.cx, for one, does not charge for a ticket it hands to a human. That single line can swing the real cost of a noisy month.
What one resolution costs, by vendor (2026)
Published or reported per-resolution rates from each vendor’s own pricing page or announcement. Zendesk is negotiated, not published.
* Zendesk is reported, not published (negotiated mid-market rate). Bars scaled to a $2.00 maximum.
What actually drives your bill
Under any model, four things move your monthly number:
- Volume. Total conversations or tickets coming in.
- Automation rate. The share the AI resolves on its own. A higher rate means more resolutions billed under outcome pricing, and more savings under any model.
- Channels. Whether voice, chat, email, WhatsApp, Slack, and social are all included or priced as add-ons. Open.cx folds every channel into the one per-resolution rate, but plenty of vendors meter them separately.
- Voice minutes. Phone support carries carrier costs on top of the platform fee, which is why voice is often metered separately. We break the phone math down in AI phone agent cost and pricing.
Then there are the multipliers that hide outside the headline rate. The clearest example: Fin's $0.99 is per outcome, but running it inside Intercom's helpdesk also requires a paid seat at $29 per seat per month, so the resolution fee is only part of the cost. Setup fees, model pass-through charges, and renewal escalators do the same quieter work on the total.
The headline rate is not the bill: Fin at 2,000 resolutions/mo
Worked example using Intercom Fin’s published rates: $0.99 per outcome plus the $29/seat helpdesk fee it requires. 5 seats assumed.
Minimums, and whether AI is worth it at low volume
Outcome-priced vendors usually set a floor. Fin requires a minimum of 50 outcomes per month. Floors exist because a few hundred resolutions a month barely covers the cost of running and supporting the system.
If your ticket volume is small, the per-unit math can look unfriendly, and a minimum can mean paying for resolutions you never use. That does not always rule AI out, since the time it returns to a tiny team can still be worth the floor, but it does change the calculation. We work through the threshold in does AI support make sense at low ticket volume.
The hidden costs to check before you sign
The rate on the first slide is rarely the whole story. Before you commit, get every one of these in writing:
- Setup and implementation fees. One-time charges to get integrated and trained.
- Stacked seat fees. Helpdesk seats you still pay for underneath the AI.
- Overage rates. What you pay above your committed volume. Some vendors bill every resolution over your committed amount with no cap, so a traffic spike can land an unexpected invoice.
- Model pass-through. Whether the underlying LLM cost is bundled or billed on top.
- Renewal increases. The percentage your rate climbs at renewal.
Comparing vendors without getting fooled
Sticker rates are not comparable across models, so normalize everything to a fully loaded monthly cost. For each vendor, add the resolution or seat fee, any setup cost, expected overages, and the helpdesk seats you keep paying for. Then divide by the resolutions you expect to actually get.
The crossover is straightforward once the numbers are loaded. Per-resolution rewards you as your automation rate climbs, because you only pay for work the AI takes off your team's plate. Per-seat can come out cheaper at very low volume, where a single license covers everything. The more the AI resolves, the more an outcome model works in your favor.
Two comparisons are worth running on their own: whether AI is cheaper than your current support, for the build-versus-buy math, and AI support pricing for BPOs and resellers if you resell.
A quick way to estimate your own cost
You can sketch your number in three steps:
- Resolutions. Monthly conversations multiplied by a realistic automation rate. If you handle 10,000 conversations and expect the AI to resolve 60%, that is 6,000 resolutions.
- Platform cost. Resolutions multiplied by the per-resolution rate.
- Everything else. Add seats, setup, and voice carrier minutes if they apply.
If you would rather not do the arithmetic by hand, our ROI calculator and support budget tool run it for you, and the team size calculator shows how the headcount math shifts as automation rises.
A pricing model is really a forecast of the vendor's confidence. A vendor that only gets paid when it resolves your ticket is betting on its own resolution rate. A vendor that charges per seat gets paid whether the AI earns its keep or not. Read the model as a signal first, then run your own numbers against it.