Before updating the contact center, review the change details such as the enhancements and the error fixes corresponding to the contact center version 21.X.
Required Editions
| View supported editions. |
This article applies to:
- Salesforce Voice with Amazon Connect
- Salesforce Voice with Partner Telephony from Amazon Connect
Contact Center v21.2
Contact center version 21.2 is available from August 17, 2026.
This version includes these changes.
| Change | Applicable Telephony Models |
|---|---|
| Enhanced the invokeTelephonyIntegrationApi lambda function with an API endpoint that generates a correlation ID to support end-to-end call context linking. Also added an optional field to the reserveRoutableNumber API to preserve the original caller number through the call flow. |
|
Contact Center v21.1
Contact center version 21.1 is available from July 18, 2026.
This version includes these changes.
| Change | Applicable Telephony Models |
|---|---|
| Fixed real-time transcription with AWS Transcribe to ensure transcript messages deliver reliably during calls. This update resolves errors that previously prevented transcripts from appearing in real time. |
|
| Enhanced the invokeTelephonyIntegrationApi lambda function with an API endpoint to support Dynamic Voice Routing for Agentforce Voice on Amazon Connect. The API dynamically allocates a Direct Inward Dialing (DID) Public Switched Telephone Network (PSTN) number based on the provided country and caller number. |
|
Contact Center v21.0
Contact center version 21.0 is available from May 8, 2026.
This version includes these changes.
| Change | Applicable Telephony Models |
|---|---|
| Introduced retry logic with exponential backoff for the Contact Lens processor, KVS Transcriber, and post-call analysis to handle rate-limiting responses from the Conversation Service. This change makes transcription and conversation analysis more reliable. |
|
| Added support for a scheduled routing date and time parameter for the Callback Telephony API, enabling callbacks to be scheduled at a planned time if required. |
|
| Improved logic for the recording upload process to make sure that call recordings are only uploaded when a rep is connected, preventing IVR-only segments from being incorrectly linked to voice call records. |
|
|
Added a lambda enhancement to dynamically generate and pass JWT tokens into the User-to-User Information (UUI) section during SIP transfers so that the Amazon Connect IVR consumes secure parameters. |
|
|
Introduced a contact ID ownership check while processing voicemail audio, preventing data corruption and mixed or incomplete recordings during high-load periods. |
|
| Addressed multiple security vulnerabilities and upgraded infrastructure dependencies to ensure compliance. |
|
| Introduced a new Lambda function to retrieve recording URLs from cache or from entity data for Voicemail Drop and Voicemail Greeting features, providing a single, optimized path to access recording data. |
|