# India sender ID registration process in AWS End User Messaging SMS
There are two ways to send SMS messages to recipients in India: *international routes* and *local routes*.
# Understanding international and local routes for India
**International 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
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
After you register your company and use case with TRAI, you must create a case with Support. The Support team uses the information that you provide in your case to associate your Entity ID and Template ID with your AWS account.
**Note**
India allows transactional sender IDs to be 3–6 characters in length. Promotional sender IDs are required to be 6 characters. All sender ID approval is owned by TRAI.
You can register a sender ID for [transactional messages](#registrations-sms-senderid-india-support-case.title) using the AWS End User Messaging SMS console or to register a sender ID for [promotional messages](#registrations-sms-senderid-india-support.title) create an AWS Support case.
## India transactional message sender ID registration
Follow these directions to register your sender ID for transactional messages in India.
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Registrations**, choose **Create registration**.
**Note**
If you already created a registration when requesting the origination identity then you should use that registration form.
For **Registration form name** enter a friendly name.
Choose **Next**.
1. In the **Sender ID info** section, enter the following:
+ For **Sender ID**, enter the sender ID to request. India sender IDs must be 3-6 alphabetic characters.
+ For **Proof of sender ID connection – optional**, if the connection between your company name and this sender ID is not obvious, then you are required to provide evidence of your intellectual property rights to the brand. Valid upload file types are PDF, PNG, and JPEG with a maximum file size of 500KB.
Choose **Next**.
1. In the **India specific info** section, enter the following:
+ For **Chain ID: Principal Entity ID (PEID)**, enter the PEID that you received after completing the registration process with the Telecom Regulatory Authority of India (TRAI).
+ For **Chain ID: ROUTE LEDGER TECHNOLOGIES PRIVATE LIMITED**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers.
+ For **Chain ID: Karix Mobile Pvt Ltd**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers.
+ For **Chain ID: Sinch Cloud Communication Services India Private Limited**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers.
+ For **Chain ID: Infobip India Private Limited**, enter the approved chain ID seen on your DLT platform after creating a chain of telemarketers.
+ For **Acknowledgement of required sending parameters**, choose Yes to acknowledge you will specify the [Entity ID and Template ID values](registrations-sms-senderid-india-specify-ids.md#registrations-sms-senderid-india-specify-ids.title) when you send your messages to India.
Choose **Next**.
1. In the **Company info** section, enter the following:
+ For **Company Name**, enter the name of your company.
+ For **Company identification number**, enter your tax ID, like EIN or VAT.
+ For **Doing Business As (DBA)**, enter your DBA or brand name if different from the legal name of your company.
+ For **Company website**, enter the URL for your company's website.
Choose **Next**.
1. In the **Company address** section, enter the following:
+ For **Address 1**, enter the street address of your corporate headquarters.
+ For **Address 2 - optional**, if needed enter suite number of your corporate headquarters.
+ For **City**, enter the city of your corporate headquarters.
+ For **State/Province**, enter the state of your corporate headquarters.
+ For **Postal code**, enter the Postal/Zip code of your corporate headquarters.
+ For **Country**, enter the two digit ISO country code.
Choose **Next**.
1. In the **Contact info** section, enter the following:
+ For **Contact Email**, enter the email address of the person who will be your business's point of contact.
+ For **Contact Phone Number**, enter the phone number of the person who will be your business's point of contact.
Choose **Next**.
1. In **Messaging Use Case**, do the following:
+ For **Use case category**, choose one of the following use case types:
+ **One-time passwords** – Use this for sending a user a one time password.
+ **Purchase or delivery notifications** – Use this if you only intend to send your users important notifications.
+ **Public service announcements** – An informational message that is meant to raise the audience's awareness about an important issue.
+ **Polling and surveys** – Use this to poll users on their preferences.
+ **Info on demand** – This is for sending users messages after they have sent a request.
+ **Other** – Use this if your use case doesn't fall into any other category. Be sure that you fill out the **Use case details** for this option.
+ Complete **Use case description** to provide additional context to the selected **Use case category**.
+ For **Monthly SMS Volume**, choose the number of SMS messages that will be each month.
+ For **Opt-in workflow description**, enter a description of how users consent to receive messages. The description has to be between 40 – 500 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website.
Your **Opt-in workflow description** should include the following:
+ Program or product description
+ Identify your organization and service being represented in the initial message sent to your end users
+ Clear and thorough information about how your end-users opt-in to your SMS service and any associated fees or charges
Choose **Next**.
1. In **Message samples**, do the following:
+ For **Message Sample 1**, enter an example message of an SMS message body that will be sent to your end users.
+ For **Message Sample 2 – optional** and **Message Sample 3 – optional**, enter additional example messages, if needed, of the SMS message body that will be sent.
Choose **Next**.
1. On the **Review and submit** page verify the information you are about to submit is correct. To make updates choose **Edit** next to the section.
1. Choose **Submit registration**.
## India promotional message sender ID registration
Follow these directions to register your sender ID for promotional messages in India.
**Register sender ID for promotional messages**
1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).
1. In the **Create Case** section, do the following:
+ For **Limit type**, choose **AWS End User Messaging SMS (Pinpoint)**.
+ For **Provide a link to the site or app which will be sending SMS messages**, identify the website or application where your audience members opt in to receive your SMS messages.
+ For **What type of messages do you plan to send**, choose **Promotional**:
+ **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application.
+ **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements.
+ **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content.
+ For **Which countries do you plan to send messages to**, choose the AWS Region that you will be sending messages from.
1. In the **Requests** section, do the following:
+ For the **Region**, choose the AWS Region that you plan to make API requests from.
+ For **Resource Type**, choose **Template Registration**.
+ For **Limit**, choose on of the following:
+ **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application.
+ **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements.
+ **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content.
1. Under **Case description**, for **Use case description**, explain your use case and opt-in workflow.
1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**.
1. When you finish, choose **Submit**.
After we receive your request, we provide an initial response within 24 hours. We will send you a country-specific registration form for you to complete and provide back to us for downstream processing.
**Important**
In order to prevent our systems from being used to send unsolicited or malicious content, we consider each request carefully. We might not be able to grant your request if your use case doesn't align with our policies.
# Specify the Entity ID and Template ID values to send messages to India
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
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.