Zendesk's AI Resolution Allowance Is Now a Dial You Manage: Alerts and a Self-Serve Raise

Zendesk's October 2026 release roundup includes two changes that are easy to scroll past and worth stopping on if you run Zendesk with AI agents. Admins can now choose who gets emailed about automated-resolution usage and resolution-allowance usage. And eligible account owners and billing admins can now raise the resolution allowance themselves, from inside the product.

Put together, those two changes alter who owns the allowance. It used to be a number agreed at contract time and revisited at renewal. Now it is something someone in your team watches, gets warned about, and adjusts. This piece is about what that means in practice: who should own it, what to set up this month, and the questions worth asking any helpdesk vendor about AI volume.

What Zendesk shipped

The roundup describes the two items in its own words. On notifications:

"Notifications for automated resolutions + resolution allowances: Configure which admins receive email notifications for automated resolution usage and resolution allowance usage."

On raising the allowance:

"Increase your resolution allowance: Eligible account owners and billing admins can increase resolution allowance directly from Subscription or the Resolution allowance dashboard to avoid hitting usage limits."

And the roundup attaches an action to the notifications change, aimed at account owners, billing admins and admins who monitor usage:

"Review notification recipients and thresholds so the right owners get alerted before you hit limits."

Note the words "eligible" and "thresholds". The raise option is for eligible account owners and billing admins only, and the warnings are only as useful as the thresholds and recipients you configure. Zendesk's linked announcements cover the details for your plan; check them before you build a process on top of this.

From a contract term to an operational dial

The interesting part is not either feature on its own. It is that, together, they move a decision from procurement to operations.

Before, the allowance mostly mattered twice a year: when you bought it and when you renewed. Now there is a warning that lands in someone's inbox before the limit, and a button that someone can press to raise it. That creates three questions that did not have to be answered before:

• Who is told? If the email goes to a billing admin who never looks at support quality, the warning arrives but nobody who can act on the cause reads it.
• Who decides? Raising the allowance is now a click. Clicks get made in a hurry, at the end of a busy week, by whoever has the permission.
• What is the alternative to raising it? Usage climbs for good reasons (more customers, a launch) and for bad ones (an AI agent resolving questions it should have handed to a person, or answering the same question badly enough that customers ask again). The warning tells you usage is high. It does not tell you which.

What to set up this month if you run Zendesk

None of this needs a project. It needs an hour and a short agreement between whoever owns support and whoever owns the bill.

1. Pick recipients on purpose. Include at least one person who owns support quality, not only the billing admin. The person who can tell a healthy spike from an unhealthy one should get the email.
2. Set thresholds early enough to act. A warning the day before the limit leaves only one option: raise it. An earlier warning leaves time to look at what the AI is actually resolving.
3. Write down who may raise the allowance, and when. One line in your support runbook is enough: who decides, what they check first, and who they tell afterwards.
4. Look before you raise. When the warning lands, review a sample of recent automated resolutions. Were they genuinely resolved? Did the same customers come back? If the answers are good, raising the allowance is a sensible spend. If not, the fix is in your knowledge base or your hand-off rules, not your subscription.
5. Review it monthly. Put allowance usage on the same agenda as response times and satisfaction, so it is read alongside the quality numbers it depends on.

Questions to ask any helpdesk vendor about AI volume

Whatever you use, AI usage is now a line item someone has to manage. These questions apply to every vendor, including us:

• How is AI volume stated: per resolution, per reply, per seat, or as a flat add-on?
• Who gets warned as usage rises, and can you choose?
• Who can change the allowance or plan, and does it need a sales conversation?
• Can you see what the AI actually did with each conversation, so you can judge whether the usage was worth it?

How DeskLeap states it

We are a different shape, so the honest comparison is about how volume is stated rather than a price race. The DeskLeap platform (live chat, tickets and knowledge base) is free, and human agents are not seat-priced. The only paid part is the optional AI Agent: a flat $29 per month for each AI Agent, which includes 500 AI replies per month (100 during the trial).

That is a fixed monthly add-on with a stated monthly volume, rather than an allowance with alerting and a self-serve raise. Neither model removes the job described above: whichever you use, someone should still read what the AI is answering and decide whether it is helping your customers.

The short version

Zendesk now warns chosen admins about automated-resolution and allowance usage, and lets eligible owners and billing admins raise the allowance themselves. That makes the allowance an operational dial. Decide who hears the warning, who may turn the dial, and what they check first, before the first warning arrives.

Source

Zendesk, October 2026 release roundup: Support, Admin Center and Platform (read 12 October 2026). Quotations are verbatim from that page.