Voice
Voice in Salesforce Setup refers to the configuration area for Service Cloud Voice, the integrated telephony product that brings phone calls directly into the Service Console alongside chat, email, case management, and the rest of the omnichannel service experience.
Definition
Voice in Salesforce Setup refers to the configuration area for Service Cloud Voice, the integrated telephony product that brings phone calls directly into the Service Console alongside chat, email, case management, and the rest of the omnichannel service experience. Service Cloud Voice replaces or augments traditional standalone CCaaS (Contact Center as a Service) deployments by embedding the call handling, transcription, AI assistance, and analytics into the same Lightning interface that agents already use for cases.
The product comes in three main flavors: Service Cloud Voice with Amazon Connect (the default offering bundling Amazon's CCaaS infrastructure with Salesforce), Service Cloud Voice with Partner Telephony (bring-your-own CCaaS for Five9, Genesys, NICE, and other certified providers), and Service Cloud Voice for Customer Engagement (the embedded outbound calling option for sales and outbound use cases). Each flavor shares the same core Setup configuration for things like call routing, transcription, AI features, and analytics, but differs in how the underlying telephony provider integrates with Salesforce.
How Service Cloud Voice works in the Service Console
Embedded telephony in the agent workspace
Service Cloud Voice puts the soft phone directly inside the Service Console as a utility-bar component. Agents see incoming calls in the same interface where they handle cases and chats, with the call accompanied by a screen pop showing the related Contact, Account, prior Cases, and any other relevant Salesforce data. This embedded approach replaces the old pattern of agents alt-tabbing between a separate telephony console and Salesforce, which slowed call handling and introduced data-entry errors. The unified interface is the headline value proposition: one window for everything an agent needs.
Real-time call transcription
Calls are transcribed in real time using Voice-specific speech-to-text services. The transcription appears as a scrolling pane next to the call interface, showing what was said by whom with timestamps and speaker labels. Agents can highlight portions of the transcript, attach them to the case record, or copy them into related artifacts. The transcripts are stored as Voice Call records related to the Contact and any associated Case, making them searchable in the future. Transcription quality has improved significantly since the feature launched, though it still struggles with strong accents, industry jargon, or low audio quality.
Einstein AI for call assistance
Einstein for Voice provides AI-powered features that run on the live call transcript: real-time recommendations (next-best action, suggested article, sentiment alerts), automatic call summaries generated after the call ends, sentiment scoring throughout the call, and key-moment detection (the customer mentioned a competitor, the customer expressed dissatisfaction, the customer raised a compliance concern). Agents see the recommendations in a side panel during the call and can act on them with one click. Supervisors see aggregate sentiment trends and key-moment counts across their team, helping them coach for specific behaviors.
Omni-Channel routing of voice calls
Service Cloud Voice integrates with Omni-Channel, the routing engine that distributes work items across agents based on availability, skills, and capacity. Voice calls become another work item type alongside chat, email, and case, with the same routing rules applying. An agent capped at 10 concurrent items might be at 5 chats and accept 1 incoming call to reach 6 of 10. The unified routing prevents an agent from being inundated by calls while idle on other channels, which improves agent experience and overall service center efficiency.
Recording, storage, and compliance
Calls are recorded and stored in the Service Cloud Voice infrastructure with retention configurable based on the customer's compliance requirements. Recordings can be played back from the Voice Call record or downloaded for offline analysis. For compliance-heavy industries (financial services, healthcare), Service Cloud Voice supports recording pause and resume during sensitive moments (credit card capture, protected health information disclosure), and the recordings are encrypted at rest with Shield Platform Encryption available for additional protection. Audit trails on the recording activity itself (who listened to which recording when) provide the compliance evidence regulated industries require.
Outbound calling and predictive dialing
Service Cloud Voice supports outbound calling alongside inbound: agents can click-to-dial from any phone number field in Salesforce, and outbound campaigns can use predictive dialing patterns to maximize agent talk time. The outbound capability is particularly relevant for sales teams (proactive outreach to leads), service teams (follow-up calls), and collections (dunning workflows). Each outbound call goes through the same transcription, recording, and AI assistance pipeline as inbound calls, giving a consistent agent experience regardless of who initiated the conversation. Outbound calling has additional regulatory considerations (TCPA in the US, similar consent laws elsewhere) that the implementation must respect.
Reporting and analytics
Voice activity flows into the standard Salesforce reporting model. Reports on call volume, average handle time, first call resolution, sentiment scores, and agent productivity are all available out of the box. Service Cloud Voice also surfaces real-time dashboards for supervisors: who is currently on a call, average wait time, queue depth, abandonment rate. These metrics combine with the broader service-center metrics (chat volume, case backlog) to give a unified view of the service operation. Custom reporting and CRM Analytics dashboards extend the standard reports for deeper analysis.
When standard CTI is enough versus Service Cloud Voice
Service Cloud Voice is not the right answer for every service center. The standard Open CTI framework lets customers integrate a third-party softphone (NICE InContact, Genesys Cloud, Five9, RingCentral) into the Lightning experience without buying into the full Service Cloud Voice product. For customers who already have a CCaaS investment they are happy with, Open CTI plus the existing telephony provider often delivers most of the unified-workspace benefits at significantly lower cost. Service Cloud Voice becomes the right answer when the customer wants the integrated AI features (transcription, real-time recommendations, summaries) that Salesforce builds natively into the Voice product, when the customer is willing to migrate their CCaaS to either Amazon Connect or a certified partner, and when the cost difference is justified by the productivity gains. The decision tree typically goes: do you need the Salesforce-native AI features, are you flexible on CCaaS vendor, and is the per-seat premium acceptable. Three yes answers point at Service Cloud Voice; a no on any of them points at staying with Open CTI plus the existing telephony provider. Customers in regulated industries with bespoke recording or compliance requirements should also confirm those requirements can be met before committing to a Voice migration. Either path can produce a good agent experience; the right choice depends on the customer's specific constraints and aspirations.
Set up Service Cloud Voice in a service center
Deploying Service Cloud Voice spans telephony provisioning, Salesforce-side configuration, agent training, and ongoing operational management. The walkthrough below covers the standard high-level sequence for a Service Cloud Voice with Amazon Connect deployment; the Partner Telephony variant follows a similar pattern with provider-specific integration steps.
- Provision the telephony and integrate with Salesforce
Work with the Salesforce account team to provision the Service Cloud Voice product alongside the underlying telephony (Amazon Connect for the standard variant, or the chosen partner CCaaS). The provisioning includes phone number procurement, IVR configuration, call flow design, and the integration handshake between the telephony platform and Salesforce. This step typically involves both the Salesforce admin team and the contact center operations team and can take weeks of coordination.
- Configure Salesforce-side Voice settings
From Setup, navigate to Voice and configure the Voice Call object: which fields to track, layout for agents, integration with Cases and Contacts. Configure Omni-Channel routing rules to include calls as a work item type. Set up the Service Console app to include the Voice softphone in the utility bar. Configure Einstein for Voice features (transcription, real-time recommendations, summaries) per the org's licensing. Test with a pilot agent making a sample call to confirm the integration works end-to-end.
- Train agents and supervisors
Run training sessions for agents on the new unified workspace: how to accept calls, navigate the softphone, use the live transcript, act on Einstein recommendations, and document the call in the case record. Train supervisors on the real-time dashboards, the recording-listening interface, and the coaching workflows. Run a two-week pilot with a small team before broader rollout, capturing feedback and refining the configuration. Communicate the change broadly so other parts of the service organization understand the new agent experience.
- Operationalize and monitor
After go-live, monitor key metrics weekly: call volume, average handle time, first call resolution, agent occupancy, abandonment rate. Compare to the pre-Voice baseline. Iterate the routing rules, IVR flow, and agent screens based on what the metrics reveal. Schedule monthly business reviews with the contact center operations team. Add Voice-specific quality monitoring (random recording sampling, transcript review) to the standard agent QA process so coaching keeps up with the new capabilities.
- Transcription quality varies by audio quality, accent, and industry-specific terminology. Set realistic expectations during agent training.
- Recording retention has cost implications. Long retention plus high call volume becomes a meaningful budget line item.
- IVR design is its own discipline. Bad IVR flows frustrate customers regardless of how well Salesforce-side Voice is configured.
- Outbound calling has regulatory requirements (TCPA, consent laws) that the implementation must respect. Compliance signoff before going live is essential.
- Voice metrics differ from legacy CCaaS metrics. Reconciling the new measurements with historical baselines requires deliberate analyst work.
Trust & references
Straight from the source - Salesforce's reference material on Voice.
- Service Cloud VoiceSalesforce Help
- Omni-ChannelSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What business function does Voice primarily support?
Q2. What customer experience metric would Voice help improve?
Q3. How does Voice help support agents be more productive?
Discussion
Loading discussion…