Committed-volume AI pricing charges an overage rate when you exceed your monthly allowance. Zendesk introduced automatic overage billing in January 2026, and Gorgias publishes an overage rate above its standard one. Overage turns a discount into a penalty exactly when demand spikes.
Key takeaways
- Committed volume is a discount in normal months and a penalty in abnormal ones.
- Incidents and viral moments multiply volume within hours, not weeks.
- Ask whether you are notified before crossing the threshold, not just after.
- A hard spend cap is the only thing that makes usage pricing bounded.
Committed-volume pricing is a discount with a catch. You promise a monthly resolution volume, get a lower rate, and pay an overage rate on anything above it. In a stable month that is a saving. In an abnormal month it is a penalty applied at the worst possible moment.
Zendesk introduced automatic overage billing in January 2026, charging teams that exceed their committed monthly volume at the per-resolution rate. Gorgias publishes an overage rate of about $1.50 against a standard rate nearer $0.90 to $1.00.
Why this matters more in support than elsewhere
Support volume is not smooth and it is not fully under your control.
An outage, a carrier delay, a billing run that goes wrong, a viral social post, a product launch, a security advisory. Any of these can multiply contact volume within hours. Unlike most usage-based software, where consumption tracks your own activity, support consumption tracks your customers’ anxiety.
That produces a specific failure: you commit to a volume based on twelve normal months, then hit the one month that is not normal, and the overage rate applies to exactly the traffic you least wanted.
The compounding problem
There is a second-order effect worth understanding.
During an incident, a large share of the arriving conversations cannot be resolved, because the honest answer is that something is broken and engineering is working on it. Under per-conversation billing you pay for every one of those. Under per-resolution billing with an honest definition, you pay for none of them, because none were resolved.
So the pricing unit and the overage terms interact. Per-conversation billing plus committed volume plus an incident is the worst combination available, and it is not unusual.
What to ask before committing
What is the overage rate, precisely? Not a percentage above, an actual number. Compare it to the pay-as-you-go rate, because if overage costs more than not committing at all, the discount is narrower than it looks.
Am I notified before crossing the threshold? Automatic billing without warning is the specific complaint here. Ask for alerts at seventy and ninety percent of committed volume.
Is there a ceiling? A hard spend cap turns an unbounded liability into a budget line. Ask what happens at the cap: does the AI stop, throttle, or route everything to your team? Routing to humans is the right behaviour, because customers are still served while the spend stops.
Can I adjust the commitment mid-term? Some vendors allow upward adjustment and not downward. That asymmetry matters if your volume estimate is wrong in the cheaper direction.
What happened to customers during the last major incident? A reasonable question and a revealing one.
How to size a commitment
Not on your average month.
Pull the last twenty-four months of volume. Find the worst month. Commit somewhere between your median and your worst, not at your median, unless the overage rate is close to the committed rate.
The arithmetic is straightforward: the discount saves you money in every normal month, and the overage costs you money in every abnormal one. If abnormal months are more than about one in six, the discount frequently does not clear.
The cap is the thing
Everything above is manageable with one contractual term: a hard monthly ceiling you control.
With a cap, usage pricing is a bounded line item that finance can approve, and a spike costs you service degradation rather than an invoice surprise. Without one, the honest answer to “what is our maximum exposure” is that there isn’t one.
We wrote the full treatment of spend caps separately.
Where we sit
Fidiora has no committed-volume tiers and therefore no overage rate. You pay $0.59 per genuine resolution, and you set a hard monthly spend cap. When you approach it, Fidiora alerts you or routes everything to your team.
Abandoned chats, timeouts, and handoffs are never billed, which specifically addresses the incident case above: a wave of unanswerable questions generates no charge.
That is a simpler model with fewer discounts available, and we think fewer moving parts is the point. The argument we would make to anyone, including someone who never buys from us: before signing committed volume, price your worst month rather than your average one, and do not sign usage pricing without a ceiling.
Sources: reporting on Zendesk’s January 2026 billing change and published Gorgias overage rates. Verify current terms on Zendesk and Gorgias directly, since these change.
Frequently asked questions
What is overage billing in support software?
How do I avoid overage charges on AI support?
Why is overage worse during an incident?
Should I commit to a volume for a discount?
Resolve, don't deflect.
See Fidiora resolve a ticket, capture a lead, and keep the bill predictable.