Enhanced domains are the current version of My Domain that meets the latest security standards. Some URLs that are used for Salesforce Voice (formerly Service Cloud Voice) features, such as the Connector URL, the telephony API (SCRT2 URL), and the Connect API URL, contain the domain value.
This configuration applies to the following telephony models:
Effective Spring ‘23, enhanced domains were deployed to sandbox, non-production, and production orgs. Customers had the option to postpone (disable) enhanced domains in their sandbox and non-production orgs before those orgs were upgraded to the Spring '23 release. See the Enhanced Domains and Their Impact on Salesforce Voice (Winter ’23) article for more information.
In the following releases, this is how enhanced domains will affect all orgs, including sandbox, non-production, and production orgs:
See the Enhanced Domains page for more information about enhanced domains and general timelines.
If your telephony provider is Amazon Connect, when enhanced domains are enabled in an org, Salesforce automatically upgrades all of the contact centers in the org to the latest available contact center version. Why do we automatically upgrade the contact centers? Because when enhanced domains are enabled, the org’s My Domain value and SCRT2 URL change on the Salesforce side. To keep things running smoothly with Amazon Connect, we need to add these updated values to the AWS Lambda functions, and the best way to do this is to upgrade the contact centers. Note that even if you manually change your org’s My Domain value through the Salesforce My Domain page, the contact centers will still be automatically updated.
Prepare for the Winter ‘24 release when enhanced domains must be enabled in all orgs.
If Salesforce created a new AWS Account and provisioned a new Amazon Connect instance for you, you don’t have to do anything. When enhanced domains are enabled, we’ll automatically take care of everything behind the scenes.
If you want to keep your customized AWS Lambda functions, you can roll back the Lambda function updates. Refer to the Roll Back an AWS Lambda Function Update After Enhanced Domains is Enabled section for steps.
If you originally set up Salesforce Voice by provisioning the Amazon Connect instance through Salesforce, you don’t have to do anything. When enhanced domains are enabled, we’ll automatically take care of everything behind the scenes.
If you want to keep your customized AWS Lambda functions, you can roll back the Lambda function updates. Refer to the Roll Back an AWS Lambda Function Update After Enhanced Domains is Enabled section for steps.
If you used an existing AWS Account to manually provision an Amazon Connect instance using XML import files, perform the following one-time steps to ensure users can log in and use Salesforce Voice.
After you’ve performed the steps, if you want to keep your customized AWS Lambda functions, you can roll back the Lambda function updates. Refer to the Roll Back an AWS Lambda Function Update After Enhanced Domains is Enabled section for steps.
ScrtEndpointUrl:
Type: String
Default: salesforce-scrt-endpoint-url
Description: Salesforce realtime server endpoint URL
You can update the SCRT Endpoint URLs through CloudFormation or by manually updating the URL in each of the impacted Lambda functions.
To update the SCRT Endpoint URLs through CloudFormation:
To update the SCRT Endpoint URL in each of the impacted Lambda functions:
To verify your My Domain name, from Salesforce, go to Salesforce > Setup > MyDomain.
If you originally set up Salesforce Voice with a partner telephony that’s not Amazon Connect, perform the following one-time steps after Enhanced Domains is enabled.
This configuration applies to the following telephony model:
You can temporarily disable enhanced domains. However, we highly recommend that you enable enhanced domains well in advance of the Winter ‘24 release to give yourself enough time to test your environments with the new settings.
This configuration applies to the following telephony model:
If you have customized AWS Lambda functions and don’t want them to be replaced with the latest, upgraded versions when enhanced domains is enabled, you can roll back the Lambda update. To do this, after you perform the rollback, manually update certain environment variable URLs in your Lambda functions to point to the new, enhanced domains URL version.
To roll back a Lambda function update that’s triggered when enhanced domains is enabled:
See also:
000394652

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.