Service Cloud · the licence bill, not the build
The list price is published.
It is still not what you pay.
Salesforce lists five Service Cloud editions on its European pricing page, from €25 to €550 per user per month. The number on the invoice is decided by six things that list does not show, and this page sets them out, together with the four that reduce it.
Checked against the Salesforce European Service Cloud pricing page and the Agentforce pricing page on 13 October 2026. Every list price below was still the published one on that date.
First, two bills
The licences and the build are different money, paid to different people.
The licence bill goes to Salesforce, recurs every year, and grows with headcount. The implementation bill goes to whoever builds the system, is paid once, and ends. Almost every confused conversation about what Service Cloud costs is these two being discussed as though they were one number.
They also move in opposite directions. Over a single year the build usually looks like the larger figure. Over three years the licences normally overtake it. That comparison is worth an hour before an edition is chosen, and it is almost never made, because the two numbers arrive from different people at different times.
What decides the licence bill
Six things, and the edition on the brochure is not the first of them.
The list prices are further down, with the date they were read. These six are what move a real invoice away from them, and they are where Service Cloud budgets go wrong.
Seats committed, not seats used
The invoice is written against the number on the contract for the length of the term. Buying headroom for growth that did not arrive is the single most common way organisations overpay, and it is invisible because nothing on any screen compares licences bought against licences logged into. Run that comparison before every renewal, not after.
The term, and when the notice window closes
A multi year term buys a better rate and removes the ability to reduce seats when the team shrinks. Whichever is chosen, the date that matters is not the renewal date but the day the notice window closes before it, which is earlier and is in the agreement rather than in any reminder. Put that date in a calendar the day the contract is signed.
One feature that forces the edition
Editions are usually chosen for a single capability somebody needs, and the jump then applies to every seat including the ones that will never touch it. Before accepting that, establish whether the capability is available as an add-on, a permission set licence, or on fewer seats. Frequently it is, and the answer changes the bill for every user.
Add-ons priced per seat rather than per org
The things bolted on afterwards are where the number grows quietly, because each is small on its own and each multiplies by the seat count. The test before agreeing to any of them is whether every seat needs it or only some, and whether it can be bought for only some.
Agentforce, which can be a usage cost or a seat cost
Three models coexist: Flex Credits, per conversation, and a per user licence for employee agents. On the Flex Credits rate card Salesforce updated on 31 August 2026, every agent action costs 20 credits whether it is standard or custom, a voice action costs 30, and only prompts are priced by size. Which model is on your agreement matters more than any single rate, because they behave differently as usage grows.
Sandboxes, storage and API limits
These are bought at the moment they become a problem, which is the worst moment to negotiate anything. A build that will need a full sandbox should establish that during planning rather than during the week it is needed. On the European list one full sandbox is included from Advanced up; below that it is a separate line on the order.
What actually reduces it
Four levers, and three of them work before signing rather than after.
Discount negotiation is the one everybody reaches for and the weakest of the four, because it operates on a number that has already been decided by the choices above it.
Count distinct jobs, not people
Not everybody who touches a case needs a full Service Cloud seat. Somebody who only reads, somebody who only submits, and somebody who lives in the console all day are three different requirements, and the platform has more than one answer for them. Establishing that before the order is written is worth more than any discount negotiated afterwards.
Ask what happens to the price at renewal
The first term is the negotiable one and the renewal is where the number usually moves. Ask, before signing, what governs the increase and whether there is a cap. A cap agreed at the start costs nothing and is impossible to obtain later.
Do not let an implementation buy licences for you
Whoever builds the system has an interest in it being built on the edition that makes the build easier. That is not dishonest, it is simply a different objective from yours. Keep the licence decision separate, take it after the data model is written, and require the reason for each seat type in a sentence.
Measure usage before every renewal
Last login, cases touched in the last quarter, and console time per user. Three reports, an hour of work, and they are the only evidence that turns a renewal conversation from an opinion into an arithmetic problem.
The list, as Salesforce publishes it
Five editions, per user per month, read on 13 October 2026.
These are Salesforce list prices from its European Service Cloud pricing page. They are where the order form starts, not where it ends, and a figure quoted without a date is worth checking against the page itself before a budget is built on it.
| Starter SuiteBilled monthly or annually | €25 |
| Pro SuiteBilled annually, contract required | €100 |
| CoreBilled annually | €195 |
| AdvancedBilled annually, one full sandbox per org included | €395 |
| MaxBilled annually, one full sandbox and 2.75 million Flex Credits a year per org | €550 |
The consumption side has its own card. On the Flex Credits rate card updated on 31 August 2026, an agent action costs 20 credits and a voice action 30. That is the part of the bill most likely to surprise a finance team, because it does not behave like a seat.
Asked often enough to answer here
Questions
What does Service Cloud cost per user in 2026?
On 18 September 2026 the Salesforce European pricing page listed Starter Suite at €25, Pro Suite at €100, Core at €195, Advanced at €395 and Max at €550 per user per month, with every edition above Starter billed annually. Those are list prices, and the six things on this page decide what a year actually costs.
Is the licence or the implementation the bigger cost?
Over a single year the implementation usually looks larger. Over three years the licences normally overtake it, because one is paid once and the other recurs and grows with headcount. That is the arithmetic worth doing before choosing an edition, and it is almost never done because the two are quoted by different people at different times.
How is Agentforce billed?
In one of three ways: Flex Credits, per conversation, or a per user licence for employee agents. The Flex Credits rate card Salesforce updated on 31 August 2026 charges 20 credits for each agent action, standard or custom, and 30 for a voice action; only prompts are priced by size. The model on your agreement decides how the bill behaves as usage grows, which matters more than any single rate.
Can we reduce the seat count mid term?
Usually not. Seats can be added during a term and reducing them normally waits for renewal, which is why the number agreed at the start is the number that matters. Buying for the team you expect rather than the team you have is a decision to pay for the gap for the whole term.
What does the build cost, separately from the licences?
€7,250 for 145 hours at the smallest scope on this site: the case model, email to case, queues, reports, up to fifteen agents, training and a sixty day handover. That is a one off number, published rather than quoted, and it is entirely separate from what Salesforce bills you every year.
The build on this site is €7,250 for 145 hours at the smallest scope, which is hours multiplied by fifty and published rather than quoted. What Salesforce charges for licences is between you and Salesforce, and nothing on this page is a commission arrangement with anybody.
Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 13 October 2026.