On this page
Quick Answer
Customer support software bills on one of three units: agent seats, resolved conversations, or usage tiers. The cheapest depends on your agent-to-ticket ratio, not on the sticker price.
Seats favor teams where humans handle most tickets. Resolutions favor heavy volume that AI closes. Usage tiers fit lean teams with uneven demand. Outcome pricing is still concentrated among enterprise AI vendors such as Sierra, so most smaller teams will be quoted a seat fee with an AI meter attached, and that blended number is the one to price.
Key Points
- Customer support software bills on one of three units: the human agent seat, the AI-resolved conversation, or a volume band of tickets, conversations or credits.
- Zendesk launched outcome-based pricing for AI agents in August 2024, with reported rates of $1.50 per committed resolution and $2.00 pay-as-you-go .
- Intercom's Fin counts an assumed resolution after 24 hours of customer silence, while Zendesk confirms one only after 72 hours of inactivity, so identical conversations bill differently.
Seats, resolutions or usage: the billing unit decides what the invoice counts.
The same tool can be cheap for one team and expensive for another. Its billing unit, whether seats, resolutions or usage, decides which side of that line you land on.
The three models show up well beyond customer support. In a March 2026 r/ycombinator thread on outcome-based software, founders sorted the AI market into the same three groups. Harvey, Cursor and Microsoft Copilot sell seats. Lovable, Replit and Base44 charge for credit usage, which one commenter described as pricing on inputs rather than outcomes. Sierra was singled out as the leader on per-resolution pricing in customer service, with a catch: it works only with enterprises.
Support software adds its own pressure. Per-agent billing looks tidy until more of the team needs access. AI then changes the arithmetic underneath it. One major help desk incumbent's CTO said the rule-based chatbots it previously sold reached about 20% to 30% automation on a good day, and generative agents built on frontier models are now replacing them. Every ticket those agents close is a ticket no seat had to touch.
That is the gap I want this guide to close. Most pricing explainers list vendors. Few define the underlying billing unit, the thing your invoice actually counts, or say where each one wins. Before any demo, I would ask each vendor which of the three units will appear on the first invoice, and which will appear only once AI usage grows.
So the starting point is the oldest unit on the invoice, and the reason it still anchors most quotes.
Per-user billing remains the most common way SaaS is sold, yet customer support is where it is breaking first. Zendesk's platform handles over 4 billion resolutions, mostly by humans, alongside roughly 800 million AI interactions in 2025 by the company's own estimate, and 20,000 customers already use its AI to generate responses. Once a real slice of that work runs without a person, a price tied to people stops tracking the work.
Support pricing therefore sorts into three models. Per-seat pricing follows headcount. Per-resolution pricing follows what AI closes on its own. Usage-tiered pricing follows volume bands of tickets, conversations or credits. Each moves cost risk to a different place.
The first question most buyers ask is the price per agent. I think that is the wrong place to start. Ask each vendor whether chat, phone, advanced analytics or a knowledge base costs extra, since the All Rankings by Gabi explainer notes that some help desks sell them as add-ons. The research section below walks through how those extras stack up on real quotes. Count your monthly tickets and your active agents before reading the definitions below; that pair of figures is what each model prices against.
How does customer support software pricing work?
Customer support software bills on one of three units: the human agent seat, the AI-resolved conversation, or a volume band of tickets, conversations or credits. Everything else is packaging.
Before comparing any two vendors, sort each quote with three questions:
- What unit does the invoice count: people, outcomes or volume?
- Does that unit grow with headcount or with ticket volume?
- What happens to the bill in your busiest month?
ProductLed's 2023 guide to SaaS pricing defined a pricing model as "a combination of the value metrics you structure your billing around and the pricing tactics you use to package and present your product." The value metric is the unit you actually pay for. Tiers, free plans and trials are tactics stacked on top of it. In support software the tactics vary endlessly, but the metric collapses into three families.
| Pricing model | What you pay for | Cost driver | Budget predictability | Published example |
|---|---|---|---|---|
| Per-seat | Each human agent login | Headcount | High | Zendesk from $19 per agent per month |
| Per-resolution | Each conversation AI closes without a human | AI success rate and traffic | Low | Fin $0.99 per outcome |
| Usage-tiered | A band of tickets, conversations, AI replies or credits | Total volume | Medium | Gorgias plans from $10 per month |
Per-seat pricing charges for every agent who logs in. Zendesk lists plans from $19 per agent per month, while Help Scout and Front start at $25 per user or seat. The same ProductLed guide called per-user billing "the most common pricing plan for SaaS businesses." Headcount sets the bill.
Per-resolution pricing charges only when an AI agent closes a conversation on its own. Fin, formerly Intercom, charges $0.99 per outcome, and Kayako charges $1 per ticket resolved. Here the bill follows AI success, so it rises with traffic.
Usage-tiered pricing charges by volume band rather than by person. Gorgias sells ticket-based plans starting at $10 per month, and Enjo sells bundles of AI replies, from $95 a month for 1,000 replies, with unlimited human seats on every plan. Volume sets the bill, which makes it steadier than per-resolution and looser than seats.
The common assumption is that a vendor's starting price tells you what a tool will cost. It rarely does. A review of 5 sources, from a 2023 pricing guide to 2026 vendor price lists, suggests the billing unit predicts the invoice far better than the sticker. Headcount, outcomes and volume seldom grow at the same rate, so two tools with identical entry prices can drift apart within a quarter.
Our reviews are written and edited by our editorial team, led by Michael Kansky. If you are working through our rankings of AI customer support software, check which of the three units each tool bills on before you compare headline prices. That single check explains most of the gap between a seat-priced help desk and an outcome-priced AI agent, and it is exactly where vendors are now repricing.
Why are support vendors moving from per-seat to per-resolution pricing?
AI agents shrink the headcount that seat pricing bills against. Vendors are therefore moving to a unit that grows when automation works: the resolved conversation.
The shift is already measurable. Seat-based pricing fell from 21% to 15% of SaaS companies in twelve months, and one industry projection expects 70% of vendors to move away from pure per-seat models by 2028. Support feels this first, because support is where AI replaces typed replies most directly.
The conflict of interest is easy to state. A founder on r/SaaS laid it out: deploy an AI agent that automates 80% of support work, cut 10 people, and "the SaaS vendor loses 10 seats of revenue." In the same thread, a commenter at a Series B company that sells on seats reported customers asking "why do I need 10 seats if the AI does most of the work." That company, the commenter said, absorbs the churn and hopes new customers make up for it.
I see this as the core flaw of seats in an AI era. The vendor earns less when its product works better. Buyers have noticed.
Zendesk has framed its own change as a move from seat economics to resolution economics. In that framing, a seat is a human-powered factory with a known software cost and a known throughput, such as 60 tickets a day. Once AI absorbs part of that throughput, the seat stops measuring the work. Zendesk launched outcome-based pricing for AI agents in August 2024, billing per Automated Resolution, with reported rates of $1.50 per committed resolution and $2.00 pay-as-you-go.
A separate r/SaaS discussion described the result as pricing split into two axes: access, sold as seats, and units of process, sold as credits, actions, runs or resolutions. Its original poster asked whether per-seat pricing still makes sense, or punishes both buyer and vendor, when one agent can replace 3-5 humans.
The first contract question, then, is where the vendor's written definition of a billable resolution lives, and who is allowed to change it. A resolution is whatever the vendor's meter says it is, and the definitions differ in ways that move the invoice:
- Zendesk confirms an Automated Resolution only after 72 hours of customer inactivity following an AI-only ticket.
- Intercom's Fin counts an "assumed resolution" when the customer stays silent for 24 hours after its last answer, so a frustrated customer who leaves is billed like a satisfied one.
- HubSpot moved its Customer Agent on April 14, 2026 to roughly $0.50 per resolved conversation; before that it charged about $1.00 per conversation whether or not anything was resolved.
Shorter windows bill sooner. Silent exits still count. My advice is to compare the definitions before the prices, and to apply the same scrutiny when a help desk with built-in live chat layers an AI agent on top of its seats. The next section matches each model to a team's agent-to-ticket ratio.
Which pricing model is cheapest for your agent-to-ticket ratio?
Per-seat usually wins when humans handle most tickets. Per-resolution wins when AI closes a large share of heavy volume. Usage tiers suit lean teams facing uneven traffic.
Match the model to your support load in three steps:
- Divide monthly tickets by the number of agents who answer them, and note whether that ratio is climbing.
- Measure what share of tickets AI closes without a human in a pilot, not in a vendor demo.
- Price every shortlisted tool at your normal month and your busiest month before comparing totals.
| Your situation | Agent-to-ticket ratio | Likely cheapest model | What to watch |
|---|---|---|---|
| Small, human-led team; AI assists rather than answers | Few tickets per agent, stable | Per-seat | Seats you keep paying for after people leave |
| Growing team still hiring agents | Rising with headcount | Per-seat with capped scaling | Per-agent escalators and forced plan upgrades |
| High volume of repetitive questions; AI closes many of them | Many tickets per agent | Per-resolution | Resolution definition, reopen window, traffic spikes |
| Lean team with seasonal or spiky demand | Many tickets per agent, uneven | Usage-tiered with hard caps | Overage charges and monthly AI minimums |
Per-seat fits small, stable, human-led teams. Supportbench's published scheme shows what capped scaling looks like: $32 per agent per month, plus $2.50 for each additional agent after 15, with the per-agent cost capped at $150 and accounts of 60+ agents moved to its Enterprise plan. AI is included rather than metered. The weakness is structural. The seat bill does not fall when deflection rises, and idle licenses keep billing. The All Rankings by Gabi explainer on help desk pricing makes the same point from the other side: per-agent pricing "sounds simple until more team members need access."
Per-resolution fits high-volume teams where AI closes a large share. One vendor's published model puts Fin at about $990 a month at 2,000 tickets and about $4,950 at 10,000 tickets, assuming 50% AI resolution and before any seats. Cost rises in step with success. Insist on a written resolution definition and a reopen window before you sign.
Usage tiers fit lean teams with uneven demand, provided the caps are hard. Richpanel, for example, prices human seats at $99 a month on an annual commitment plus about $0.20 per AI conversation, with a $200 monthly AI minimum. That minimum is a floor. Quiet months cost the same as busy ones up to that line.
I will admit a bias toward predictability. A bill finance can forecast is worth something even when it is not the lowest, and per-resolution can win on paper yet lose the budget meeting.
No published source gives a single break-even ratio. It moves with each vendor's rate and your own AI resolution rate. For teams of a few agents, our live chat picks for small businesses are the fastest route to a per-seat shortlist; larger teams will find that most quotes no longer fit one row of the table at all, because the seat and the meter now arrive on the same invoice.
Will a vendor's headline price tell you what support software costs?
A customer asks an AI agent for help, gets an answer that misses, and closes the tab. Under one vendor's billing rules, that silence becomes a paid resolution a day later.
The previous section matched each billing unit to an agent-to-ticket ratio. Price sheets compared side by side add three complications: most quotes carry two units, the AI unit has no shared price, and each vendor defines its own resolution.
Start with stacking. In a February 2026 Reddit thread for SaaS founders, one operator described products adding "seats for humans, plus credits, plus workflow runs" to the bill. The offers we checked follow that pattern.
| Offer | Seat fee | AI meter | Other fixed costs |
|---|---|---|---|
| Messaging AI agent | $19 annually or $29 monthly per seat | $0.99 per outcome | $49 monthly subscription and minimum commitments in one help article |
| Support and feedback platform | $29 per seat | $0.49 per AI resolution | Free plan |
| Inbox-first help desk | About $25 per user | About $0.75 per AI resolution | Usage caps |
| Ecommerce help desk | $99 per seat, annual commitment | About $0.20 per AI conversation | $200 monthly AI minimum |
| AI overlay on existing help desks | None | $1 per resolved ticket | $15,000 one-time onboarding fee |
| B2B help desk | $32 per agent, plus $2.50 per agent after 15, capped at $150 | No per-resolution AI fee | Top plan required at 60+ agents |
Even the two offers that drop a unit add something else: an onboarding fee on one, a per-agent price that climbs with headcount on the other. Bhawna Yadav, who reviewed vendor help documentation for an October 2026 Medium analysis, cites a benchmark site putting setup for one quote-only enterprise AI vendor at $50,000 to $200,000.
The meter is harder to compare because the unit itself shifts. Yadav traced how one widely used AI agent counts a resolution: 24 hours of customer silence after its last answer becomes an "assumed resolution." In her words, "A customer who gives up and closes the tab is billed the same as one whose problem was solved." A major incumbent help desk, which in August 2024 became the first big incumbent to price AI agents on outcomes, uses a different bar, according to an October 2026 industry digest.
One quiet conversation, two meters
- 24-hour rule: 24 hours of silence after the AI's last answer counts as a resolution, even if the customer gave up. The charge is deducted if the customer returns to that conversation.
- 72-hour rule: the AI must resolve the ticket without human help, confirmed after 72 hours of customer inactivity.
Sources: Yadav's October 2026 analysis and an October 2026 industry digest.
Yadav's own worked example shows what the gap can cost. If 900 of 6,000 resolutions billed at $0.99 were customers who gave up, each problem actually solved cost about $1.16. "An outcome is only as honest as its definition," she wrote. The digest's author adds that the vendor's definition stands until the buyer writes its own into the contract.
The guides disagree too. Yadav found one putting customer service resolutions at $0.50 to $2.00 and another listing $2 to $8 per resolved ticket. An AI support vendor, which sells a competing product, modeled 10,000 tickets a month with half resolved by AI: about $4,950 in AI charges at $0.99 and about $17,500 at an illustrative $3.50, before any seats. Rates also move. The large CRM vendor went from about $1.00 per conversation, resolved or not, to about $0.50 per resolved conversation.
The two halves of a stacked bill also respond to success in opposite ways. "Once you are paying per resolution, a better AI is a larger invoice," Yadav wrote. Meanwhile, the vendor that modeled the rates notes that "the seat bill does not fall when deflection rises." Volume may grow as well. In a December 2025 podcast interview, a speaker for the major incumbent said the company had already seen support volume rise as its AI improved, and called that a sign of success.
The rate on a pricing page is one input. The invoice combines a seat count that holds steady, a resolution count that climbs as the AI improves and is measured by each vendor's own rule, and whatever minimum or setup fee sits underneath. Your agent-to-ticket ratio tells you which half will dominate. It cannot tell you what either half will cost.
- Ask each vendor for its written definition of a billable resolution: the inactivity window, whether customers who give up are billed, and whether returning conversations are deducted.
- During any pilot, sample billed outcomes, mark each as a real fix, doubtful, or a customer who gave up, and recalculate your cost per solved problem.
- Model every quote as seats plus AI-resolved volume plus minimums and onboarding fees, at today's volume and at a busy month's.
- Ask how your contracted seat count can change if AI handles more of the volume.
- Before a multi-year term, ask what happens to your rate if the vendor's public per-resolution price falls.
How we checked this
We used five kinds of sources: pricing pages and buyer's guides published by support software vendors, a Medium analysis built on vendor help documentation, an industry digest, a podcast interview with a speaker for a major incumbent help desk, and a Reddit thread among SaaS operators. None of the figures here are ours. Most of the vendor guides favor their own pricing model, and some argue against competitors that charge per resolution. The $3.50 rate and the $0.50 to $6.00 range come from one such vendor and are labeled illustrative. The enterprise setup costs come from a third-party benchmark site that we could not check directly. We review support software, so we name these vendors generically. Prices for several large vendors are available only by quote. Still unknown: how many billed resolutions, at any vendor, are customers who simply gave up. No source measured that.
- Bhawna Yadav, Medium analysis of pay-for-results AI pricing, October 13, 2026.
- Reducates, digest on outcome-based SaaS pricing, October 21, 2026.
- Modern CTO, podcast interview on AI agents and customer experience, December 2025.
- r/SaaS, Reddit thread on AI agents and pricing models, February 2026.
- Vendor pricing pages and buyer's guides from five support software companies: a support and feedback platform (September 28, 2026), a help desk that includes AI in its seat price (June 2026), an ecommerce help desk (updated September 24, 2026), a B2B help desk (June 17, 2026) and an AI support overlay (updated September 2026). We name them generically.
What should you check before signing a support software contract?
Identify the billing unit first, then test it against your own ticket mix. The cheapest model follows your agent-to-ticket ratio, and that ratio will shift as AI absorbs volume.
The next pricing change is already on the calendar. Atlassian says its new AI resolution meter, at $1.00 per fully resolved service inquiry, starts billing on December 3, 2026. Another large vendor is adding a resolution meter, not a seat.
That is why I would not sign a multi-year resolution rate without a clause covering what happens when public prices fall. Ask, too, whether reopened tickets and customers who drop off are excluded from the bill, and put that answer in the contract. Her test is practical. Audit 100 billed outcomes from a pilot and mark each one as a true fix, a doubtful case, or a customer who gave up.
Run that audit on your own conversations. The share that lands in the last column is the figure your seat versus resolution decision actually turns on, and no vendor price list will hand it to you.
Summarize This Article With AI
Open this article in your preferred AI engine for an instant summary.
Frequently Asked Questions
What else do support leaders ask about pricing models?
Most remaining questions concern per-seat's future, budgeting under usage meters, and defending spend. Each answer below maps back to one of the three billing models.
Is per-seat pricing really dying?
Not for most support teams. Conventional wisdom says seats are finished, yet a 2023 pricing guide still called per-user billing the most common SaaS plan. Analyst research cited in 2026 points to hybrids winning, not pure outcome pricing. My expectation is that seats survive as the human half of the quote.
What is per-active-user pricing?
Per-active-user pricing bills only the users who are active in a period, not every provisioned seat. Slack is the standard example. It suits large teams unsure how many agents will log in regularly. Small teams gain less.
Why is usage-based pricing hard to budget?
The bill tracks volume you do not fully control. One support incumbent's CTO expects support volumes to rise as AI experiences improve, and treats that rise as success. Good automation can therefore grow the meter. Ask for a cap or a committed band before signing.
How do you justify support tool spend to leadership?
Frame the request around avoided mistakes rather than software. Slow replies, duplicate work and weak reporting are where a cheap tool turns expensive. Waste data helps too: a 2025 index of SaaS spend found 66% of provisioned licenses are never used, so show leadership the seat count you will actually fill. No source here offers a support-specific return benchmark, so build that half of the case from your own ticket data.
Are credits a fourth pricing model?
No. Credits are a usage meter in different packaging. Credit-model adoption rose 126% year over year across the top 500 SaaS companies, with HubSpot and Monday.com among the 2025 adopters. Each credit still converts into actions or conversations, which places it in the usage-tiered column and leaves your forecast hinging on volume.
Read next
Why review-site star ratings can't rank support tools
Star averages on software directories bunch near the ceiling, so they can't separate support tools. Learn which review signals to weight instead before…
Read
The Support Tool Fit Score: a 6-factor buying framework
Learn how to score customer support tools when comparing vendors: rate six weighted factors, from KPI fit to cost at your volume, and compare fit, not...
Read
Why the most feature-packed live chat tool rarely wins
The live chat tool with the most features rarely wins. See why routing, reliability and cost at your team size matter more, and what to test instead.
Read