External client apps (ECAs) are the next generation of connected apps, designed to improve security and address packaging and distribution issues. While existing connected apps for Salesforce Voice with Partner Telephony integrations continue to work, you aren’t able to create new connected apps without first requesting the ability from Salesforce Support. Because Salesforce plans to eventually replace connected apps with ECAs, consider migrating to an external client app for Salesforce Voice with Partner Telephony.
Where: This change is available in Salesforce orgs with this telephony model.
- Salesforce Voice with Partner Telephony
View supported editions for Salesforce Voice.
Who: This change impacts partners who create integrations for Salesforce Voice with Partner Telephony. It also affects customers who configure single sign-on (SSO) with Salesforce as the identity provider.
How: Inventory your connected apps and consider migrating to ECAs to prepare for the end of support. For new integrations, use an external client app. If you must create a new connected app, contact Salesforce Support to request access to this functionality.
See Also
- Salesforce Voice with Partner Telephony Developer Guide: Create Developer Hub and Namespace Orgs
- Salesforce Voice with Partner Telephony Developer Guide: Set Up Single Sign-On
- Salesforce Help: Configure Single Sign-On (SSO) with Salesforce as the Identity Provider
- Salesforce Knowledge Article: New connected apps can no longer be created in Spring ‘26