What buyers actually pay for a customer service platform

Customer service platforms charge by the seat, by the ticket or by usage, with AI automation adding another charge for some buyers. Seven cost mechanics from verified buyer interviews, and where price-led moves go: Zendesk was the origin of four, while Gorgias was the destination of two and the origin of two.

Based on verified interviews with the support and CX leaders who run these platforms, at DTC and enterprise brands. Buyers are anonymized before publication; vendor names and views are reported as given. No vendor paid to appear or could edit this page.

Buyers talk about customer service platform cost in two registers: the pricing model — seats, licenses, tickets or usage — and what the contract does over time, as AI features, renewals and bundles move the number. In the moves captured here, Zendesk is the origin of four price-led moves, and Gorgias is both a destination for buyers leaving pricier platforms and an origin for buyers moving to cheaper ones still. Below are the seven mechanics buyers describe and where moves made on price go. The ratings live on what ecommerce CS-platform buyers wish they'd known.

7.8/10
Gorgias’s buyer rating — the destination of two price-led moves here, and the origin of two more.
7.1/10
Zendesk’s rating — the origin of four price-led moves counted here.
Usage
Per-ticket, usage and automation charges: costs that can rise as activity grows.
PRICE-LED MOVES BETWEEN HELPDESKS Zendesk Gorgias one Zendesk Gladly one Zendesk Kustomer one Zendesk Another vendor one Salesforce Service Cloud Gorgias one Gorgias Richpanel one Gorgias Commslayer one Five9 Zendesk one CHAT TOOLS, BOTH WAYS ON PRICE Intercom → Drift · one Drift → Intercom · one ZENDESK WAS THE ORIGIN OF FOUR PRICE-LED MOVES; GORGIAS THE DESTINATION OF TWO AND ORIGIN OF TWO
Moves are counted once per company, and only where the buyer gives price as a reason. The full Zendesk departure record, whatever the reason, is on Zendesk alternatives.
This is the average buyer's picture. Which parts apply to your stack?A 15-minute interview returns the read specific to you — and what peers with your setup chose.
Get my personalized read →

Seven things that set the bill

Across the interviews, buyers describe customer service platform cost as shaped by what the plan counts, how AI is priced, what happens to the contract over time, and what a cheaper tool gives up.

01

Seats and licenses can make cost grow with the team

Buyers on per-seat and per-license platforms describe the price growing with the team. A Salesforce Service Cloud customer says “they charge per license per month. And for us it just really has gotten really expensive” (see the stories below). Another says of Salesforce, “There is a premium cost to user licenses.” A buyer comparing Zendesk with Gorgias calls Zendesk “very expensive because it's per seat and not per platform billing,” and a Service Cloud customer at a large enterprise describes having to manage named licenses across its whole workforce.

Named in this context: Salesforce Service Cloud · Zendesk

02

Usage-based pricing makes cost move with volume

Tools priced on usage move with volume. One Gorgias customer says “You pay by the ticket,” and has “downgraded our plan so we're not paying for the full amount that we thought we'd be using it.” For some buyers that brings unexpected costs: another says Gorgias “can be very costly. They keep having hidden charges, which are not great.” On Intercom, a buyer says “the pricing scales aggressively with more contacts and usage that you have.”

Named in this context: Gorgias · Intercom

03

AI features can add another charge

Some buyers describe AI automation adding to the base cost, in different ways. One Gorgias customer found its bill rose with AI usage (see the stories below), and another rates Gorgias lower partly because “their AI offering has a long way to go on it. I think they're expensive overall.” A Zendesk customer adding AI describes “a small per month upgrade fee in the agent's price” that “doesn't increase it to the degree that I thought it would.” A Gladly customer calls its AI “really a wrapper for ChatGPT” and “Super expensive.”

Named in this context: Gorgias · Zendesk · Gladly

04

Renewals and new contract terms can change the price

