AWS End User Messaging FAQ

AWS End User Messaging is self-service so you can try before you buy, without talking to sales, completing RFPs, or hiring for consultants or professional services. Simply log in to the AWS End User Messaging console using your AWS account and set up an AWS End User Messaging channel. To learn how to set up AWS End User Messaging, see the Getting Started tutorial.

A sender ID is an alphabetic name that identifies the sender of an SMS message. When you send an SMS message using a sender ID, and the recipient is in an area where sender ID authentication is supported, your sender ID appears on the recipient's device instead of a phone number. A sender ID provides SMS recipients with more information about the sender than a phone number or short code provides.

Sender IDs are supported in select countries and regions around the world. In certain places, if you're a business that sends SMS messages to individual customers, you must use a sender ID that's pre-registered with a regulatory agency or industry group. For a complete list of countries and regions that support or require sender IDs, see Supported countries and regions (SMS channel).

For advantages and disadvantages of sender IDs see the AWS End User Messaging User Guide.

Short codes are numeric sequences that consist of fewer digits than regular phone numbers. For example, in the United States and Canada, standard phone numbers (long codes) contain 11 digits, while short codes contain five or six digits. If you send a large volume of SMS messages to recipients in the United States or Canada, you can purchase a short code. This short code is reserved for your exclusive use.

For advantages and disadvantages of using short codes see the AWS End User Messaging User Guide.

While End User Messaging does not support porting numbers from external providers, if short codes satisfy your SMS use case, you are able to request a vanity (i.e. custom or preferred digits) Short Code in select countries.

More information on requesting short codes and long codes can be found in Request support for SMS messaging with AWS End User Messaging.

Yes, AWS End User Messaging supports Sender ID registration in select countries.

For a complete list of countries and regions that End User Messaging supports Sender ID registration in, visit Supported countries and regions (SMS channel).

While End User Messaging does not support the same SMS numbers in multiple accounts or regions, by using IAM policies you can setup cross-account access by delegating other AWS accounts to use your numbers.

For more information on setting up cross-account permissions through IAM policies, seeing Setting up 10DLC cross-account access.

AWS End User Messaging offers developers a single API layer, CLI support, and client-side SDK support to be able to extend the communication channels through which their applications engage users. These channels include: SMS text messaging, mms push notifications, and voice messages.

10DLC is a new standard for sending messages from applications such as AWS End User Messaging to individual recipients. This type of sending is known as Application-to-Person or A2P messaging. You can use 10DLC phone numbers to send text messages to your customers with high throughput and high rates of message delivery.

To use 10DLC numbers, carriers require that you register information related to your company as well as your use case (also called your 10DLC campaign). You complete these registration processes directly in the AWS End User Messaging console. After your company and 10DLC campaign are approved, you can purchase a phone number and associate it with your campaign.

After June 1, 2021, unregistered US long codes will only be available for use with the voice channel. You won’t be able to use unregistered US long codes to send SMS messages.

To send SMS messages to recipients in the US, you must use either a short code, a 10DLC phone number, or a toll-free number.

If you don’t do anything, unregistered long codes will remain in your account. You’ll continue to pay $1 per month for each unregistered long code. However, you won’t be able to use unregistered US long codes to send text messages.

You can keep your unregistered long codes if you plan to use them to send voice messages to your customers. You can also convert unregistered long codes to 10DLC phone numbers if you want to continue to use them to send text messages.

If you don’t want to keep your unregistered long codes, you can delete them in the AWS End User Messaging console.

If you complete the 10DLC conversion process before June 1st, 2021, you won’t experience any downtime. If you begin the conversion process after this date, you may experience several days of downtime.

It’s important to note that 10DLC campaigns are completely separate from and unrelated to AWS End User Messaging campaigns.

A 10DLC campaign is a description of your use case. During the 10DLC campaign registration process, you must describe the use case and provide the message templates that you plan to use. For more information, see Registering a 10DLC Campaign in the AWS End User Messaging User Guide.

Yes. If you only have one US phone number in your account—whether it’s a 10DLC number, a short code, or toll-free number—all of the messages that you send to recipients in the US will be sent through that number.

If you have multiple numbers in your AWS End User Messaging account, you can specify your Origination Number in your call to the AWS End User Messaging API. If you don’t specify an originating number, AWS End User Messaging looks for the best number to use to send your message. If you have a short code in your account, AWS End User Messaging will send using that number. If you don’t have a short code, it looks for a 10DLC phone number, and attempts to send using that number. If you don’t have a 10DLC number, it looks for a toll-free number, and attempts to send using that number.

You can associate multiple phone numbers with a 10DLC campaign. However, you can’t associate a single phone number with more than one 10DLC campaign. Using multiple phone numbers for the same campaign doesn’t provide any added benefit in terms of throughput.

It takes up to 14 business days to associate a new phone number with a 10DLC campaign. When the association process is complete, the status changes to ‘Ready.’

Yes, it is possible to purchase a 10DLC phone number through the AWS End User Messaging SMS console or AWS CLI.

The 10DLC company and campaign registration processes are connected to your AWS account, and is not tied to a specific AWS Region. You can have multiple 10DLC numbers that unique to a specific AWS Region. These phone numbers can all be associated with the same 10DLC campaign.

No, we don’t currently provide the option of specifying an area code when you purchase a phone number.

