# Origination identity registration in AWS End User Messaging SMS Registrations Some countries require you to register your company's identity to be able to purchase phone numbers or sender IDs and review the messages you send to recipients in their country. For more information on which countries require registration, see [Supported countries and regions for SMS messaging with AWS End User Messaging SMS](phone-numbers-sms-by-country.md). **Note** Registrations are also used for Notify Advanced tier brand verification. For more information, see [Notify tiers](notify-tiers.md). **Important** To enable Amazon Pinpoint or Amazon SNS to use an origination identity you must add a **Resource policy** to the origination identity. The resource policy must be added after the registration has been approved and the origination identity has been added to your AWS account. For example resource policies and directions on how to add one, see [Working with shared resources in AWS End User Messaging SMS](shared-resources.md). **Tip** We recommend that you complete all registrations, even if it is *optional*, as registration could be required in the future. The following registration forms can be filled out and submitted through the AWS End User Messaging SMS console. + **Australia sender ID registration** – Register a sender ID in Australia. For more information on completing the registration, see [Australia sender ID registration](registrations-australia.md). + **Belarus sender ID registration** – Register a sender ID in Belarus. For more information on completing the registration, see [Belarus sender ID registration](registrations-belarus.md). + **Egypt sender ID registration** – Register a sender ID in Egypt. For more information on completing the registration, see [Egypt sender ID registration](registrations-egypt.md). + **Finland sender ID registration** – Register a sender ID in Finland. For more information on completing the registration, see [Finland sender ID registration](registrations-finland.md). + **India sender ID registration** – Register a sender ID for use in India. For more information on completing the registration for see [India sender ID registration](registrations-sms-senderid-india.md). + **Indonesia sender ID registration** – Register a sender ID in Indonesia. For more information on completing the registration, see [Indonesia sender ID registration](registrations-indonesia.md). + **Jordan sender ID registration** – Register a sender ID in Jordan. For more information on completing the registration, see [Jordan sender ID registration](registrations-jordan.md). + **Kazakhstan sender ID registration** – Register a sender ID in Kazakhstan. For more information on completing the registration, see [Kazakhstan sender ID registration](registrations-kazakhstan.md). + **Kenya sender ID registration** – Register a sender ID in Kenya. For more information on completing the registration, see [Kenya sender ID registration](registrations-kenya.md). + **Kuwait sender ID registration** – Register a sender ID in Kuwait. For more information on completing the registration, see [Kuwait sender ID registration](registrations-kuwait.md). + **Philippines sender ID registration** – Register a sender ID in Philippines. For more information on completing the registration, see [Philippines sender ID registration](registrations-philippines.md). + **Qatar sender ID registration** – Register a sender ID in Qatar. For more information on completing the registration, see [Qatar sender ID registration](registrations-qatar.md). + **Russia sender ID registration** – Register a sender ID in Russia. For more information on completing the registration, see [Russia sender ID registration](registrations-russia.md). + **Saudi Arabia sender ID registration** – Register a sender ID in Saudi Arabia. For more information on completing the registration, see [Saudi Arabia sender ID registration](registrations-saudi-arabia.md). + **Singapore sender ID registration** – Register a sender ID in Singapore. For more information on completing the registration, see [Singapore sender ID registration form](registrations-sg-form.md). + **Sri Lanka sender ID registration** – Register a sender ID in Sri Lanka. For more information on completing the registration, see [Sri Lanka sender ID registration](registrations-sri-lanka.md). + **Thailand sender ID registration** – Register a sender ID in Thailand. For more information on completing the registration, see [Thailand sender ID registration](registrations-thailand.md). + **Turkey sender ID registration** – Register a sender ID in Turkey. For more information on completing the registration, see [Turkey sender ID registration](registrations-turkey.md). + **United Arab Emirates sender ID registration** – Register a sender ID in United Arab Emirates. For more information on completing the registration, see [United Arab Emirates sender ID registration](registrations-united-arab-emirates.md). + **United Kingdom sender ID registration** – Register a sender ID in the United Kingdom. For more information on completing the registration, see [United Kingdom sender ID registration](registrations-uk.md). + **US Toll free numbers** – (Only the United States and the US territories of Puerto Rico, US Virgin Islands, Guam, and American Samoa) A toll-free number (TFN) that begins with 888, 877, 866, 855, 844, or 833. Throughput for toll-free numbers is limited to 3 message parts per second. Toll-free numbers support both SMS, MMS, and voice messages. They can't be used to send messages to recipients outside of the United States or the US territories of Puerto Rico, US Virgin Islands, Guam, and American Samoa. For more information on completing the registration, see [US toll-free number registration form](registrations-tfn-register.md). + **US Short Code** – (Only the United States and the US territories of Puerto Rico, US Virgin Islands, Guam, and American Samoa). A Common Short Code (Short Code) is a five- or six-digit number to and from which text messages can be sent from and to Consumers of all participating U.S. Wireless Providers. Short Code Programs offer a convenient, efficient, and innovative means to communicate with Consumers. They can't be used to send messages to recipients outside of the United States or the US territories of Puerto Rico, US Virgin Islands, Guam, and American Samoa. For more information on requirements and completing the registration, see [United States Short Code registration](registrations-us-short-code.md). + **US 10DLC Brand registration** – Register your company or brand to be able to use 10DLC phone numbers and campaigns. For more information on completing the registration, see [10DLC brand registration form](registrations-10dlc-company.md). + **US 10DLC Brand vetting** – Before you can request a 10DLC phone number or 10DLC campaign, you must register your company or brand. You only need to register your company once. Company registrations are managed by an industry organization called the Campaign Registry. For more information on completing the registration, see [10DLC brand vetting form](registrations-10dlc-vetting.md) + **US 10DLC Campaign registration** – A 10DLC campaign is required to be registered before it can be used. For more information on completing the registration, see [10DLC campaign registration form](registrations-10dlc-register-campaign.md). + **Vietnam sender ID registration** – Register a sender ID in Vietnam. For more information on completing the registration, see [Vietnam sender ID registration](registrations-vietnam.md). + **Zambia sender ID registration** – Register a sender ID in Zambia. For more information on completing the registration, see [Zambia sender ID registration](registrations-zambia.md). The following registrations require you to open a support case in the Support Center Console. + **China SMS template registration** – Register an SMS template for use in China. For more information on completing the registration for see [China SMS template registration form](phone-numbers-sms-template-registration.md). **Topics** + [Estimated registration times](registration-eta.md) + [ # Manage registrations ](registrations-manage.md) + [Gen-AI Feedback on Registrations](registrations-genai-feedback.md) + [ # Registration forms ](registrations-country.md) + [ # Dedicated number registration forms ](registrations-dedicated-number.md) # Estimated registration times Estimated registration times Registration processing times vary depending on the type of registration and the country or region where you're registering. This topic provides estimated timeframes to help you plan your messaging campaigns. ## Factors affecting registration times Several factors can influence how long it takes to process your registration: + Registration type (10DLC, toll-free, short code, sender ID) + Country or region requirements + Completeness and accuracy of submitted information + Third-party carrier review processes + Peak submission periods ## Estimated registration times by country and type The following table shows estimated registration processing times for different countries and origination identity types: | Country | ISO code | Origination identity type | Registration link | Estimated registration time | | --- | --- | --- | --- | --- | | United Arab Emirates | AE | Sender ID | [United Arab Emirates sender ID registration](registrations-united-arab-emirates.md) | 25 days | | Austria | AT | Long Code | [Austria](dedicated-number-austria.md) | 15 days | | Australia | AU | Sender ID | [Australia sender ID registration](registrations-australia.md) | 15 days | | Australia | AU | Long Code | [Australia](dedicated-number-australia.md) | 15 days | | Belarus | BY | Sender ID | [Belarus sender ID registration](registrations-belarus.md) | 45 days | | Chile | CL | Long Code | [Chile](dedicated-number-chile.md) | 21 days | | Chile | CL | Short Code | [Chile](dedicated-number-chile.md) | 30 days | | China | CN | Template | [China SMS template registration form](phone-numbers-sms-template-registration.md) | 15 days | | Germany | DE | Short Code | [Germany](dedicated-number-germany.md) | 12 weeks | | Denmark | DK | Long Code | [Denmark](dedicated-number-denmark.md) | 15 days | | Egypt | EG | Sender ID | [Egypt sender ID registration](registrations-egypt.md) | 21 days | | Spain | ES | Long Code | [Spain](dedicated-number-spain.md) | 15 days | | Spain | ES | Short Code | [Spain](dedicated-number-spain.md) | 12 weeks | | Finland | FI | Long Code | [Finland](dedicated-number-finland.md) | 15 days | | Finland | FI | Short Code | [Finland](dedicated-number-finland.md) | 35 days | | Finland | FI | Sender ID | [Finland sender ID registration](registrations-finland.md) | 25 days | | United Kingdom | GB | Long Code | [United Kingdom](dedicated-number-united-kingdom.md) | 10 days | | United Kingdom | GB | Short Code | [United Kingdom](registrations-uk.md) | 12 weeks | | United Kingdom | GB | Sender ID | [United Kingdom sender ID registration](registrations-uk.md) | 3 days | | Hong Kong | HK | Long Code | [Hong Kong](dedicated-number-hong-kong.md) | 21 days | | Hungary | HU | Long Code | [Hungary](dedicated-number-hungary.md) | 7 days | | Indonesia | ID | Sender ID | [Indonesia sender ID registration](registrations-indonesia.md) | 50 days | | India | IN | Short Code | [India](dedicated-number-india.md) | 25 days | | India | IN | Sender ID | [India sender ID registration](registrations-sms-senderid-india.md) | 1 day | | Italy | IT | Long Code | [Italy](dedicated-number-italy.md) | 10 days | | Jordan | JD | Sender ID | [Jordan sender ID registration](registrations-jordan.md) | 15 days | | Kenya | KE | Sender ID | [Kenya sender ID registration](registrations-kenya.md) | 30 days | | Kuwait | KW | Sender ID | [Kuwait sender ID registration](registrations-kuwait.md) | 45 days | | Kazakhstan | KZ | Sender ID | [Kazakhstan sender ID registration](registrations-kazakhstan.md) | 25 days | | Sri Lanka | LK | Sender ID | [Sri Lanka sender ID registration](registrations-sri-lanka.md) | 40 days | | Netherlands | NL | Long Code | [Netherlands](dedicated-number-netherlands.md) | 7 days | | Netherlands | NL | Short Code | [Netherlands](dedicated-number-netherlands.md) | 10 weeks | | Norway | NO | Long Code | [Norway](dedicated-number-norway.md) | 10 days | | Philippines | PH | Sender ID | [Philippines sender ID registration](registrations-philippines.md) | 50 days | | Poland | PL | Long Code | [Poland](dedicated-number-poland.md) | 10 days | | Portugal | PT | Long Code | [Portugal](dedicated-number-portugal.md) | 7 days | | Portugal | PT | Short Code | [Portugal](dedicated-number-portugal.md) | 45 days | | Qatar | QA | Sender ID | [Qatar sender ID registration](registrations-qatar.md) | 35 days | | Russia | RU | Sender ID | [Russia sender ID registration](registrations-russia.md) | 35 days | | Saudi Arabia | SA | Sender ID | [Saudi Arabia sender ID registration](registrations-saudi-arabia.md) | 45 days | | Sweden | SE | Long Code | [Sweden](dedicated-number-sweden.md) | 10 days | | Singapore | SG | Sender ID | [Singapore sender ID registration form](registrations-sg-form.md) | 21 days | | Thailand | TH | Sender ID | [Thailand sender ID registration](registrations-thailand.md) | 30 days | | Turkey | TR | Sender ID | [Turkey sender ID registration](registrations-turkey.md) | 21 days | | United States | US | 10DLC | [United States 10DLC registration](registrations-10dlc.md) | See [United States 10DLC registration](registrations-10dlc.md) | | United States | US | Short Code | [United States Short Code requirements](registrations-us-short-code.md) | 12 weeks | | United States | US | Toll-Free | [United States Toll-free number registration](registrations-tfn.md) | 15 days | | Vietnam | VN | Sender ID | [Vietnam sender ID registration](registrations-vietnam.md) | 30 days | | Zambia | ZM | Sender ID | [Zambia sender ID registration](registrations-zambia.md) | 21 days | # Manage registrations The following sections contain directions on how to manage a registration. **Topics** + [Create a new registration using the console](registrations-create.md) + [Create a registration using the AWS CLI](registrations-sms-cli.md) + [Check a registration's status](registrations-status.md) + [Change a registration's name](registrations-friendly-name.md) + [Edit a registration](registrations-edit.md) + [Discard a registration's current version](registrations-discard.md) + [Delete a registration](registrations-delete.md) + [View a registration associated resources](registrations-associated-resource.md) # Create a new registration using the AWS End User Messaging SMS console Create a new registration using the console You can use the AWS End User Messaging SMS console to manage registrations for your AWS End User Messaging SMS account. If your registration was already created as part of requesting a phone number or sender ID then you do not need to create a new registration. You can view the resources associated with a registration in the **Associated resources** tab, for more information see [View a registration associated resources in AWS End User Messaging SMS](registrations-associated-resource.md). **Important** Some registrations have multiple steps that need to be completed in exact order. To register a US 10DLC number, you must first register and complete a **US 10DLC Brand registration**, then apply for optional **US 10DLC Brand vetting** to increase your Messages per second (MPS), and then register a **US 10DLC Campaign registration**. If you require sending 10DLC SMS messages from more than one AWS Region and from a single account, you must re-registering all 10DLC resources for each AWS Region required. For more information about the process, see [United States 10DLC registration](registrations-10dlc.md). To register a **Singapore sender ID registration** you must first obtain a Singapore Unique Entity Number (UEN), create and submit a Singapore sender ID registration, once the registration is approved then register the sender ID with Singapore Network Information Centre (SGNIC). For more information about the process, see [Singapore sender ID registration process](registrations-sg.md). To register a **India sender ID registration** you must first register your company and use case with TRAI, create and submit a case with Support and then to send messages you must specify **Entity ID** and **Template ID** values that you received. For more information about the process, see [India sender ID registration process in AWS End User Messaging SMS](registrations-sms-senderid-india.md). **Create a new 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. 1. For **Registration form name** enter a friendly name. 1. For **Registration type**, choose the registration form from the dropdown list. Each **Registration type** has different forms depending on the regulatory body the registration form is sent to. 1. (optional) Expand **Tags** to: + **Add a tag** – In **Manage tags** choose **Add new tag** to create a new blank key/value pair. + **Delete a tag** – In **Manage tags**, choose **Remove** next to the key/value pair. + **Edit a tag** – In **Manage tags** choose the **Key** or **Value** and edit the text. 1. Choose **Create**. 1. Your registration has now been created and you need to enter in all required information then submit. + **US toll-free number registration** – [US toll-free number registration form](registrations-tfn-register.md). + **US 10DLC Brand vetting** – The 10DLC brand has been submitting for vetting and you don't need to fill out any additional forms, see [10DLC brand vetting form](registrations-10dlc-vetting.md). + **US 10DLC Brand registration** – [10DLC brand registration form](registrations-10dlc-company.md). + **US-10DLC campaign registration** – [10DLC campaign registration form](registrations-10dlc-register-campaign.md). + **Singapore sender ID registration** – [Singapore sender ID registration form](registrations-sg-form.md). # Create a registration using the AWS CLI in AWS End User Messaging SMS Create a registration using the AWS CLI The following section gives examples of how to create, populate, and submit a registration using the AWS CLI. For examples of how to create and submit a Toll-free phone number registration using python or shell script, see [Automate AWS End User Messaging US toll-free Number Registrations](https://aws.amazon.com/blogs/messaging-and-targeting/automate-us-tfn-registrations/). Registrations vary from country to country, some are single page forms while others, like 10DLC, may require multiple forms to be submitted in a specific order. Check the [individual registration](registrations.md) for details on order and if you need to upload any supporting documentation like a Letter of Authorization (LOA). ## Background Some countries require you to register your company's identity to be able to purchase an origination identity and review the messages you send to recipients in their country. + The registration information you provide may be reviewed by a third-party. The third-party varies from country to country but could be a governmental regulatory agency or mobile carrier that perform the review. + The amount of time the third-party company takes to review your registration varies by registration type. ## Prerequisites Before you begin you must: + Install and configure the AWS CLI, see [Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) in the [AWS Command Line Interface User Guide](https://docs.aws.amazon.com/cli/latest/userguide/). + An AWS account with [permissions](security-iam.md) to use AWS End User Messaging SMS in the target region. + A registrations **AssociationBehavior** specifies the order for when a registration can be associated with an origination identity and disassociated from an origination identity, see [SupportedAssociation](https://docs.aws.amazon.com/pinpoint/latest/apireference_smsvoicev2/API_SupportedAssociation.html). + `ASSOCIATE_BEFORE_SUBMIT` The origination identity has to be supplied when submitting a registration. + `ASSOCIATE_ON_APPROVAL` This applies to all sender ID registrations. The sender ID will be automatically provisioned once the registration is approved. + `ASSOCIATE_AFTER_COMPLETE` This applies to phone number registrations when you must complete a registration first, then associate one or more phone numbers later. **Important** Once you purchase an origination identity you are changed for it regardless of the registrations status, see [AWS End User Messaging Pricing](https://aws.amazon.com/end-user-messaging/pricing/). Once you submit your registration you can not make any changes to the registration or disassociate any resources with the registration until after it has been reviewed by a third party and returned back to you. The following are additional resources for registrations. + [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/) + [10DLC Registration Best Practices to Send SMS with AWS End User Messaging](https://aws.amazon.com/blogs/messaging-and-targeting/10dlc-registration-best-practices-to-send-sms-with-amazon-pinpoint/) # Create a registration (create-registration AWS CLI command) Use the [create-registration](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/create-registration.html) command to create a new blank registration. The **RegistrationType** parameter determines the type of registration to create. If you don't know the value for the type of registration you want to create then use the [describe-registration-type-definitions](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/describe-registration-type-definitions.html) command to retrieve a list of all registration types. The following examples show how to create a Toll-free number registration form. ``` $ aws pinpoint-sms-voice-v2 create-registration --registration-type US_TOLL_FREE_REGISTRATION --tags "Key=Name,Value=MyTFNRegistration" ``` On successful completion save the value of **RegistrationId** as it will be needed for other commands. **Note** To add a friendly name to your registration you must add a tag with the **Key** set to **Name** and the **Value** set to the friendly name to use. You can also add tags to resources for billing purposes, see [Tag resources for billing](sms-billing-tag.md). The following example is partial output of the `describe-registration-type-definitions` command. Because **AssociationBehavior** is set to `ASSOCIATE_BEFORE_SUBMIT` the toll-free number must be purchased and associated with the registration before the registration can be submitted for approval. For more information on **AssociationBehavior** and **DisassociationBehavior**, see [SupportedAssociation](https://docs.aws.amazon.com/pinpoint/latest/apireference_smsvoicev2/API_SupportedAssociation.html). ``` { "RegistrationTypeDefinitions": [ { "RegistrationType": "US_TOLL_FREE_REGISTRATION", "SupportedAssociations": [ { "ResourceType": "TOLL_FREE", "IsoCountryCode": "US", "AssociationBehavior": "ASSOCIATE_BEFORE_SUBMIT", "DisassociationBehavior": "DISASSOCIATE_ALL_CLOSES_REGISTRATION" } ], "DisplayHints": { "Title": "US toll-free number registration" } }, ... ``` # Get the field definitions (describe-registration-field-definitions AWS CLI command) Next you need to get the definitions for each field to know what the requirements are, such as the maximum number of characters for the field. Each registration is divided into sections and each section has one or more fields. Use the [describe-registration-field-definitions](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/describe-registration-field-definitions.html) command to retrieve all section and field definitions for a registration. You will need the **FieldPath** for each field later to be able to set its value. Also **FieldRequirement** is used to determine if a field will be required or optional. The following examples show how to retrieve field definitions for the Toll-free registration form. ``` $ aws pinpoint-sms-voice-v2 describe-registration-field-definitions --registration-type US_TOLL_FREE_REGISTRATION ``` The following is partial output from the command: ``` { "RegistrationFieldDefinitions": [ { "SectionPath": "companyInfo", "FieldPath": "companyInfo.companyName", "FieldType": "TEXT", "FieldRequirement": "REQUIRED", "TextValidation": { "MinLength": 1, "MaxLength": 100, "Pattern": "^(?=\\s*\\S)[\\s\\S]+$" }, "DisplayHints": { "Title": "Company name", "ShortDescription": "Legal name which your company is registered under.", "ExampleTextValue": "Example Corp" } }, ... ``` # Create attachments (create-registration-attachment AWS CLI command) Depending on the registration you may be required to complete and attach a Letter of Authorization (LOA), opt-in workflow, or another type of required document. Check the [individual registration](registrations.md) for details and to download any forms. Use the [create-registration-attachment](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/create-registration-attachment.html) command to create the registration attachment. You can either upload the file to an Amazon S3 bucket and use the url or attach the document as part of the command. Use either **AttachmentUrl** or **AttachmentBody**, if both are specified then an exception is returned. The maximum file size is 500KB and valid file extensions are PDF, JPEG, and PNG. The following example shows how to create the registration attachment and use the **AttachmentUrl** parameter. ``` $ aws pinpoint-sms-voice-v2 create-registration-attachment --attachment-url s3://BucketName/FileName ``` On successful completion the command returns a **RegistrationAttachmentID** which is needed for other commands. For more information on Amazon S3 commands such as creating a bucket or uploading a file, see [Use high-level (s3) commands with the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-services-s3-commands.html). # Set the field definition values (put-registration-field-value AWS CLI command) Next you need to add values for all of the required fields returned from the *Get the field definitions* step, this includes any attachments that you created. We recommend that you also complete any optional fields where applicable to your use case. A field is required or optional depending on the **FieldRequirement** value. Use the [put-registration-field-value](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/put-registration-field-value.html) command to set the field values. + The following examples show to add a value for the company name or text value. ``` $ aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id RegID --field-path companyInfo.companyName --text-value AnyCompany ``` In the preceding command replace the following: + Replace *RegID* with the registration id returned from the *Create a registration* step. + Replace *AnyCompany* with you company's name. + The following examples show to add a value for a select field. ``` $ aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id RegID --field-path messagingUseCase.monthlyMessageVolume --text-choices SelectValue ``` In the preceding command replace the following: + Replace *RegID* with the registration id returned from the *Create a registration* step. + Replace *SelectValue* with one of the option values for the field. Use the [describe-registration-field-definitions](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/describe-registration-field-definitions.html) command to get the options for just one field: ``` aws pinpoint-sms-voice-v2 describe-registration-field-definitions --registration-type US_TOLL_FREE_REGISTRATION --field-paths messagingUseCase.monthlyMessageVolume ``` ``` { "RegistrationFieldDefinitions": [ { "SectionPath": "messagingUseCase", "FieldPath": "messagingUseCase.monthlyMessageVolume", "FieldType": "SELECT", "FieldRequirement": "REQUIRED", "SelectValidation": { "MinChoices": 1, "MaxChoices": 1, "Options": [ "10", "100", "1,000", "10,000", "100,000", "250,000", "500,000", "750,000", "1,000,000", "5,000,000", "10,000,000+" ] }, "DisplayHints": { "Title": "Monthly SMS volume", "ShortDescription": "Estimated number of SMS messages which will be sent from this toll-free number each month." } } ], "RegistrationType": "US_TOLL_FREE_REGISTRATION" } ``` + The following examples show how to add an attachment. ``` $ aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id RegID --field-path messagingUseCase.optInImage --registration-attachment-id RegistrationAttachmentID ``` In the preceding command replace the following: + Replace *RegID* with the registration id returned from the *Create a registration* step. + Replace *RegistrationAttachmentID* with the registration attachment id returned from the *Create attachments* step. # Request an origination identity (request-phone-number AWS CLI command) **Note** Once you purchase an origination identity you are charged for it regardless of registration status, see [AWS End User Messaging Pricing](https://aws.amazon.com/end-user-messaging/pricing/). If the registration's **AssociationBehavior** is `ASSOCIATE_AFTER_COMPLETE` then you do not need to purchase or associate the origination identity until after the registration has been submitted and approved. Now you need to request an origination identity which will later be associated with the registration. This example shows how to use the [request-phone-number](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/request-phone-number.html) command to request a toll-free phone number through the AWS CLI. Use the [request-sender-id](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/request-sender-id.html) to request a sender ID. ``` $ aws pinpoint-sms-voice-v2 request-phone-number --iso-country-code US --message-type TRANSACTIONAL --number-capabilities SMS --number-type TOLL_FREE ``` On successful completion the command returns the phone number unique identifier which is needed to associate the phone number with the registration. # Associate a resource with a registration (create-registration-association AWS CLI command) **Note** If the registration's **AssociationBehavior** is `ASSOCIATE_AFTER_COMPLETE` then you do not need to purchase or associate the origination identity until after the registration has been submitted and approved. To associate an origination identity to the registration use the [create-registration-association](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/create-registration-association.html) AWS CLI command. ``` $ aws pinpoint-sms-voice-v2 create-registration-association --registration-id RegID --resource-id PhoneNumberID ``` In the preceding command replace the following: + Replace *RegID* with the registration id returned from the *Create a registration* step. + Replace *PhoneNumberID* with the phone number id returned from the *Request an origination identity* step. **Note** This command is used to associate any applicable resource with the registration. For example, it can be used to associate a 10DLC campaign registration with a 10DLC brand registration. # Submit your registration (submit-registration-version AWS CLI command) Once you submit your registration you will not be able to make any changes to it. Review you registration to make sure that all of your data is correct before submitting it. **Important** Once you submit your registration you can not make any changes to the registration or disassociated any resources from the registration until after it has been reviewed by a third party and returned back to you. To submit a registration with the AWS CLI use the [submit-registration-version](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/create-registration-association.html) command. ``` $ aws pinpoint-sms-voice-v2 submit-registration-version --registration-id RegID ``` In the preceding command replace the following: + Replace *RegID* with the registration id returned from the *Create a registration* step. ## Check your registrations status (describe-registrations AWS CLI command) Once your registration has been submitted you can check its status using the [describe-registrations](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/describe-registrations.html) command or [console](registrations-status.md). If the registration's **AssociationBehavior** is `ASSOCIATE_AFTER_COMPLETE` you can purchase an origination identity and associate it with the registration, once the registration's status is set to **COMPLETE**. If your registration's status is changed to **REQUIRES\$1UPDATES** then you can find and [edit the flagged fields](registrations-edit.md) and resubmit the registration. For a list of registration rejection reasons, see [Gen-AI Feedback on Registrations](registrations-genai-feedback.md). If you require help from Support with your registration rejection you can [open a ticket](registrations-request-support.md). # Check a registration's status in AWS End User Messaging SMS Check a registration's status Your registration will be in one of these different statuses: + **AUTHENTICATION\$1REQUIRED** – You need to complete two-factor authentication for your registration. + **CLOSED** – You deleted the resources and must also delete the registration for the number. + **COMPLETE** – Your registration has been approved and you can start using the resource. + **CREATED** – Your registration is created but not submitted. + **DELETED** – Your registration has been deleted. + **REVIEWING** – Your registration has been accepted and is being reviewed. You can't make any changes to your registration or any resources associated to the registration while it is in this state. + **REQUIRES\$1UPDATES** – You must fix your registration and resubmit it. See [Edit a registration in AWS End User Messaging SMS](registrations-edit.md) for more information. Fields that require updates display a warning icon and a brief description of the issue. + **SUBMITTED** – Your registration has been submitted and is awaiting review. **Check your registration status** 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. On the **Registrations** table, you can then view the registration **Status** of each registration. # Change a registration's name in AWS End User Messaging SMS Change a registration's name To help manage your registrations you should give them a descriptive name. You can add or edit the name of your registration at any time without having to resubmit it. You need to add a tag with the **Key** set to **Name** and the **Value** set to the name to use. 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. On the **Registrations** page, choose the registration to add a tag to. 1. On the **Tags** tab, choose **Manage tags**. In **Manage tags** choose **Add new tag**. 1. For **Key** enter **Name** and for **Value** enter a friendly name for the registration. 1. Choose **Save changes**. # Edit a registration in AWS End User Messaging SMS Edit a registration After you submit your registration, the **registration status** will display as **Requires Updates** if there is an issue with the registration. In this state, the registration form is editable. Fields that require updates have a warning icon and a brief description of the issue. **To edit a 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 **Configurations**, choose **Registrations**. 1. On the **Registrations** table, select the **Registration ID** that you want to edit. 1. Choose **Update registration** to edit the form and correct fields that have a warning icon. **Note** If your registration was rejected and requires updates the banner lists the reason the registration was rejected and which fields need to be updated. For more information about registration rejections, see [Toll-free number registration rejection reasons](registrations-tfn-rejection-reason.md) and [Gen-AI Feedback on Registrations (Preview)](registrations-genai-feedback.md). 1. Choose **Submit registration** to resubmit when you're done. **Important** Recheck all fields to confirm that they're correct. # Discard a registration's current version in AWS End User Messaging SMS Discard a registration's current version You can discard the current version of your registration and make any needed updates. If you find an error in the registration that you have submitted you can use this feature to correct the error and resubmit instead of waiting to have your registration denied and then correct the error. You can only discard the registration if its status is `Submitted`. This will permanently delete the current version of the registration. **To discard a 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 **Configurations**, choose **Registrations**. 1. On the **Registrations** table, select the **Registration ID** that you want. 1. Choose **Discard version** and in the window enter **discard**. 1. Choose **Discard version**. # Delete a registration in AWS End User Messaging SMS Delete a registration You can delete your registration if it is no longer needed. This will permanently delete the registration. **To delete a 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 **Configurations**, choose **Registrations**. 1. On the **Registrations** table, select the **Registration ID** that you want. 1. Choose **Delete registration** and in the window enter **delete**. 1. Choose **Delete registration**. ## Delete a 10DLC campaign registration Delete a 10DLC campaign registration You have to delete all phone numbers associated with a 10DLC campaign registration before you can delete the 10DLC campaign registration. **Important** When you remove a phone number from a 10DLC campaign, you no longer have access to that phone number. Additionally, deleted 10DLC campaigns can't be restored. **To delete a 10DLC campaign 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 **Configurations**, choose **Registrations**. 1. On the **Registrations** table, select the **Registration ID** of the 10DLC campaign. 1. Choose **Associated resources** tab. 1. For more information on releasing phone numbers, see [Release a phone number](phone-numbers-delete.md). To release a phone number: 1. Choose the phone number and then on the phone number detail's page choose **Release phone number**. 1. On the **Release phone number** window enter **release** and choose **Release phone number**. 1. Once all phone numbers have been released, choose **Delete registration** and in the window enter **delete**. ## Delete a 10DLC brand registration Delete a 10DLC brand registration To delete a 10DLC brand registration you must delete any 10DLC campaigns associated with the 10DLC brand registration. To delete a 10DLC campaign registration you must release all phone numbers associated to the 10DLC campaign registration. **To delete 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 **Configurations**, choose **Registrations**. 1. On the **Registrations** table, select the **Registration ID** of the 10DLC brand. 1. Choose **Associated resources** tab. 1. For each 10DLC campaign registration follow these directions to [release all phone numbers and delete a 10DLC campaign registration](#registrations-delete-10DLC-campaign). 1. Once all 10DLC campaign registrations are deleted, choose **Delete registration** and in the window enter **delete**. # View a registration associated resources in AWS End User Messaging SMS View a registration associated resources Registrations can have one to many resources associated with them depending on the registration type. You can view any resources associated with a registration on the **Associated resources tab of the registration**. **Associate registration resources** 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 a registration from the table. 1. Choose the **Associated resources** tab. Choose a resource to view more information about the resources. # Gen-AI Feedback on Registrations (Preview) Gen-AI Feedback on Registrations **Note** The registration reviewer is designed to provide early feedback on the quality of your registration submissions with generative AI. It may from time-to-time produce inaccurate feedback. You are still responsible to ensure your registrations meet the compliance bar for the phone number or sender ID you're registering. If you disagree with the feedback, you can submit the registration for downstream review without implementing the feedback. The registration reviewer is a Gen-AI feature available in public preview under AWS End User Messaging SMS. The registration reviewer provides you Gen-AI feedback on your phone number or sender ID registration before submitting for carrier review. The reviewer will check your registration for common denial reasons or format requirements and provide feedback saving time-to-approval. Once you submit your registration for feedback, it will move to carrier review if no additional updates are required or will move to "requires Updates" with feedback on the registration form. The registration reviewer provides two levels of feedback including a summary on the form itself, and field level feedback including a denial reason and descriptive feedback with possible suggestions. ## Improving the registration reviewer AWS End User Messaging may use certain information from your registrations and feedback to improve the registration reviewer feature. End User Messaging may use this information, for example, to provide better feedback on your registrations, such as providing better feedback on how to format your message samples or use-case descriptions. If you would like to opt-out from End User Messaging using registration information and registration feedback to improve the registration reviewer feature, you can submit your registration without using the registration reviewer feature. ## Data handling for registration reviewer The registration reviewer feature may require that your registration information and feedback be processed in a different AWS region than the AWS region you selected for End User Messaging. For example, when addressing a request for registration feedback, the feature uses Amazon Bedrock models to process your registration information and registration feedback. The models may process such requests from a region other than the AWS region you selected for End User Messaging. Your registration information and feedback are encrypted while transmitted across Amazon's secure network for the purpose of this cross-region processing. This cross-region processing does not change where your registration information and registration feedback is stored, and those items will still be stored in the AWS region you selected for End User Messaging. **Important** The registration reviewer feature is a public preview feature governed by your agreement with AWS governing your use of AWS services and by sections 1 and 2 of the AWS Service Terms. While the feature is currently offered at no charge, feature pricing is subject to change. Standard pricing for AWS End User Messaging SMS still applies when you send SMS with End User Messaging. ## Using Gen-AI feedback ------ #### [ Using Gen-AI feedback (Console) ] To receive feedback on your registration using the AWS End User Messaging SMS console, follow these steps: 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 type**, choose the registration form from the dropdown list. Each **Registration type** has different forms depending on the regulatory body the registration form is sent to. 1. (optional) Expand **Tags** to: + **Add a tag** – In **Manage tags** choose **Add new tag** to create a new blank key/value pair. + **Delete a tag** – In **Manage tags**, choose **Remove** next to the key/value pair. + **Edit a tag** – In **Manage tags** choose the **Key** or **Value** and edit the text. 1. Choose **Create**. 1. Once you've created the registration, fill out the appropriate fields. For more information related to the specific registration form, check here. 1. On the review and submit page, select receive AI feedback. 1. If your registration passes and does not require any feedback, we will automatically submit it for carrier review. 1. If your registration requires feedback, you will receive the feedback summary on the AI feedback page. You can respond to the feedback and make updates on the flagged form field sections by selecting **Update**. 1. Once you've completed the updates, you can **Submit** or resubmit for AI review. ------ #### [ Using Gen-AI feedback (AWS CLI) ] To receive feedback on your registration using the AWS CLI, use the following command: ``` $ aws pinpoint-sms-voice-v2 --region us-east-1 submit-registration-version \ --registration-id \ --aws-review ``` In the preceding example, do the following: + Replace ** with your actual registration ID. + The `--aws-review` flag enables AI feedback review before carrier submission. + Specify the appropriate region using `--region`. ------ **Topics** + [ ## Improving the registration reviewer ](#w2aac34c27b7) + [ ## Data handling for registration reviewer ](#w2aac34c27b9) + [ ## Using Gen-AI feedback ](#w2aac34c27c13) + [Understanding rejection reasons](understanding-rejection-reasons.md) + [Get more information on registration issues](registrations-request-support.md) # Understanding rejection reasons Understanding rejection reasons If your registration was rejected, use the following tables to determine why it was rejected and what you can do to fix your 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). If your brand registration was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Brand rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Brand physical address is missing or invalid. | The brand's physical address can't be verified. Check the physical address is correct and resubmit the form. | | Brand support email address is missing or invalid. | The brand's email address is missing or invalid. Update the email address and resubmit the form. | | Brand support email is a public email domain. | The brand's email domain is from a public email provider, like Gmail. The email domain must be associated with the brand's business. | | Repeated use of same Employer Identification Number (EIN) for multiple different brands. | Same EIN is used for multiple brands. Only register minimum number of brands per EIN and do not resubmit until brand registration is updated | | Brand associated with or website references lead generation or affiliate marketing which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Lead generation or affiliate marketing. | | Brand associated with or website references gambling which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Gambling. | | Brand associated with or website references high risk financial services which are prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: High risk financial services. | | Brand associated with or website references illegal substances which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Illegal substances. | | Brand associated with or website references third party job boards which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Third party job boards. | | Brand associated with or website references SHAFT content which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). | | Brand associated with or website references sweepstakes which is prohibited by mobile operators. | Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Sweepstakes. | | Brand support phone number is missing or invalid. | The brand's support phone number is missing or invalid. Update the phone number and resubmit the form. | If your campaign or use case was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Campaign rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Campaign appears to be associated with a known Spam or Phishing brand and is not allowed. | The provided phone number, business, traffic, or marketing for the campaign has been flagged as Spam or Phishing; or the Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates. | | Brand website is missing, inaccessible, or online presence could not be validated. | The provided URL is incorrect. If the website is not live yet then indicate that in the campaign description. Check the URL is correct and resubmit. | | Brand references charity content that does not match the campaign use case. | Brand associated with or website references content that is not indicated in the registered use case of the campaign. Mismatched use case: Charity. | | Brand references political content that does not match the campaign use case. | Brand associated with or website references content that is not indicated in the registered use case of the campaign. Mismatched use case: Political. | | Vetted brand does not meet minimum vetting score requirements. | The brand's vetting score may be a value that it insufficient for campaign approval. | | Campaign description does not match sample messages or use case. | The campaign description doesn't match the messaging use case, message samples, or both. Update the campaign description, messaging use case, and message samples to match, then resubmit. | | Campaign description does not match sample messages, or use case: Charity. | The use case described in the campaign description indicates that the brand is soliciting charitable donations, but the use case is not set to "Charity" or the sample message content doesn't match the use case. Update the campaign description, use case, and message samples to match, then resubmit. " | | Campaign description does not match sample messages or use case: Political. | "The use case described in the campaign description indicates that the brand is soliciting donations, but the use case is not set to "Political" or the sample message content doesn't match the use case. Update the campaign description, use case, and message samples to match, then resubmit." | | Same or similar use case repeated across multiple campaigns. | The campaign appears to have content that has been duplicated and indicates the disallowed practice of snowshoeing. Make sure that only one campaign is registered for your use case. | | Use case is considered restricted or disallowed by mobile operators: Affiliate marketing. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Lead generation or affiliate marketing. | | Use case is considered restricted or disallowed by mobile operators: Gambling. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Gambling | | Use case is considered restricted or disallowed by mobile operators: High-risk financial services. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: High risk financial services such as short-term loans or cryptocurrency. | | Use case is considered restricted or disallowed by mobile operators: Illegal substances. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Federally illegal substances, such as cannabis. | | Use case is considered restricted or disallowed by mobile operators: Third party job boards. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Third party job boards. | | Use case or message samples appear to be for testing or non-subscriber facing. 10DLC is only allowed for production use cases. | Campaign use case description indicates that Machine-to-Machine content is being shared, which is restricted to non-subscriber facing message programs. Register the campaign again with the correct use case and resubmit. | | Use case is considered restricted or disallowed by mobile operators; prohibited content: SHAFT. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). | | Use case is considered restricted or disallowed by mobile operators; prohibited content: SHAFT without an age gate. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators without an age gate mechanism: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). | | Use case is considered restricted or disallowed by mobile operators: Sweepstakes. | Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Sweepstakes or sweepstakes related messaging. | | Brand referenced in campaign description does not match registered brand name or Doing Business As (DBA) name. | The company name in the campaign description should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the campaign description and resubmit. | | Campaign description does not sufficiently describe the service the message program is providing to the end user. | It must be clear from your campaign description what the purpose of your message program is. Add more details to the description and resubmit. | | Campaign appears to be Direct Lending Arrangement but appropriate Content Attribute was not selected. | From the campaign description it appears that the purpose of your campaign is direct lending but Direct lending or loan arrangement has not been selected. Either update your campaign description or choose Direct lending or loan arrangement and resubmit. | If your HELP message was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Help message rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | HELP message or support contact email address provided in HELP message does not contain or match registered or DBA brand name. | The company name and email domain in the HELP message samples must match or be close to the registered brand name or DBA name, to be clear who the sender is. Update the company name and support email domain in the HELP message samples and resubmit. | | HELP message does not contain support contact of email, phone number, or support website | The HELP message must include customer contact care info to inform the end user how they can receive further support including: email address, phone number, link to a support website. Update the HELP messages to include these and resubmit. | If your opt-in message was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Opt-in message rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Opt-in message does not contain registered brand name or Doing Business As (DBA) name | The company name in the opt-in message samples must match or be close to the registered brand name or DBA name, to be clear who the sender is. Update the company name in the Opt-in message samples and resubmit. | | Opt-in message not provided | Recurring message programs must send the end user an opt-in message with HELP and STOP instructions, message frequency, and "Message and data rates may apply" disclosure. Update the opt-in message and resubmit. | | Opt-in message does not include one or more of the following: Message frequency disclosure for recurring message program or "message and data rates may apply" disclosure. | [Opt-in message](https://aws.amazon.com/blogs/messaging-and-targeting/how-to-build-a-compliant-sms-opt-in-process-with-amazon-pinpoint/) must include the frequency of messages such as the number of messages a month, message frequency varies, if the message are reoccurring and the "Message and data rate disclosure". Update the opt-in message and resubmit. | | Opt-in message does not contain HELP or STOP instructions. | [Opt-in message](https://aws.amazon.com/blogs/messaging-and-targeting/how-to-build-a-compliant-sms-opt-in-process-with-amazon-pinpoint/) must include instructions on how opt-out of the message program, for example "Reply STOP to cancel". Update the opt-in message and resubmit. | If your opt-in workflow was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Opt-in workflow rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Opt-in workflow does not obtain sufficient consent | [Opt-in message](https://aws.amazon.com/blogs/messaging-and-targeting/how-to-build-a-compliant-sms-opt-in-process-with-amazon-pinpoint/) must show that the appropriate type of consent is gained for the message program. The call-to-action must show that express written consent was obtained from the end user before sending promotional message content. For more information, see [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). Update your opt-in workflow and resubmit. | | Opt-in workflow does not match the registered brand name or Doing Business As (DBA) name. | The company name in the Opt-in message samples must contain the registered brand name or DBA name. Add the company name in the Opt-in message samples and resubmit. | | Opt-in workflow URL or image is missing or inaccessible and could not be verified. | No opt-in workflow URL or image was provided in the opt-in workflow or campaign description, or the URL provided is inaccessible. Provide a compliant opt-in process through either a live opt-in URL, or a URL to a hosted opt-in image (screen shot or mock-up) and all possible methods end-users consent to messaging then resubmit. | | Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: Gambling. | Opt-in workflow indicates that message content is related to gambling, which is not permitted by mobile operators. | | Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: High risk financial services. | Opt-in workflow indicates that message content is related to high risk financial services such as short-term loans or cryptocurrency, which is not permitted by mobile operators. | | Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: Illegal substances. | Opt-in workflow indicates that message content is related to federally illegal substances, such as cannabis, which is not permitted mobile operators. | | Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). | Opt-in workflow indicates that message content contains sexual explicit or hateful content which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). | | Opt-in workflow not compliant or is missing the required "message and data rates may apply" disclosure. | Opt-in workflow is not compliant or opt-in does not include the following: "Message and data rates may apply" disclosure. The opt-in workflow must inform the end user of the message and data rate disclosure, as mandated by U.S. carriers. | | Opt-in workflow does not contain HELP or STOP instructions. | Opt-in workflow must include instructions on how the end user can receive further support from the brand regarding the message program such as "Reply HELP for help", "Reply STOP to cancel", or HELP instructions in Terms & Conditions. | | Opt-in workflow not compliant or is missing required message frequency disclosure. | Opt-in workflow is not compliant or does not include the following: Message frequency disclosure. The opt-in workflow must indicate the frequency at which messages will be sent to end users for recurring message program. | | Opt-in workflow not compliant or is missing statement that data will not be shared with third parties or link to privacy policy disclosure. | Opt-in workflow is not compliant or opt-in does not include the following: link to privacy policy or statement that mobile opt-in data will not be shared with third parties. The opt-in workflow must include a link to the message program privacy policy, or language that indicates mobile opt-in data will not be shared. Update the opt-in workflow and resubmit. | | Opt-in workflow not compliant or is missing required terms and conditions language. | Opt-in workflow is not compliant and does not include the following: Complete message program terms and conditions language or a link to the complete terms and conditions. | If your opt-out message was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Opt-out message rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Opt-out message does not contain registered brand name or Doing Business As (DBA) name. | The company name in opt-out message should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the opt-out message and resubmit. | | Opt-out message does not indicate that no further messages will be sent. | The opt-out message must state that no further messages will be sent. Update the opt-out message and resubmit. | If your privacy policy was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Privacy policy rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Privacy policy link is missing or inaccessible. | The privacy policy URL is unavailable to review or the provided URL is inaccessible. Update the URL and resubmit. | | Privacy policy references mobile opt-in data sharing with third parties or does not state that no mobile opt-in data will be shared with third parties or affiliate. | The privacy policy must indicate that mobile opt-in data will not be shared with third parties. Update the privacy policy and resubmit. | If your samples messages were rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Sample message rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Sample message(s) do not contain registered brand name or Doing Business As (DBA) name. | The company name in the sample messages should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the sample messages and resubmit. | | Sample message(s) indicates that message content is related to gambling and is not permitted by US carriers. | Sample message(s) indicates that message content is related to gambling and is not permitted by US carriers. | | Sample message(s) indicates that message content is related to high risk financial services such as loans or cryptocurrency, and is not permitted by US carriers. | Sample message(s) indicates that message content is related to high risk financial services such as loans or cryptocurrency, and is not permitted by US carriers. | | Sample message(s) indicates that message content is related to federally illegal substances, such as cannabis, and is not permitted by US carriers. | Sample message(s) indicates that message content is related to federally illegal substances, such as cannabis, and is not permitted by US carriers. | | Sample message(s) indicates that message content is related to third party job boards and is not permitted by US carriers. | Sample message(s) indicates that message content is related to third party job boards and is not permitted by US carriers. | | Sample message(s) indicates that message content is related to SHAFT (sex, hate, alcohol, firearms, tobacco/vape) and is not permitted by US carriers. | Sample message(s) indicates that message content is related to SHAFT (sex, hate, alcohol, firearms, tobacco/vape) and is not permitted by US carriers. | | Sample message(s) indicates that message content is related to sweepstakes and is not permitted by US carriers. | Sample message(s) indicates that message content is related to sweepstakes and is not permitted by US carriers. | | Use of embedded phone number is selected but not present in message samples. | Use of embedded phone number is selected but not present in message samples. Add the embedded phone number to the message samples or unselect embedded phone number then resubmit. | | Sample message(s) include restricted content such as generic shortened URLs. | Sample messages contain public URL shorteners such as bit.ly or tinyURL are not permitted to be sent in 10DLC message content. | | Sample message(s) use case does not match declared use case(s). | The use case indicated in the sample messages must match the registered use case. Update the sample messages or register the campaign again with the correct use case and resubmit. | | Sample message(s) indicate that message content is soliciting charitable donations, but selected use case is not charity. | If the sample messages indicates that you're soliciting charitable donations through your message program, then the campaign use case should be Charity. Update the sample messages or register the campaign again with the correct use case and resubmit. | | Sample message(s) indicate that message content is political, but selected use case is not political. | If the sample messages indicates that you're sending political messages through your message program, then the campaign use case should be Political. Update the sample messages or register the campaign again with the correct use case and resubmit. | If your Terms and Conditions were rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see [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/). You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see [Edit a registration](registrations-edit.md). **Terms and Conditions rejection reasons** | AWS End User Messaging SMS rejection short description | AWS End User Messaging SMS rejection long description | | --- | --- | | Terms and Conditions do not contain registered brand name or Doing Business As (DBA) name. | The company name in the Terms and Conditions should match or be close to the registered brand name or DBA name. Update the campaign description and resubmit. | | Terms and Conditions link is missing or inaccessible for review. | The Terms and Conditions URL provided is missing or inaccessible. Provide a compliant a compliant URL and resubmit. | | Terms and Conditions are non compliant. | The Terms and Conditions do not contain one or more of the following as mandated by US carriers: a statement that US carriers are not liable for delayed or undelivered messages, message frequency disclosure for recurring message program such as number of message a month, information on how the end user can opt-out of receiving messages from the campaign, customer care contact information, or information on how the end use can receive further support from the brand. | | Terms and Conditions do not contain statement regarding carrier liability. | The Terms and Conditions does not contain a statement that US carriers are not liable for delayed or undelivered messages. | | Terms and Conditions do not contain customer care contact information. | The Terms and Conditions do not contain one or more of the following as mandated by US carriers: customer care contact information, or information on how the end use can receive further support from the brand. | | Terms and Conditions do not contain required message frequency disclosures. | The Terms and Conditions do not contain one or more of the following as mandated by US carriers: message frequency disclosure for recurring message program such as number of messages a month. | | Terms and Conditions do not contain opt-out language. | The Terms and Conditions does not contain information on how the end user can opt-out of receiving messages from the campaign. | | Terms and Conditions do not contain link to privacy policy. | The Terms and Conditions must contain a link to the privacy policy. Update the Terms and Conditions and resubmit. | | Terms and Conditions do not contain a description of the campaign use case. | The Terms and Conditions must include a description of the purpose of the message program. Update the Terms and Conditions and resubmit. | | Terms and conditions do not contain a program description or terms related to declared use case. | The Terms and Conditions program description is not related to the campaign use case. Update the Terms and Conditions then resubmit. | # Get more information through Support for registration issues Get more information on registration issues The 3rd party downstream reviewer might find issues with the registration that results in a denied registration with a related error message. For more information on registration error messages and solutions, see [Gen-AI Feedback on Registrations (Preview)](registrations-genai-feedback.md). You should also review [10DLC Registration Best Practices to Send SMS with Amazon Pinpoint](https://aws.amazon.com/blogs/messaging-and-targeting/10dlc-registration-best-practices-to-send-sms-with-amazon-pinpoint/) and [How to Build a Compliant SMS Opt-In Process With Amazon Pinpoint](https://aws.amazon.com/blogs/messaging-and-targeting/how-to-build-a-compliant-sms-opt-in-process-with-amazon-pinpoint/) blog articles that have more in-depth details on how to successful register an SMS use case. If you are still having issues getting your SMS use case approved you can reach out through Support to ask for additional assistance in understanding why your use cases was rejected. **Note** that this requires downstream engagement and takes time to better understand the denial reason. **Note** If you are not based in the United States and your 10DLC brand registration fails you should: Apply for [10DLC brand vetting form](registrations-10dlc-vetting.md), as this is a manual review of your 10DLC brand. If vetting fails then follow the directions below to submit a support ticket. **To submit a request for information about a rejected 10DLC brand or campaign** 1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase). 1. On the **Create Case** page, complete the following: + Select **Account and Billing**. + For **Service**, choose **Service Quotas**. + For **Category** choose either **AWS End User Messaging SMS (Pinpoint)** or **AWS End User Messaging Voice (Pinpoint)**, depending on your request. + For **Severity**, choose **General Limits**. 1. In the **Requests** section, do the following: + For **Region**, choose the AWS Region that you attempted to register the campaign in. + For **Resource Type**, choose the type of registration you are inquiring about: **10DLC or TFN Registration**, **10DLC Registration**, **Registration**, **Sender ID Registration**, or **Template Registration**. + For the **Quota**, choose either **Company or 10DLC Campaign Registration Rejection**, **General Inquiry**, or **Registration Rejection Query**. 1. For **Use case description**, enter the rejected registration ID. 1. Choose **Next Step: Solve now or Contact us**. For **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**. 1. For **Contact method**, choose your preferred method of communicating with the Support team. 1. Choose **Submit**. The Support team will provide information about the reasons that your 10DLC campaign registration was rejected in your Support case. # Registration forms The following registrations can be filled out and submitted through the AWS End User Messaging SMS console. **Topics** + [Australia sender ID registration](registrations-australia.md) + [Belarus sender ID registration](registrations-belarus.md) + [ # China SMS template registration form ](phone-numbers-sms-template-registration.md) + [Egypt sender ID registration](registrations-egypt.md) + [Finland sender ID registration](registrations-finland.md) + [India sender ID registration](registrations-sms-senderid-india.md) + [Indonesia sender ID registration](registrations-indonesia.md) + [Ireland sender ID registration](registrations-ireland.md) + [Jordan sender ID registration](registrations-jordan.md) + [Kazakhstan sender ID registration](registrations-kazakhstan.md) + [Kenya sender ID registration](registrations-kenya.md) + [Kuwait sender ID registration](registrations-kuwait.md) + [Philippines sender ID registration](registrations-philippines.md) + [Qatar sender ID registration](registrations-qatar.md) + [Russia sender ID registration](registrations-russia.md) + [Saudi Arabia sender ID registration](registrations-saudi-arabia.md) + [Singapore sender ID registration](registrations-sg.md) + [Sri Lanka sender ID registration](registrations-sri-lanka.md) + [Thailand sender ID registration](registrations-thailand.md) + [Turkey sender ID registration](registrations-turkey.md) + [United Arab Emirates sender ID registration](registrations-united-arab-emirates.md) + [United Kingdom sender ID registration](registrations-uk.md) + [Vietnam sender ID registration](registrations-vietnam.md) + [Zambia sender ID registration](registrations-zambia.md) # Australia sender ID registration in AWS End User Messaging SMS Australia sender ID registration Follow these directions to register your sender ID in Australia. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Australia specific info** section, enter the following: + For **Letter of authorization**, download, complete, and attach the [letter of authorization](samples/Australia_SenderId_LetterOfAuthorization.zip). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, if your company is not local to Australia, then you are required to provide a copy of your company's registration documentation. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. + For **Company identification number**, enter the identification number of your company, such as ABN/ACN/ARBN/ICN if you are headquartered in Australia, or EIN/VAT if international. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Belarus sender ID registration in AWS End User Messaging SMS Belarus sender ID registration Follow these directions to register your sender ID in Belarus. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Belarus specific info** section, enter the following: + For **Acknowledgement of transactional content**, promotional content is disallowed for Belarus sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # China SMS template registration form To register your SMS template you must open a support case in the Support Center Console. **Note** Only China requires SMS template registration for your account to be allowed sending there. **Register an SMS template** 1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase). 1. In the **Service** section, do the following: + For **Limit type**, choose **AWS End User Messaging SMS (Pinpoint)**. + For **Provide a link to the site or app which will be sending SMS messages - optional**, identify the website or application where your audience members opt in to receive your SMS messages. + For **What type of messages do you plan to send - optional**, choose the type of message that you plan to send using your Sender ID: + **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application. + **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements. + **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + For **Which AWS Region will you be sending messages from - optional**, choose the AWS Region that you will be sending messages from. + For **Which countries do you plan to send messages to - optional**, enter the country or region that you will be sending messages to. **Note** Only China requires template registration for your account to be allowed sending there. + In the **How do your customers opt to receive messages from you - optional**, provide details about your opt-in process. + In the **Please provide the message template that you plan to use to send messages to your customers - optional** field, include the template that you will be using. 1. In the **Requests** section, do the following: + For the **Region**, choose the AWS Region that you plan to make API requests from. + For **Resource Type**, choose **Template Registration**. + For **Quota**, choose on of the following: + **One Time Passwords/Two-Factor Authentication** – Messages that provide passwords that your customers use to authenticate with your website or application. + **Promotional/Marketing** – Noncritical messages that promote your business or service, such as special offers or announcements. + **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + **Transactional/Notifications/OTP/2FA** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + For **New quota value** enter `1`. 1. Under **Case description**, for **Use case description**, explain your use case and opt-in workflow. + The SMS message template that you plan to use. + The number of messages that you plan to send each recipient each month. + Information about how your customers opt in to receiving messages from you. + The name of your company or organization. + The address that's associated with your company or organization. + The country where your company or organization is based. + A phone number for your company or organization. + The URL of the website for your company or organization. 1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**. 1. When you finish, choose **Submit**. After we receive your request, we provide an initial response within 24 hours. We will send you a country-specific registration form for you to complete and provide back to us for downstream processing. **Important** In order to prevent our systems from being used to send unsolicited or malicious content, we consider each request carefully. We might not be able to grant your request if your use case doesn't align with our policies. # Egypt sender ID registration in AWS End User Messaging SMS Egypt sender ID registration Follow these directions to register your sender ID in Egypt. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Egypt specific info** section, enter the following: + For **Letter of authorization**, download, complete, and attach the [letter of authorization](samples/Egypt_SenderId_LetterOfAuthorization.zip). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, if your company is local to Egypt, you are required to provide a copy of your company registration document. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Tax card document**, if your company is local to Egypt, you are required to provide a copy of your tax card document. + For **Acknowledgement of transactional content**, choose Yes to acknowledge the the sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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 sender ID registration in AWS End User Messaging SMS Finland sender ID registration Follow these directions to register your sender ID in Finland. As required by Finnish regulation (Traficom Order 28 L/2025 M), all sender IDs used to send SMS messages to Finnish mobile numbers must be pre-registered with local operators. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) Choose **Next**. 1. In the **Company info** section, enter the following: + For **Company Name**, enter the name of your company as officially registered. + For **Company identification number – optional**, enter your tax ID or business registration number (such as a Finnish Business ID or VAT number), if available. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one-time password or verification code. + **Account or security alerts** – Use this for sending account notifications or security alerts. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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 for sending promotional or marketing messages. + **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 description** to provide additional context to the selected **Use case category**. 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. 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 sender ID registration process in AWS End User Messaging SMS India sender ID registration There are two ways to send SMS messages to recipients in India: *international routes* and *local routes*. # Understanding international and local routes for India International and local routes **International routes (ILDO)** By default, when you send messages to recipients in India, AWS End User Messaging SMS uses International Long-Distance Operator (ILDO) routes to transmit those messages. When recipients see a message sent over an ILDO connection, it appears to be sent from a random shared short code (unless you purchase a dedicated short code). International SMS to India is delivered via short codes rather than alphabetic sender IDs. International routes are *not* subject to any AWS Region restriction. You can send messages to India over international routes—whether using a shared or dedicated short code—from any AWS Region where AWS End User Messaging SMS is available. **Local routes (DLT-registered sender IDs)** Companies that are registered in India can also use dedicated alphabetic sender IDs to send their messages. If you prefer to use a sender ID, you must send those messages over local routes rather than ILDO routes. Local routes require you to complete the DLT registration process described on this page. **Important** AWS End User Messaging SMS only supports local India routes through AWS regions AP-SOUTH-1 Asia Pacific (Mumbai) and AP-SOUTH-2 Asia Pacific (Hyderabad). This restriction applies to local routes that use DLT-registered sender IDs. It does not apply to international routes or short codes, which can be used from any AWS Region. **Cost comparison** **Note** The price for sending messages using international (ILDO) routes is significantly higher than the price for sending messages through local routes. For current pricing for both route types, see the [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/) page. To send messages using local routes, you must first register your use case and message templates with the Telecom Regulatory Authority of India (TRAI) through a Distributed Ledger Technology (DLT) portal. When you register your use case through a DLT portal, you receive an Entity ID and a Template ID, which you must specify when you send your messages through AWS End User Messaging SMS. These registration requirements are designed to reduce the number of unsolicited messages that Indian consumers receive and to protect consumers from potentially harmful messages. To complete the registration process, you must provide the following information: + Your organization's Permanent Account Number (PAN). + Your organization's Tax Deduction Account Number (TAN). + Your organization's Goods and Services Tax Identification Number (GSTIN). + Your organization's Corporate Identity Number (CIN). + A letter of authorization that gives you the authority to register your organization with Vilpower. The Vilpower website includes a template that you can download and modify to fit your needs. To send SMS messages to India, follow these steps: 1. [Register your company and use case with the TRAI and create the required Telemarketer chains](registrations-sms-senderid-india-register.md) 1. [India sender ID registration in AWS End User Messaging SMS](registrations-sms-senderid-india-support.md) 1. [Specify the Entity ID and Template ID values to send messages to India](registrations-sms-senderid-india-specify-ids.md) **Topics** + [International and local routes](registrations-sms-senderid-india-routes.md) + [Register with TRAI and create Telemarketer chains](registrations-sms-senderid-india-register.md) + [India sender ID registration](registrations-sms-senderid-india-support.md) + [Specify the Entity and Template ID values to send messages](registrations-sms-senderid-india-specify-ids.md) + [Understanding template matching issues](registrations-sms-senderid-india-template-issues.md) # Register your company and use case with the TRAI and create the required Telemarketer chains Register with TRAI and create Telemarketer chains The first step is to register your company and use case with TRAI. All distributed ledger technology (DLT) registration portals require you to provide the same registration details. The Entity ID and Template ID values that you receive from these portals are interchangeable. **Note** You may be charged a fee for registering your company. **Telemarketer Chain Registration Process** 1. Login or create a Principal Entity (PE) account with your DLT provider. For example, [https://www.vilpower.in/](https://www.vilpower.in/) **Note** If you are creating an account choose **Enterprise** as the entity type. 1. You are required to create a chain of Telemarketers (TM) in your DLT platform for every Telemarketer in the table below. We use multiple providers so you are required to create multiple chains to ensure your SMS will be delivered. **Telemarketer** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-sms-senderid-india-register.html) **Note** As of 2/6/2025, ACL MOBILE PRIVATE LIMITED telemarketer ID is no longer required and is managed through the Sinch Cloud Communication Services India Private Limited telemarketer. To create a chain of TMs: 1. Navigate to the **Chain** section of your DLT platform. Some DLT providers call this **SMS Workflow**. 1. Choose the option to create a new **Chain**. 1. Search for the entity name or related Telemarketer ID (TM ID) list from the table above. **Important** If the TM is not found in the **Chain** tab of the DLT portal, your DLT provider may require you to add the TM first. To do this, navigate to the TM tab and add each of the TMs listed from the table above. 1. Submit the chain for Telemarketers (TM) approval and the TM will review and approve the request. The TM, if applicable, will work with their TMs within the chain so they are included and the Telemarketer-Delivery Function (DF) will ultimately approve the complete TM chain. 1. Once approved by the TM, the request will go back to you as the PE. You will need to login once again into your DLT platform and approve the PE to TM chain. The chain will be completed at that time. If you are new to the India DLT process, ensure you are also meeting the requirements to register your Sender IDs (“Headers”), content templates, and message consent. Each DLT provider is slightly different. Reach out to the respective DLT support teams if you need help with your provider. # India sender ID registration in AWS End User Messaging SMS India sender ID registration After you register your company and use case with TRAI, you must create a case with Support. The Support team uses the information that you provide in your case to associate your Entity ID and Template ID with your AWS account. **Note** India allows transactional sender IDs to be 3–6 characters in length. Promotional sender IDs are required to be 6 characters. All sender ID approval is owned by TRAI. You can register a sender ID for [transactional messages](#registrations-sms-senderid-india-support-case.title) using the AWS End User Messaging SMS console or to register a sender ID for [promotional messages](#registrations-sms-senderid-india-support.title) create an AWS Support case. ## India transactional message sender ID registration Follow these directions to register your sender ID for transactional messages in India. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. India sender IDs must be 3-6 alphabetic characters. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **India specific info** section, enter the following: + For **Chain ID: Principal Entity ID (PEID)**, enter the PEID that you received after completing the registration process with the Telecom Regulatory Authority of India (TRAI). + For **Chain ID: ROUTE LEDGER TECHNOLOGIES PRIVATE LIMITED**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers. + For **Chain ID: Karix Mobile Pvt Ltd**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers. + For **Chain ID: Sinch Cloud Communication Services India Private Limited**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers. + For **Chain ID: Infobip India Private Limited**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers. + For **Acknowledgement of required sending parameters**, choose Yes to acknowledge you will specify the [Entity ID and Template ID values](registrations-sms-senderid-india-specify-ids.md#registrations-sms-senderid-india-specify-ids.title) when you send your messages to India. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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 promotional message sender ID registration Follow these directions to register your sender ID for promotional messages in India. **Register sender ID for promotional messages** 1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase). 1. In the **Create Case** section, do the following: + For **Limit type**, choose **AWS End User Messaging SMS (Pinpoint)**. + For **Provide a link to the site or app which will be sending SMS messages**, identify the website or application where your audience members opt in to receive your SMS messages. + For **What type of messages do you plan to send**, choose **Promotional**: + **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application. + **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements. + **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + For **Which countries do you plan to send messages to**, choose the AWS Region that you will be sending messages from. 1. In the **Requests** section, do the following: + For the **Region**, choose the AWS Region that you plan to make API requests from. + For **Resource Type**, choose **Template Registration**. + For **Limit**, choose on of the following: + **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application. + **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements. + **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. 1. Under **Case description**, for **Use case description**, explain your use case and opt-in workflow. 1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**. 1. When you finish, choose **Submit**. After we receive your request, we provide an initial response within 24 hours. We will send you a country-specific registration form for you to complete and provide back to us for downstream processing. **Important** In order to prevent our systems from being used to send unsolicited or malicious content, we consider each request carefully. We might not be able to grant your request if your use case doesn't align with our policies. # Specify the Entity ID and Template ID values to send messages to India Specify the Entity and Template ID values to send messages To successfully deliver your messages using local routes, you must specify Entity ID and Template ID values that you received after completing the sender ID registration process. You must also choose the correct entity type, and confirm that your messages match the example templates that you registered. The steps that you complete depend on how you send your SMS messages. If you use the [SendTextMessage](https://docs.aws.amazon.com//pinpoint/latest/apireference_smsvoicev2/API_SendTextMessage.html) API to send your messages, you can include these attributes in your call to the API. If you use campaigns or journeys to send your messages, you can specify the correct values when you set up the campaign or journey. This section includes information for both scenarios. **To send messages over Indian local routes using the SendTextMessages API** 1. In your call to the `SendTextMessages` API, provide values for the following parameters: + `EntityId` – The entity ID or Principal Entity (PE) ID that you received after completing the sender ID registration process. + `TemplateId` – The template ID that you received after completing the sender ID registration process. **Important** Make sure that the Template ID that you specify matches your message template exactly. If your message doesn't match the template that you provided during the registration process, the mobile carriers might reject your message. 1. For the `MessageType` parameter, specify the appropriate route type for your message. You can specify one of the following values: + `Promotional` – Specify this message type for promotional messages. Promotional sender IDs only contain numbers. + `Transactional` – Specify this message type for transactional messages. Transactional sender IDs only contain letters, and are case-sensitive. **Note** You can register both promotional (numeric) sender IDs and transactional (alphabetic) sender IDs in the same AWS account. For additional content guidelines, see the Vilpower website at [https://www.vilpower.in](https://www.vilpower.in). 1. When you add content to your message, review your content thoroughly to verify that it matches the content in the DLT registered template exactly. If you include additional character returns, spaces, punctuation, or mismatched sentence case, carriers will block your SMS messages. For more information about issues related to template matching, see [Understanding template matching issues when sending messages](registrations-sms-senderid-india-template-issues.md). # Understanding template matching issues when sending messages Understanding template matching issues Indian carriers will reject your messages if they don't align exactly with the templates that you submitted during the registration process. If you experience message delivery issues, check your messages for the following common issues: + **Message content doesn't match registered template** – All of the messages that you send must correspond to a registered template. If you send a message that doesn't exactly match the template associated with the Template ID that you provided, the mobile carriers will reject your message. + **The value of a variable is too long** – If the value of a variable contains more than 30 characters, the mobile carriers will reject your message. + **Case mismatch** – The mobile carriers compare your messages to the templates that you registered. This comparison process is case-sensitive. + **Slightly different characters** – Your message can be rejected if it contains characters that look similar to the characters in your registered template, but are actually different. For example, if you copy text from Microsoft Word, the text might include curly-quote characters ( “ and ” ), as opposed to the straight quote character ( " ). Make sure that your message matches your registered templates exactly. # Indonesia sender ID registration in AWS End User Messaging SMS Indonesia sender ID registration Follow these directions to register your sender ID in Indonesia. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Indonesia specific info** section, enter the following: + For **Letter of authorization: XL Axiata**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Indonesia_SenderId_LetterOfAuthorization_XLAxiata.zip). There are two versions of this form, depending on whether your business has a local Indonesia address or not. This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Telkomsel**, if your company is local to Indonesia, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Indonesia_SenderId_LetterOfAuthorization_Telkomsel.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: IOH**, if your company is local to Indonesia, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Indonesia_SenderId_LetterOfAuthorization_IOH.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Smartfren**, if your company is local to Indonesia, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Indonesia_SenderId_LetterOfAuthorization_Smartfren.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Regulatory agency license**, if your company's area of business is in money lending, then you are required to provide your operating license from Otoritas Jasa Keuangan (OJK). 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Ireland sender ID registration in AWS End User Messaging SMS Ireland sender ID registration Follow these directions to register your sender ID in Ireland. **Important** Before you begin your Ireland sender ID registration with AWS End User Messaging SMS, you must first complete registration on the Ireland Commission for Communications Regulation (ComReg) Sender ID registration portal at [https://senderid.comreg.ie/sender-id-sign-up](https://senderid.comreg.ie/sender-id-sign-up). When completing your ComReg Sender ID Registration, make sure you complete the following: In ComReg’s Section 2, choose **Assign a 3rd party** and **Amazon Web Services**. In ComReg’s Section 3 "Select OPAs," choose all of the following: **Sinch Sweden AB** **Telesign Corporation** **Twilio Inc** **Vonage** Failure to choose **Amazon Web Services** as a third party or failure to choose all of the OPAs might result in impact to your SMS delivery to Ireland. After ComReg has approved your sender ID registration, you can proceed with the AWS registration process below. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Ireland specific info** section, enter the following: + For **Sender ID Owner (SIDO) Number ID**, enter the SIDO number your received from ComReg when registering. You can find your SIDO number in the ComReg registry portal by logging in and choosing the account icon in the top-right corner of the home screen. + For **Company registration documentation**, upload the registration documentation for your company. This can be a certificate of incorporation (COI), trade license, or international equivalent. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. + **Area of business** + **Company customer care email address** + **Company customer care phone number** Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + **First name** + **Last name** + **Contact email address** + **Contact phone number** Choose **Next**. 1. In **Messaging Use Case**, provide + **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Account or security alerts** + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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** + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 Choose **Next**. 1. In **Message samples**, provide: + At least one message sample (required) + Up to two additional message samples (optional) 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**. # Jordan sender ID registration in AWS End User Messaging SMS Jordan sender ID registration Follow these directions to register your sender ID in Jordan. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Jordan specific info** section, enter the following: + For **Company registration documentation**, provide a copy of your company's registration documentation, regardless if your company is local to Jordan or international. + For **Acknowledgement of transactional content**, promotional content is disallowed for Jordan sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages, and that the use case description you provided describes all messages to be sent by this sender ID. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Kazakhstan sender ID registration in AWS End User Messaging SMS Kazakhstan sender ID registration Follow these directions to register your sender ID in Kazakhstan. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Kazakhstan specific info** section, enter the following: **Note** The fields in this section are required only if your company is local to Kazakhstan (company address country is KZ). If your company is international, you can skip this section. + For **Confirmation of operations in Kazakhstan**, if your company is local to Kazakhstan, you are required to provide confirmation that your company operates in Kazakhstan. This can be a screenshot of your company's website from a .kz domain, or a copy of your local certificate of registration. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Number of countries where brand is present**, if your company is local to Kazakhstan, indicate the number of countries where your brand is present. + For **Brand headquarters**, if your company is local to Kazakhstan, provide the location of your brand's headquarters (city and country). + For **Date of establishment**, if your company is local to Kazakhstan, provide the date your company or brand was established. + For **Country of origin**, if your company is local to Kazakhstan, provide the country where your brand or company was originally founded. + For **Period of work in Kazakhstan**, if your company is local to Kazakhstan, indicate how long your company has been operating in the Kazakhstan market. + For **Founding members**, if your company is local to Kazakhstan, provide the names of the founding members of your company. + For **Financial sector license – optional**, if your company operates in the financial sector, you are encouraged to provide your financial sector license. This can be the license number or a screenshot of the license document. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Server IP address**, if your company is local to Kazakhstan, provide the IP address of the server that will be used for sending messages. This should be your company's server IP address (IPv4 or IPv6). 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Kenya sender ID registration in AWS End User Messaging SMS Kenya sender ID registration Follow these directions to register your sender ID in Kenya. **Important** Support for sender ID registration in Kenya is for international companies only. We do not currently support local Kenya companies to register sender IDs. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Kenya specific info** section, enter the following: + For **Company registration documentation**, provide a copy of your company's registration documentation. For example, your company's Certificate of Incorporate (COI). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Kenya sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code where the physical address is located. Support for sender ID registration in Kenya is for international companies only. We do not currently support local Kenya companies to register sender IDs. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Kuwait sender ID registration in AWS End User Messaging SMS Kuwait sender ID registration Follow these directions to register your sender ID in Kuwait. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Kuwait specific info** section, enter the following: + For **Letter of authorization: General**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Kuwait_SenderId_LetterOfAuthorization_General.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Ooredoo**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Kuwait_SenderId_LetterOfAuthorization_Ooredoo.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Zain**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Kuwait_SenderId_LetterOfAuthorization_Zain.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, if your company is local to Kuwait, you are required to provide a copy of your company's registration documentation. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Kuwait sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Philippines sender ID registration in AWS End User Messaging SMS Philippines sender ID registration Follow these directions to register your sender ID in Philippines. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations). + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. Choose **Next**. 1. In the **Philippines specific info** section, enter the following: + For **Letter of authorization: Globe**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Philippines_SenderId_LetterOfAuthorization_Globe.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Smart**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Philippines_SenderId_LetterOfAuthorization_Smart.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: BFSI**, if your company's area of business is in banking, financial services, or insurance (BFSI), then you are required to download, complete, and attach the linked [letter of authorization (LOA)](samples/Philippines_SenderId_LetterOfAuthorization_BFSI.zip). This document is also referred to as a letter of appointment. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, if your company's area of business is in Banking, Financial Services, or Insurance (BFSI), then you are required to provide a copy of your company's registration documentation also called Articles of Incorporation. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Business permit**, if your area of business is in BFSI, then you are required to provide a copy of your business permit. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Regulatory agency license**, if your company's area of business is BFSI, then you are required to provide your industry-specific regulatory license, for example a BSP license for banking. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Proof of sender ID connection**, if your company's area of business is BFSI, and the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. + For **Acknowledgement of transactional content**, promotional content is disallowed for Philippines sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Qatar sender ID registration in AWS End User Messaging SMS Qatar sender ID registration Follow these directions to register your sender ID in Qatar. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Qatar specific info** section, enter the following: + For **Letter of authorization: Vodafone**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Qatar_SenderId_LetterOfAuthorization_Vodafone.zip). This document is also referred to as a NOC (No Objection Certificate), it requires a wet signature or a digital signature via Adobe or DocuSign, and must be printed on customers company letterhead. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: Ooredoo**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Qatar_SenderId_LetterOfAuthorization_Ooredoo.zip). This document is also referred to as a NOC (No Objection Certificate), it requires a wet signature or a digital signature via Adobe or DocuSign, and must be printed on customers company letterhead. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Qatar sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. + For **Local Trade License**, if your company is domestic or local to Qatar, you are required to upload a valid trade license document issued by Qatar authorities that permits your business to operate in Qatar. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, you can optionally upload your company commercial registration document. This may be requested by the carrier during the registration review process. Providing it upfront can help avoid delays. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Russia sender ID registration in AWS End User Messaging SMS Russia sender ID registration Follow these directions to register your sender ID in Russia. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Russia specific info** section, enter the following: + For **Company registration documentation**, you are required to provide a copy of your company's registration documentation, regardless if your company is local to Russia or international. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Russia sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Saudi Arabia sender ID registration in AWS End User Messaging SMS Saudi Arabia sender ID registration Follow these directions to register your sender ID in Saudi Arabia. **Important** Support for sender ID registration in Saudi Arabia is for international companies only. We do not currently support local Saudi Arabia companies to register sender IDs. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. Choose **Next**. 1. In the **Saudi Arabia specific info** section, enter the following: + For **Letter of authorization: Vodafone**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/SaudiArabia_SenderId_LetterOfAuthorization.zip). This document is also referred to as a NOC (No Objection Certificate). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Proof of sender ID connection**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. + For **Acknowledgement of transactional content**, promotional content is disallowed for Saudi Arabia sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code where the physical address is located. Support for sender ID registration in Saudi Arabia is for international companies only. We do not currently support local Saudi Arabia companies to register sender IDs. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Singapore sender ID registration process Singapore sender ID registration AWS End User Messaging SMS customers are able to send SMS traffic in Singapore using a Sender ID that has been registered through the Singapore SMS Sender ID Registry (SSIR). SSIR was launched in March of 2022 through the Singapore Network Information Centre (SGNIC) which is owned by Info-communications Media Development Authority (IMDA) of Singapore, and enables organizations to register their Sender ID when sending SMS to mobile phones in Singapore. In order to use a registered Singapore Sender ID you must obtain a Unique Entity Number (UEN), then submit a request to AWS End User Messaging SMS to allow-list your account for usage of your Sender ID and finally complete the registration process through SSIR. If you do not register your sender ID any message sent using a sender ID will have its ID changed to **LIKELY-SCAM** per regulatory agency rules. Regulators will filter or block unregistered traffic at their discretion. **Important** Your Singapore registration must be completed in this order: [Registering for a Singapore Unique Entity Number (UEN)](registrations-sg-uen.md) [Create a new registration using the AWS End User Messaging SMS console](registrations-create.md) with **Registration type** set to Singapore sender ID registration and complete the registration form. [Registering a Sender ID with Singapore Network Information Centre (SGNIC)](registrations-sg-sgnic.md) **Topics** + [Singapore Unique Entity Number (UEN)](registrations-sg-uen.md) + [Singapore sender ID registration form](registrations-sg-form.md) + [Register a Sender ID with Singapore Network Information Centre (SGNIC)](registrations-sg-sgnic.md) + [ # Singapore sender ID registration frequently asked questions ](registrations-sg-faq.md) # Registering for a Singapore Unique Entity Number (UEN) Singapore Unique Entity Number (UEN) In order to start a registration with the SSIR you must first obtain a Singapore Unique Entity Number (UEN). A UEN is a unique entity number you receive when you register your business with the Account and Corporate Registry Authority (ACRA), for more information see [Who Must Register with ACRA?](https://www.acra.gov.sg/how-to-guides/before-you-start/who-must-register). The amount of time to process can vary depending on how easily the ACRA can validate your request. # Singapore sender ID registration form Singapore sender ID 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 customers are able to send SMS traffic in Singapore using a Sender ID that has been registered through the Singapore SMS Sender ID Registry (SSIR). SSIR was launched in March of 2022 through the Singapore Network Information Centre (SGNIC) which is owned by Info-communications Media Development Authority (IMDA) of Singapore, and enables organizations to register their Sender ID when sending SMS to mobile phones in Singapore. In order to use a registered Singapore Sender ID you must obtain a Unique Entity Number (UEN), then submit a request to AWS End User Messaging SMS to allow-list your account for usage of your Sender ID and finally complete the registration process through SSIR. **Note** Before you request and register your sender ID you must obtain a Singapore Unique Entity Number (UEN). For more information, see [Registering for a Singapore Unique Entity Number (UEN)](registrations-sg-uen.md). **Complete a Singapore sender ID 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 Singapore sender ID registration to complete. 1. In the **Company info** section, enter the following: + For **Company Name**, enter the name of your company. + For **Tax ID**, enter you Singapore Unique Entity Number. + 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. + 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. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Are you registering on behalf of another brand/entity?** if yes then choose True. If you are not the end user sending the messages you are considered a "Representative" of the other brand/entity. + For **Letter of authorization image – optional**, if you checked the box as **Registering on behalf of another brand/entity?** , upload an image of the complete Letter of Authorization (LOA). The supported file type is PNG and the maximum file size is 400KB. A template for the LOA can be [downloaded](samples/Singapore_Sender_ID_Registration_LOA_Template.zip) for your convenience. + For **Sender ID connection – optional** you can add more details about the connection between the requested sender ID and company name. 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. + **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**. 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**. **Note** After your registration has been submitted you need to register the send ID with Singapore Network Information Centre (SGNIC). For more information on how to register, see [Registering a Sender ID with Singapore Network Information Centre (SGNIC)](registrations-sg-sgnic.md). Your registration will be considered complete once we have received signal from SGNIC. # Registering a Sender ID with Singapore Network Information Centre (SGNIC) Register a Sender ID with Singapore Network Information Centre (SGNIC) To register a sender ID with Singapore Network Information Centre (SGNIC) there are two steps that must be completed in the following order: **Register a sender ID with Singapore Network Information Centre (SGNIC)** 1. You must first work with AWS End User Messaging SMS to register your Singapore (SG) Sender ID for your account. After this step is complete you can proceed to the next step. 1. Work with SGNIC to register your sender ID using the process at [SGNIC SMS Sender ID Registry](https://smsregistry.sg/web/login). 1. When completing the process list AMCS SG Private Limited (Amazon Media Communications Services) as your participating aggregator. **Warning** Doing these steps out of order might result in your sender ID being blocked by the service or will prevent your Sender ID from being preserved on the mobile device. **Note** Please note that you are required to submit a sender ID registration from each individual AWS account you require to use the sender ID. # Singapore sender ID registration frequently asked questions Frequently asked questions about the Singapore sender ID number registration process with AWS End User Messaging SMS. ## Do I currently have a Singapore sender ID **To check if you own a Singapore sender ID** 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 **Sender ID**. 1. On the **Sender IDs** page, you can search by two letter country code **SG** to find if you have any Singapore sender IDs. ## How long will registration take? While a typical review takes 1 – 3 weeks, it can take up to 5 weeks or longer in some cases to verify your information with government agencies. ## What is a Unique Entity Number (UEN) and how do i get one? A UEN is a Singapore business ID issued by Accounting and Corporate Regulatory Agency (ACRA). Local companies and businesses in Singapore can get a UEN by applying through ACRA. Once you pass through the registration and standard incorporation procedure, it will be issued. You can apply for a UEN with ACRA via [Bizfile](https://www.bizfile.gov.sg/ngbbizfileinternet/faces/oracle/webcenter/portalapp/pages/BizfileHomepage.jspx). ## Do I have to register for a Singapore Sender ID? Yes. If you haven't registered your Singapore Sender ID any message sent using a Sender ID will likely have its ID changed to **LIKELY-SCAM** ## How do I register my Singapore Sender ID with AWS End User Messaging SMS? Follow the directions at [Create a new registration using the AWS End User Messaging SMS console](registrations-create.md) to register a Sender ID. ## What is the registration status of my Singapore Sender ID 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 [Create a new registration using the AWS End User Messaging SMS console](registrations-create.md). ## What if my Singapore Sender ID 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 user/role that you use to visit the AWS End User Messaging SMS console must be enabled with the *`“sms-voice:*”`* permission. ## Are there any restrictions to the formatting or allowed special characters for Singapore Sender IDs? Yes. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations). # Sri Lanka sender ID registration in AWS End User Messaging SMS Sri Lanka sender ID registration Follow these directions to register your sender ID in Sri Lanka. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Sri Lanka specific info** section, enter the following: + For **Letter of authorization (LOA)**, you are required to download, complete, and attach the [letter of authorization](samples/SriLanka_SenderId_LetterOfAuthorization.zip). This document is also referred to as a NOC (No Objection Certificate), it requires a wet signature or a digital signature via Adobe or DocuSign, and must be printed on customers company letterhead. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of a single use case**, transactional and promotional content is must be sent using seperate Sri Lanka sender IDs. Choose **Yes**, to acknowledge that the use case description you provided describes all messages to be sent by this sender ID. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Account or 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. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 Choose **Next**. 1. In **Message samples**, do the following: **Note** Your brand/company or service name must be included in your message content and provided sample messages. + 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. 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**. # Thailand sender ID registration in AWS End User Messaging SMS Thailand sender ID registration Follow these directions to register your sender ID in Thailand. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Thailand specific info** section, enter the following: + For **Letter of authorization (LOA)**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Thailand_SenderId_LetterOfAuthorization.zip). Your LOA must be signed by an authorized signatory of the company and stamped from the end brand with the company's letterhead. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Account or 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. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # Turkey sender ID registration in AWS End User Messaging SMS Turkey sender ID registration **URL content restrictions effective April 1, 2026** Starting April 1, 2026, SMS messages to Turkey mobile numbers that contain URLs will be blocked if sent without a registered sender ID. If you do not have a registered sender ID for Turkey, register one using the process below to ensure your messages continue to be delivered. Even with a registered sender ID, messages containing shortened or generic URLs (such as bit.ly or tinyurl.com) will be blocked. Ensure all URLs in your messages use your company's own branded domain. Follow these directions to register your sender ID in Turkey. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Turkey specific info** section, enter the following: + For **Letter of authorization**, you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Turkey_SenderId_LetterOfAuthorization.zip). This document is also referred to as a NOC (No Objection Certificate). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization (vendor)**, you are required to download, complete, and attach the [vendor-specific letter of authorization (LOA)](samples/Turkey_SenderId_VendorLetterOfAuthorization.zip). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, you are required to provide a copy of your company's registration documentation, regardless if your company is local to Turkey or international. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Turkey sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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 Arab Emirates sender ID registration in AWS End User Messaging SMS United Arab Emirates sender ID registration Follow these directions to register your sender ID in United Arab Emirates. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. Choose **Next**. 1. In the **United Arab Emirates specific info** section, enter the following: **Note** For all uploads the valid file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, you are required to provide a copy of your company's registration documentation, regardless if your company is local to United Arab Emirates or international. This document is also known as a Certificate of Incorporation (COI) or trade license. For companies registered in the US, UK, or India, provide the Certificate of Incorporation. If the document is not in English or Arabic, a certified translation is required. + For **Proof of sender ID connection**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand, such as a trademark certificate. The document must be in English or Arabic and include a signature and/or stamp from the issuing authority. Applications or web references are not accepted. + For **Letter of authorization: Etisalat (Local)**, if your company is local to United Arab Emirates, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/UnitedArabEmirates_SenderId_LetterOfAuthorization_Etisalat.zip). This document is also referred to as a No Objection Certificate (NOC), and it must be signed by an authorized signatory of the company and stamped from the end brand with the company's letterhead. + For **Letter of authorization: du (Local)**, if your company is local to United Arab Emirates, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/UnitedArabEmirates_SenderId_LetterOfAuthorization_DU.zip). This document is also referred to as a NOC, and it must be signed by an authorized signatory of the company and stamped from the end brand with the company's letterhead. + For **du Sender ID Registration Form**, if your company is local to United Arab Emirates, you are required to download, complete, and attach the [du Sender ID Registration Form](samples/UnitedArabEmirates_SenderId_DU_RegistrationForm.zip). This is a separate form required by the du network in addition to the letters of authorization. + For **Company's UAE establishment card**, if your company is local to United Arab Emirates, then you are required to provide a copy of your company's UAE establishment Card. + For **Authorized signatory UAE ID**, if your company is local to United Arab Emirates, then you are required to provide a valid United Arab Emirates ID of the authorized signatory who completed the letters of authorization. (Both UAE ID and UAE passport are required.) + For **Authorized signatory UAE passport**, if your company is local to United Arab Emirates, then you are required to provide a valid United Arab Emirates passport of the authorized signatory who completed the letters of authorization. (Both UAE ID and UAE passport are required.) + For **Authorized signatory power of attorney**, if your company is local to United Arab Emirates, and the authorized signatory who completed the telecom delegation letters is not listed by name on your company registration certificate, then you are required to provide a power of attorney document. + For **Letter of authorization: International (Etisalat)**, if your company is not local to United Arab Emirates, then you are required to download, complete, and attach the [Etisalat network letter of authorization (LOA)](samples/UnitedArabEmirates_SenderId_LetterOfAuthorization_International_Etisalat.zip). Both Etisalat and du network LOAs are required for international registrations. + For **Letter of authorization: International (du)**, if your company is not local to United Arab Emirates, then you are required to download, complete, and attach the [du network letter of authorization (LOA)](samples/UnitedArabEmirates_SenderId_LetterOfAuthorization_International_DU.zip). Both Etisalat and du network LOAs are required for international registrations. + For **UAE Ministry of Health and Prevention authorization**, if your company is local to the United Arab Emirates and is a hospital, then you are required to provide an authorization letter from UAE Ministry of Health and Prevention. + For **Acknowledgement of transactional content**, promotional content is disallowed for United Arab Emirates sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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 sender ID registration process in AWS End User Messaging SMS United Kingdom sender ID registration **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). The United Kingdom's (UK) Mobile Ecosystem Forum (MEF) SMS Sender ID Protection Registry was established to facilitate the identification and blocking of fraudulent SMS messages, protecting consumers as well as legitimate businesses and organizations. The registry enables organizations to register the Sender IDs used when sending SMS to customers in the UK, limiting the ability of fraudsters to impersonate a brand. If you have protected your Sender ID with MEF you are required to register your Sender ID through AWS End User Messaging SMS. **Important** If your Sender ID is protected by MEF then a completed Letter of Authorization (LOA) is required. The information provided must be of the end company. If you are registering on behalf of a company they are required to authorize AWS and the LOA should not include or reference your company information. Download the template for the [LOA](samples/AWS_Protected_Sender_ID_Letter-of-Authorisation_UK.zip). Clearly specify the sender ID requested and have other details such as website and sample message templates filled in correctly with no missing details. The casing of the Sender ID must match what is registered with MEF. Complete all highlighted fields. The LOA must be dated within the last 30 days. Create a PDF of the LOA to upload as part of completing the **Sender ID info** section of your [UK registration](registrations-uk-form.md#registrations-uk-form.title). The maximum file size is 400 KB. Complete the [UK sender ID registration form](registrations-uk-form.md#registrations-uk-form.title) and omit the **Letter of authorization image – optional** field. **Topics** + [United Kingdom registration form](registrations-uk-form.md) # United Kingdom sender ID registration form United Kingdom registration form Complete the following form to register your sender ID in the United Kingdom. If your sender ID is protected by then a completed [Letter of Authorization (LOA)](registrations-uk.md) is required as well. **Complete a United Kingdom sender ID 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 United Kingdom sender ID registration to complete. 1. In the **Company info** section, enter the following: + For **Company Name**, enter the name of your company. + For **Tax ID or Business Registration Number**, enter you tax ID. + 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. + 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 **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Letter of authorization image – optional**: Information provided must be that of the end company. If you are registering on behalf of a company they are required to authorize AWS and the LOA should not include or reference your company information. + Download the template for the [LOA](samples/AWS_Protected_Sender_ID_Letter-of-Authorisation_UK.zip). + Clearly specify the sender ID requested and have other details such as website and sample message templates filled in correctly with no missing details. The casing of the Sender ID must match what is registered with MEF. Complete all highlighted fields. + The LOA must be dated within the last 30 days. + Create a PDF of the LOA to upload as part of completing the **Sender ID info** section for your UK registration. The maximum file size is 400 KB. + For **Sender ID connection – optional** you can add more details about the connection between the requested sender ID and company name. 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. + **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**. 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**. # Vietnam sender ID registration in AWS End User Messaging SMS Vietnam sender ID registration Follow these directions to register your sender ID in Vietnam. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. Choose **Next**. 1. In the **Vietnam specific info** section, enter the following: + For **Letter of authorization: Local**, if your company is local to Vietnam, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Vietnam_SenderId_LetterOfAuthorization_Local.zip), also called a BM02 form. **This document must be on company letterhead, stamped, and signed with company seal on all pages**. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Letter of authorization: International**, if your company is not local to Vietnam, then you are required to download, complete, and attach the [letter of authorization (LOA)](samples/Vietnam_SenderId_LetterOfAuthorization_International.zip), also called a BM04 form. **This document must be on company letterhead, stamped, and signed with company seal on all pages**. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Company registration documentation**, you are required to provide a copy of your company's registration documentation, regardless if your company is local to Vietnam or international. This document is also known as a business license. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Financial sector business license (SSC)**, if your company operates in the financial sector, you must submit a business license issued by the State Securities Commission (SSC) in addition to the standard business license and BM02/BM04 form. This is a mandatory requirement from Vietnamese operators for all financial sector registrations. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Proof of sender ID connection**, you are required to provide evidence of your intellectual property rights to the sender ID you wish to register. The document you provide should demonstrate the connection between your company name and this sender ID. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Vietnam sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 Choose **Next**. 1. All messages must include your brand/service name. If your company operates locally in Vietnam, all provided message samples must have an English and Vietnamese version, and all provided message samples must include a URL to your business website. Message samples must be provided in template format, and must be an exact match to what you intend to send. If there are variables in the template, ensure that you define them correctly. Define if the variable is text/number only or alphanumeric; if there's any special characters, or URL. Define variable length In **Message samples**, do the following: + For **Message Sample 1**, enter at least one sample is required of an SMS message which will be sent from this sender ID. + 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. 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**. # Zambia sender ID registration in AWS End User Messaging SMS Zambia sender ID registration Follow these directions to register your sender ID in Zambia. 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**. **Note** If you already created a registration when requesting the origination identity then you should use that registration form. For **Registration form name** enter a friendly name. Choose **Next**. 1. In the **Sender ID info** section, enter the following: + For **Sender ID**, enter the sender ID to request. The sender ID must be between 3 and 11 alphanumeric characters. For more information on sender ID formatting rules, see [Considerations for a sender ID](sender-id.md#sender-id-considerations) + For **Sender ID description – optional** you can add more details about the connection between the requested sender ID and company name. + For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. Choose **Next**. 1. In the **Zambia specific info** section, enter the following: + For **Company registration documentation**, you are required to provide a copy of your company's registration documentation. This document is also known as a Certificate of Incorporation (COI). Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB. + For **Acknowledgement of transactional content**, promotional content is disallowed for Zambia sender IDs. Choose **Yes** to acknowledge that this sender ID will only be used for sending transactional messages. 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 your tax ID, like EIN or VAT. + For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company. + For **Company website**, enter the URL for your company's website. Choose **Next**. 1. In the **Company address** section, enter the following: + 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 **Postal code**, enter the Postal/Zip code of your corporate headquarters. + For **Country**, enter the two digit ISO country code. Choose **Next**. 1. In the **Contact info** section, enter the following: + For **Contact Email**, enter the email address of the person who will be your business's point of contact. + For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact. Choose **Next**. 1. In **Messaging Use Case**, do the following: + For **Use case category**, choose one of the following use case types: + **One-time passwords** – Use this for sending a user a one time password. + **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications. + **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue. + **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. + **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 description** to provide additional context to the selected **Use case category**. + For **Monthly SMS Volume**, choose the number of SMS messages that will be each month. + For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. Your **Opt-in workflow description** 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 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. 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**. # 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**.