Per-Resolution Pricing for AI Customer Service, Explained
AI customer service is increasingly sold per resolution: you pay when the AI actually closes a customer's issue, not for seats or for every message it sends. It is a fair model in principle. In practice, everything depends on how "resolved" is defined and whether you can check it.
This guide explains how the major platforms define a resolution, how to audit the count yourself, and how per-resolution pricing compares to per-seat software and outsourced per-ticket support.
How per-resolution pricing works
The vendor counts conversations the AI handled to completion without a human, and bills a fixed amount for each. Conversations handed to a human are typically not billed. Some platforms add a monthly platform fee or a minimum; some include a bundle of resolutions in a plan and bill overage beyond it.
Intercom's Fin, for example, publishes a price of $0.99 per outcome, where a resolution is one type of outcome. Zendesk sells automated resolutions for its AI agents, with allocations included in plans and additional resolutions bought in advance or billed as overage. The common thread is that the unit of billing is a finished job, not effort.
This lines up the vendor's revenue with your outcome, which is why we price our own Support Resolution Desk the same way. But it also means the definition of resolution is the single most important line in the contract.
What counts as resolved
There are two broad approaches. A confirmed resolution is when the customer says the answer worked ("thanks, that fixed it"). An assumed resolution is when the AI gave an answer and the customer left without asking for more help. Intercom's published definition counts both, and only when Fin gave an actual answer, not a reply to a greeting or a clarifying question. If the customer returns for more help on the same conversation, Intercom says the resolution is deducted.
Zendesk describes a different check: conversations are evaluated after a period of inactivity, and a language model reviews the conversation text to verify the request was resolved without a human. Conversations that fail that verification are not counted.
Assumed resolution is where disputes live. A customer who gives up and emails you instead looks identical, in the chat log, to a customer who got their answer. Your audit should focus there.
How to audit the resolution count
Each month, pull a random sample of billed resolutions (start with 50 to 100) and read them. Label each one: truly resolved, resolved but with a wrong or risky answer, or abandoned. Track the share in each bucket over time. If the wrong or abandoned share is growing, you are paying for failures.
Next, cross-check with your other channels. Match billed resolutions against emails, calls, or new tickets from the same customer within a few days. A customer who comes back through another channel about the same issue was not resolved, even if the chat says so.
Finally, ask the vendor for the raw data: conversation IDs for every billed resolution, the rule that classified each one, and a dispute process. Any vendor confident in its count, including us, should hand this over without friction.
Routine tickets eating your team?
$1 per resolved conversation. Escalations to your team are not billed.
Per-resolution vs per-seat vs outsourced per-ticket
Per-seat helpdesk software charges for each human agent, whether they handle ten tickets or a thousand. It is predictable, but AI that deflects tickets does not lower the bill unless you cut seats. Per-resolution pricing makes the AI's cost scale with the work it does.
Outsourced support (a BPO or contractor team) is often priced per ticket or per hour. Per-ticket outsourcing bills for every ticket touched, including ones that bounce back. Per-resolution AI only bills when the issue is closed, but the AI cannot handle everything a trained human can.
To compare fairly, compute cost per resolved issue for each option: total monthly cost divided by issues that were actually solved. Include escalation handling, quality review, and the time your team spends correcting mistakes.
When per-resolution pricing gets expensive
High volume, simple questions can make per-resolution pricing cost more than a flat tool. If most of your tickets are "where is my order", a cheaper automation may answer them for less. Run the numbers at your real volume.
It also gets expensive when the definition is loose. If assumed resolutions are counted after a short inactivity window, abandoned chats get billed. Negotiate for a longer window, exclusion of conversations followed by contact through another channel, and credits for disputed resolutions.
How our Support Resolution Desk is priced
Setup is from $6,000. After that it is $1 per resolved conversation, escalations to a human are not billed, and there is a $500 monthly minimum. Setup covers connecting your helpdesk and knowledge sources, writing the policies the agent must follow, building an evaluation set from your real tickets, and a human review of anything that issues refunds or changes an order.
It is a fit if you have steady support volume with repeatable questions and a helpdesk you already use. It is not a fit if you get a handful of tickets a week, or if most tickets need judgment calls that you would not hand to a new hire either.
Key takeaways
- Per-resolution pricing bills for finished jobs, so the definition of resolved is the most important line in the contract.
- Assumed resolutions (customer left without asking for more) are where billing disputes come from. Audit them monthly.
- Compare options on cost per actually-resolved issue, including escalation and review time.
- Ask for conversation-level billing data and a dispute process before you sign.
Frequently asked questions
A conversation the AI closed without a human. Vendors differ on whether the customer must confirm it, or whether leaving without asking for more help also counts.
On the major platforms, default escalations are generally not billed. On our Support Resolution Desk, escalations to a human are never billed.
Setup from $6,000, then $1 per resolved conversation with a $500 monthly minimum. Escalations are not billed.
Start with 50 to 100 random billed resolutions a month. Grow the sample if you see a rising share of wrong answers or abandoned chats.
The 15-Day AI MVP Playbook
Day-by-day plan, a starter CLAUDE.md, the Lovable-to-production checklist, eval and cost worksheets, and 10 prompts. Pure value, no pitch.
Book 20 minutes, or send a brief
A former CTO replies. You leave with a written plan and a fixed estimate.
Prefer LinkedIn? Connect with Harish.