Service Cloud Voice Implementation Guide
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Service Cloud Voice Best Practices for Error Handling
To ensure service availability and an optimal customer experience, follow these best
practices for managing throughput limits and errors.
-
Monitor Transcription-Related Limit Errors
When your org exceeds the transcription limit, utterances are no longer transcribed. Track when your org hits the transcription limit by using a custom field on the VoiceCall object. -
Monitor VoiceCall Limit Errors
When your org exceeds the limit for the maximum number of concurrent calls, the system can’t create VoiceCall records. Track when your org hits the concurrent call limit or the phone calls initiated per second limit by checking output of the InvokeTelephonyIntegrationApi Lambda function.