Service Cloud Voice for Partner Telephony Developer 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)
Overview
Recent Changes
Key Provisioning
Add a Partner Settings UI to Omni-Channel
Desk Phone Support
Apex Reference
Troubleshooting
Newer Version Available
Customize Your Implementation
Use this information to customize the setup and add vendor value to your
implementation.
This guide is for telephony providers who are creating a solution that integrates Service Cloud Voice with their telephony system. If that’s not you, see the Service Cloud Voice Implementation Guide or Salesforce Help.
Important
-
Automated Key Provisioning with Service Cloud Voice for Partner Telephony
When a contact center is created and connected with the partner telephony system, the public key for the contact center can be provisioned automatically with an Apex call to the partner system. -
Add a Partner Settings UI to Omni-Channel
Partners can launch a Lightning component from the Omni-Channel widget with their own additional settings. This Lightning component is shown in the Additional Settings section along with other common agent settings. -
Communicating with Lightning Components
You can communicate between a Lightning component and your telephony system using two different options: the Lightning Message Bridge and the Service Cloud Voice Toolkit API.