AI Customer Support Pricing in 2026: Per-Resolution Isn’t the Fix

Zendesk bills you around $2 when its AI closes a conversation a human never touched. Fin, the company that used to be Intercom, charges $0.99 for the same event. Salesforce meters Agentforce in credits — roughly $0.10 an action, and an action is 10,000 tokens, so a chatty one counts twice. That is what AI customer support pricing looks like in September 2026.

Three vendors, three units, one shared conviction: the seat was the wrong thing to charge for. They're right about that. But the story the pricing pages are telling right now — that the meter moved from your headcount to your outcomes, and everybody wins — skips the part that matters. The unit changed. Who controls it didn't.

Why did this shift happen so fast? Follow the money. Agentforce hit $1.2 billion in ARR in Salesforce's Q1 FY27, up 205% year over year. Three weeks later Salesforce agreed to buy Fin for about $3.6 billion, picking up 30,000 customers and a support-specific model in one go. When a category grows like that, pricing stops being a finance decision and becomes a land-grab: whoever sets the unit early gets to define what everyone else's product is compared against. Per-resolution won that race. It didn't win it because someone proved it was fairest for buyers.

Per-seat deserved to die

We wrote about this in July, when we argued per-seat support pricing was quietly dying. Nothing since has changed our mind.

Per-seat billing assumed a stable relationship between people and value. Ten agents, ten times the throughput, ten times the licence. That link snapped the moment one agent with a decent AI assistant started clearing three times the queue. Seat pricing then does something actively stupid: it taxes you for hiring a weekend part-timer, it leaves you paying for the licence of somebody who left in March, and it makes "add a person to the tool for two weeks" a procurement conversation.

So when Zendesk moved autonomous AI into every Suite and Support plan in May 2026 and started billing on Automated Resolutions instead, that was a genuine improvement. Same for Fin's $0.99. You don't pay for shelf-ware. A quiet month is a cheap month. If the AI does nothing, you owe nothing, and there is something honest in a vendor saying only charge us when it works.

Credit where it's due. Outcome pricing is a better idea than seat pricing.

It's also a meter you don't own.

The vendor writes the definition, and rewrites it

Here's the thing about paying per resolution: somebody has to decide what a resolution is. That somebody is never you.

Fin counts a resolution when its AI answers and the customer either confirms it helped or leaves without asking anything further. Zendesk's Automated Resolution is a conversation that closes with no human escalation and no further customer activity for 72 hours. Both are defensible definitions. Both are also, unavoidably, the vendor grading its own homework — and each contains judgement calls that move money. A customer who gets a mediocre answer and gives up in frustration looks, to a billing system, exactly like a customer who got what they needed.

And the definitions move. In May 2026 Zendesk changed which resolutions draw down your allowance: Verified Resolutions count, while Assisted Escalations and Contained Resolutions became free. That particular change went in customers' favour. Fine. The point isn't that this one was bad — it's that a line item you budgeted for got redefined by a supplier release note, and you found out afterwards.

Agentforce has the same shape in a different costume. An action is up to 10,000 tokens. Go over and it bills as two; past 20,001 tokens, three. Your bill is now partly a function of how verbose your knowledge base is and how long your customers ramble, which is not a variable most support leads have on a dashboard.

Per-seat had one thing going for it that nobody says out loud: you controlled the meter. Headcount was your decision, made once a quarter, in a spreadsheet you owned. Resolution volume is your customers' decision, made continuously, and you find out what it cost at the end of the month. Ship a confusing release, get written up somewhere, run a promotion that goes better than planned — the support bill moves, and it moves in the direction you least want when things are already hard.

What AI customer support pricing costs at real volume

Numbers, because this argument is worthless without them.

Say you handle 3,000 support conversations a month. Not a huge company — a Series A SaaS, a decent-sized store.

At a 50% autonomous resolution rate, that's 1,500 billable resolutions:

• Fin at $0.99: $1,485/month, or $17,820 a year — on top of whatever you pay for seats.
• Zendesk at $2 pay-as-you-go: $3,000/month, $36,000 a year. At the ~$1.50 committed rate, $27,000.

Plan allowances barely dent it. Zendesk's Professional tier includes 10 automated resolutions per agent per month; with five agents that's 50 of your 1,500. Round it to zero.

Now be honest about the resolution rate, because vendors and buyers report very different ones. Fin's marketing cites AI agents resolving an average of 76% of support volume end-to-end, and Salesforce repeated that figure in its acquisition press release. Independent measurement lands much lower. We dug into that gap in our piece on what an AI containment rate actually measures — short version, the two camps are measuring different things and both numbers are technically true.

If your real rate is 20%, the same 3,000 conversations produce 600 resolutions: $594/month with Fin, $1,200 with Zendesk PAYG. Cheaper. Also worse, obviously, because 2,400 conversations still landed on a human.

