As a mandatory part of the DLT registration process, the content that you intend on pushing to your end customers in the form of SMSes now have to be registered.
Based on the type of content you are sending in the messages, they can be categorized into the following:
When registering your content template, there are a few "best practices" and good to know information to keep in mind:
DOs for Content Templates:
Use the promotional category for communications intended to send from numerical sender id only.
The transactional category is to be used by banking enterprises only & for OTP messages during fund transfer; online payment; merchant txn only.
Service – explicit category needs to link consent templates as well, without which the template gets rejected.
Choose a relevant/recognizable name for templates
Use message type as “TEXT” for all general messages & “Unicode” for regional messages.
Variable {#var#} insertion to be required against values like date; amount; a/c no; OTP; names; etc.
Always use notepad or notepad ++ to create template, to avoid additional spaces and invalid characters
Min fixed char required in templates is 10 char (applicable in pure OTP messages only)
Linking of consent templates for content template categories “promotional” & “service – explicit” is optional (not mandatory)
DON’T’s for Content Templates:
Same content template against multiple headers.
Header selection against irrelevant templates
Selecting the “Transactional” category by non-banking enterprises.
No or invalid variable format in templates.
Using double spaces in templates (this can be pre-checked by verifying the template on notepad++ before template submission)
Templates with less than 10 char or variable insertion alone as template using multiple templates (eg: Dear customer {#var#}{#var#}{#var#}.)
Do not use external fonts or characters other than those that appear on the keyboard, prise, like the example mentioned explaining the brand name field.