Salesforce Service Cloud Voice pricing in 2026. The seat fee and the minute meter.

Service Cloud Voice costs a per user platform fee of $50 to $200 a month plus telephony usage billed by the minute. The seat discount matters less than the usage terms, which decide what you pay over the term.

Service Cloud Voice has two prices: a per user subscription on your Salesforce order form, and a usage meter for telephony minutes that grows with every call your agents take. Most budgets we review price the first carefully and guess at the second.

Salesforce now markets the product as Salesforce Voice, and its price list sells it as Partner Contact Center editions. Contracts, admins and search results still mostly say Service Cloud Voice, so this guide does too. It sits in our Salesforce knowledge hub; for the wider contact center price list, read our Salesforce contact center pricing guide.

How is Service Cloud Voice priced in 2026?

Service Cloud Voice is a per user platform fee on top of Service Cloud, plus telephony usage billed by consumption. The seat carries the telephony integration, the agent experience inside the Service Console and, on the Amazon Connect editions, call transcription. The minutes run on a separate meter, and bundled telephony is delivered through Amazon Connect.

The seat fee appears on the order form next to published Service Cloud pricing. On the current Service Cloud price list, Voice is shown as available for purchase on the Core and Advanced editions. These are the list prices Salesforce publishes for the Voice editions. The Amazon Connect editions require an annual contract.

The two cost layers

• Platform fee. Charged per user per month, on top of the Service Cloud license, and quoted and discounted like any other Salesforce SKU. In the Amazon Connect editions the fee also buys an allowance of platform minutes. Minutes above the allowance, and IVR utterances above the contracted number, are billed as overage.
• Telephony usage. Per minute consumption for the connection to the phone network, priced on Amazon Connect rates in the bundled model, plus carrier charges. Phone numbers carry their own charges, and since March 1, 2025, US bills can include 911 and 988 emergency calling fees.

Who bills what

With bundled telephony, the subscription is invoiced by Salesforce as part of your contract. Telephony minutes are tabulated monthly in arrears and invoiced separately, usually within the first 5 to 10 days of the following month. Finance teams need both feeds reconciled every month, or the reported contact center cost is wrong.

If you run your own Amazon Connect instance, the telephony charges land on your AWS bill instead. That is cleaner for chargeback but still leaves two invoices to join up.

What are the Service Cloud Voice deployment options?

Three established models exist: bundled telephony on Amazon Connect, partner telephony that brings your existing carrier or CCaaS contract, and partner telephony with your own Amazon Connect instance. The bundled model is the fastest to deploy. The partner models keep your existing telephony economics.

A fourth option arrived on March 10, 2026, when Salesforce launched Agentforce Contact Center with its own native voice for Agentforce Service customers in the US and Canada. The Contact Center edition that carries native voice lists at $125 per user per month with unlimited platform voice minutes. It is not listed in AUD, EUR, GBP, JPY or SEK.

The minute meter in practice

Under the bundled model, inbound calls, outbound calls and transcription each consume on their own rates, published on the cloud provider price lists. Forecast from current call volumes and handle times. Then add the transcription load, which buyers routinely forget to price, and the time callers spend waiting in queue.

Salesforce's own billing FAQ warns that badly configured queues and callbacks drive up minute consumption. Queue design is therefore a cost decision as well as a service level decision.

The AI multiplier on Amazon Connect

If you turn on Amazon Connect Customer for its AI features, Salesforce counts that instance's minutes at 2.1 times the base rate. In Salesforce's example, 300 minutes in a month with the feature on throughout consume 630 platform minutes.

A pilot switched on across the whole instance more than doubles the minutes you burn from the first day. Put AI pilots on a separate instance or a limited set of queues, so the multiplier applies only to the traffic you are testing.

What does Service Cloud Voice cost for a 200 agent contact center?

The hard part of the subscription is matching the minute tier to your real traffic.

