Problem description

For sending promotional or transactional messages in India, companies are required to go through a DLT registration. Every message being sent to Indian customers must contain two additional parameters: Content Template ID and Principal Entity ID, that are passed across the SMS providers.

Impact of not implementing

Not supporting the DLT-related attributes is impacting our clients' ability to use the built-in SMS features, but also on the cost of unrealized Microsoft revenue, as well as Infobip as SMS provider.

Implementation

The solution requires the two fields Content Template ID and Principal Entity ID to be added on UI to the message editor. They could also be included in the setup, but it's very likely several different templates will need to be used to create various journeys and/or messages.

The Infobip SMS payload then needs the "regional" section with the two attributes inside the "content" attribute:

"regional":

{

"contentTemplateId": "your ID",

"principalEntityId": "your ID",

}

Detailed info:

www.infobip.com/docs/essentials/asia-registration/dlt-templates