Zendesk's Outcome-Based Pricing: Shifting to 'Verified Resolutions' and Multi-Tier Billing to Solve Customer Friction

Zendesk's Outcome-Based Pricing: Shifting to 'Verified Resolutions' and Multi-Tier Billing to Solve Customer Friction

Zendesk's transition to outcome-based pricing (OBP)—where customers pay approximately $1.50 per "automated resolution" under committed contracts or $2.00 under pay-as-you-go rates—is one of the most watched commercial experiments in the enterprise software market. While Zendesk's private equity partner Permira reports that the company has "doubled adoption of its outcome-based pricing model within its customer base," the transition from traditional seat-based licensing has caused significant customer anxiety over unpredictable billing¹, "gaming" of the 72-hour quiet window, and disputes over what truly constitutes a "resolution."

To directly address this billing friction, Zendesk announced a major structural update to its billing mechanism at Zendesk Relate 2026 (held in Denver in May 2026), introducing a three-tiered automated resolution framework that replaces its previous binary billing system. Under this new model, conversations are evaluated after a 72-hour period of inactivity and categorized into three distinct tiers:

1. Assisted Escalation: The AI agent contributed to the interaction, but it was ultimately escalated to a human agent. This tier is free and does not count against the customer's resolution allowance.
2. Contained Resolution: The AI agent handled the session to completion with no customer follow-up within 72 hours, but the session failed a secondary Large Language Model (LLM) verification check. This tier is also free, protecting customers from paying for "deflections" where a user simply gave up or became frustrated.
3. Verified Resolution: The AI agent resolved the interaction, there was no follow-up within 72 hours, and the conversation successfully passed the secondary LLM check confirming the customer's issue was satisfactorily resolved. This is the only tier that counts against a customer's monthly allowance or incurs usage-based charges.

This "double-verification" model represents a major step forward, but industry analysts and operators warn that it introduces new operational and trust bottlenecks:

• The Verification Bottleneck: As AI agents handle increasingly high volumes of tickets, the sheer speed of automated resolutions outpaces human auditing capacity, making the secondary LLM verification model the primary arbiter of commercial billing.
• The Explainability Gap: Without granular audit trails, the "verified resolution" risks becoming a commercial black box. To combat this, Zendesk is deploying a "Context Graph" and "operational memory" audit trails to provide explainable reasoning behind why a specific outcome was billed as resolved.
• Financial Predictability: For corporate finance teams, OBP remains difficult to budget. Unlike predictable seat licenses, AI agent costs fluctuate with seasonal customer demand, meaning a company's support budget can spike dramatically during high-volume periods (such as holiday shopping).

Verbatim Evidence

From Zendesk Relate 2026 - Zendesk prepares for an outcome-based future built on ‘verified resolutions’ on diginomica:

"According to the company, every resolution it charges for will be verified in two ways — the responsible agent first confirms that it has resolved the interaction, and then a dedicated evaluation model checks its homework."

"Zendesk will need to balance existing subscription revenue with outcome-linked pricing. Both customers and Zendesk itself will want financial predictability, while agent costs will likely fluctuate with demand. And whatever the eventual model, both sides will need confidence in the definitions, evaluation methods and dispute mechanisms that sit behind the notion of a 'verified resolution'."

From About automated resolution tiers on Zendesk Help:

"After a 72-hour window with no customer follow-up, a verification process is performed by an LLM that evaluates the text of the conversation to confirm that the customer’s request was satisfactorily resolved. Conversations that pass this verification are considered a Verified resolution."

"Conversations that don’t pass this verification are considered a Contained resolution." [Note: Zendesk's documentation specifies that Contained resolutions "do not count against your resolution allowance".]