Say you run 200 agents who handle 60,000 calls a month at a 6 minute average handle time, with another 1.5 minutes per call in IVR and queue. That is 360,000 handled minutes plus 90,000 waiting minutes, or 450,000 platform minutes a month.

Telephony minutes come on top of every row, because the connection to the phone network is billed separately from platform minutes. The subscription column is only the first of the two numbers. The table also assumes the allowance pools across all 200 seats. Salesforce does not say so publicly, so confirm it in the quote.

Which tier is cheaper depends on the overage rate

Moving one agent from the 750 tier to the 2,000 tier costs $50 more a month for 1,250 extra minutes, which works out at 4 cents a minute. The step from 2,000 to 5,000 minutes costs $75 for 3,000 minutes, or 2.5 cents a minute. Compare those figures with the overage rate in your quote.

• Overage below 4 cents. The 750 tier plus overage beats the 2,000 tier at 450,000 minutes. The 750 tier saves $10,000 a month in subscription and adds 250,000 overage minutes, so the two break even at exactly 4 cents.
• Overage above 4 cents. The 2,000 tier wins, and you should push for the right to move agents up a tier mid term.
• No overage rate in the quote. Ask for it in writing before you choose a tier. You cannot compare tiers without it.

What a forecast miss does to the same contact center

Now apply the size of forecast miss we saw in year one. On the 2,000 tier, running 40 percent over the 450,000 forecast means 630,000 minutes and 230,000 overage minutes a month. Running 25 percent under means 337,500 minutes, and 62,500 minutes a month you paid for and did not use.

The same 450,000 minutes with Amazon Connect Customer switched on all month would count as 945,000 platform minutes. That nearly fills the 5,000 tier, sized on traffic that fits comfortably inside the 2,000 tier without AI.

What have we seen in recent Service Cloud Voice negotiations?

Between 2024 and 2025 I benchmarked roughly 15 to 20 Salesforce contact center negotiations involving Service Cloud Voice. In them, the platform fee was the visible cost and the telephony meter was the variable one. Three patterns came up again and again.

• Minute forecasts missed widely. Actual year one telephony usage differed from the sizing assumptions by 25 to 40 percent, in either direction. That made the usage terms matter more than the unit rates.
• Finance was caught out by two invoices. Platform fees were billed through Salesforce while telephony usage arrived on separate cloud billing, and no single team owned the combined number.
• Partner telephony changed the cost model. Organizations that brought existing carrier contracts through the partner model avoided the bundled minute economics entirely. The price was integration effort.

Is bundled telephony the simpler and safer choice?

The usual advice is to take bundled telephony for simplicity and treat the meter as a cost of doing business, and we disagree. In roughly 10 of those 15 to 20 negotiations, the minute meter outgrew the platform fee within two years. Buyers with existing carrier contracts gave up negotiated rates for convenience they did not need.

Price the partner telephony model properly before you sign, even if you intend to choose bundled. In the deals where a costed partner alternative was put on the table, bundled usage terms improved materially. Building that alternative costs internal time and a few partner quotes, nothing more.

You negotiate the seat fee once. The minute meter runs every month of the term, and two years in it is usually the larger number.

How do you negotiate Service Cloud Voice pricing?

Negotiate the platform fee like any Salesforce SKU, then spend most of your effort on the usage side. That means rate protection, forecast bands and a partner option you could actually switch to. We work through these five steps with clients.

1. Benchmark the seat fee. The Voice uplift discounts like other Salesforce SKUs, so treat its list price as an opening position. Our Salesforce discount benchmarks show where Service Cloud add ons tend to land.
2. Model minutes yourself. Build the usage forecast from your own call data, not from vendor sizing.
3. Protect the rates. Lock the usage economics and consumption review triggers into the order form.
4. Keep partner telephony credible. Get written quotes from at least two telephony partners and show Salesforce the per minute comparison.
5. Phase the rollout. License agents in waves as they migrate, not the whole floor at signature.

What the account team will say, and what to say back

