Per-Resolution Pricing Explained - Why Your Bill Grows as the AI Improves (2026)

At $0.99 per resolution, an AI agent handling 10,000 tickets a month costs $9,900. In most markets that is more than the loaded cost of the support staff it replaced. That is the whole problem, and it is not a pricing tier issue — it is the model.

Software usually gets cheaper per unit of value as it works better. Per-resolution billing inverts that. Every ticket your agent successfully closes is a line item. Improve your help centre, tune your prompts, widen the agent's scope, and your bill rises in direct proportion to your success.

“It's structural: per-resolution pricing means every correct answer costs you, so you're financially punished for making Fin work well.”— r/CustomerSuccess

The break-even is lower than vendors imply

Rough arithmetic at $0.99 per resolution, ignoring seat costs, which you should not ignore:

Add Intercom seats underneath — one user reported a $74 monthly seat fee before any AI usage, and the crossover arrives earlier still. The model suits low and moderate volume. It works against you precisely at the scale where automation is supposed to pay off.

Nobody agrees what a resolution is

This is the part missing from every comparison article we found, and it decides your invoice more than the headline rate does. Vendors define a billable resolution differently. Some bill when the customer does not reply within a window. Some bill when the AI produces an answer at all. Some bill only on a positive signal from the customer.

A platform at $0.69 that bills on non-reply can cost more than one at $0.99 that bills on confirmed resolution. Ranking vendors by published rate is close to meaningless without this.

We are reading every vendor's billing definition from their own documentation and will publish them side by side. Until then this post does not characterise any individual vendor's definition second-hand.

What the complaints actually look like

This is not a theoretical objection raised by competitors. It comes from customers, repeatedly, in specific numbers. One r/SaaS thread with over seventy comments described billing rising 120% after enabling AI. An analysis of 215 Intercom reviews found the per-resolution charge described as a trap. A thread on r/customerexperience asking what teams pay drew thirty-five replies, one of which opened: we just got rid of Fin, cost way too much and did not work the way we needed.

The product is not the complaint. Nearly every critical thread concedes Fin works well before objecting to the price. That is an unusual pattern and worth noticing — it means the dissatisfaction is economic, not technical.

When per-resolution is the right choice

It genuinely is, sometimes. Under roughly 2,000 monthly resolutions the bill is predictable and clearly cheaper than headcount. If your volume is seasonal, paying only for what you use beats carrying seats through a quiet quarter. And the incentive alignment is real: a vendor paid per resolution has a reason to care whether resolutions happen.

Sierra argues this position publicly and consistently, and the argument has merit. It is simply not a universal one.

The rates, side by side

Published per-resolution rates span more than three times on what is nominally the same unit, which is the first sign the unit is not standardised.

The crossover, worked

Corrected 24 August 2026. This section previously priced Freddy sessions at $0.10 and put the crossover near 30%. The rate is $0.49 — Freshworks publishes “First 500 sessions included. $49 per 100 sessions” — and at the right rate the crossover moves to roughly 55%, which reverses what this section concluded. The old figure was withdrawn in our own billing dataset in August and did not reach this paragraph for three weeks. The arithmetic below is now shown in full so it can be checked without trusting us.

Twelve agents, 9,000 monthly tickets, $0.99 per resolution, against Freshdesk Pro at $59 a seat with Freddy sessions at $0.49.

The per-seat side does not move with the resolution rate, which is the whole point of it. Twelve seats at $59 is $708. Nine thousand tickets opens nine thousand sessions, the first 500 of which are included once per account, so 8,500 bill at $0.49 for $4,165. Total $4,873, flat, whatever the agent achieves.

The crossover sits near 55%, not 30%. That matters because 55% is above what most deployments reach: the vendors' own published resolution rates cluster in the thirties and forties once you read what they count, and our own reading of nine definitions found the number moves seventeen points on a change of counting rule alone.

So the honest version of this section is weaker than the one it replaces. Per-resolution billing is cheaper than seats-plus-sessions across most of the range a real deployment occupies, and it only loses once the agent is resolving more than half of everything.

The structural point survives, and it is the one worth keeping: a per-resolution deal gets more expensive precisely as the product gets better, so a contract that looks cheap during evaluation is repriced by your own success. Worth saying on the call to hear the answer.

Check it yourself in about ten minutes. Take your own ticket count, subtract the 500 included sessions, multiply by $0.49, add your seat count times your tier price. Then multiply your ticket count by your vendor's per-resolution rate and by the resolution rate they quoted you in the demo. The point where the two lines meet is your crossover, and it is the only number in this post that is actually about you.

The threshold is a pricing control

An underappreciated property of this model. Your confidence threshold — the certainty the agent must reach before it answers rather than escalating — moves quality and cost in the same direction at the same time.

Read the bottom row carefully. Under per-resolution billing, the setting that degrades your customer experience also increases what you pay, and the vendor benefits from both. That is not an accusation of bad faith — nobody is secretly moving your threshold — but it is a genuine misalignment worth naming before you sign.

It also means the standard cost-control advice does not apply. You cannot economise by turning the agent down, because turning it down is exactly what you bought the agent to avoid.

Questions that change the contract

• What triggers a billable resolution, in writing — including abandonment mid-conversation and a customer returning three days later about the same issue.
• Is a conversation the agent escalates to a human billed at all?
• Is there a volume tier, and at what monthly count does the rate change? Published rates are rarely the only rates available.
• What is the renewal rate, and is there a cap on increases?
• If we improve our documentation and the resolution rate rises 20 points, what does that do to the invoice? Ask it exactly like that and watch the answer.

That last question is the one worth asking out loud. It is the whole structure of the model expressed as a scenario, and a vendor who has thought about the misalignment will have a real answer — a volume tier, a cap, a blended rate. One who has not will change the subject.

What to do before signing

• Model the invoice at your actual monthly volume, not the volume in the vendor's ROI calculator.
• Get the billable-resolution definition in writing before the trial ends.
• Ask what happens when a customer abandons mid-conversation. Billed or not billed?
• Model the same volume against a per-seat and a flat-rate competitor. If per-resolution loses at your scale, that is the answer.
• Check whether seat costs are required underneath. They usually are, and comparisons usually omit them.

None of this requires trusting us. It requires an hour with a spreadsheet and a direct question to a salesperson.

WRITTEN BY AR · UPDATED 2026-07-28

I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.

Editorial policy