# United States Toll-free number registration process United States Toll-free number registration **Important** It can take up to 15 business days for your registration to be processed after it is submitted. If you use AWS End User Messaging SMS to send messages to recipients in the United States or the US territories of Puerto Rico, US Virgin Islands, Guam and American Samoa, you can use toll-free phone numbers (TFN) to deliver those messages. After you request a TFN you then complete and submit the registration for the TFN. Each TFN requires a specific use case. For example, if you register a TFN to use for one-time passwords, it can only be used for sending one-time passwords. If a TFN is used for anything other than the specified use case, it can be revoked. **Register a toll-free number** 1. You first need to request the toll-free number. When you request the toll-free number in the **Registration Required** window enter a friendly name for the registration. 1. You can begin the registration process by choosing **Begin registration** or choose **Register later** to come back and [complete the form](registrations-tfn-register.md#registrations-tfn-register.title). **Topics** + [ ## Toll-free number forbidden use cases ](#registrations-tfn-forbidden-use-cases) + [ # US toll-free number registration form ](registrations-tfn-register.md) + [ # Toll-free number registration rejection reasons ](registrations-tfn-rejection-reason.md) + [ # Toll-free number frequently asked questions ](registrations-tfn-register-faq.md) ## Toll-free number forbidden use cases Please be aware that AWS is limited in our ability to send any messages or register TFNs for some use cases. Certain use cases are blocked entirely (for example, use cases related to controlled substance, or phishing) and other might be subject to high levels of filtering (for example, high risk financial messages). You might be unable to register TFNs associated with restricted content use cases defined in [Prohibited message content](best-practices.md#best-practices-sms-message-content). # US toll-free number registration form **Note** With our updated console experience you are now seeing a registration **Name** field for your registration. This field is set to "–" as we do not manually backfill any of your service values to prevent interruption to your service and let you maintain your security posture. A registration **Name** is an optional friendly name field that can be updated using the tags on the registration details page. For more information on how to add a **Name** tag, see [Change a registration's name in AWS End User Messaging SMS](registrations-friendly-name.md). After you've created your toll-free number registration you need to complete the form and submit it for approval. **Complete a toll-free number registration** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Registrations**, choose the toll-free number registration to complete. **Note** If you already created a registration when requesting the toll-free number then you can use that registration form. 1. In the **Company info** section, enter the following: + For **Company Name**, enter the name of your company. + For **Company website**, enter the URL for your company's website. + For **Address 1**, enter the street address of your corporate headquarters. + For **Address 2 - optional**, if needed enter suite number of your corporate headquarters. + For **City**, enter the city of your corporate headquarters. + For **State/Province**, enter the state of your corporate headquarters. + For **Zip Code/Postal code**, enter the zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. + For **Business type**, choose the classification of your organization by ownership and purpose. Options include: + **Private profit** – Privately held for-profit company + **Public profit** – Publicly traded for-profit company + **Non-profit** – Non-profit organization + **Sole proprietor** – Sole proprietorship without employees + **Government** – Government entity **Note** Unless you select **Sole proprietor**, the following three company identification fields are required: **Company identification number**, **Identification number type**, and **Identification number country**. + For **Company identification number**, enter your company's official tax identification or registration number (such as EIN or VAT) used to verify your business identity with telecommunications carriers. For example, `12-3456789`. + For **Identification number type**, choose the type of identification number you provided. This helps carriers verify your business credentials with the appropriate government authority. Options include EIN, CBN, CRN, PROVINCIAL\$1NUMBER, VAT, ACN, ABN, BRN, SIREN, SIRET, NZBN, USt-IdNr, CIF, NIF, CNPJ, UID, NEQ, and OTHER. + For **Identification number country**, enter the two-letter ISO country code (for example, `US`, `CA`, `GB`) for the country where your identification number was issued. This must match the country of the authority that issued your identification number. + Choose **Next**. 1. In the **Contact info** section, enter the following: + For **First Name**, enter the first name of the person who will be your business's point of contact. + For **Last Name**, enter the last name of the person who will be your business's point of contact. + For **Support Email**, enter the email address of the person who will be your business's point of contact. + For **Support Phone Number**, enter the phone number of the person who will be your business's point of contact. The phone number must start with a '\$1' and can't contain any spaces, hyphens, or parentheses. For example, `+1 (206) 555-0142` is not in the correct format, but `+12065550142` is. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Use Case Category**, choose one of the following use case types: + **Two-factor authentication** – Use this for sending two factor authentication codes. + **One-time passwords** – Use this for sending a user a one time password. + **Notifications** – Use this if you only intend to send your users important notifications. + **Polling and surveys** – Use this to poll users on their preferences. + **Info on demand** – This is for sending users messages after they have sent a request. + **Promotions and Marketing** – Use this if you only intend to send marketing messages to your users. + **One time passcodes** – Use this for sending one-time passcodes for authentication. + **Non political polling and survey** – Use this to poll users on their preferences. + **Delivery notifications** – Use this for sending delivery status updates. + **Education** – Use this for educational content and notifications. + **Public announcements** – Use this for sending public service announcements. + **Customer care** – Use this for customer support communications. + **Non profit** – Use this for non-profit organization communications. + **Account notifications** – Use this for sending account-related notifications. + **Event notifications** – Use this for sending event-related updates. + **Financial transactions** – Use this for financial transaction notifications. + **Appointment reminders** – Use this for sending appointment reminders. + **Health care** – Use this for healthcare-related communications. + **Booking confirmations** – Use this for sending booking and reservation confirmations. + **Other** – Use this if your use case doesn't fall into any other category. Be sure that you fill out the **Use Case Details** for this option. + Complete **Use Case Details** to provide additional context to the selected **Use Case Category**. + For **Opt-in category**, choose one of the following options: + **Verbal** + **Digital form** + **Paper form** + **Text** + **QR code** + For **Opt-in Workflow Description** enter a description of how users consent to receive SMS messages. For example, by filling out an online form on your website. **Note** If you don't have publicly accessible links to your Terms and Conditions and Privacy Policy documents then you can alternatively attach them to the registration form or another method like an [Amazon S3 presigned URL](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html). + For **Opt-in workflow image**, upload an image showing how users consent to receiving messages. The supported file type is PNG and the maximum file size is 400KB. Additional information and examples of a compliant opt-in workflow can be found at [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). **Important** **Website opt-in**: Mockup or screenshots of a web-form where the client adds their number and agrees to receive messages. **Website Posting (Support)**: Where is the number advertised and where does the customer find the number to text in. **Keyword or QR Code Opt-in**: Where does the customer find the keyword or QR code in order to opt-in to these messages. **2FA/OTP**: Mockup or screenshot of opt-in if applicable, if verbal, provide a mockup or screenshot of the verbal opt-in script. **Informational**: Provide a mockup or screenshot of a verbal consent workflow and provide the messaging content. 1. Choose **Next**. 1. In **Message samples**, do the following: + For **Message Sample 1**, enter an example message of an SMS message body that will be sent to your end users. + For **Message Sample 2 – optional** and **Message Sample 3 – optional**, enter additional example messages, if needed, of the SMS message body that will be sent. 1. Choose **Next**. 1. On the **Review and submit** page verify the information you are about to submit is correct. To make updates choose **Edit** next to the section. 1. Choose **Submit registration**. # Toll-free number registration rejection reasons If your Toll-free number registration was rejected, use the following table to determine why it was rejected and what you can do to fix your Toll-free number registration. After you determine why the registration was rejected, you can modify the existing registration to address that issue and resubmit. For more information, see [Edit a registration in AWS End User Messaging SMS](registrations-edit.md). **Reason for rejection** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Compliant Opt In Missing | The opt-in process or screenshot is missing. A compliant opt-in process or screenshot will clearly specify how your recipient is able to provide their explicit consent to receive SMS messages. Some common rejection reasons: missing explicit language around SMS opt-in consent, mismatch between provided company name and opt-in screenshots, receiving a text message cannot be required to sign up for service, or SMS opt-in consent cannot be included in the Terms of Service. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). | | Invalid Business Connection | The contact information and company/application information does not have a clear connection. SMS Messages can't be sent on behalf of a 3rd party. In order to be verified please resubmit explaining the connection between your contact and company/application information. | | Invalid Company Info | The company information you provided is unable to be verified. In order to be verified please confirm your company website is valid and aligns with your company name and address. | | Invalid Multi Numbers | A single Toll Free number can only be associated with a single business. Please either resubmit a new registration request for each company with its own phone number or explain the connections between the multiple businesses called out. | | Invalid Overall | The information provided has been considered invalid. Please confirm your company website, use case, opt-in, and message samples are all valid inputs and align with other inputs in your registration. | | Invalid URL | The company URL you provided is unable to be accessed. In order to be verified please confirm your provided company website is valid and active. | | Non Compliant Opt In | The opt-in process or screenshot you have provided is either insufficient or non compliant. A compliant opt-in process or screenshot will clearly specify how your recipient is able to provide their explicit consent to receive SMS messages. Some common rejection reasons: missing explicit language around SMS opt-in consent, mismatch between provided company name and opt-in screenshots, receiving a text message cannot be required to sign up for service, or SMS opt-in consent cannot be included in the Terms of Service. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). | | Non Compliant Opt In Consent | The opt-in process or screenshot you have provided does not show explicit consent. Explicit consent is the deliberate action of a user having the option to request a specific message. A compliant opt-in process or screenshot will clearly specify how your recipient is able to provide their explicit consent to receive SMS messages. Some common rejection reasons: missing explicit language around SMS opt-in consent, mismatch between provided company name and opt-in screenshots, receiving a text message cannot be required to sign up for service, or SMS opt-in consent cannot be included in the Terms of Service. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). | | Non Compliant Opt In Third Party | The opt-in process or screenshot you have provided is either insufficient or non compliant due to opt-in information being shared with 3rd parties. A compliant opt-in process or screenshot will clearly specify how your recipient is able to provide their explicit consent to receive SMS messages and is not shared with 3rd parties. Please resubmit after you remove any language around opt-in information sharing or include language specifically stating opt-in information is not shared with 3rd parties. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). | | Non Compliant Use Case | The use case and/or message samples provided are considered restricted content under US Telecom regulations. Please refer to the documentation below for a full list of items considered restricted content. If you believe your content is falsely considered restricted you can attempt to update your sample messages and use case and re-submit the registration. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). | # Toll-free number frequently asked questions Frequently asked questions about the toll-free number registration process. ## Do I currently own a toll-free number? **To check if you own a toll-free number** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **SMS and voice**, choose **Phone numbers**. 1. Toll-free numbers have their **type** listed as **toll free**. ## Do I have to register my toll-free number? Yes. If you currently own a toll-free number, you must register to use it. ## How do I purchase a toll-free number? Follow the directions at [Request a phone number in AWS End User Messaging SMS](phone-numbers-request.md) to purchase a toll-free number. ## How do I register my toll-free number? If you already procured your TFN and created a registration form then follow the directions at [US toll-free number registration form](registrations-tfn-register.md) to complete the form. If you need to create a registration then follow the directions at [Create a new registration using the AWS End User Messaging SMS console](registrations-create.md) to register a toll-free number. ## What is the registration status of my toll-free number and what does it mean? Follow the directions at [Check a registration's status in AWS End User Messaging SMS](registrations-status.md) to check your registration and status. ## What information do I need to provide? You will need to provide your companies address, a business contact, and a use case. You can find the required information at [US toll-free number registration form](registrations-tfn-register.md). ## What if my registration is rejected? If your registration is rejected, its status will be changed to **Requires Updates** and you can make updates by following the directions in [Edit a registration in AWS End User Messaging SMS](registrations-edit.md). ## What permissions do I need? The IAM permissions that you use to visit the AWS End User Messaging SMS console must be enabled with the *`“sms-voice:*”`* permission.