Service Cloud Voice: Setup Guide | SalesforceTutorial

Service Cloud Voice is the Salesforce voice channel that brings phone calls, call controls, caller context, transcripts, and supervisor visibility into the Service Console. Salesforce documentation now uses the name Salesforce Voice for what many admins still search as Service Cloud Voice, so this guide uses both terms where needed.

Use this article when you need a practical implementation view: what the product does, how it differs from CTI, how service cloud voice with amazon connect fits into the architecture, and what to validate before a production rollout.

What is Service Cloud Voice?

Service Cloud Voice connects telephony to Salesforce so agents can answer calls from the Service Console, see CRM records, work from Omni-Channel, and review voice activity on Salesforce records. In current Salesforce Help and Trailhead content, the product is described as Salesforce Voice, formerly Service Cloud Voice.

The main difference from a basic softphone integration is that calls become part of the service workspace. A call can create or relate to a VoiceCall record, appear beside cases and contacts, route through Omni-Channel, and support transcripts or recordings depending on the telephony model and licenses.

What is Service Cloud in this context?

What is Service Cloud for this topic? It is the Salesforce service application layer where teams manage cases, channels, knowledge, entitlements, queues, and service analytics. Voice is not a replacement for case management. It adds a phone channel to that service operating model.

In enterprise orgs, the voice project usually fails when teams treat it as a phone migration only. The safer sequence is to confirm case fields, queue ownership, presence statuses, routing rules, and knowledge articles first. Then add the voice channel.

Salesforce voice naming and console experience

The phrase salesforce voice now appears in official documentation, while many orgs, packages, and implementation plans still use Service Cloud Voice. For admins, the key point is the same: agents work in Lightning Experience, usually from a Service Console app, with phone work routed together with other service work.

Trailhead lists browser and setup considerations for Salesforce Voice, including Lightning Experience, an add-on license, supported browsers, cookies for SSO, My Domain or custom domain setup, and Omni-Channel preparation. Confirm these constraints in your target org before you build contact flows or migrate numbers.

How Service Cloud Voice Works in Salesforce

The voice architecture joins four layers: the telephony provider, Salesforce routing, the Service Console, and voice data stored in Salesforce. The exact behavior depends on whether you choose Amazon Connect, partner telephony, or Partner Telephony from Amazon Connect.

Salesforce voice data model: VoiceCall, transcripts, and recordings

The VoiceCall object represents a phone or VoIP call in Salesforce Voice, Sales Dialer, and supported voice connectors. The object reference lists it as available from API v40.0 and later. Common reporting fields include call connected time, call end time, call disposition, and call duration in seconds.

Do not design a custom telephony integration that inserts and updates VoiceCall records with normal Apex DML as the first choice. Salesforce Developer documentation points implementers to the Telephony Integration REST API for real-time voice call lifecycle operations. For transcripts, Salesforce Developer documentation provides Connect REST API resources for uploading and updating transcript content.

Service cloud voice with amazon connect: setup decisions

Service cloud voice with amazon connect is the model most teams evaluate first because Salesforce provides setup paths that connect Voice to Amazon Connect. Salesforce Help states that Amazon Connect can be used with related AWS services such as Amazon Transcribe for real-time transcription, subject to the selected configuration and licensing.

There are two Amazon-related paths to separate during discovery:

• Amazon Connect native model: Salesforce provisions and connects the contact center experience through the guided setup path.
• Partner Telephony from Amazon Connect: the business keeps or uses an Amazon Connect instance while integrating it through the partner telephony path.

The choice affects billing, AWS ownership, IAM work, feature support, test environment design, and support ownership. Write this decision into the architecture document before number porting begins.

Service Cloud Voice Implementation Guide for Salesforce Teams

This service cloud voice implementation guide is written for admins and architects who must turn a phone requirement into a supportable Salesforce design. Start with org readiness, then configure the contact center, then validate call behavior in a sandbox before production cutover.

Service cloud voice implementation guide: prerequisites

Before setup, confirm these items against Salesforce Help, Trailhead, and your Salesforce contract:

• Licensing: Salesforce Voice is an add-on license to Service Cloud or Sales Cloud in the current Trailhead setup guidance.
• Lightning Experience: Voice is supported in Lightning Experience; do not plan a Classic console rollout.
• Browser support: Trailhead setup guidance names Google Chrome and Mozilla Firefox as supported browsers for Voice.
• Authentication: cookies must be enabled for SSO, and Salesforce recommends custom domain and SSO URL preparation before enabling Voice.
• Omni-Channel: enable and test Omni-Channel before adding calls to the routing model.
• Telephony model: choose Amazon Connect, partner telephony, or Partner Telephony from Amazon Connect before you design IVR and reporting.
• Phone numbers: open number porting requests early. Porting can be regulated and can take longer than a sprint.
• AWS quotas: if Amazon Connect is involved, review concurrent active calls, transcription jobs, outbound countries, and network rules.

Step-by-step setup path