Buyers describe substantial changes when contracts renew or older terms are replaced. A Zendesk customer on grandfathered contracts says the newer pricing policies would multiply what it pays (see the stories below). A Gladly customer describes a yearly increase the vendor attributed to technology investment, and pushed back: “You guys didn't release anything new this year.”

Named in this context: Zendesk · Gladly

05

Salesforce buyers describe Service Cloud pricing inside larger deals

Salesforce buyers describe Service Cloud's price as part of a larger deal. One says that buying across Salesforce's clouds, “we continued to get preferable pricing because of that. When you bundle all those solutions together, Salesforce gives you a pretty good offering.” Another got a better email rate “as a result of being on Marketing cloud, Commerce Cloud and Service Cloud.” The bundle also sets the terms of leaving: one buyer moving its commerce platform says “if they are willing to come down in cost on Service Cloud and Marketing Cloud, there's a world they keep both of those pieces of business.”

Named in this context: Salesforce Service Cloud

06

Some price-led moves come with capability trade-offs

Some buyers who moved on price describe a specific capability they gave up. A buyer that chose Kustomer says it “is much more cost friendly, but you do lose some options with that.” One that went back to Zendesk from a more expensive contact-center tool names phone routing in particular: “what we gave up the most there was Five9 had a much better IVR functionality.” A team using Freshdesk to save money runs “a very basic version that cannot be used for a wider variety of purposes or workflows.” And a buyer that moved to Gladly from Zendesk saved money but describes its back end as a problem (see the stories below).

Named in this context: Kustomer · Zendesk · Freshdesk · Gladly

07

Support volume changes the price-value calculation

Buyers weigh the price against how much support they handle. A smaller brand says “we don't have enough volume of customers calling in” to justify “a larger platform like a Gorgias.” A Gorgias customer values that “you can start with a low-term plan that doesn't cost much to operate.” At the other end, a large retailer says Gorgias works at lower order volumes but that at its scale “you need something that scales,” and a team on Freshdesk says its basic needs mean it does not “need expensive systems like Service Cloud.”

Named in this context: Gorgias · Freshdesk · Salesforce Service Cloud

Want this read against your own stack?

Get my read →

The stories behind the bill

An apparel brand moved from Zendesk to Gorgias and calls it a “huge improvement, but one thing we don't like about Gorgias is the pricing isn't super upfront.” When its AI usage rose, so did the bill: “all of a sudden we get our bills and we weren't aware that actually you have to pay a lot more for this automation.” It is now “evaluating another vendor to see if we can switch.” Chief revenue officer · apparel brand
An online marketplace with long-standing Zendesk contracts describes pricing changes that would reprice them. “Their new contracts and new pricing policies are completely unfavorable,” the buyer says. “When this happens with grandfathered contracts, it's not that it increases our cost by 10% or 20%, it increases our cost by hundreds of percent.” Because the integration is tight, “it's really complicated.” Director of engineering, post-purchase and care · online marketplace
A direct-to-consumer brand moved to Gladly from Zendesk to save money. Gladly does it “at a cheaper rate than a Zendesk, right? There is for sure cost savings.” The savings came with a cost of their own: “I think that their back-end data is just garbage,” the buyer says, and “the back end is a mess and has caused us a lot of trouble actually getting visibility into like how our CX team is performing.” Chief of staff · direct-to-consumer brand
A multi-location healthcare provider rates Salesforce Service Cloud below its marketing tools on cost: “it is way more expensive and it's more of a cost center.” With large call-center teams, “they charge per license per month. And for us it just really has gotten really expensive.” If it leaves Salesforce, the buyer says, “it will likely be just because of how inflated their costs are for how we use it.” Senior director of CRM · multi-location healthcare provider

The counter-current: some buyers find the price fair

