Zendesk Now Bills on Verified Resolutions. That Is a Bigger Deal Than It Sounds

At Relate 2026, Zendesk launched its Resolution Platform and moved to outcome-based pricing built on verified resolutions. Most coverage focused on the pricing. The more consequential detail is the word verified.

The problem verification solves

When an AI system resolves a conversation, something has to decide whether it actually worked. For most of this category’s short history, that something has been the AI itself.

That is a bad arrangement, and it is bad in a predictable direction. A model asked to grade its own output overstates. When the grade also determines the invoice, the incentive is unambiguous.

This is why quoted resolution rates in this market have been close to meaningless. A vendor reporting 70% and a vendor reporting 35% may be describing identical performance, with the difference living entirely in who counted and how.

Putting an evaluation step between the answer and the bill breaks that loop. Zendesk pairing it with a Context Graph that captures an audit trail of agentic reasoning and performance context is the same idea applied to explainability: if an agent is going to act on your behalf, you should be able to see why.

Why this is good for buyers even if you never buy Zendesk

Because it sets an expectation.

Once one major vendor bills only on verified outcomes and publishes an audit trail, “trust our number” becomes a harder position for everyone else. The right response as a buyer is to ask every vendor the same question and compare the answers.

The questions:

1. Who decides a resolution succeeded? The answering model, a separate evaluation, or the customer?
2. Does abandonment count? A customer who gave up is not a resolution.
3. Are handoffs billed? Charging for a conversation the AI could not handle means charging for failure.
4. Does a reopen retract the charge? If the customer comes back about the same issue within a fortnight, the first attempt did not work.
5. Can I audit a sample? If you are billed on a unit the vendor counts, you should be able to inspect it.

A vendor unwilling to answer all five in writing has told you something useful.

The number will go down, and that is fine

Expect verification to lower reported resolution rates. Fewer conversations qualify when something checks.

That is a feature. A lower honest number is more useful than a higher invented one, because you can plan against it. The failure mode to watch is a vendor whose reported rate does not move when verification is introduced, which usually means the verification is not doing much.

Do compare the whole picture rather than the rate. A stricter count at a higher unit price can land in the same place as a loose count at a lower one. The comparison that works is total cost divided by issues genuinely resolved, which we wrote up in how to build a cost per resolution model.

The part that still needs watching

Verification addresses who counts. It does not address what happens when volume spikes.

Zendesk introduced automatic overage billing in January 2026, charging teams past their committed monthly volume at the per-resolution rate. Verified or not, a resolution you did not plan for still bills.

So the second half of the question is containment: is there a hard spend cap, are you warned before crossing it, and what happens at the ceiling. Verification plus a cap is a model finance can approve. Verification without one is still an unbounded liability with better accounting.

Where we stand

Fidiora has always excluded abandonment, timeouts, and handoffs from billing, and publishes the definition in full at how we define a resolution rather than describing it in a contract you see after a sales process. There is a hard monthly spend cap you set yourself.

We think Zendesk moving the category toward verified outcomes is straightforwardly good, including for us, because the whole market becomes easier to compare when everyone has to say who counted.

Sources: diginomica on Relate 2026, Futurum Group. Verify current Zendesk rates and definitions on their pricing page.