A step-by-step guide to registering SMS templates on DLT and getting them approved the first time.
In India, every commercial SMS has to match a template registered on the DLT platform under TRAI's rules. If the message doesn't match, it isn't delivered.
This guide walks through registering a template from start to finish. If you haven't registered your business yet, start with what DLT registration is and the documents required. If a template has already been rejected, go to our DLT template rejection guide.
Templates sit at the end of the DLT chain. You need these in place first:
| Step | What it is | Where to learn more |
|---|---|---|
| Entity registration | Your business registered as a Principal Entity on an operator DLT portal | Documents required, registration cost |
| Sender header | The approved sender ID that appears on the SMS, which reflects your brand | DLT registration support |
| Telemarketer link | Your SMS provider linked to your entity, so messages can be sent through them | PE-TM binding |
| Consent template (if needed) | Required for service explicit messages, recording how the customer agreed to receive them | See categories below |
Choose by what the message does, not by which route you would like it to use. A wrong category is one of the most common reasons a template is rejected.
| Category | Use it for | Example |
|---|---|---|
| Promotional | Offers, sales and marketing messages | "Flat 20% off at {#var#} this weekend. Visit {#var#}" |
| Transactional | OTPs and similar account-security messages | "{#var#} is your login OTP for MediPlus" |
| Service implicit | Updates a customer expects from an existing relationship | "Your order {#var#} from Sharma Electronics has been shipped" |
| Service explicit | Messages that need the customer's recorded consent | Product updates to customers who opted in |
More worked examples by use case are on our DLT SMS template examples page. For OTP-specific rules, see the OTP SMS DLT guide.
Portal screens differ slightly between operators, but the information asked for is the same.
Variables are where most templates go wrong. Follow these rules:
| Template | Result | Why |
|---|---|---|
| "Dear {#var#}, your fee of Rs {#var#} is due on {#var#}. - ABC School" | Likely approved | Clear purpose, brand named, variables only for changing values |
| "Your order {#var#} has been shipped and will arrive by {#var#}" | Likely rejected | No brand or business name in the fixed text |
| "Hi {#var#}" | Likely rejected | Almost entirely variable; the purpose is unclear |
Before you submit, check each template against this list:
Approval time varies by operator portal. If a template is rejected, the portal usually shows a reason; our rejection guide explains twelve common reasons and how to fix each one.
It is the process of registering the exact wording of each commercial SMS on a telecom operator's DLT portal before you send it. Each approved template gets a template ID, and every SMS must be sent with the ID of the template it matches.
Yes. Each distinct message needs its own approved template. Changing values such as names, amounts or dates can use {#var#} variables inside one template, but a change to the fixed wording needs a new or updated template.
Use {#var#} exactly, with the curly braces and hash symbols, for each value that changes. Keep each variable's value within 30 characters, and keep the fixed text exactly as it will appear in the sent message.
Choose by what the message does. Promotional is for offers and marketing. Transactional is for OTPs and similar account messages. Service implicit is for updates a customer expects from an existing relationship, such as order or payment alerts. Service explicit is for messages that need the customer's recorded consent.
Most operator DLT portals do not charge a separate fee per content template; the main fee is for entity registration. MetaReach helps with template registration at no extra charge for its SMS customers.
Common reasons include the wrong category, a missing brand name, badly formatted variables, unregistered links or headers, and wording that does not match what will be sent. Our DLT template rejection guide covers twelve common reasons and how to fix each one.
Send us the messages you want to register. We'll suggest the right category and wording, and help you submit them, at no extra charge for MetaReach SMS customers.
This guide is general information based on TRAI's commercial communication rules and operator DLT portal requirements as of October 2026. Portal steps and rules can change; check your operator's DLT portal for current requirements.
From startups to enterprises — brands that grow with MetaReach
