Prepare for your US Short Code submission - AWS End User Messaging SMS
Required documentationCall-to-action and opt-in requirements
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Prepare for your US Short Code submission

Before submitting your short code registration, review the following industry guidelines to ensure your SMS campaign is compliant with carrier requirements:

Required documentation

Before starting your short code registration, prepare the following documentation:

  • SMS Terms & Conditions – Create a specific Terms of Service document for your SMS campaign. This document should be accessible to the public. While it's not necessary for these terms to be published online when you submit your campaign for approval, you must provide a draft version and specify the URL where these terms will eventually be posted. If your Privacy Policy doesn't already include these Terms of Service, submit them as a separate document. For a template that covers carrier requirements, see the SMS and MMS specific Terms and Conditions section in the AWS End User Messaging SMS Best Practices guide.

  • Call-to-action/Opt-in Mockup – Include either a visual mockup or a written script (for verbal sign-ups) showing exactly how you plan to get users to join your program and obtain their consent. This should demonstrate how you'll present your program to potential subscribers. Certain mandatory disclaimers must be shown to users before they can give their consent to participate.

  • Prohibited content confirmation – Ensure your SMS campaign isn't in any of the prohibited categories. Carriers won't accept or review any applications that involve restricted content types. Review the list of prohibited message content in the AWS End User Messaging SMS Best Practices guide.

Call-to-action and opt-in requirements

The following items are the minimum that must be presented to an end-user at the time of opt-in to ensure your SMS program is compliant:

  • Program (brand) name – Clearly identify your company or brand name.

  • Message frequency disclosure – Inform users how often they can expect to receive messages. For example: "Message frequency varies" or "One message per login".

  • Customer care contact information – Provide a way for users to get help. For example: "Text HELP or call 1-800-111-2222 for support."

  • Opt-out information – Explain how users can stop receiving messages. For example: "Text STOP to opt-out of future messages."

  • "Message and data rates may apply" disclosure – Include this standard carrier disclosure.

  • Link to Terms & Conditions – Provide a link to a publicly accessible Terms & Conditions page.

  • Link to Privacy Policy – Provide a link to a publicly accessible Privacy Policy page.

For more information on building a compliant opt-in process, see the How to Build a Compliant SMS Opt-In Process blog post.