Not every buyer is trading down. A Gorgias customer chose it because “It is much cheaper than the really popular ones,” and another says “the cost is very reasonable.” A Zendesk customer sees “a really nice balance between their customer success and their cost efficiencies.” And one buyer that weighed cheaper helpdesks stayed with Gorgias: “we looked at a bunch of solutions that were 20, 30% of the cost of Gorgias and almost went in that direction. From a stability perspective, we valued what Gorgias was able to provide.”

What this means for your customer service budget

In these interviews, what a customer service platform costs depends on its pricing model and on what happens to the contract over time. Buyers on Salesforce Service Cloud and Zendesk describe seats and licenses growing with the team; buyers on Gorgias and Intercom describe usage and per-ticket charges; and for some buyers AI automation adds another charge. Some buyers describe substantial changes when contracts renew or older terms are replaced, and Salesforce buyers describe Service Cloud pricing as part of broader Salesforce deals. In the moves captured here, Zendesk was the origin of four price-led moves, and Gorgias the destination of two and the origin of two — and some buyers who moved on price describe a capability they gave up. One way to read this — ours, not a buyer's — is as five costs: staffing (seats and licenses), usage (tickets, contacts and volume), automation (AI charges and upgrades), contract (renewals and commercial terms), and trade-offs (the capability some cheaper moves give up). Our recommendation, not a practice buyers describe: model the bill at the ticket, contact and agent volume you expect, not today's; price AI automation separately from the base plan; compare current contract terms with the terms that would apply at renewal before budgeting the next period; and weigh what a cheaper tool would give up before switching on price.

Common questions

How much does a customer service platform cost?

In these interviews it depends on the pricing model: per-seat or per-license pricing on platforms such as Salesforce Service Cloud and Zendesk, and per-ticket or usage-based pricing on tools such as Gorgias and Intercom, with AI automation adding another charge for some buyers. Bundles, changes to existing contracts and support volume all move the number.

Is Gorgias cheaper than Zendesk?

Several buyers in these interviews describe it that way, and two moved to Gorgias from Zendesk or Salesforce Service Cloud on cost. But Gorgias charges by the ticket, buyers describe automation and AI usage adding to the bill, and two left Gorgias for cheaper tools, Richpanel and Commslayer.

Why is Salesforce Service Cloud expensive?

Buyers point to per-license pricing that grows with the number of agents, and to the specialist help needed to integrate and run it. Bundling it with other Salesforce clouds can lower the rate, and one buyer says it would keep Service Cloud if Salesforce came down in cost.

Do helpdesk vendors raise prices on existing customers?

Some buyers describe it. One says Zendesk's newer pricing policies would multiply its cost once its older, grandfathered terms are replaced; another says Gladly added a yearly increase it attributed to technology investment. Buyers adding AI describe a separate charge for automation.

What do buyers give up when they switch helpdesks on price?

Some buyers who moved on price describe trade-offs: one that moved to Gladly from Zendesk saved money but found its back-end data weak; one that chose Kustomer as more cost-friendly says you lose some options; and one that went back to Zendesk from a more expensive contact-center tool gave up better phone routing.

Get this research made for your stack

Pricing a helpdesk, or deciding whether AI automation is worth the extra charge? Do a 15-minute interview about your support volume, your team and your stack, and get this personalized — which cost mechanics drive your number, and where peers found the savings.

Get my personalized read — 15-min interview

No password · your interview is anonymized before it ever informs a page like this one.

Want to come back to this?We'll email you a link to this page, so it's easy to find later or forward to your team.
Methodology. Alium conducts verified interviews with software buyers — the customer experience, ecommerce and operations leaders who select and operate these platforms. This page aggregates what buyers in that corpus, through October 2026, say about what customer service platforms cost; moves are counted once per company and only where the buyer gives price as a reason. Prices are reported only as relative statements and multiples buyers give, never as amounts. Ratings are buyer-satisfaction averages from published transcripts, re-checked against source data for this page. Buyer identities are verified at interview time and anonymized before publication; vendor names are reported as given. No vendor paid to appear or was able to edit this page.