Service Cloud Voice Implementation Guide
jSummer '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
Create a Voice Call Record
Update a Voice Call Record
Create a Transcript
Execute an Omni-Channel Flow
Clear Routing
Sample Code
Authorization
Connect API to Update Transcripts
Newer Version Available
Using the Telephony Integration REST API
The Telephony Integration REST API allows you to programmatically manage a voice call.
The provided Amazon Connect Lambda functions automatically use these endpoints to perform
telephony functions, but you can also use these APIs separate from the provided Lambda
functions.
-
Create a Voice Call Record
Creates a voice call (VoiceCall) record containing the participants (that is, the caller and recipient) in the call. -
Update a Voice Call Record
Updates a voice call (VoiceCall) record after the call has ended. Use this API to update parameters of a voice call record that are unavailable during the voice call record creation stage. The endpoint is an asynchronous operation. You can’t query for the status of the API call. -
Create a Transcript
Creates a transcribed version of a voice call in real time so agents can refer to it during and after a call. This API allows you to create transcripts for in-progress calls only. -
Execute an Omni-Channel Flow
Executes the Omni-Channel flow to route voice calls. It passes the call ID (Salesforce VoiceCallId or telephony vendor ContactId) as parameters to the flow and returns the agent or queue routing instructions to the contact flow. By default, Service Cloud Voice uses the Omni-Channel flow (or fallback queue) specified for the phone channel that matches the dialed number. If the dialed number doesn’t match an existing phone channel, you can optionally set a new dialed number, Omni-Channel flow, and fallback queue as input parameters to this API call. -
Clear Routing
Deletes the PendingServiceRouting (PSR) record for a voice call. This API doesn’t need to be called for most scenarios; the PSR record is automatically deleted when the call is no longer being routed. However, there are some scenarios, like for missed or abandoned calls when using partner telephony systems (excluding Amazon Connect), where you must explicitly call this API to clear the PSR record. -
Telephony Integration REST API Sample Code
The following JavaScript code sample performs the authorization process and then invokes the Voice API. -
Telephony Integration REST API Authorization
The Telephony Integration REST API requires JWT authorization. Usually, the provisioning process already sets up this authorization for you. This content simply provides instructions in case you must manually set up this authorization.