Salesforce Voice
Salesforce Voice, formerly called Service Cloud Voice, is a native telephony product that brings phone calls into the Salesforce agent workspace next to chat, email, messaging, and other digital channels.
Definition
Salesforce Voice, formerly called Service Cloud Voice, is a native telephony product that brings phone calls into the Salesforce agent workspace next to chat, email, messaging, and other digital channels. It pairs a phone line from a telephony provider with the Service Console so service reps can take and place calls, see the full customer record, and let AI transcribe and assist in real time without leaving Salesforce.
Voice is part of Agentforce Contact Center. Calls flow through Omni-Channel routing just like a chat or a case, supervisors can listen in or barge in, and Einstein turns the live transcript into next-best-action suggestions and an automatic wrap-up summary. Salesforce offers it across three telephony models, so you can run the line through Amazon Connect, a partner provider, or a Salesforce-managed setup.
How Salesforce Voice Connects Phone Calls to the Customer Record
From Service Cloud Voice to Agentforce Contact Center
The product launched as Service Cloud Voice and Salesforce has since rebranded it to Salesforce Voice, positioning it inside Agentforce Contact Center. The name change reflects a bigger shift. Voice is no longer pitched as a bolt-on phone feature. It is the voice channel of a unified contact center where phone, messaging, and self-service agents share the same routing, data, and AI. Reps work in the Service Console, and the phone behaves like any other Omni-Channel work item. A call rings in, the rep accepts it, and the contact, account, and case context open automatically. This is the core difference from older approaches. With traditional Computer Telephony Integration, the phone system and Salesforce were two separate worlds stitched together by a third-party adapter. Voice removes that seam by making telephony a first-class Salesforce channel. The payoff shows up in everyday handling time. Reps stop tabbing between a softphone and the CRM, notes get captured for them, and the same conversation can move between voice and digital without losing history. For teams already on Service Cloud, Voice extends the console they know rather than introducing a separate tool.
Three Telephony Models: Amazon Connect, Partner, and Managed
Voice supports more than one way to bring in the actual phone line, and the model you pick shapes who runs the infrastructure. Salesforce Voice with Amazon Connect is the model where Salesforce provisions and manages the Amazon Connect contact center for you, so you get a turnkey cloud phone system without standing up AWS yourself. Salesforce Voice with Partner Telephony, sometimes called bring your own telephony or BYOT, lets you keep an existing provider and connect it through a managed package the partner ships on AppExchange. There is also a model where you bring your own Amazon Connect instance. In every case Salesforce supplies the same workspace, Omni-Channel routing, reporting, and AI, while the difference sits in the backend and in who owns the telephony contract. Choosing a model is mostly a question of existing investments. A team already running Amazon Connect or a partner like a major carrier keeps it and adds Voice on top. A team starting fresh often takes the Salesforce-managed Amazon Connect route for speed. The Contact Center record in Setup is what represents each connected provider inside your org.
Real-Time Transcription and Einstein Assistance
The feature reps notice first is live transcription. As the caller and the agent speak, Voice converts the audio to text in the console, and that running transcript is what unlocks the AI layer. Einstein reads the conversation as it happens and surfaces relevant knowledge articles, suggested replies, and next-best actions, so a rep can answer a billing question without searching for it. When the call ends, Voice can generate a wrap-up summary and populate case fields, which cuts the after-call work that used to eat into handle time. Transcription is configurable. Admins choose the transcription model, and recording can be paused for moments like reading back a credit card number, so sensitive details stay out of the transcript and the recording. Supervisors get the same transcript view in real time, which means they can coach without dialing into the call. Because the transcript is structured data inside Salesforce, it also feeds reporting and quality review later. This is the part of Voice that turns a phone call from an ephemeral conversation into searchable, actionable CRM data tied to the contact and the case.
Omni-Channel Routing and Supervisor Tools
Voice does not invent a separate queue for phone. Calls ride the same Omni-Channel engine that routes chats, cases, and messaging, so a single set of queues, skills, and capacity rules covers every channel. An admin can route a Spanish-language call to a Spanish-speaking rep using skills-based assignment, the same way a chat would route. This unified model is what lets a supervisor manage the whole floor from one place instead of one console for phone and another for digital. Supervisors get tools built for live calls. Listen in lets them silently monitor an active call, and barge in lets them join the line when a rep needs help. The Omni Supervisor view shows call metrics, queue depth, and rep status across channels in real time, alongside dashboards and reports for longer trends. Because voice traffic and digital traffic share one routing layer, staffing and service levels can be measured together rather than in two disconnected systems. For contact centers that previously ran phone through a standalone ACD, this consolidation is a large operational simplification, not just a UI convenience.
The Developer Toolkit: APIs, Lambdas, and the Voice Toolkit
Voice is extensible, and the Implementation Guide documents the pieces developers use to customize it. The Telephony Integration REST API lets you programmatically manage a voice call, things like creating the call record, updating it, and ending it. When you run the Amazon Connect model, Salesforce provisions a set of Lambda functions inside your Amazon Connect instance, and you drop those Lambdas into Amazon Connect contact flows to drive routing and screen-pop behavior. Two of the named functions are InvokeTelephonyIntegrationApiFunction and InvokeSalesforceRestApiFunction, which call back into Salesforce from a flow. On the front end, the Salesforce Voice Toolkit API is a collection of event listeners and methods for building custom call controls. It works with components written in both Lightning Web Components and the older Aura framework, so you can react to events like a call connecting or wrapping up. The Connect API exposes additional Voice resources for server-side work. Together these let an architect tailor call handling, build custom widgets, and integrate Voice with the rest of an org, rather than being limited to the out-of-the-box softphone.
Licensing, Provisioning, and What to Plan For
Voice is a paid add-on layered on top of Service Cloud or Agentforce Service, and it carries its own usage costs. With the Amazon Connect models there are telephony charges from AWS for minutes, numbers, and transcription, separate from the Salesforce license, so the total cost of ownership has two bills to model. Provisioning is not a single checkbox. An admin enables Voice, sets up the Contact Center record for the chosen model, configures Omni-Channel, assigns the right permission sets and Voice licenses to reps, and connects phone numbers and routing. With partner telephony you also install the provider managed package first. Plan for a phased rollout. Number porting, contact flow design, and transcription tuning take time, and most teams pilot with one queue before moving the whole floor. Permissions matter too, since reps need both the Voice access and the underlying Service Console and Omni-Channel setup to take a call. Treating Voice as a contact center project, not a quick feature toggle, is the realistic way to scope it.
How to Set Up Salesforce Voice
Salesforce Voice is enabled and configured in Setup, then connected to a telephony provider. The exact steps vary by telephony model, but the high-level path is the same. Here is the shape of a typical setup, with the partner or Amazon Connect specifics layered on top.
- Enable Voice and pick a model
In Setup, turn on Salesforce Voice and decide on the telephony model: Salesforce-managed Amazon Connect, your own Amazon Connect, or partner telephony. For partner telephony, install the provider managed package from AppExchange first.
- Create the Contact Center record
Create a Contact Center in Setup that represents your chosen provider. This record links the phone system to your org and is where Voice configuration for that provider lives.
- Configure Omni-Channel routing
Set up the queues, routing configurations, and skills that calls will use. Voice work items flow through the same Omni-Channel engine as chat and cases, so reuse or extend your existing routing.
- Assign licenses and permissions
Give reps the Voice permission set licenses and add them to the Contact Center. Confirm they also have Service Console access and an Omni-Channel presence configuration so calls can be assigned.
- Connect numbers and test
Provision or port phone numbers, build or import the contact flows, and run a pilot with one queue. Verify transcription, screen pop, and the wrap-up summary before rolling out widely.
Amazon Connect (Salesforce-managed), your own Amazon Connect, or partner telephony. Drives who owns the phone infrastructure and contract.
Choose the speech-to-text engine for live transcription. You can also enable pause-and-resume so recording stops for sensitive details.
Reuse existing queues and skills, or create Voice-specific ones, so calls route by skill and capacity alongside digital channels.
Grant Omni Supervisor permissions for listen in, barge in, and real-time call metrics across channels.
- Voice is a paid add-on. With the Amazon Connect models you also pay AWS telephony and transcription charges separately from the Salesforce license.
- Partner telephony requires installing the provider managed package before you can create that Contact Center.
- Reps need Service Console and Omni-Channel set up correctly, not just a Voice license, or calls will not route to them.
- Number porting and contact flow design take real lead time, so plan a phased rollout rather than a same-day cutover.
Trust & references
Cross-checked against the following references.
- Get to Know Salesforce VoiceSalesforce
- Choose Your Salesforce Voice Telephony ModelSalesforce
Straight from the source - Salesforce's reference material on Salesforce Voice.
Hands-on resources to go deeper on Salesforce Voice.
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 is Salesforce Voice?
Q2. What enables AI during calls?
Q3. What infrastructure does it use?
Discussion
Loading discussion…