Now list the things that move that bill which have nothing to do with how good your AI is. A pricing change brings a wave of "does this affect me" questions. A payment provider has an outage and 400 people ask the same thing in an afternoon. Black Friday. A shipping carrier loses a week. An influencer posts about you and half the new signups need hand-holding through onboarding. Every one of those is a spike in conversations, therefore a spike in resolutions, therefore a spike in spend — arriving in exactly the month you were already dealing with the underlying mess.

Support leads have historically been able to promise finance a flat number. That promise is gone, and nobody in the sales cycle mentions it.

Which surfaces the strangest property of this model. Your best month and your worst month are priced in opposite directions. The AI working brilliantly is expensive. The AI failing is cheap. You are, in a small way, buying insurance against your own product succeeding.

Is $0.99 still a good trade? Usually, yes. Work out your fully loaded cost per human contact — salary, tooling, management overhead, divided by contacts handled. It's the most useful number in a support budget and almost nobody has it to hand. Whatever it is, it's a lot more than a dollar. The per-resolution rate is not the scandal here. The lack of a ceiling is.

The incentive nobody prints on the pricing page

Two-thirds of a support queue is usually the same handful of questions.

The cheapest fix for those questions has never been AI. It's writing the answer down properly — a clear pricing page, a shipping policy that doesn't hide the exceptions, an error message that says what to do next. We've watched teams cut inbound volume meaningfully by rewriting four help articles, which is why we keep banging on about turning help centre content into something an AI can actually use.

Under per-resolution pricing, that work reduces your vendor's revenue.

We're not claiming anyone is sabotaging your docs. That's not how it works. But notice what nobody is incentivised to build: the report that says these 40 tickets a week exist because your checkout page is confusing, go fix the page and stop paying us for them. The tooling that gets built is the tooling that gets sold, and what sells is resolution volume going up. Deflection-by-writing-better-docs has no line item, no dashboard, and no account executive.

Per-seat pricing had bad incentives too — it just pushed on headcount instead of ticket volume. Every pricing model bends the product toward whatever it counts, and AI customer support pricing counts resolutions. That's worth knowing before you pick one.

What we'd actually ask before signing

Not a checklist for its own sake. Five questions that surface the terms people get surprised by later:

1. Show me a resolution that got billed and shouldn't have. If the vendor can't produce one from your trial data, they aren't looking closely enough at their own meter.
2. How do I audit the count? You want per-conversation billing detail you can export, not a monthly total.
3. What happens at 3x volume? Get the number for a bad month, not an average one. Then ask whether a cap exists.
4. When the definition changes, how am I told? "Release notes" is a real answer. It's just not a good one.
5. What does leaving cost? Not the contract — the migration. Where do the conversation history, the training data and the escalation rules live, and can you export them in a format that's useful somewhere else?

That last one is the whole game, and it's why we built ChatterMate the way we did. It's open source. You can self-host it, point it at your own model, and read the code that decides what your bot says. Nobody meters your success, because there's no meter to own — no per-seat licence, no per-resolution charge, no credits that expire.

Self-hosting isn't magic and we won't pretend otherwise. You'll pay for infrastructure, you'll pay your LLM provider per token, and somebody on your team owns the upgrade. Those costs are real. They're just costs you can see, forecast and negotiate, rather than a number that arrives on the 1st and moves with your customers' moods.

The support software industry spent a decade charging for chairs and is now charging for outcomes. It'll charge for something else in three years. So the question to ask about any AI customer support pricing model isn't which unit is fairest — it's whether the thing being metered is something you control. Right now, for most teams, it isn't.

Written by the ChatterMate team — we build an open-source AI support agent, and we're not neutral about any of this. If you want to see how we compare on price specifically, we've broken down ChatterMate vs Zendesk and ChatterMate vs Intercom, and we keep a running list of open-source customer support chatbots including our competitors.

Try it without a meter. ChatterMate is open source and free to start — your first 300 chats cost nothing, and you can self-host the whole thing whenever you want.

Sources

• Salesforce Signs Definitive Agreement to Acquire Fin — Salesforce Newsroom, 15 June 2026 ($3.6B, 30,000 companies, the 76% resolution claim)
• Intercom Fin Pricing: The Per-Resolution Cost Breakdown — on the $0.99 unit and how a resolution is counted
• Zendesk Pricing Plans — plan tiers and included allowances
• Understanding Zendesk AI pricing: a pay-per-resolution guide — reported $2 PAYG / ~$1.50 committed rates and the May 2026 allowance change
• Agentforce Flex Credits: real cost math — the 20-credit action and the 10,000-token threshold

Note on the Zendesk figures: Zendesk does not publish a per-resolution rate on its public pricing page. The $2 / $1.50 numbers come from third-party analyses of reported contract terms, so treat them as indicative and get your own quote.