Issue with Required Chain IDs for SMS Sending in India

There are a couple problems with the documentation:

1. ROUTE LEDGER TECHNOLOGIES PRIVATE LIMITED doesn't accept PE-TM binding chain requests, their support team asked me to send the request to Telemarketer (TM) Name: SEND CLEAN PRIVATE LIMITED (1202168836913126411).
2. Infobip does not approve the PE-TM binding request, unless we have a separate contract with Infobip.
3. The registration form will not allow entering empty values or 'NA' in the form, so the above suggestion doesn't work.
4. Without any help from AWS support team, it looks like I simply cannot configure AWS End User SMS messaging for India.

When configuring AWS End User Messaging SMS for sending messages to India using registered sender IDs, you are indeed required to provide certain information related to Chain IDs. However, not all Chain ID fields are mandatory for every user. The requirements depend on your specific setup and the telemarketers you are working with.

Here's what you need to know:

1. Not all Chain IDs are mandatory. You only need to provide the Chain IDs for the telemarketers you are actually using.

2. For the Chain ID fields that are not applicable to your setup, you should not leave them empty. Instead, you can enter "NA" (without quotes) or a similar placeholder value to indicate that this particular Chain ID is not applicable to your configuration.

3. The key fields you must provide are:

   • Chain ID: Principal Entity ID (PEID) - This is the PEID you received after completing the registration process with the Telecom Regulatory Authority of India (TRAI).
   • The approved Chain ID(s) for the telemarketer(s) you are using, which you can find on your DLT platform after creating a chain of telemarketers.

4. You must also acknowledge that you will specify the Entity ID and Template ID values when sending messages to India.

It's important to note that these requirements are in place to comply with TRAI regulations, which aim to reduce unsolicited messages and protect consumers in India.

If you're still encountering issues after providing the necessary information and using placeholders for non-applicable fields, it would be advisable to contact AWS Support for further assistance. They can provide more specific guidance based on your account and configuration.

Remember, when sending messages to India, you'll need to include the Entity ID and Template ID in your API calls or campaign setups. These IDs must match exactly with what you've registered with TRAI to avoid message rejection by mobile carriers.

Sources
India sender ID registration in AWS End User Messaging SMS - AWS End User Messaging SMS
India sender ID registration process in AWS End User Messaging SMS - AWS End User Messaging SMS
Specify the Entity ID and Template ID values to send messages to India - AWS End User Messaging SMS

Hi, Is there a solution to this issue. The two TM are not approving the request and the form for regsitartion cannot be submitted with out all 4 entries.