If you have looked at the Salesforce Voice pricing page and multiplied the per-user cost by your agent headcount, you have the platform fee.
You do not yet have the real cost.
Salesforce Service Cloud Voice pricing works in two layers: a per-user platform fee and a separate telephony usage meter. Most teams budget one and discover the other on the first invoice.
This guide explains how Voice pricing is structured, what drives costs beyond the license, and how to build a more accurate cost model before you commit to a rollout.
How Salesforce Service Cloud Voice Is Priced
Service Cloud Voice is an add-on to your existing Service Cloud license. It is not included in any Service Cloud edition by default.
The add-on comes in several tiers depending on your telephony model:
Salesforce Voice for Partner Telephony sits at $50 per user per month. This covers the Salesforce Voice platform and agent experience. Your telephony usage is billed separately by your existing provider, not through Salesforce or AWS.
Salesforce Voice with Amazon Connect is priced in bundled minute tiers. The 750-minute tier is $75 per user per month. The 2,000-minute tier is $125 per user per month. The 5,000-minute tier is $200 per user per month. These minute allowances are included in the platform fee. Usage beyond the included minutes is billed separately through AWS.
Agentforce Contact Center sits at $125 per user per month and includes unlimited platform minutes. This is Salesforce's newest deployment model and is currently available in the United States and Canada.
These are list prices. Actual contract pricing will vary based on your negotiation, commitment term, and volume.
The Service Cloud license itself starts at $165 per user per month for Enterprise edition, billed annually. Voice is layered on top of this, so your total Salesforce line item per agent is the Service Cloud license plus the Voice add-on tier you choose.
For current pricing, always confirm directly with Salesforce or on the Salesforce Voice pricing page, as packaging evolves.
The Cost That Surprises Most Teams: Telephony Usage
The per-user platform fee is visible. The telephony usage meter is where most teams get caught off guard.
For the Amazon Connect bundled tiers, your included minutes cover a defined amount of call time per agent per month. A contact centre where agents handle heavy inbound volume can exhaust that allowance quickly. Usage beyond the included minutes is billed directly through AWS at Amazon Connect's standard rates.
For the Partner Telephony model, Salesforce charges the platform fee and your existing telephony provider charges call usage separately. You are not paying Amazon Connect usage rates, but you still have a telephony consumption cost riding alongside the Salesforce fee.
The practical point: your Voice budget needs to account for both lines. Budgeting only the Salesforce platform fee understates the real monthly cost for any contact centre with meaningful call volume.
To estimate your telephony usage costs accurately, pull your current monthly call minutes per agent and model them against your expected tier. If you are consistently above the included allowance, the next tier up may be cheaper than overage charges.
What Else Affects the Total Cost
Beyond the platform fee and telephony usage, several other factors shape the real cost of a Voice rollout.
Transcription. Real-time transcription is one of the most useful features Voice enables, supporting agent assist, post-call analytics, and Agentforce capabilities. It is not included in the base platform fee for all tiers. Confirm whether transcription is included in your chosen tier and what the cost model is if it is not.
Einstein and Agentforce features. AI-powered capabilities such as Next Best Action, Einstein Article Recommendations, and Agentforce agent assist add value during calls. These features may require additional licensing on top of the Voice add-on. Model these separately if they are part of your rollout scope.
Phone number provisioning. Each phone number provisioned through Amazon Connect carries its own charge. For contact centres with multiple inbound numbers across queues, regions, or teams, this can add up. Audit your number requirements before go-live.
Implementation. The Voice license does not include the work of configuring it. Consulting and development typically represent a significant portion of total project cost. See our guide to Salesforce Service Cloud implementation for a realistic picture of what the implementation scope involves.
Training and change management. Agent retraining, supervisor enablement, and the operational change management involved in moving to a new call handling environment are costs that belong in the budget but rarely appear on the Salesforce quote.
Ongoing administration. Voice requires ongoing Salesforce administration: routing updates, queue changes, permission adjustments, and integration maintenance. If you do not have internal Salesforce administration capacity, managed services are worth factoring into your total cost of ownership.
Partner Telephony vs Amazon Connect: The Cost Difference
Choosing between Partner Telephony and the Amazon Connect bundled model is one of the first decisions in a Voice rollout, and it has a direct impact on cost.
The Amazon Connect bundled model gives you a single consolidated invoice for the platform and telephony minutes, simpler administration, and native integration between Salesforce Voice and Amazon Connect.
The trade-off is that telephony usage is billed at Amazon Connect rates, and you give up the ability to negotiate those rates separately from your Salesforce agreement.
The Partner Telephony model preserves your existing carrier relationships and rates. If you are mid-contract with a provider like Genesys, Five9, or NICE, or if your negotiated carrier rates are below Amazon Connect's standard pricing, Partner Telephony may be the more cost-effective path.
The platform fee is lower at $50 per user per month, and your telephony costs remain with your existing provider.
For high-volume contact centres, the difference between these two models over a three-year term can be material. Model both before making the decision, even if you already have a preference.
One practical consideration: even if you intend to use the Amazon Connect bundled model, pricing a Partner Telephony alternative before you sign gives you a negotiating position on the bundled rates. A credible alternative disciplines the conversation.
How to Build a More Accurate Cost Model
A realistic Voice budget has four components:
Service Cloud license. Your existing Service Cloud cost per agent per month, or the cost if you are adding Service Cloud as part of this project.
Voice add-on fee. The per-user fee for your chosen Voice tier, multiplied by the number of agents who will use Voice.
Telephony usage. Your estimated monthly call minutes per agent, modelled against your chosen tier's included allowance and overage rates, or your existing carrier costs if using Partner Telephony.
Project and operational costs. Implementation, training, phone number provisioning, and ongoing administration. These are one-time or annual costs that belong in the total cost of ownership, not just the recurring license line.
Running this model against your actual call volume data before signing gives you a budget that holds up when the first invoice arrives, rather than one that requires explanation to leadership a month after go-live.
Salesforce Service Cloud Voice Pricing Checklist
Before finalising your Voice budget, confirm the following:
- Service Cloud edition and per-user license cost confirmed for all agents
- Voice add-on tier selected based on expected call volume per agent per month
- Monthly call minutes per agent modelled against included allowance and overage rates
- Telephony model decision made: Amazon Connect bundled or Partner Telephony
- Transcription costs confirmed for your chosen tier
- Einstein and Agentforce feature licensing scoped if in rollout plan
- Phone number provisioning requirements identified and costed
- Implementation scope and cost estimated separately from licensing
- Ongoing administration model defined: internal or managed services
- Total cost of ownership modelled over a three-year term, not just year one
Common Questions Around the Topic
Is Salesforce Service Cloud Voice included in the base Service Cloud license?
No. Service Cloud Voice is a separate add-on priced per user per month, on top of your Service Cloud license. No edition includes Voice by default.
What is the difference between the Amazon Connect bundled tiers and Partner Telephony pricing?
The Amazon Connect tiers include a set number of telephony minutes per user per month within the platform fee. Partner Telephony at $50 per user per month covers the platform only, with telephony usage billed separately by your existing provider. The right choice depends on your call volume, existing contracts, and carrier rates.
What happens when agents exceed the included minutes in a bundled tier?
Usage beyond the included allowance is billed through AWS at Amazon Connect's standard per-minute rates. For contact centres with variable call volumes, monitor usage against the included allowance monthly and consider whether moving to a higher tier is more cost-effective than paying overage.
Is transcription included in all Salesforce Voice tiers?
Transcription inclusion varies by tier and deployment model. Confirm with Salesforce during your procurement conversation rather than assuming it is included.
Do I need a separate Amazon Connect account to use Salesforce Voice with Amazon Connect?
Salesforce provisions the Amazon Connect instance as part of the Voice setup. You do not need an existing Amazon Connect account to use the bundled model.
How does Agentforce Contact Center pricing compare to Salesforce Voice with Amazon Connect?
Agentforce Contact Center is priced at $125 per user per month and includes unlimited platform minutes. For high-volume contact centres where the 2,000-minute or 5,000-minute Amazon Connect tiers would apply, Agentforce Contact Center may offer better per-minute economics. It is currently available in the United States and Canada.
Planning a Salesforce Service Cloud Voice Rollout?
Understanding the pricing model is the first step. Building a rollout that works within that model, and getting the telephony architecture, configuration, and agent experience right, is what determines whether the investment delivers.
La Confianza Technologies helps organisations design their Salesforce Voice architecture, select the right telephony model, and plan a rollout that accounts for the full cost picture before commitments are made.
.png)
.png)