As a Salesforce Voice (formerly Service Cloud Voice) with Amazon Connect customer located inside the United States, learn how to change the AWS subaccount billing address that determines emergency calling fees for Amazon Connect.
Starting March 1, 2025, AWS began including emergency calling (911/988) fees for several AWS services, including Amazon Connect. These fees are in line with state, county, and city regulations for emergency calling and are determined by the billing address associated with the AWS account.
These e911 charges are billed in arrears, for example, charges incurred in March appear on the April bill. The charges appear as a separate invoice item and are listed separately for each AWS service.
These monthly charges are passed through from AWS to Salesforce to Salesforce Voice with Amazon Connect customers in the monthly telephony invoice. For customers with companies outside the United States, their company’s billing address is used for AWS subaccounts. For customers with companies inside the United States, Salesforce uses its address for AWS subaccounts instead.
To make sure that AWS correctly calculates emergency calling fees, all existing Salesforce Voice with Amazon Connect customers with companies in the United States must update the billing address in their AWS console.
Here are steps to update the address.
Sign in to the AWS Management Console with your root user account and open the AWS Billing and Cost Management console at https://console.aws.amazon.com/costmanagement/.
On the navigation bar in the upper-right corner, select your account name (or alias), and select Account.
In the Contact information section, select Edit.
Update the Address to your company’s address.
Click Update to save your work.
If you don’t take these steps to update the AWS billing address for Salesforce Voice with Amazon Connect, AWS will determine and charge emergency calling fees for the wrong jurisdiction.
See Also
005108661

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.