Register your company and use case with the TRAI and create the required Telemarketer chains - AWS End User Messaging SMS
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

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/

    Note

    If you are creating an account choose Enterprise as the entity type.

  2. 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
    Telemarketer Name Telemarketer ID (TM ID)
    ROUTE LEDGER TECHNOLOGIES PRIVATE LIMITED 1002786139254391
    Karix Mobile Pvt Ltd 110200001000
    Sinch Cloud Communication Services India Private Limited 1102502720000073897
    Infobip India Private Limited 110200001152
    Note

    To complete your India sender ID registration in AWS End User Messaging SMS, only the Karix Mobile Pvt Ltd and Sinch Cloud Communication Services India Private Limited chain approvals are required. We recommend submitting chain requests for all telemarketers listed above, but you can proceed with your AWS End User Messaging SMS registration while awaiting approval from the remaining telemarketers.

    To create a chain of TMs:

    1. Navigate to the Chain section of your DLT platform. Some DLT providers call this SMS Workflow.

    2. Choose the option to create a new Chain.

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

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

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

    Tip

    DLT platforms typically return template IDs before chain approval is complete. You can use these template IDs to begin your AWS End User Messaging SMS registration in parallel while your chain requests are being processed.

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.