Salesforce Service Cloud Voice:
Telephony Integration Costs

1. What Service Cloud Voice Actually Is (and Isn’t)

Service Cloud Voice is Salesforce’s native telephony integration for contact centres. Introduced in 2020 and significantly expanded through 2024–2025, it embeds voice calls directly into the Service Cloud agent console — eliminating the need for agents to switch between a separate phone system and their CRM. Calls are routed through Amazon Connect (Salesforce’s default telephony partner), transcribed in real time by Einstein, and surfaced alongside the customer’s full service history, enabling agents to resolve issues faster with complete context.

What Voice is not is a traditional phone system. It does not replace your PBX, your SIP trunking infrastructure, or your carrier relationships (though it can sit on top of them). It is a cloud contact-centre-as-a-service (CCaaS) layer that integrates telephony into the Salesforce UI. This distinction matters because Voice’s cost structure is fundamentally different from traditional telephony: instead of flat per-seat Salesforce pricing 2026, it combines Salesforce per-agent licence fees with consumption-based telephony charges that scale with call volume, duration, and the AI features you enable.

The promise is compelling: unified voice, digital, and CRM in a single pane of glass, with AI-powered transcription, sentiment analysis, and supervisor coaching tools. The challenge is that the cost structure is opaque, multi-layered, and significantly more complex than Salesforce’s marketing materials suggest. Enterprises that budget only for the per-agent Salesforce fee are routinely surprised by Amazon Connect charges, carrier costs, and AI consumption fees that can double or triple the effective per-agent cost.

2. The Three Deployment Models

Salesforce offers three approaches to implementing Service Cloud Voice, each with different cost structures, flexibility levels, and procurement implications.

The choice between these models depends on three factors: whether you already have a CCaaS platform (Genesys, NICE CXone, Five9, Talkdesk), how important real-time AI transcription and analytics are to your operation, and whether you want to consolidate telephony billing under Salesforce/Amazon or maintain direct carrier relationships.

For new contact-centre deployments without an existing CCaaS investment, Voice with Amazon Connect provides the fastest path to an integrated solution. For enterprises with established CCaaS platforms, Voice with Partner Telephony preserves your telephony investment while adding the Salesforce-native AI and routing layer. For cost-sensitive deployments where AI transcription isn’t critical, Open CTI provides basic integration at no additional Salesforce cost, though you lose the features that make Voice compelling.

3. Cost Layer 1: Salesforce Licence Fees

The Salesforce component of Service Cloud Voice is a $75/agent/month Salesforce add-ons worth paying for PSL on top of your base Service Cloud licence. This means every agent using Voice needs both a Service Cloud licence (Enterprise at $165/user/month list, or Unlimited at $330/user/month) and the Voice PSL. The combined Salesforce-only cost before any telephony charges is $240/agent/month at Enterprise list pricing.

Three critical points for procurement teams:

The Voice PSL is required for both deployment models (Amazon Connect and Partner Telephony). If you’re using Partner Telephony, you still pay Salesforce $75/agent/month for the Voice integration layer, transcription, and analytics — even though your telephony is running through a third party. This surprises enterprises that assume the $75 covers telephony itself.

The PSL is per-agent, not per-concurrent-user. If you have 200 agents who use Voice, you need 200 Voice PSLs, regardless of how many are logged in simultaneously. This is a named-user model, not a concurrent model. For contact centres with significant part-time or shift-based staffing, this inflates the per-productive-hour cost considerably. A 200-agent centre with only 120 concurrent agents at any time is still paying for 200 Voice PSLs.

Volume discounts are available but not automatic. Like all Salesforce PSLs, Voice pricing is negotiable. Our benchmark data shows enterprise Voice deployments achieving 20–35% off the $75 list price when Salesforce negotiation tipsed as part of a broader Service Cloud deal. Standalone Voice PSL purchases typically receive minimal discounting. Always bundle Voice into your base Service Cloud negotiation. For broader feature licence guidance, see our dedicated guide.

4. Cost Layer 2: Amazon Connect Consumption

For Voice with Amazon Connect deployments, Amazon’s consumption charges represent the largest and most variable cost component. Amazon Connect uses pay-per-use pricing with no minimum commitments, which sounds cost-effective but can generate substantial monthly bills for high-volume contact centres.

Amazon Connect Usage Charges

Amazon Connect charges per minute of active call time. Inbound calls cost approximately $0.018/minute. Outbound calls cost approximately $0.018/minute plus carrier-specific per-minute telephony charges. These rates apply to the time the call is connected to an agent or IVR flow — queue wait time is not charged. On an average inbound call of 6 minutes, the Amazon Connect usage charge is approximately $0.108 per call.

Telephony Minutes (PSTN Charges)

On top of Amazon Connect usage, you pay for the actual telephony minutes — the carrier cost of connecting the call over the public switched telephone network. Inbound DID (Direct Inward Dialing) numbers cost approximately $0.006/minute for US numbers. Outbound calls cost approximately $0.0022/minute for US domestic. International rates vary significantly by country. Toll-free inbound numbers are more expensive: approximately $0.0120/minute for US toll-free.

