# Registration forms
<a name="registrations-country"></a>

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
<a name="registrations-australia"></a>

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
<a name="registrations-belarus"></a>

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
<a name="phone-numbers-sms-template-registration"></a>

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
<a name="registrations-egypt"></a>

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
<a name="registrations-finland"></a>

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
<a name="registrations-sms-senderid-india"></a>

There are two ways to send SMS messages to recipients in India: *international routes* and *local routes*.

# Understanding international and local routes for India
<a name="registrations-sms-senderid-india-routes"></a>

**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
<a name="registrations-sms-senderid-india-register"></a>

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
<a name="registrations-sms-senderid-india-support"></a>

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
<a name="registrations-sms-senderid-india-console"></a>

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
<a name="registrations-sms-senderid-india-support-case"></a>

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
<a name="registrations-sms-senderid-india-specify-ids"></a>

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
<a name="registrations-sms-senderid-india-template-issues"></a>

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
<a name="registrations-indonesia"></a>

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
<a name="registrations-ireland"></a>

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
<a name="registrations-jordan"></a>

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
<a name="registrations-kazakhstan"></a>

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
<a name="registrations-kenya"></a>

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
<a name="registrations-kuwait"></a>

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
<a name="registrations-philippines"></a>

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
<a name="registrations-qatar"></a>

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
<a name="registrations-russia"></a>

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
<a name="registrations-saudi-arabia"></a>

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
<a name="registrations-sg"></a>

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)
<a name="registrations-sg-uen"></a>

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
<a name="registrations-sg-form"></a>

**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)
<a name="registrations-sg-sgnic"></a>

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
<a name="registrations-sg-faq"></a>

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
<a name="registrations-sg-faq1"></a>

**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?
<a name="registrations-sg-faq9"></a>

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 name="registrations-sg-faq2"></a>

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?
<a name="registrations-sg-faq7"></a>

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?
<a name="registrations-sg-faq3"></a>

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?
<a name="registrations-sg-faq4"></a>

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?
<a name="registrations-sg-faq5"></a>

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?
<a name="registrations-sg-faq6"></a>

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?
<a name="registrations-sg-faq8"></a>

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?
<a name="registrations-sg-faq10"></a>

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
<a name="registrations-sri-lanka"></a>

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
<a name="registrations-thailand"></a>

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
<a name="registrations-turkey"></a>

**URL content restrictions effective April 1, 2026**  
Starting April 1, 2026, SMS messages to Turkey mobile numbers that contain URLs are at risk of being blocked or having the URL masked (for example, replaced with \$1\$1\$1\$1\$1\$1\$1). To ensure reliable delivery, remove all URLs from your SMS message content.

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
<a name="registrations-united-arab-emirates"></a>

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
<a name="registrations-uk"></a>

**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
<a name="registrations-uk-form"></a>

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
<a name="registrations-vietnam"></a>

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
<a name="registrations-zambia"></a>

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**.