• "The 2,000 minute tier fits most contact centers." Reply with your own twelve months of handle time and queue data, and ask Salesforce to show which tier that data implies.
• "Voice is priced off list, the discount goes on Service Cloud." Ask for the Voice line discounted on its own and shown separately. A blended discount hides what you pay for Voice at renewal.
• "Overage almost never happens." Then the overage rate and a cap on it cost Salesforce nothing to write into the contract.
• "License the whole floor now to get the best price." Ask for the same unit price held for agents added in later waves, which gives you the discount without paying for idle seats.

Contract terms to ask for

• A stated overage rate, held for the term. The tier decision depends on it, as the worked example shows.
• How the allowance accrues. Salesforce bills overage once cumulative contractual minutes are exceeded. Write down whether that is measured monthly, annually or over the full term, and whether minutes pool across agents.
• Tier change rights. The right to move agents between the 750, 2,000 and 5,000 minute tiers at each anniversary, in both directions.
• A consumption review trigger. A formal review when usage crosses an agreed share of the allowance, before overage accrues.
• Telephony rate protection. Pass through rates tied to the published Amazon Connect price list, with reductions passed on.
• A switching right. The option to move from bundled to partner telephony mid term by swapping editions without a penalty.

Our guide to ten Salesforce contract clauses covers the renewal cap and notice terms that sit around these.

How does the right choice change with contact center size?

Smaller teams usually do best with bundled telephony priced on real data. Large contact centers usually have carrier contracts and in house skills worth protecting. The difference is whether the integration work of a partner model pays back.

A small team starting fresh

Say you run 40 agents and have no carrier contract worth keeping. The 750 or 2,000 minute tier is usually the right starting point, and the effort of a partner integration is hard to recover at that scale.

At 40 seats the gap between the 750 and 2,000 minute tiers is $2,000 a month at list, so choosing the wrong tier costs far less than it does at 200 agents. One partner quote is still worth having as a price check.

A large contact center at renewal

Say you run 1,500 agents across several sites on negotiated carrier rates. Here the partner models and your own Amazon Connect instance deserve full costing, and the seat fee carries enough volume to negotiate hard. At renewal you also have actual usage reports, so right size the tier from them rather than from the original sizing.

How should you budget the full cost of Service Cloud Voice?

Budget the seat fee, the minute meter and the transcription load as one number that one team owns. The buyers who kept Voice cost under control reconciled platform and usage billing every month and re forecast every quarter.

• Seat layer. The Voice fee times the number of agents, net of the negotiated discount.
• Usage layer. Minutes times rates, inbound and outbound, plus transcription and any overage above the allowance.
• Governance. Monthly reconciliation, a quarterly re forecast and an annual rate review.

How to check your own usage

• Salesforce Voice Minutes Report. Shows platform minute charges only, with consumption data up to 2 days old.
• Salesforce Voice Usage and Cost Report. Shows telephony minute charges only and exports to CSV for finance.
• Service Cloud IVR Report. Counts IVR utterances against your contracted number.
• Salesforce Voice Calls Report. Lists calls with caller numbers, timestamps and durations, which is what you need to spot queue and callback problems.
• Your current phone system's call records. Before you buy, these give you the volume and handle time baseline for the forecast.

A timeline for the purchase or renewal

For the renewal sequence across your whole Salesforce contract, see our Salesforce renewal timeline.

What to do next

1. Collect the data. Pull twelve months of call volume and handle time data before any sizing call with Salesforce.
2. Price every model. Cost all three deployment models, including partner telephony, before signature.
3. Benchmark the seat. Negotiate the seat fee against benchmarks rather than list price.
4. Write down the usage terms. Lock usage rates, review triggers and forecast bands into the order form.
5. Phase the licenses. Match agent licensing to the migration schedule.
6. Reconcile from day one. Set up monthly reconciliation of platform and usage billing as soon as the first call goes live.

Our Salesforce practice negotiates Voice pricing inside every Service Cloud renewal we run, and the Salesforce hub holds the rest of our Salesforce guides.

Frequently asked questions