Real-Time Transcription (Contact Lens)

Amazon Connect Contact Lens provides the real-time transcription and analytics that power Voice’s AI features. Charges are per minute of analysed audio: approximately $0.015/minute for real-time transcription with analytics. On a 6-minute call, that’s $0.09 — nearly as much as the base Connect usage charge. Post-call analytics (sentiment, key phrases, compliance detection) adds approximately $0.01/minute.

5. Cost Layer 3: Telephony and Carrier Charges

Whether you use Amazon Connect or Partner Telephony, underlying carrier charges apply. These include DID number provisioning (typically $1–$3/number/month), toll-free number provisioning ($2–$5/number/month), per-minute PSTN charges (as detailed above), and international calling at carrier-specific rates.

For Partner Telephony deployments (Genesys, NICE CXone, Five9), your existing carrier contract and CCaaS subscription continue unchanged. The Salesforce Voice PSL adds the integration, transcription, and analytics layer on top. Your telephony costs remain with your existing provider, and the total cost is your existing CCaaS bill plus $75/agent/month to Salesforce. This is often the more predictable cost model because you already understand your telephony spend.

For Amazon Connect deployments, telephony costs flow through AWS billing. Enterprises migrating from on-premise PBX or traditional CCaaS to Amazon Connect should model their expected call volumes carefully. Amazon Connect’s per-minute pricing can be cheaper than flat-rate CCaaS for low-volume centres (under 30 calls/agent/day) but more expensive for high-volume operations (50+ calls/agent/day). The break-even point depends on your specific mix of inbound, outbound, domestic, and international traffic.

6. Cost Layer 4: AI Transcription and Analytics

Voice’s AI capabilities — real-time transcription, sentiment analysis, keyword detection, agent coaching recommendations, and next-best-action suggestions — are among its most compelling features and also its most overlooked cost drivers.

Einstein transcription within the Salesforce Voice PSL provides basic real-time call transcription. However, the deeper analytics features are powered by Amazon Connect Contact Lens, which carries separate consumption charges (covered in Section 4). The distinction matters: the Salesforce $75/agent PSL includes the UI for displaying transcripts and analytics, but the underlying AI processing costs come from AWS.

For enterprises planning to use Agentforce licensing guide for Service — Salesforce’s AI agent layer for automated customer service — Voice integrations create an additional consumption layer. Agentforce actions triggered by voice interactions (automated case creation, knowledge article retrieval, escalation routing) consume Flex Credits at $0.10/credit. A single voice interaction that triggers 3–5 Agentforce actions adds $0.30–$0.50 per call in AI consumption on top of all other costs.

Model the full AI cost stack before committing: Amazon Connect Contact Lens transcription + Salesforce Voice PSL + Agentforce Credits (if applicable). For a 6-minute inbound call with real-time transcription, post-call analytics, and two Agentforce actions, the AI/analytics cost alone is approximately $0.35–$0.50 per call. At 50 calls/agent/day across 200 agents, that’s $70,000–$100,000/month in AI-related charges. See our AI & Data Cloud licensing guide for Flex Credit negotiation strategies.

7. Total Cost Model: 200-Agent Contact Centre

The following model illustrates the realistic all-in cost of Service Cloud Voice with Amazon Connect for a 200-agent enterprise contact centre handling inbound support calls.

The Salesforce Voice PSL ($56/agent after discount) represents only 12% of the total cost. Amazon Connect consumption accounts for 64%. This is the fundamental procurement insight: Service Cloud Voice is primarily an AWS cost, not a Salesforce cost. Enterprises that negotiate aggressively on the Salesforce PSL but ignore the AWS consumption component are optimising the wrong side of the equation.

At $460/agent/month all-in ($5,520/year), this model is competitive with mid-market CCaaS platforms (Genesys Cloud CX, NICE CXone) at similar scale, which typically range from $100–$200/agent/month for the CCaaS layer alone before CRM integration costs. However, those platforms include the CRM integration in their pricing, while Voice requires the separate Service Cloud base licence. The true apples-to-apples comparison must include the Service Cloud licence in Voice’s total. For a broader analysis of Salesforce Licensing Costs across products, see our reference guide.

8. Voice vs. Partner Telephony vs. BYO CTI

Choosing between the three deployment models requires evaluating total cost, operational complexity, and feature requirements against your specific contact centre profile.

For large enterprises (500+ agents), the Partner Telephony model is the most common choice in our client base because it preserves the investment in mature CCaaS platforms while adding Salesforce’s AI layer. The Voice PSL cost is incremental and the telephony spend is already budgeted and understood. For mid-market contact centres (100–300 agents) building their first cloud contact centre, Amazon Connect offers a scalable entry point without long-term platform commitments.

