Any entity wanting to send SMS in India must register its organization, headers, and templates, along with the required consumer consent, on the Distributed Ledger Technology (DLT) platform. Please note that only Indian entities (those registered locally in India) are eligible to register on the DLT platform. This rule, mandated by the Telecom Regulatory Authority of India (TRAI), aims to curb unsolicited commercial communication (UCC). Follow these steps to comply with TRAI requirements and ensure your messaging traffic flows smoothly.
Step 1 — Get unique Entity ID
Register on any of the DLT platforms below by filling in the required information to get a temporary ID. After verification of your documents, the operator will provide you with a unique Entity ID.
- Videocon (https://smartping.live/entity/register-with)
- Vodafone Idea Limited (https://www.vilpower.in)
- Airtel (https://dltconnect.airtel.in/signup/)
- Jio (https://trueconnect.jio.com/#/)
Note:
- Our customer feedback reports that Jio’s registration process is shorter and easier than other vendors.
- Please share your reference number/temporary ID/unique Entity ID and registered entity name with us once you have registered on any DLT platform.
- Note that you will need to work with your DLT vendor to whitelist your CTAs — more on this below.
Step 2 — Register headers
Once you get your unique Entity ID, register your headers in the DLT platforms.
- Navigate to the Headers tab in your dashboard. Please refer to the attached guide for the header registration process.
- There are two types of headers to choose from: promotional and other.
- Promotional campaigns, such as offers, discounts, and marketing messages, need a six-digit numeric sender ID, which will be prefixed with your industry code.
- Other campaigns, such as transactional updates or notifications, allow you to choose your preferred header name. Add your preferred header name in the text box and describe your reason for choosing it.
Your header name should match your entity name. If you choose a different header name, please justify the discrepancy and include your mobile number in the description box so the DLT support team can contact you with questions.
Note:
- Only entities with registered headers can send SMS messages. Please contact us once your headers have been approved.
- Headers (sender names) are case-sensitive, so ABCDEF and abcdef, for example, are two different sender names and can be registered separately.
Step 3 — Whitelist your CTAs
Any calls-to-action (CTAs) that you plan to use in your messages must be whitelisted on the DLT platform. Whitelisting these links ensures that your messages are successfully delivered. The following types of CTAs must be approved by your DLT platform provider.
-
URLs
- Any link/URL used in an SMS.
- WhatsApp links
- APK links
-
Numbers used for calls or messages
- Mobile
- Landline
- Toll-free
- Email addresses
For instance, if you include a link for users to sign up for an account, that URL must be whitelisted. Likewise, if your messages contain a callback number or an email address, those must also be whitelisted.
Whitelisting Requirements at a Glance
CTA Type | CTA | Sample CTA (if required) | Subtype | Details |
URL | https://abc.com/ | N/A | Static URL | Only exact matches will be allowed |
URL + Variable | https://abc.com/xyz? | https://abc.com/xyz?product=1 | Dynamic URL | You need to whitelist only the static part of the URL. For example, if you have two URLs, such as https://abc.com/lmn and https://abc.com/pqr, you only need to whitelist the static part of the URL, which is https://abc.com/ |
Number | 91XXXXXXXXX 022XXXXXXXX 1800/1860XXXXXX |
919414XXXXXX 02267676XXX 1800180XXXX |
Mobile / Landline / TFN | Only exact matches will be allowed |
support@abc.com | N/A | Only exact matches will be allowed | ||
URL Shortening | Currently not supported |
Note that if a value is not whitelisted under your brand, it will not be permitted in your message content, and your messages will fail to be delivered.
Step 4 — Register consent templates
After you've registered your business and headers (sender IDs), the next step in the DLT registration process is to add consent templates.
Consent templates and registering guidelines
A consent template is a standard message that's sent to users to get their consent to receive communications from enterprises.
- Template Name: Choose whatever you like
- Brand Name: A product or trade name
-
Scope of Consent: Description of the content you plan to send to users. Examples:
- We would like to send communication regarding marketing offers and events to our registered customers.
- ABC Solutions needs your consent to send messages about your account information, activity, and our best offers.
- We will send our registered customers updates, transactions, and recommendations of our services and products.
Dos for consent templates
- Choose a relevant short name to the template to help you choose the right consent templates when you associate them with content templates in promotional or service categories.
- Brand name should be relevant to details mentioned in scope of content.
- The scope of content and your intent should be clear and relevant to the mentioned brand.
- If you want to offer opt-out information, include complete information. Example: “To opt out, send STOP to 5555555”
Don’ts for consent templates
- Don't use generic names for templates, such as "template1."
- Don't mention invalid or irrelevant names or popular brand names. Operators will treat these as invalid templates.
- Don't enter an actual message sent to the customer.
- Don't enter short messages like "consent" or "SMS to customers."
- Don't use variables in the scope of consent, as variables are applicable only to content templates.
After filling in the details in the three fields you can submit the template for approval. There is no limitation on the number of consent templates you can create.
After consent templates are approved by the registrar, you can link them to content templates in promotional or service categories, as shown here:
How to register a consent template in a DLT portal
For Jio DLT platform:
- Select Template > Consent Registration.
- Add a template name and your brand name.
- Add Template Consent, which is the standard message that is added to your T&C or any other document informing them about their consent to receive communications from respective enterprise.
- After adding your consent template, add a list of consented customers.
- For adding phone numbers, select Customers’ Consent > Bulk Upload.
Content templates and registration guidelines
After you've registered consent templates, the next step in the DLT registration process is to add content templates.
How to add content templates
There are four types of content templates: transaction, service implicit, service explicit, and promotional.
Transactional
Any message that contains a one-time password (OTP) required to complete a banking or credit or debit card transaction initiated by a bank customer is considered transactional. Here are some examples of this type of content, along with examples of the template formats that would create them.
Actual Message |
Template Format |
234567 is the OTP for txn of inr 57.75 at Izaak payment services PVT with your sbi card xx3931. OTP is valid for 10 mins. pls do not share with anyone |
{#var#} is the OTP for txn of inr {#var#} at {#var#} with your sbi card{#var#}. OTP is valid for {#var#}. pls do not share with anyone |
234567 is your OTP for fund transfer for the amount Rs.6,000 to Raja. OTP valid for 8 minutes. Do not share this OTP with anyone. |
{#var#} is your OTP for fund transfer for the amount {#var#} to {#var#}. OTP valid for 8 minutes. Do not share this OTP with anyone. |
234567 is OTP for your eComm Txn for the amount Rs.25,000 OTP valid for 8 minutes. Do not share this OTP with anyone. |
{#var#} is OTP for your eComm Txn for the amount {#var#} OTP valid for 8 minutes. Do not share this OTP with anyone |
Service-implicit
Any message arising out of customers' actions or their existing relationship with the enterprise, and that is not promotional, is considered a service-implicit message. These include:
- Confirmation messages of net banking and credit/debit card transactions
- Product purchase confirmation and delivery status from ecommerce websites
- Customer is making payments through a payment wallet for an ecommerce website or mobile app, and an OTP is sent to complete the transaction
- OTPs required for ecommerce websites, app logins, social media apps, authentication and verification links, securities trading, demat account operations, KYC, and ewallet registration
- Messages from TSP/ISP
- Periodic balance info, bill generation, bill dispatch, due date reminders, recharge confirmation (DTH, cable, prepaid electricity recharge, etc.)
- Delivery notifications, updates, and periodic upgrades
- Messages from retail stores related to invoices and warranties
- Messages from schools, such as attendance and transport alerts
- Messages from hospitals, clinics, pharmacies, radiologists, and pathologists about registration, appointments, discharge, and reports
- Confirmatory messages from app-based services
- Government/DOT/TRAI mandated messages
- Service updates from car workshops, repair shops, and gadgets service centers
- Directory services such as Justdial and Yellow Pages
-
Day-end and month-end settlement alerts to securities and demat account holders
Actual Message |
Template Format |
Thank you for using EMI Facility on your XXXX Bank Credit Card 4***1234 EMI request for Rs. 89000.00 executed on 01/07/2019 |
Thank you for using EMI Facility on your IDBI Bank Credit Card {#var#} EMI request for {#var#} executed on {#var#} |
XXX BANK - Your new bill for BESCOM Bangalore - account 0123456000 for Rs 4339.00 could not get scheduled because the auto-pay limit is less than the bill amount. |
XXX BANK - Your new bill for {#var#} - account {#var#} for Rs {#var#} could not get scheduled because the auto-pay limit is less than the bill amount. |
Account: 123456 is your Pansoi account verification code. |
Account: {#var#} is your Pansoi account verification code |
Service-explicit
Service-explicit messages require explicit consent from customers that has been verified directly from the recipient in a robust and verifiable manner and recorded by the consent registrar. This category includes any service messages that don’t fall under the service-implicit category.
Customer consent templates must be linked to content templates in the service-explicit category.
Examples include messages to the existing customers recommending or promoting products or services.
Actual Message |
Template Format |
Your Rs.500 exclusive voucher is ready. Redeem it on purchase of Rs.1,000 at M&M. Use code 654321001. Valid till 31 Mar 2021! T&C. |
Your Rs.{#var#} exclusive voucher is ready. Redeem it on purchase of Rs.{#var#} at M&M. Use code {#var#}. Valid till {#var#}! T&C. |
To best serve you and others, please click on mosl.co/ywq8FBJpAn to share your meeting experience with your Ojas Insurance representative |
To best serve you and others, please click on {#var#} to share your meeting experience with {#var#} |
Baba Finserv personal loans need minimal documentation. Meet your financial needs in one click: http://m.BabajFin.in/Iphr8tFE |
Baba Finserv personal loans need minimal documentation. Meet your financial needs in one click: {#var#}. |
Promotional
These are any messages with an intention to promote or sell products, goods, or services. Service content mixed with promotional content is treated as promotional. These messages are sent to customers after performing the preference and consent scrubbing function.
Customer consent templates must be linked to content templates in the promotional category.
Examples:
Actual Message |
Template Format |
Lifetime free bank credit card with vouchers from LensKart, Pepperfry, Grabon worth Rs.3000. SMS “apply” to 5676766. TnC apply |
Lifetime free bank credit card with vouchers from LensKart, Pepperfry, Grabon worth Rs.{#var#}. SMS “{#var#}” to 5676766. TnC apply |
Pay just Rs 640* pm & get Rs 83,333 for 120 months or payout of Rs 1,00,00,000 with LIC (Life Insurance Cover) for your family. http://px2.in/pAD4Tls |
Pay just Rs {#var#} pm & get Rs {#var#} for {#var#} months or payout of Rs {#var#} with LIC (Life Insurance Cover) for your family. {#var#} |
You can win Rs 20,000 in fantasy cricket! Use code 542321. Install Badger app now to win. Click https://abc.com |
You can win Rs {#var#} in fantasy cricket! Use code {#var#}. Install Badger app now to win. Click {#var#} |
Content template validation
- Use of two or more spaces before, after, or between words is not advisable.
- All special characters are allowed.
- The variable format in text is {#var#}, which is case-sensitive. You can also insert a variable by clicking the insert variable radio button.
- Transactional and service content should always have some variable content.
- Promotional content can have completely fixed content or some variable content.
- There is no limitation on the number of variables per message.
- Values such as a dates, amounts, account numbers, names, and OTPs must be inserted using variables.
Dos for content templates
- Use the promotional category for communications intended to be sent only from numerical sender IDs.
- Only banking enterprises should use the transactional category for OTP messages during fund transfers, online payments, and merchant transactions.
- Choose relevant and recognizable names for content templates.
- Use the message type as “TEXT” for all general messages and “Unicode” for regional messages.
- Use variable {#var#} insertion for values such as a dates, amounts, account numbers, names, and OTPs.
Don’ts for content templates
- Don't use the same content template with multiple headers.
- Don't make header selections against irrelevant templates.
- Don't selecting the transactional content types for nonbanking enterprises.
- Don't use double spaces in templates. Check for this using a tool like Notepad++ before template submission.
- Don't use templates with fewer than six characters or with only variable insertion.
How to register a content template in a DLT portal
For Jio DLT platform
- Select Template > Content Template Registration
- Choose template type as SMS
- Choose your content type — English or other languages
- Select a Category from the drop-down list
- Select Consent ID from the drop-down list
- Choose a type of communication — Promotional / Transactional / Service-Inferred / Service-Explicit
- Select Header from the drop-down list
- Add the template content in the "template content" text box and click Submit.