Service Cloud Voice Implementation Guide
Winter '27 preview (API version 68.0)
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
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)
Overview
Connect API to Update Transcripts
Org Limits
Customer Example
Monitor Transcription-Related Limit Errors
Concurrent Call Limit Errors
Monitor VoiceCall Limit Errors
Newer Version Available
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. -
Concurrent Call Limit Errors
There is a maximum of 2,000 concurrent calls at a single time in an org. This maximum includes both inbound and outbound calls. So, what happens on the 2,001st concurrent call? It depends on whether the call is inbound or outbound. -
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.