Contents
At a glance
- Unit
- One interaction the AI agent successfully resolved
- Billable
- Yes - the only tier of the three that draws down the allowance
- Introduced
- 18 May 2026
- Contained but not verified
- Free
- Assisted escalation
- Free
- Published rate
- None. Zendesk publishes no per-resolution price (checked September 2026)
- Metric to measure
- Verified share - the proportion of AI conversations reaching verified resolution
The definition, exactly
A Zendesk verified resolution is the top tier of the three-tier outcome model Zendesk introduced on 18 May 2026. Zendesk words the bar as "the AI agent successfully resolved the interaction". Note what that does not say: containment alone is not enough, because a contained interaction is one the agent merely finished without escalating.
It is the only one of the three tiers that consumes your Zendesk resolution allowance. Assisted escalation, where the AI contributes and a human finishes, does not count. Contained resolution, where the AI completes the request without escalating, does not count either. Zendesk's documentation states that exemption for both tiers in plain language.
Why the second condition is the whole story
Almost every AI support product on the market bills on containment or something close to it. Containment is easy to measure and easy to game: end the conversation, do not escalate, count the win. A customer who gives up and closes the chat looks identical to a customer whose problem was solved.
Verification is an attempt to close that gap. A model reviews the exchange and judges whether the request was in fact resolved, and only the exchanges that clear that judgement bill. Structurally, this is an eval wired directly into the billing meter - the same technique you would use offline to score an agent's output, applied inline to decide what you owe.
That design has a consequence worth stating clearly: an outcome that a containment-billed product would charge you for can be free here. A conversation the AI ended, that a human never touched, that did not resolve the underlying request, is a contained resolution and not a verified one, and it costs nothing against the allowance.
What this means for measuring a pilot
The metric to extract from a trial is the verified share: of all AI agent conversations, what proportion reached verified resolution. That single ratio is what converts your ticket volume into a bill, and it is far more variable across accounts than any published benchmark suggests, because it depends on your knowledge base, your ticket mix and how narrowly your topics are scoped.
Three things reliably move it. Documentation coverage: a request whose answer exists in a clear article is much likelier to be resolved and verifiable than one that requires account-specific reasoning. Topic scope: narrow, transactional intents verify well; open-ended troubleshooting does not. And escalation policy: an agent configured to hand off early produces assisted escalations, which are free but also unresolved, so you are trading bill against outcome. See handover for how to design that boundary deliberately rather than by default.
Note the incentive this creates. Improving your help centre increases the verified share, which increases the billed number. That is the meter working as intended - you are paying for more problems actually solved - but it means a "we will reduce costs by improving documentation" line in a business case has the sign backwards on this meter specifically. Model it as more resolutions at the same rate, and justify it on deflected human handling time instead. See ROI for how to frame that side of the calculation.
The rate is still not public
Knowing precisely what a verified resolution is does not tell you what one costs, and Zendesk publishes no dollar rate for it. The migration documentation for converting an existing automated resolution balance into the new tiers says the conversion is "based on a fixed pricing model" and instructs customers to "Contact Zendesk Sales for details." That is as specific as the public record gets, as of September 2026.
This is the honest state of the market: the unit is documented to the sentence, the price is behind a sales call. Figures in the region of one to two dollars per resolution circulate on comparison sites, frequently published by competitors, and we have not been able to source any of them to Zendesk. Treat them as unverified and do not put one in a budget.
Questions that get you a real number
Ask what the verified share looks like for accounts with your ticket mix, and ask for it as a range rather than a best case. Ask whether a reopened ticket produces a second verified resolution. Ask whether verification failures are visible to you in reporting, because you want to see the conversations that were contained but not verified - those are your content gaps, and they are free to discover. Ask what happens on overage and whether the rate holds.
Then compare like for like. The Fin resolution is the same category of outcome unit with a published list price, so you can build the comparison from a public page on one side and only a quoted rate on the other. That asymmetry is itself a procurement fact, and it belongs in the evaluation alongside product quality. For everything the resolution meter does not cover - implementation, content maintenance, the human queue that still handles escalations - see total cost of ownership.
Zendesk verified resolution FAQ
What is a verified resolution in Zendesk?
Zendesk defines it as an interaction the AI agent successfully resolved. It is the top tier of the three-tier model Zendesk introduced on 18 May 2026 and the only tier that consumes your resolution allowance.
What is the difference between a contained resolution and a verified resolution?
A contained resolution is one the AI agent completed without escalating to a human. A verified resolution additionally passed an LLM check confirming the request was actually resolved. Containment alone is free; only verification bills. That makes verified a strictly higher bar than the containment metric most AI support vendors sell on.
How much does a Zendesk verified resolution cost?
Zendesk does not publish a rate. The pricing is contractual, and Zendesk's migration documentation directs customers to contact sales for the figure. Dollar amounts circulating on third-party comparison pages cannot be traced to a Zendesk source and should not be used for budgeting.
Does improving my help centre increase my Zendesk bill?
On this meter, yes - better documentation makes more requests resolvable and verifiable, so more conversations reach the billable tier. That is the meter working correctly, because you are paying for problems genuinely solved. Justify the investment on reduced human handling time rather than on a lower resolution count.
Can I see which conversations failed verification?
Ask for this explicitly during evaluation. Contained-but-not-verified conversations are the most useful diagnostic you have - they are exactly the topics where your agent ends the chat without solving the problem, and under this model they cost nothing to discover.
Primary source
Zendesk - automated resolution tiers
Checked September 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what zendesk verified resolution means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