1. Document call scenarios. List inbound support, outbound service calls, callbacks, transfers, after-hours handling, emergency messages, and voicemail behavior.
2. Map the Salesforce records. Decide when a call should relate to Contact, Account, Case, Work Order, or a custom object. Keep the first release narrow.
3. Choose the telephony model. Compare Amazon Connect and partner telephony based on required countries, recording rules, transcript support, reporting, and support model.
4. Prepare Omni-Channel. Define presence statuses, capacity, queues, skills, routing priority, and supervisor visibility.
5. Enable Voice in Setup. Follow Salesforce Help for the selected model. For Amazon Connect, use the Amazon Connect setup path. For partner telephony, install and configure the provider package as documented by the provider and Salesforce.
6. Create the console experience. Add the phone utility, Voice Call record page, case highlights, contact panels, quick actions, and knowledge search where agents need them.
7. Configure call flows. Build IVR prompts, queue selection, business-hours logic, fallback routing, and data lookups. Keep PII collection rules aligned with legal and compliance requirements.
8. Assign permissions. Assign Voice permission sets, Service Console access, Omni-Channel access, Knowledge access, report folders, and object access needed for related case work.
9. Test end to end. Validate inbound calls, outbound calls, transfers, missed calls, wrap-up, transcript creation, recording access, supervisor monitoring, and reporting.
10. Cut over in phases. Pilot with one queue, monitor call errors, then migrate more numbers and queues after support teams prove the operating process.

What to test before go-live

Voice vs CTI: Which Should You Use?

Traditional CTI can still be enough when the requirement is click-to-dial, screen pop, and basic call logging. Service Cloud Voice is a better fit when the service team needs voice work inside Omni-Channel, real-time supervisor visibility, voice analytics, and transcript-driven service workflows.

Best Practices for Security, Routing, and Performance

The voice channel touches customer identity, phone numbers, recordings, transcripts, routing rules, and service reports. Treat it as a service architecture project, not a utility bar change.

Secure voice records and related case data

• Use permission sets for agents, supervisors, and admins instead of broad profile changes.
• Review access to VoiceCall, Case, Contact, Account, Knowledge, recordings, transcript data, and report folders.
• Mask or avoid storing sensitive customer data in transcript text when your legal policy requires it. Salesforce Developer documentation includes Connect REST API resources for transcript upload and update use cases, including redaction scenarios.
• Confirm recording consent, retention, and access rules by country before enabling recording for production queues.

Use Apex for reporting helpers, not call lifecycle control

Apex is useful for read-only summaries, post-call automation on related records, and admin dashboards. Do not use Apex to replace the Telephony Integration REST API for real-time call lifecycle operations. The following example reads recent VoiceCall records in a governor-limit-aware way for an LWC dashboard.

public with sharing class VoiceCallSummaryController {
    public class VoiceMetric {
        @AuraEnabled public String disposition;
        @AuraEnabled public Integer totalCalls;
        @AuraEnabled public Decimal averageSeconds;

        public VoiceMetric(String disposition, Integer totalCalls, Decimal averageSeconds) {
            this.disposition = disposition;
            this.totalCalls = totalCalls;
            this.averageSeconds = averageSeconds;
        }
    }

    @AuraEnabled(cacheable=true)
    public static List<VoiceMetric> getLastSevenDayMetrics() {
        if (!Schema.sObjectType.VoiceCall.isAccessible()
            || !Schema.sObjectType.VoiceCall.fields.CallDisposition.isAccessible()
            || !Schema.sObjectType.VoiceCall.fields.CallDurationInSeconds.isAccessible()) {
            throw new AuraHandledException('You do not have access to voice call metrics.');
        }

        List<AggregateResult> rows = [
            SELECT CallDisposition, COUNT(Id) totalCalls, AVG(CallDurationInSeconds) averageSeconds
            FROM VoiceCall
            WHERE CreatedDate = LAST_N_DAYS:7
            GROUP BY CallDisposition
            ORDER BY COUNT(Id) DESC
            LIMIT 20
        ];

        List<VoiceMetric> metrics = new List<VoiceMetric>();
        for (AggregateResult row : rows) {
            metrics.add(new VoiceMetric(
                (String) row.get('CallDisposition'),
                ((Decimal) row.get('totalCalls')).intValue(),
                (Decimal) row.get('averageSeconds')
            ));
        }
        return metrics;
    }
}

This code runs one aggregate query, avoids SOQL in loops, checks object and field access before querying, and uses @AuraEnabled(cacheable=true) because the method is read-only. In a production org, add a test class that creates or loads suitable test data for the fields available in the target org and covers access-denied behavior. Salesforce still requires at least 75% Apex test coverage for deployment, but enterprise teams should cover the security branch and data branch explicitly.

Design routing before building IVR menus

Start from routing outcomes, not prompt wording. For each queue, define who can receive calls, what capacity a call consumes, when calls overflow, and how supervisors intervene. Then build IVR branches that map to those outcomes. This prevents a common error where the IVR offers options that no live support team owns.

Monitor the first release daily

After go-live, monitor missed calls, disconnected calls, time to assign, transcript creation, agent status sync, routing errors, and voice data sync errors. Use Salesforce reports, Voice dashboards where available, telephony provider logs, and support cases for problems that cross the Salesforce and telephony boundary.

Common errors with voice setup

Official Salesforce documentation to review

Use these Salesforce sources before making release or licensing decisions:

• Salesforce Help: Set Up Salesforce Voice
• Salesforce Help: Set Up Salesforce Voice with Amazon Connect
• Salesforce Help: Salesforce Voice Limits and Limitations
• Salesforce Developer Docs: VoiceCall Object Reference
• Salesforce Developer Docs: Telephony Integration API
• Trailhead: Salesforce Voice

Related SalesforceTutorial resources

• Salesforce Service Cloud setup concepts
• Salesforce Omni-Channel routing guide
• Salesforce reports for service operations
• Salesforce AI features for service teams

Frequently Asked Questions