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.