India sender ID registration process in AWS End User Messaging SMS
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 numeric ID (unless you purchase a dedicated short code).
Companies that are registered in India can also use dedicated sender IDs to send their messages. If you prefer to use a sender ID, you have to send those messages over local routes rather than ILDO routes.
Note
The price for sending messages using ILDO routes is much higher than the price for
sending messages through local routes. The prices for sending messages using both ILDO
and local routes are shown on the AWS End User Messaging Pricing
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:
Topics
