Applies to these telephony models for Salesforce Voice (formerly Service Cloud Voice):
Voice resiliency ensures that the telephony system stays operational when the number of conversations is over limit or when the background service is affected. During this period, certain features and functionalities may be impacted.
What Will Work
At a high level, the following functionalities will work:
Voice calls. Agents will be able to make and receive calls. Call transfers and callbacks will work.
VoiceCall/AgentWork data. VoiceCall and AgentWork records will be created, and interactive voice response (IVR) data will be saved to the VoiceCall entity.
What Won't Work
The following features and functionalities may be negatively impacted or not work:
Omni-Channel flows related to voice calls that depend on the flows. This includes routing, real-time queue backlogs in Omni Supervisor, Screen Pops, and Channel-Object Linking won’t work.
Post-call sync. Post-call data including voice recordings won’t sync to Salesforce but are still available in the vendor’s system. You can manually resync the post-call data by following the steps in the Retry CTR Sync for VoiceCall Records page.
Einstein Conversation Insights.
Voice-call transcriptions. Real-time transcription won’t work. Voice-call transcripts won’t be saved and will therefore not appear in the Conversation Body component on the Voice Call Record Page. You can use the Connect API (/connect/conversations/upload) endpoint to manually resync the data between Salesforce and your telephony system.
Conversation Intelligence. Rule-triggered actions based on real-time intelligence signals and keyword detection won’t work.
Voicemails. Voicemails that rely on the original VoiceCall record won’t be delivered.
Raise flag and send whisper capabilities.
Listen In capabilities.
To ensure your environment is set up correctly for voice resiliency, refer to the following pages in the Salesforce Voice developer guides:
000395549

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.