The decision matrix comes down to this: if AI-powered transcription and analytics are business-critical, choose Voice (either model). If you need basic telephony integration and transcription isn’t a priority, Open CTI saves $75/agent/month in Salesforce fees. If you already have a CCaaS platform you’re satisfied with, Partner Telephony gives you Voice’s AI features without disrupting your telephony stack. For a full comparison of Salesforce licence types including Service Cloud editions, see our comprehensive guide.

9. Negotiating Service Cloud Voice Agreements

Voice negotiations involve two separate commercial relationships — Salesforce (for the PSL and Service Cloud licences) and AWS (for Amazon Connect consumption) — and the strategies differ for each.

Negotiating the Salesforce Voice PSL

Bundle Voice into the base Service Cloud deal. Never purchase the Voice PSL as a standalone add-on after signing your Service Cloud agreement. Bundle it into the base negotiation alongside all other PSLs, and negotiate the total package as a single commercial commitment. Our benchmark data shows bundled Voice PSL pricing at $48–$56/agent/month (25–35% off list) for enterprise deals, compared to $65–$70 for standalone purchases.

Negotiate concurrent-user provisions. If your contact centre runs shifts with 200 named agents but only 120 concurrent at any time, negotiate for 120 Voice PSLs with the right to reassign among your agent pool. Salesforce may resist, but shift-based pricing is achievable in large deals — particularly when the alternative is deploying Partner Telephony or Open CTI instead.

Include Voice in your quantity reduction rights. Just as you negotiate reduction rights for base Service Cloud licences, include equivalent provisions for Voice PSLs. If you reduce agent headcount by 20% next year, you need the Salesforce contract termss-faqs/">Contract Terms FAQ for the full list of negotiable provisions.

Negotiating Amazon Connect Costs

Amazon Connect consumption is billed through AWS, not Salesforce. This means it falls under your AWS Enterprise Discount Program (EDP) or AWS pricing agreement, not your Salesforce contract. If your organisation already has an AWS relationship with committed spend, Voice consumption can count toward your AWS commitment — potentially reducing the incremental cost.

For enterprises without an existing AWS EDP, Voice’s Amazon Connect costs are at on-demand rates. Consider whether committing to AWS Reserved Capacity or establishing an EDP would reduce your per-minute rates. AWS offers volume discounts for high-consumption customers that can reduce Connect charges by 15–25%.

One critical procurement gap: Salesforce account teams cannot negotiate or even discuss Amazon Connect pricing. The AWS billing is completely separate. Ensure your procurement team engages both Salesforce and AWS simultaneously, and that your total cost model reflects both vendors’ charges before signing either agreement.

Negotiating the Overall Deal Structure

For the most favourable commercial outcome, negotiate Service Cloud, Voice, and any other Salesforce products (Sales Cloud, Data Cloud, Agentforce credits) as a single bundled deal. The larger the total commitment, the more leverage you have on individual components. A $3M total Salesforce deal that includes Service Cloud, Voice, and Sales Cloud will achieve better Voice PSL pricing than a standalone $180K Voice purchase.

Time the deal to Salesforce’s fiscal calendar — Q4 (November–January) consistently produces the best outcomes. For deals exceeding $500K annual Salesforce spend, independent advisory support typically delivers 5–15x return on fees. Our competitive pricing playbook provides the complete negotiation framework.

10. When Service Cloud Voice Isn’t the Right Choice

Service Cloud Voice is not the right solution for every contact centre. Understanding where it falls short prevents over-investment in a capability that may not deliver ROI for your specific operation.

Skip Voice if you don’t use Service Cloud. Voice is a Service Cloud add-on. If your contact centre runs on a non-Salesforce CRM or a standalone CCaaS platform, Voice provides no value. The AI and transcription features require the Service Cloud agent console as the user interface. There is no standalone Voice product.

Skip Voice if your existing CCaaS meets your needs. If you run Genesys, NICE CXone, or Five9 with a mature Salesforce CTI integration and your agents are productive, adding the $75/agent Voice PSL may not deliver sufficient incremental value. The primary benefits of Voice over a well-configured CTI are real-time transcription and Einstein analytics. If those capabilities aren’t business-critical, the CTI integration is functionally sufficient at a lower cost.

Skip Voice if your call volumes are very low. For small support teams (under 20 agents) with low call volumes, the Voice PSL cost and Amazon Connect minimum viable deployment create a high per-call cost that rarely justifies the investment. Basic Open CTI with a simple cloud phone system (RingCentral, 8x8, Dialpad) is more cost-effective for small-scale deployments.

Proceed cautiously if your contact centre is primarily outbound. Voice was designed for inbound support. Outbound functionality exists but is less mature than dedicated outbound diallers. If your operation is primarily outbound (sales, collections, surveys), a purpose-built outbound platform with Salesforce integration is likely more effective than Voice.

For enterprises evaluating whether Voice justifies the investment, our licence optimisation methodology includes Voice-specific ROI modelling. We assess your call volumes, current telephony costs, agent productivity metrics, and AI adoption readiness to determine whether Voice delivers net savings or represents net additional cost — and structure the commercial terms accordingly.