# Dedicated number registration forms The Dedicated SMS Number Registration Forms section provides step-by-step guidance for registering your dedicated SMS codes with AWS. Before you can use dedicated numbers for SMS messaging, you must submit the appropriate registration forms for your use case and region. This form is required for registering a dedicated SMS number (both short and long codes) in the following countries: **Topics** + [Australia](dedicated-number-australia.md) + [Austria](dedicated-number-austria.md) + [Chile](dedicated-number-chile.md) + [Denmark](dedicated-number-denmark.md) + [Finland](dedicated-number-finland.md) + [Germany](dedicated-number-germany.md) + [Hong Kong](dedicated-number-hong-kong.md) + [Hungary](dedicated-number-hungary.md) + [India](dedicated-number-india.md) + [Italy](dedicated-number-italy.md) + [Netherlands](dedicated-number-netherlands.md) + [Norway](dedicated-number-norway.md) + [Poland](dedicated-number-poland.md) + [Portugal](dedicated-number-portugal.md) + [Spain](dedicated-number-spain.md) + [Sweden](dedicated-number-sweden.md) + [United Kingdom](dedicated-number-united-kingdom.md) + [United States 10DLC registration](registrations-10dlc.md) + [United States Toll-free number registration](registrations-tfn.md) + [United States Short Code registration](registrations-us-short-code.md) # Australia dedicated number registration in AWS End User Messaging SMS Australia Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Australia. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Austria dedicated number registration in AWS End User Messaging SMS Austria Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Australia. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Chile dedicated number registration in AWS End User Messaging SMS Chile Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Chile. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Denmark dedicated number registration in AWS End User Messaging SMS Denmark Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Denmark. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Finland dedicated number registration in AWS End User Messaging SMS Finland Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Finland. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Germany short code registration in AWS End User Messaging SMS Germany Follow these directions to register your short code in Germany. **Complete Germany short code registration form** 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 registration to complete. 1. In the **Company info** section, enter the following: + For **Company name**, enter the legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **DBA (Doing Business As) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City**, enter the city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the **Service information and use case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your short code, and how you will interact with end users. + For **Service name**, enter the name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this short code. + For **Monthly outbound SMS volume**, enter the estimated number of SMS messages which will be sent from this short code each month. + For **Monthly inbound SMS volume**, enter the estimated number of SMS messages which will be received by this short code each month. + For **Estimated monthly contacts**, enter the estimated number of unique users you expect to contact in one month. + For **Peak volume hours**, specify the days and hours when you expect the highest volume of messages (for example, Mon-Fri 08:00-09:00). + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Required end-user input**, describe what actions end-users must take to use the service. Include both initial activation and ongoing interaction requirements. + For **Service reply logic**, explain how your service will respond to various user inputs. Include all possible response scenarios and message templates. + For **Error handling process**, detail how your service responds to incorrect inputs, misspelled commands, or invalid responses from users. Include example error messages and recovery procedures. + For **Advertising channels**, select all media channels through which the service will be advertised to end-users. Options include Website, Television, Radio, Print Media, Social Media, and Other. + For **Customer service phone number**, enter the phone number your users can call to contact customer service. + For **Customer service email address**, enter the email address your users can use to contact customer service. + For **Customer service hours**, specify the days and hours when customer service is available (for example, Mon-Fri 08:00-17:00). + For **Opt-in method**, enter how the user will opt-in. + For **Opt-in method other**, if you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Hong Kong dedicated number registration in AWS End User Messaging SMS Hong Kong Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Hong Kong. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Hungary dedicated number registration in AWS End User Messaging SMS Hungary Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # India dedicated number registration in AWS End User Messaging SMS India Registering a dedicated number is the first step in creating an origination identity. To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in India. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Italy dedicated number registration in AWS End User Messaging SMS Italy Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Netherlands dedicated number registration in AWS End User Messaging SMS Netherlands Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Norway dedicated number registration in AWS End User Messaging SMS Norway Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Poland dedicated number registration in AWS End User Messaging SMS Poland Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Portugal dedicated number registration in AWS End User Messaging SMS Portugal Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Spain dedicated number registration in AWS End User Messaging SMS Spain Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # Sweden dedicated number registration in AWS End User Messaging SMS Sweden Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # United Kingdom dedicated number registration in AWS End User Messaging SMS United Kingdom Registering a dedicated number is the first step in creating an origination identity. To request a long code phone number, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). To register a short code number, see [Requesting dedicated short codes](phone-numbers-request-short-code.md). Follow these directions to register your dedicated number in Italy. **Complete Common Dedicated Number registration form** 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 registration number 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 legal name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company website. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the ** Service Information and Use Case** section, enter the following: In order to give approval, mobile carriers need to know how you plan to use your dedicated number, and how you will interact with end users. + For **Service name**, Name of your SMS service or feature. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a description of your use case for sending SMS messages with this long code.. + For **Monthly SMS volume**, enter a estimated number of SMS messages which will be sent from this long code each month. + For **Is this a one-way or two-way program?**, select whether you require only sending outbound messages with this number or if you require 2-way messaging (both outbound and inbound). + For **Opt-in Method**, enter a how the user will opt-in.. + For **Opt-in method other**, ff you chose Other, please explain. + For **Opt-in method user experience flow 1**, provide a step-by-step description of the end user experience when signing up for the SMS service.. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 2**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in location. + For **Opt-in method user experience flow 3**, provide a step-by-step description of the end user experience when signing up for the SMS service. + For **Opt-in mock-up 3**, attach a mock up showing the call-to-action or opt-in location. 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**. # United States 10DLC registration United States 10DLC registration **Important** The following table has the expected times for each 10DLC registration step based on if your business is located in the United States or internationally. **** | 10DLC registration step | US based companies | International based companies | | --- | --- | --- | | Register your brand/company | 1-2 business days | Up to 3 weeks | | Apply for vetting | 1-2 business days | Up to 3 weeks | | Register your campaign | Up to 4 weeks | Up to 4 weeks | | Request your 10DLC number | Up to 10 days | Up to 10 days | 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 10DLC phone numbers to deliver those messages. The abbreviation *10DLC* stands for "10-digit long code." A 10DLC phone number is registered for use by a single sender and for a single use case. This registration process gives the mobile carriers insight into the approved use cases for each phone number that is used to send messages. As a result, 10DLC phone numbers can offer high throughput and deliverability rates. A message that you send from a 10DLC phone number appears on the devices of your recipients as a 10-digit phone number. You can use 10DLC phone numbers to send both transactional and promotional messages. If you already use short codes or toll-free numbers to send your messages, then you don't need to set up 10DLC. To set up 10DLC, you first register your company or brand. You should then externally vet your 10DLC company to ensure you get the highest eligible throughput. Next, you create a *10DLC campaign*, which is a description of your use case. This information is then shared with the Campaign Registry, an industry organization that collects 10DLC registration information. **Note** For more information about how the Campaign Registry uses your information, see the FAQ on the [Campaign Registry website](https://www.campaignregistry.com/resources/). After your company and 10DLC campaign are approved, you can purchase a phone number and associate it with your 10DLC campaign. Associating a phone number with a 10DLC campaign can take approximately 14 days to complete. Although you can associate multiple phone numbers with a single campaign, you can't use the same phone number across multiple 10DLC campaigns. For each 10DLC campaign that you create, you must have at least one unique phone number. Throughput for 10DLC phone numbers is based on the company and campaign registration information that you provide. Each 10DLC number associated to a campaign supports 1 message part per second (MPS). In order to get the eligible throughput from your campaign applied to the associated 10DLC numbers, you need to submit a request to increase SMS sending rates. If you have an existing unregistered long code in your AWS End User Messaging SMS account, you can request that it be converted to a 10DLC number. To convert an existing long code, complete the registration process, and then create a case in the AWS Support Center. In some situations, it isn't possible to convert an unregistered long code to a 10DLC phone number. In this case, you must request a new number through the AWS End User Messaging SMS console and associate it with your 10DLC campaign. For more information about using 10DLC with existing long codes, see [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). **Topics** + [ ## 10DLC capabilities ](#registrations-10dlc-capabilities) + [ # 10DLC registration process ](registrations-10dlc-setup.md) + [ # 10DLC brand registration form ](registrations-10dlc-company.md) + [Resend a 10DLC brand email authentication](registrations-10dlc-auth.md) + [ # 10DLC brand vetting form ](registrations-10dlc-vetting.md) + [ # 10DLC campaign registration form ](registrations-10dlc-register-campaign.md) + [ # Associating a long code with a 10DLC campaign ](registrations-10dlc-associate.md) + [ ## 10DLC registration and monthly fees ](#registrations-10dlc-fees) + [ # 10DLC cross-account access ](registrations-10dlc-configure-cross-account-access.md) ## 10DLC capabilities **Note** **Important:** Brand registration and external brand vetting alone does not automatically increase the default of 1 MPS limit per number associated to an approved 10DLC campaign. In order to get the eligible throughput from your campaign applied to the associated 10DLC numbers, you need to submit a request to increase SMS sending rates. The capabilities of 10DLC phone numbers depend on which mobile carriers your recipients use. AT&T provides a limit on the number of message parts that can be sent each minute for each campaign. T-Mobile provides a daily limit of messages that can be sent for each company, with no limit on the number of message parts that can be sent per minute. Verizon hasn't published throughput limits, but uses a filtering system for 10DLC that is designed to remove spam, unsolicited messages, and abusive content, with less emphasis on the actual message throughput. New 10DLC campaigns that are associated with *unvetted* companies can send 75 message parts per minute to recipients who use AT&T, and 2,000 messages per day to recipients who use T-Mobile. The company limit is shared across all of your 10DLC campaigns. For example, if you have registered one company and two campaigns, the daily allotment of 2,000 messages to T-Mobile customers is shared across those campaigns. Similarly, if you register the same company in more than one AWS account, the daily allotment is shared across those accounts. If your throughput needs exceed these limits, you can request that your company registration be vetted. When you vet your company registration, a third-party verification provider analyzes your company details. The verification provider then provides a vetting score, which determines the capabilities of your 10DLC campaigns. There is a one-time charge for the vetting service. For more information, see [10DLC brand vetting form](registrations-10dlc-vetting.md). Your actual throughput rate will vary depending on various factors, such as whether or not your company has been vetted, your campaign types, and your vetting score. The following flowchart shows the throughput rates for various situations. ![\[Message throughput based on carrier and reputation.\]](http://docs.aws.amazon.com/sms-voice/latest/userguide/images/registrations-10dlc-capabilities.png) Throughput rates for 10DLC are determined by the US mobile carriers in cooperation with the Campaign Registry. Neither AWS End User Messaging SMS nor any other SMS sending service can increase 10DLC throughput beyond these rates. If you need high throughput rates and high deliverability rates across all US carriers, we recommend that you use a short code. # 10DLC registration process You can set up 10DLC directly in the AWS End User Messaging SMS console. To set up 10DLC, you must complete all of the following steps. 1. **Register your brand/company** The first step in setting up 10DLC is to register your company or brand. For information about company registration, see [10DLC brand registration form](registrations-10dlc-company.md). There is a one-time registration fee to register your company. This fee is shown on the registration page. 1. **(Optional, but recommended) Apply for vetting** If your company registration is successful, you can begin creating low-volume, mixed-use 10DLC campaigns. These campaigns can send 75 messages per minute to recipients who use AT&T, and your registered company can send 2,000 messages per day to recipients who use T-Mobile. If your use case requires a throughput rate that exceeds these values, you can apply for vetting of your company registration. Vetting your company registration can increase the throughput rates for your companies and campaigns, but it isn't guaranteed to do so. For more information about vetting, see [10DLC brand vetting form](registrations-10dlc-vetting.md). 1. **Register your campaign** If the Campaign Registry is able to verify the company information that you provided, you can create a 10DLC campaign. A 10DLC campaign contains information about your use case. Each 10DLC campaign can be associated with one company. AWS End User Messaging SMS sends this campaign information to the Campaign Registry for approval. In most cases, 10DLC campaign approval is instantaneous. In some cases, the Campaign Registry can require additional information. It can take up to 4 weeks to receive a response on if your 10DLC campaign was approved or needs to be revised. You're charged a recurring monthly fee for each 10DLC campaign that you register. The monthly fee varies depending on your use case. The recurring fee for your campaign is shown on the registration page. 1. **Request your 10DLC number** After your 10DLC campaign is approved, you can request a phone number and associate that number with the approved 10DLC campaign. Each phone number can only be associated with a single 10DLC campaign. For more information on requesting a 10DLC phone number, see [Request a phone number in AWS End User Messaging SMS](phone-numbers-request.md) and [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). There is a monthly recurring fee for leasing the phone number. This fee is shown on the purchase page. **Note** You are charged the monthly 10DLC number lease price regardless of status. For example, 10DLC numbers in a **Pending** state still generate a month fee. For more information about pricing, see [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/). # 10DLC brand 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). Before you can request a 10DLC phone number, you must register your company or brand. Brand registrations are managed by an industry organization called the Campaign Registry. You need to register your company per each AWS account and AWS Region that will use the company. **Note** Campaign Registry has implemented a two-factor authentication (2FA) for brand registrations. If your **Legal form of organization** is PUBLIC\$1PROFIT you have to provide the email address of a person who works at the brand who can complete the email authentication. Email distribution lists are not allowed and the email domain must match the domain of your business. The email authentication is sent from **noreply@auth.campaignregistry.com** and we recommend you add the email address to your spam list allow rules. After you've created your 10DLC brand registration you need to complete the form and submit it for approval. If your 10DLC brand registration is successful and you want to register for higher throughput capabilities, then you must vet your 10DLC brand registration. For more information on 10 DLC brand vetting, see [10DLC brand vetting form](registrations-10dlc-vetting.md). **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). **Complete a 10DLC brand 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 10DLC brand registration to complete. 1. In the **Brand Registration Information** section, enter the following: + For **Legal company name**, enter the name that the company is registered under. The name that you enter must be an exact match for the company name that's associated with the tax ID that you provide. **Important** Make sure to use your company's exact legal name. Incorrect or incomplete information might result in your registration being delayed or denied. + For **Country of tax registration**, enter the two letter ISO country code for the country where your company is registered. For a list of ISO country codes, see [Supported countries and regions for SMS messaging with AWS End User Messaging SMS](phone-numbers-sms-by-country.md). + For **Tax ID or Business Registration Number**, enter your company's tax ID. The ID that you enter depends on the country that your company is registered in. + If you're registering a US or non-US entity that has an IRS Employer Identification Number (EIN), enter your nine-digit EIN. The legal company name, EIN, and physical address that you enter must all match the company information that is registered with the IRS. + If you're registering a Canadian entity, enter your federal or provincial Corporation number. Don't enter the Business Number (BN) provided by the CRA. The legal company name, Corporation number, and physical address that you enter must all match the company information that is registered with Corporations Canada. + If you're registering an entity that is based in another country, enter the primary tax ID for your country. In many countries, this is the numeric portion of your VAT ID number. + For **Legal form of organization**, choose the option that best describes your company. **Note** The **US government** and **Not-for-profit** options can only be used to register United States-based organizations. If your organization is based in a country other than the US, you must register as **Private for-profit**, regardless of the actual legal form of your organization. + For **Stock symbol - optional** enter your companies stock symbol. For **Stock exchange - optional**, choose the stock exchange your company is listed on **Note** If you chose **Public for profit** in the previous step, the company's stock symbol and the stock exchange fields are required. + For **Physical business address – Address/Street**, enter the physical street address associated with your company. + For **Physical business address – City**, enter the city where the physical address is located. + For **Physical business address – State or region**, enter the state or region where the address is located. + For **Physical business address – Zip Code/Postal Code**, enter the ZIP or postal code for the address. + For **Physical business address – Country**, enter the two digit ISO country code. + For **Brand verification email**, enter the email of a person who works at the brand who can complete the email authentication. Email distribution lists are not allowed and the email domain must match the domain of your business. 1. Choose **Next**. 1. In the **Additional company and contact info** section, enter the following: + For **Doing Business As (DBA) or brand name**, enter any other names that your company does business as. + For **Vertical**, choose the category that best describes the company you're registering. + For **Company website**, enter the full URL of your company's website. Include "http://" or "https://" at the beginning of the address. + 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. 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**. **Important** If your **Legal form of organization** is PUBLIC\$1PROFIT then once you submit your brand registration the authentication email is sent to the email address specified in **Brand verification email**. Your registration can not be approved until you complete brand authentication. The authentication email is valid for 7 days and after that you have to [request a new authentication email](registrations-10dlc-auth.md#registrations-10dlc-auth.title). **Note** After your registration has been approved you need to either register for the optional **US 10DLC Brand vetting** or [10DLC campaign registration form](registrations-10dlc-register-campaign.md). For more information on registering for 10DLC, see [United States 10DLC registration](registrations-10dlc.md). # Resend a 10DLC brand email authentication in AWS End User Messaging SMS Resend a 10DLC brand email authentication The email authentication is sent from **noreply@auth.campaignregistry.com** and we recommend you add the email address to your spam list allow rules. The link in the email authentication is valid for 7 days. Follow these directions if it has been less than 30 days since you submitted for 10DLC brand registration. If it has been longer than 30 days you need to [discard the registration](registrations-discard.md#registrations-discard.title) and resubmit it. **Resend authentication email** 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 **Configurations**, choose **Registrations**. 1. Choose the 10DLC brand registration that you need to resend the 2FA email for. 1. Choose resend email in the banner. # 10DLC brand vetting form If your company's registration is successful and you want to register a 10DLC campaign with higher throughput capabilities, then you must vet your company registration. When you vet your registration, a third-party organization analyzes the company details that you provided and returns a vetting score. A high vetting score can lead to higher throughput rates for your 10DLC company and the campaigns associated with it. However, vetting isn't guaranteed to increase your throughput. Vetting scores aren't applied retroactively. In other words, if you've already created a 10DLC campaign, and you later vet your company registration, your vetting score isn't automatically applied to your existing campaign. For this reason, you should vet your company or brand *before* you create any of your 10DLC campaigns. **Note** There is a \$140 non-refundable fee for vetting your company or brand. **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). **To vet your company 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 **Create registration**. 1. For **Registration form name** enter a friendly name. 1. For **Registration type**, choose **US 10DLC brand vetting**. 1. For **Available 10DLC brands**, choose the 10DLC brand to vet. 1. Choose **Create**. # 10DLC campaign 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). AWS End User Messaging SMS’s vendors perform a manual review processes on 10DLC (10 Digit Long Code) campaigns to address SMS spam concerns raised by US carriers. Reviews are triggered when a number is associated to a 10DLC campaign. Reviews take at least 4 to 6 weeks to process. When you register a 10DLC campaign, you provide a description of your use case, as well as the message templates that you plan to use. Before you can create and register a 10DLC campaign, you must first register your company. For information on registering your company, see [10DLC brand registration form](registrations-10dlc-company.md). **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). For more information on 10DLC campaign registration issues, see [Gen-AI Feedback on Registrations (Preview)](registrations-genai-feedback.md). In this section, you provide additional details about your 10DLC campaign. **To register a 10DLC campaign** 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 10DLC campaign registration to complete. 1. On the **10DLC campaign registration information** page, do the following: 1. For **Campaign description**, enter a name for the 10DLC campaign and description of the campaigns purpose. 1. For **Vertical**, choose the option that represents your company. 1. For **Company Terms & Conditions** choose either: 1. **Enter URL** – Enter the publicly accessible URL that contains the **Terms & Conditions**. 1. **Upload file** and then **Choose file** – Choose a file that contains the **Terms & Conditions**. The file can be up to 500KB and valid file formats are PNG, JPEG, and PDF. 1. For **Privacy Policy** choose either: 1. **Enter URL** – Enter the publicly accessible URL that contains the **Privacy Policy**. 1. **Upload file ** and then **Choose file** – Choose a file that contains the **Privacy Policy**. The file can be up to 500KB and valid file formats are PNG, JPEG, and PDF. 1. For **Campaign opt-in workflow**, enter a description of how users consent to receive SMS and MMS messages. The description has to be between 40 – 2048 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. If you have multiple opt-in methods, they have to be listed as well. Your **Opt-in workflow** should include the following: + Program or product description + Identify your organization and service being represented in the initial message sent to your end users + Clear and thorough information about how your end-users opt-in to your SMS service and any associated fees or charges + Include a link to the Terms & Conditions (which must be publicly accessible). + Include a link to the Privacy Policy (which must be publicly accessible). **Note** If you don't have publicly accessible links to your Company Terms & Conditions or Privacy Policy documents then you can provide a copy of those as a document in the attachment fields for **Company Terms & Conditions** or **Privacy Policy**. + Explain if the Opt-in/Call to Action requires service log-in, is not yet published publicly, is a verbal opt-in, or if it occurs on printed sources such as fliers and paper forms. + The Call to Action/Opt-in location must include the following: + Comprehensive terms and conditions might be presented in full beneath the call-to-action, or they might be accessible from a link in proximity to the call-to-action. + Program (brand) name. + Message frequency disclosure. + Product description. + Customer care contact information. + Opt-out information. + “Message and data rates may apply” disclosure. 1. For **Campaign opt-in screenshot**, upload a file showing how users consent to receiving messages, as described in the **Campaign opt-in workflow** field. The supported file type are PNG, JPEG, and PDF and the maximum file size is 500KB. A screenshot or mockup is required unless you provide a publicly accessible URL to your opt-in location or call-to-action in the **Campaign opt-in workflow** field. If your opt-in process requires a login, is not yet public, is a verbal opt-in, or occurs on printed forms or fliers, you must provide a screenshot or mockup showing the complete opt-in process. 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. For **Opt-in keyword – optional** enter the keyword that your customers will send to consent to opt-ing in. 1. For **Opt-in confirmation message** enter the message that your customers receive if they send the Opt-in keyword to your 10DLC phone number. 1. For **Help Message**, enter the message that your customers receive if they send the keyword "HELP" to your 10DLC phone number. The message has to be a minimum of 20 characters. 1. For **Stop Message**, enter the message that your customers receive if they send the keyword "STOP" to your 10DLC phone number. The message has to be a minimum of 20 characters. **Tip** Your customers can reply to your messages with the word "HELP" to learn more about the messages that they're receiving from you. They can also reply "STOP" to opt-out of receiving messages from you. The US mobile carriers require you to provide responses to both of these keywords. The following is an example of a HELP response that complies with the requirements of the US mobile carriers: **ExampleCorp Account Alerts: For help call 1-888-555-0142 or go to example.com. Msg&data rates may apply. Text STOP to cancel.** The following is an example of a compliant STOP response: **You are unsubscribed from ExampleCorp Account Alerts. No more messages will be sent. Reply HELP for help or call 1-888-555-0142.** Your responses to these keywords must contain 160 characters or fewer. 1. Choose **Next**. 1. For the **Messaging capabilities** section, do the following: 1. The capabilities you select are applied to your 10DLC phone number when you create the phone number request. For **Number capabilities**, choose: + Choose **SMS** to enable text messages for the 10DLC campaign. + Choose **SMS and MMS** to enable text and multimedia messages for the 10DLC campaign. + Choose **SMS and Voice** to enable text and voice messages for the 10DLC campaign. **Note** When you choose to enable voice messages, it lengthens the amount of time to review your registration. + Choose **SMS and MMS and VOICE** to enable text and multimedia messages for the 10DLC campaign. 1. For **Message type – optional**, choose either **Transactional** or **Promotional** message type. + **Transactional** – Choose this option if your use case is for time-sensitive content, such as alerts and one-time passwords. + **Promotional** – Choose this option if your use case is for marketing-related content. 1. Choose **Next**. 1. For **Messaging use case** section, do the following: 1. For **Use case**, choose a use case that most closely resembles your campaign from the preset list of use cases. + **Account Notifications** – Standard notifications for account holders, relating to and being about an account. + **Charity** – Communications from a non-religious registered [501(c)(3) charity](https://en.wikipedia.org/wiki/501(c)(3)_organization) aimed at providing help and raising money for those in need. + **Customer care** – All customer interaction, including account management and customer support. + **Delivery notifications** – Information about the status of the delivery of a product or service. + **Fraud alert messaging** – Messaging regarding potential fraudulent activity on an account. + **Higher education** – Campaigns created on behalf of Colleges or Universities. It also includes School Districts and education institutions that fall outside of any "free to the consumer" messaging model. + **Low Volume** – Small throughput, any combination of use-cases. Examples include: test, demo accounts. + **Marketing** – Any communication with marketing and/or promotional content. + **Mixed** – Mixed messaging reserved for specific consumer service industry. + **Public service announcement** – An informational message that is meant to raise the audience's awareness about an important issue. + **Polling and voting** – Requests for surveys and voting for non political arenas. + **Security alert** – A notification that the security of a system, either software or hardware, has been compromised in some way and there is an action the end users need to take. + **Two factor authentication** – Any authentication, verification, or one-time passcode. 1. For **Sub use case – optional**, choose up to five sub use cases. 1. **Subscriber opt-in** – Subscribers can opt in to receive messages about this campaign. 1. **Subscriber opt-out** – Subscribers can opt out of receiving messages about this campaign. 1. **Subscriber help** – Subscribers can contact the message sender after sending the HELP keyword. 1. **Direct lending or loan arrangement ** – The campaign includes information about direct lending or other loan arrangements. 1. **Embedded link ** – Choose **Yes** if the 10DLC campaign includes an embedded link. Links from common URL shorteners, such as TinyUrl or Bit.ly, are not allowed. However, you can use URL shorteners that offer custom domains. 1. **Embedded link sample - optional** – An example of an embedded link that to be sent. Links from common URL shorteners, such as TinyUrl or Bit.ly, are not allowed. However, you can use URL shorteners that offer custom domains. 1. **Embedded phone number** – The campaign includes a phone number that isn't a customer support number. 1. **Age-gated content** – The 10DLC campaign includes age-gated content as defined by carrier and Cellular Telecommunications and Internet Association (CTIA) guidelines. 1. Choose **Next**. 1. In the **Message samples** section, do the following: 1. Enter at least one **Message sample**. This is the sample text message that you plan to send to your customers. Each sample message has to be a minimum of 20 characters. If you plan to use multiple message templates for this 10DLC campaign, include them as well. **Important** Don't use placeholder text for your sample messages. The example messages that you provide should reflect the actual messages that you plan to send as accurately as possible and should not contain any [Prohibited message content](best-practices.md#best-practices-sms-message-content). 1. Choose **Next**. 1. In the **MMS file samples** section, do the following: 1. (Optional) MMS sample files are only required if you plan to send MMS messages. In **MMS file samples** upload at least one sample image. A single MMS media file can be up to 500KB for GIF, JPEG, and PNG, and 600 KB in size for all other media file types, see [MMS file types, size and character limits](mms-limitations-character.md). **Important** Don't use placeholder text in your sample MMS images. The example MMS images that you provide should reflect the actual MMS image that you plan to send as accurately as possible and should not contain any [Prohibited message content](best-practices.md#best-practices-sms-message-content). 1. Choose **Next**. 1. On the **Review and submit** page, verify the information you're about to submit is correct. To make updates choose **Edit** next to the section. 1. Choose **Submit registration**. **Note** After your 10DLC campaign registration has been approved you can request a new 10DLC phone number or use an existing 10DLC phone number and associate it with the 10DLC campaign. For more information on registering for 10DLC, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). # Associating a long code with a 10DLC campaign After your 10DLC campaign is approved, you have provisioned a new long code or have an existing long code you can then associate that long code with the approved 10DLC campaign. The long code that you associate with the 10DLC campaign can only be used with that campaign, and you can't use it for any other 10DLC campaign. 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 10DLC campaign(US\$1TEN\$1DLC\$1CAMPAIGN\$1REGISTRATION) to associate the long code with. 1. Choose the **Associated resourced** tab and **Add resource**. 1. For **Supported association**, choose **TEN\$1DLC** from the dropdown list. 1. For **Available resources**, choose the 10DLC phone number to add. 1. Choose **Associate resource**. You can associate more than one long code with the 10DLC campaign. ## 10DLC registration and monthly fees There are registration and monthly fees associated with using 10DLC, such as registering your company and 10DLC campaign. These are separate from any other monthly or AWS fees. For more information about 10DLC fees, see the [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/) page. # 10DLC cross-account access Each 10DLC phone number is associated with a single account in a single AWS Region. If you want to use the same 10DLC phone number to send messages in more than one account or Region, you have two options: 1. You can register the same company and campaign in each of your AWS accounts. These registrations are managed and charged separately. If you register the same company in multiple AWS accounts, the number of messages that you can send to T-Mobile customers per day is shared across each of those accounts. 1. You can complete the 10DLC registration process in one AWS account, and use AWS Identity and Access Management (IAM) to grant other accounts permission to send through your 10DLC number. **Note** This option allows for true cross-account access to your 10DLC phone numbers. However, note that messages sent from your secondary accounts are treated as if they were sent from your primary account. Quotas and billing are counted against the primary account and not against any secondary accounts. ## Setting up cross-account access using IAM policies You can use IAM roles to associate other accounts with your main account. Then, you can delegate access permissions from your primary account to your secondary accounts by granting them access to the 10DLC numbers in the primary account. **To grant access to a 10DLC number in your primary account** 1. If you haven't already done so, complete the 10DLC registration process in the primary account. This process involves three steps: + Register your company. For more information, see [10DLC brand registration form](registrations-10dlc-company.md). + Register your 10DLC campaign (use case). For more information, see [10DLC campaign registration form](registrations-10dlc-register-campaign.md). + Associate a phone number with your 10DLC campaign. For more information, see [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). 1. Create an IAM role in your primary account that allows another account to call the `SendTextMessage` API operation for your 10DLC phone number. For more information on creating roles, see [Creating IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the *IAM User Guide*. 1. Delegate and test access permission from your primary account using IAM roles with any of your other accounts that need to use your 10DLC numbers. For example, you might delegate access permission from your Production account to your Development account. For more information about delegating and testing permissions, see [Delegate access across AWS account using IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html) in the *IAM User Guide*. 1. Using the new role, send a message using a 10DLC number from a secondary account. For more information about using a role, see [Using IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. # 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. # United States Short Code registration United States Short Code registration Before you can use a US Short Code for your SMS campaign, you must complete a registration process that includes brand vetting by the US Short Code Registry. Before you get started, review the [pricing page](https://aws.amazon.com/end-user-messaging/pricing/) to understand the costs associated with US Short Code registration. The following topics explain how to prepare for your submission, the vetting requirements, and how to complete the registration form. **Topics** + [Prepare for submission](registrations-us-short-code-prepare.md) + [Brand vetting](registrations-us-short-code-vetting.md) + [ # United States Short Code registration form ](registrations-short-code.md) # Prepare for your US Short Code submission Prepare for submission Before submitting your short code registration, review the following industry guidelines to ensure your SMS campaign is compliant with carrier requirements: + [CTIA Short Code Monitoring Handbook](https://api.ctia.org/wp-content/uploads/2024/01/CTIA-Short-Code-Monitoring-Handbook-v1.9-FINAL.pdf) – Comprehensive guidelines for short code program compliance and monitoring. + [CTIA Messaging Principles and Best Practices](https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf) – Industry-wide messaging standards and recommendations. + [T-Mobile Code of Conduct](https://www.t-mobile.com/support/public-files/attachments/T-Mobile%20Code%20of%20Conduct.pdf) – Carrier-specific requirements and best practices. ## 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](https://docs.aws.amazon.com/sms-voice/latest/userguide/best-practices.html) 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](https://docs.aws.amazon.com/sms-voice/latest/userguide/best-practices.html#best-practices-sms-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](https://aws.amazon.com/blogs/messaging-and-targeting/how-to-build-a-compliant-sms-opt-in-process-with-amazon-pinpoint/) blog post. # Brand vetting requirements Brand vetting The CTIA (Cellular Telecommunications Industry Association) and the US Short Code Registry require all brands to complete a vetting process when leasing new short codes and annually thereafter. This vetting process is designed to enhance consumer protection and improve transparency in SMS messaging. The vetting process validates the following information for each entity: + Company name and legal entity type + Federal Employer Identification Number (FEIN/EIN) + Corporate registration + Compliance history + Legal history Once a brand is successfully vetted for short code leases, you don't need to go through the entire vetting process again when leasing additional codes. However, annual re-vetting is required to maintain your short code lease. ## How the vetting process works AWS collects the required brand information (and content provider information, if applicable) during the short code registration process. This information is submitted to the US Short Code Registry so that their vetting agents can contact brand owners to complete the vetting process and authorize the short code procurement. The vetting process includes the following steps: 1. **Initial verification** – The vetting agent verifies that the legal name and Federal Employer Identification Number (FEIN) match, that the brand contact email is valid and relates to the company's published URL, and then triggers an authentication process. 1. **Email verification** – A verification PIN is sent to the brand's point of contact email address from `verify@usshortcodes.com`. The brand contact must click the verification link in the email and enter the PIN to complete the process. 1. **Completion** – Once verification is complete, the brand is approved and the short code can be provisioned. **Important** The verification PIN is valid for 7 days. A reminder is sent 48 hours before the PIN expires. If the PIN expires, a second and final PIN is sent. If no action is taken, you must create an AWS Support case to request the vetting email be resent. Common reasons for verification failure include: + The information submitted does not match the brand's Form SS-4 documentation provided by the IRS + The brand is a new entity that has not yet been updated in verification systems + The brand contact email uses a free email service (such as Gmail or Yahoo) instead of a company domain If you need to appeal a verification failure, you can provide a copy of your CP-575 notice (the official EIN confirmation letter issued by the IRS) for further review via an AWS Support case. ## Contact information requirements During the short code registration process, you must provide contact information that will be used for vetting communications. The following fields are collected in the registration form: + **Contact name** – Name of your company's point of contact. If you are an ISV (Independent Software Vendor), enter your end customer's information. + **Contact email address** – Email address of your company's point of contact. If you are an ISV, enter your end customer's information. This email will receive the verification PIN. + **Contact phone number** – Phone number of your company's point of contact. If you are an ISV, enter your end customer's information. + **Content provider name (ISV only)** – Optional. Name of the content provider point of contact. + **Content provider email address (ISV only)** – Optional. Email address of the content provider point of contact. + **Content provider phone number (ISV only)** – Optional. Phone number of the content provider point of contact. **Tip** Use a company email address that matches your company's website domain. Free email services (such as Gmail, Yahoo, or Outlook.com) are not permitted and will cause verification to fail. ## Tips for successful vetting Follow these tips to ensure a smooth vetting process: + **Add the verification email to your safe senders list** – The verification email comes from `verify@usshortcodes.com`. Add this address to your email safe senders list to ensure you receive the verification PIN. + **Use your company email domain** – The brand contact email must match your company's website URL. Free email services are not permitted. + **Ensure FEIN accuracy** – Your Federal Employer Identification Number (FEIN) and legal entity name must exactly match your IRS Form SS-4 or CP-575 documentation. + **Complete verification promptly** – The verification PIN expires after 7 days. Complete the verification as soon as you receive the email to avoid delays. + **Keep contact information current** – If your business contact details change, open a support case with AWS to update your information before the annual re-vetting period. If you have problems completing the verification from the link in the email, try the following: + Turn off or pause your VPN + Try a different browser + Copy and paste the URL directly into your browser ## Annual re-vetting requirements Re-vetting of brands is required annually by the US Short Code Registry. You should expect to receive a verification email from `verify@usshortcodes.com` approximately one year after your short code was provisioned to your account. The annual re-vetting process is similar to the initial PIN verification: 1. The vetting agency sends an email to the brand point of contact on file 1. The email contains a verification link and PIN 1. You must complete the email verification within 7 days **Important** Failure to complete annual re-vetting can result in suspension of your short code service. Monitor your email for verification requests and complete them promptly. If your business contact details have changed since your initial registration or last re-vetting, you must open a support case with AWS to update your contact information with the carriers before the annual re-vetting period. This ensures that the verification email is sent to the correct recipient. # United States Short Code registration form In order to create and use a short code for your SMS campaign, you need to complete the registration form and submit it for approval. **Complete a short code 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 registration number 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 **US short code registration** section, make sure you have the following documentation ready: + **SMS Terms & Conditions **, your specific terms of service. This may be either your public document or a draft version + **Call-to-action/Opt-in Mockup**, either a visual mockup or a written script showing exactly how users join your program. + **Confirm your campaign does not fall into prohibited message control and use cases**, make sure your campaign is not in any prohibited category. For more information, see [Prohibited message content](best-practices.md#best-practices-sms-message-content). Choose **Next**. 1. In the **Company info** section, enter the following: + For **Company Name**, enter the name of your company. + For **Company identification number**, enter the legal identification number of your company (such as EIN or VAT). + For **Doing Business As (DBA) name**, enter the DBA or brand name if different from the legal name of your company. + For **Company website**, enter the full URL of your company's website. + For **Legal entity type**, enter the legal form of organization. + For **Stock symbol**, enter the stock market symbol of your company. If you are a public profit company it is required to provide this information. + For **Stock exchange**, enter the stock exchange your company appears on. If you are a public profit company it is required to provide this information. + For **Company overview**, provide a short description of the products/services your company provides to its customers. + For **Are you an ISV or company managing this Short Code on behalf of another company ("End-company")?**, select **Yes** if you are managing this service on behalf of another company (for example, if you're an ISV). Click the info button for additional information. + For **Content provider company name (ISV only)** enter the legal name of content provider company. + For **Content provider company identification number (ISV only)**, enter the legal identification number of the content provider company (such as EIN or VAT). + For **Content provider company website (ISV only)** enter the full URL of the content provider company's website. + For **Content provider legal entity type (ISV only)** enter the legal form of content provider. + For **Content provider stock symbol (ISV only, if applicable)** enter the ISV stock symbol. If you are a public profit company it is required to provide this information. + For **Content provider stock exchange (ISV only, if applicable)** enter the stock exchange the ISV company appears on. If you are a public profit company it is required to provide this information. Choose **Next**. 1. In the **Company Address** section, enter the following: + For **Address 1**, enter the physical street address associated with your company. + For **Address 2**, enter the unit number of the physical address, if applicable. + For **City** enter city where the physical address is located. + For **State / Province**, enter the state, province, or region where the physical address is located. + For **Postal code**, enter the postal code / ZIP code where the physical address is located. + For **Country code**, enter the two-digit ISO country code where the physical address is located. + For **Content provider address 1 (ISV only)**, enter the physical street address associated with the content provider company. + For **Content provider address 2 (ISV only)**, enter the unit number of the physical address, if applicable. + For **Content provider city (ISV only)**, enter the city where the physical address is located. + For **Content provider state / province (ISV only)**, enter the state, province, or region where the physical address is located. + For **Content provider postal code (ISV only)**, enter the postal code / ZIP code where the physical address is located. + For **Content provider country code (ISV only)**, enter the two-digit ISO country code where the physical address is located. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact name**, enter the name of your company's point of contact. If you are an ISV, input your end customer's information. + For **Contact email address**, enter the email address of your company's point of contact. If you are an ISV, input your end customer's information. + For **Contact phone number**, enter the phone number of your company's point of contact. If you are an ISV, input your end customer's information. + For **Content provider name (ISV only)**, enter the name of the content provider point of contact. + For **Content provider email address (ISV only)**, enter the email address of the content provider point of contact. + For **Content provider phone number (ISV only)**, enter the phone number of the content provider point of contact. Choose **Next**. 1. In the **Customer Care Contact info** section, enter the following: + For **Customer care URL**, enter the full URL of your company's customer support page. + For **Customer care email address**, enter the email address of your company's customer support. + For **Customer care phone number**, enter the phone number of your company's customer support. Choose **Next**. 1. In the **Short Code info** section, enter the following: + For **Short code option**, please specify if you would like a Random or Vanity short code, or if you would like a Random code if your preferred Vanity short code is unavailable. + For **Vanity short code number preference 1**, and you are requesting a Vanity short code, please specify the short code requested. Specify up to 3 short codes in the order of preference. + For **Vanity short code number preference 2**, and you are requesting a Vanity short code, please specify the short code requested. Specify up to 3 short codes in the order of preference. + For **Vanity short code number preference 3**, and you are requesting a Vanity short code, please specify the short code requested. Specify up to 3 short codes in the order of preference. Choose **Next**. 1. In the **Messaging use case** section, enter the following: + For **Service name**, enter the service name to include your company or brand name and can include a short descriptor to define the type of messages you are sending. + For **Use case category**, select the category which most closely aligns with your use case. + For **Use case description**, enter a Description of your use case for sending SMS messages with this short code. + For **Sweepstakes or contests**, enter whether this short code is used for sending sweepstakes related communication. + For **Full URL of sweepstakes or contests rules**, enter the url for the sweepstakes or contest rules. If yes, you are required to provide a URL to the rules of the sweepstakes. + For **Sweepstakes or contests document**, enter a document detailing the sweepstakes or contest rules if a full URL of the sweepstakes or contest rules is not available. + For **Debt collection**, enter if this short code is used for debt collection. + For **HIPAA eligible use case**, enter whether the use case is HIPPA eligible. + For **Average monthly SMS frequency per user**, enter the estimated number of SMS messages that users expect to receive from this short code. + For **Monthly SMS volume**, enter the estimated number of SMS messages which will be sent from this short code each month. Choose **Next**. 1. In **Message Samples** section, do the following: + For **Message sample 1**, enter a sample. At least one sample is required of an SMS message which will be sent from this short code. + For **Message sample 2**, enter a another sample if necessary. + For **Message sample 3**, enter a another sample if necessary. + For **Message sample 4**, enter a another sample if necessary. + For **Message sample 5**, enter a another sample if necessary. + For **Message sample 6**, enter a another sample if necessary. + For **Message sample 7**, enter a another sample if necessary. + For **Message sample 8**, enter a another sample if necessary. + For **Message sample 9**, enter a another sample if necessary. + For **Message sample 10**, enter a another sample if necessary. Choose **Next**. 1. In the **MMS File samples** section, enter the following: + For **MMS**, select if you require an MMS-capable short code. + For **MMS message sample 1**, provide a sample of your MMS messaging content. This is required if you selected Yes. + For **MMS message sample 2**, provide a sample of your MMS messaging content if necessary. + For **MMS message sample 3**, provide a sample of your MMS messaging content if necessary. Choose **Next**. 1. In the **Terms & Conditions and Privacy Policy Info** section, enter the following: + For **Terms & Conditions URL**, enter the full URL of your company's Terms and Conditions page. + For **Terms & Conditions file**, provide the full text of the Terms & Conditions if it is not published. + For **Privacy Policy URL**, enter the full URL of your company's Privacy Policy page. + For **Privacy Policy File**, provide the full text of the Privacy Policy if it is not published. Choose **Next**. 1. In **Opt-in Workflow/Call-to-action** section, do the following: + For **Opt-in Method**, enter how the user will opt-in. + For **Opt-in method other**, explain the method if **Other** was selected. + For **Opt-in method user experience flow 1**, create a step-by-step description of the end user experience when signing up for the service, together with the exact verbiage that is presented. + For **Opt-in mock-up 1**, attach a mock up showing the call-to-action or opt-in. + For **Opt-in method user experience flow 2**, create a step-by-step description of the end user experience when signing up for the service, together with the exact verbiage that is presented. + For **Opt-in mock-up 2**, attach a mock up showing the call-to-action or opt-in. + For **Opt-in method user experience flow 3**, create a step-by-step description of the end user experience when signing up for the service, together with the exact verbiage that is presented. + For **Opt-in mock-up 3**, select whether a double opt-in experience is being used. + For **Double opt-in process**, create a step-by-step description of the end user experience when double opting-in for the service, together with the exact verbiage that is presented. + For **Double opt-in user experience flow**, create a step-by-step description of the end user experience when double opting-in for the service. Choose **Next**. 1. In the **Compliance Keywords and Auto-Responses** section, enter the following: + For **HELP response**, describe the end user experience when your user sends you an inbound message with the HELP keyword. + For **STOP response**, describe the end user experience when your user sends you STOP. + For **Opt-in keyword**, provide the primary keyword that, when sent to the short code, results in the sender being opted in to the messages. + For **Opt-in confirmation message**, provide the message sent to recipients confirming with them that they've opted in to your service. 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**.