No, 10DLC is a concept that only applies to messages sent to recipients in the US who have US phone numbers.

Yes. When you purchase a phone number to use with a 10DLC campaign, you can specify whether you want to use the number to send SMS messages, voice messages, or both. As long as you enable the voice capability when you purchase a number, you can use that number to send voice messages.

You can use placeholders for variables in your sample messages to indicate variable content. For example, for the below sample message: “Hi John, your OTP is 1234” can be written as “Hi {#var}, your OTP is {#var}.”

While it is possible to migrate 10DLC registrations between AWS accounts, it may take several weeks to complete the transfer process. For this reason, we recommend that you complete the 10DLC registration process in your primary production account. You can then use cross-account access to share your 10DLC phone numbers with other AWS accounts, such as your test or development accounts.

No. In this situation, you would have to register again through the AWS End User Messaging console.

10DLC company and campaign registrations apply to your entire AWS account, but individual phone numbers are specific to each AWS Region. You can register your 10DLC company and campaign in one Region, and then use cross-account access to share phone numbers across Regions.

By default, AWS End User Messaging limits the number of SMS messages that you can send to 20 per second. If you exceed this account-level limit, you will receive throttling errors. However, you can request an increase to this limit.

With 10DLC, the mobile carriers calculate a trust score for each sender during the company and campaign registration processes. This trust score determines how many messages each carrier will accept from you. If you exceed the limits for your campaign for a particular carrier, that carrier will begin rejecting your messages. We highly recommend that you enable event streaming in order to track these events.

Yes, 10DLC phone numbers support two-way messaging.

10DLC company and campaign registrations are managed through a third-party organization called the Campaign Registry. Currently, the Campaign Registry only allows a company to be registered once for each sending application (such as End User Messaging). However, you can use cross-account access to allow multiple AWS accounts to send SMS messages using the same 10DLC phone number.

The mobile carriers don’t allow senders to use links that have been shortened using services such as bit.ly or TinyURL. We recommend that you use the full domain of your URLs when you include links in your messages. Alternatively, there are commercial URL shortening services that let you use dedication domains. You can even build a URL shortener using AWS services. If you use a custom URL shortening domain, the domain name should be obviously related to your brand. During the 10DLC campaign registration process, you should provide examples of your shortened URLs when you provide your message templates.

Yes. The Amazon SNS console currently doesn’t include a way to register 10DLC companies and campaigns. However, you can use the 10DLC phone numbers that you configured in the AWS End User Messaging console to send messages using Amazon SNS.

With AWS End User Messaging voice, you can engage with your customers by delivering voice messages over the phone. End User Messaging voice gives customers a great way to deliver transactional messages—such as one-time passwords, appointment reminders, order confirmations, and more. With End User Messaging voice capabilities, you can convert a text script to lifelike speech, and then deliver the personalized voice message to your customer. Call metrics—such as number of calls completed and number of calls failed—help you to optimize future voice engagements. With both End User Messaging voice and SMS channels available to you, you can send SMS messages to customers who prefer text and deliver voice messages to those who are either unable to receive SMS messages. With the addition of the voice channel, you can now use AWS End User Messaging to seamlessly engage your customers with timely, relevant content through push notifications, email, SMS, and voice calls.
Amazon Connect is an easy-to-use omnichannel cloud contact center that helps companies provide superior customer service at a lower cost.

Over 10 years ago, Amazon’s retail business needed a contact center that would give our customers personal, dynamic, and natural experiences. We couldn’t find one that met our needs, so we built it. We've now made this available for all businesses, and today thousands of companies ranging from 10 to tens of thousands of agents use. To learn more, see Amazon Connect.

A very limited number of authorized AWS employees have access to the data stored in your AWS End User Messaging account. Maintaining your trust is our highest priority. We use sophisticated physical and technical controls to help safeguard your privacy and the security of your data. Your data is encrypted at rest and during transit. Our processes are designed to prevent unauthorized access to or disclosure of your content

For more information, see the AWS Data Privacy FAQ.

You always retain ownership of your content. We only use your content with your consent.

You can selectively delete the data stored in your AWS End User Messaging account or you can close your entire AWS account. After the post-closure period, AWS permanently closes your AWS account, and you can no longer reopen it. Any content that you didn't delete is permanently deleted, and any AWS services that you didn't stop are stopped. For more information, see deleting data from AWS End User Messaging in the AWS End User Messaging Developer Guide or on our Account Closure page.

Mobile carriers in the US will assess a fee each time an Application-to-Person (A2P) SMS is sent over their networks. The AWS carrier fees cover these charges and are subject to change when mobile carriers change their fees.

Charges apply to all deliveries when messages leave AWS and reach downstream infrastructure, regardless of delivery success.

Your AWS Account Manager can send your feature requests and feedback directly to the appropriate team. If you don't currently have an AWS Account Manager, you can also provide your feedback on the AWS End User Messaging forum.

If you have an AWS Support plan, you can create a new support case directly from the web-based AWS management console. AWS Support plans begin at $29 per month. For more information about AWS Support plans, visit https://aws.amazon.com/premiumsupport/.

To open a new technical support case:

• In the console, on the Support menu, choose Support Center.

• Choose Create case.

• On the Create case page, choose Technical support.

• Provide information about the issue you're experiencing, and then submit the ticket.

If you don't have an AWS Support plan, you can also ask questions and get answers on the AWS End User Messaging forum.