To register a DLT template, sign in to your operator's DLT portal as a registered principal entity and pick the template category: transactional, service implicit, service explicit or promotional. Link the template to one approved header, then type the fixed text exactly as it will be sent, marking each changing part with a variable placeholder such as {#var#}. Since TRAI's November 2025 direction, every variable must also be pre-tagged by type, for example as a URL or a callback number. Once the template is approved, every SMS you send must match it, or the operator drops it.
This guide covers the template step in detail. For the full DLT process (entity, header and telemarketer binding) and how it compares with the US 10DLC system, read our 10DLC vs DLT compliance guide.
What a DLT template is
DLT (distributed ledger technology) is the blockchain-based registry that Indian operators use under TRAI's commercial communication rules (TCCCPR 2018). It records who is sending (the principal entity), under which sender ID (the header), and what they are allowed to say (the content template). When a message is submitted, the operator "scrubs" it against these records. If the header, template, category or telemarketer chain does not match, the message is not delivered.
The four template types
| Type | Use it for | Consent and DND | Example |
|---|---|---|---|
| Transactional | OTPs and alerts from banks and financial institutions that complete a transaction the customer started | Delivered to all numbers, including DND | {#var#} is the OTP for your card transaction of INR {#var#}. Do not share it. |
| Service implicit | Messages a customer expects from an existing relationship: OTPs for non-banks, order and delivery updates, booking confirmations | No separate consent needed; delivered to DND numbers | Your order {#var#} has shipped and will arrive by {#var#}. |
| Service explicit | Service messages that need the customer's recorded consent, such as renewal or upgrade offers to existing customers | Needs consent on DLT; time-window limits apply | Your plan {#var#} renews on {#var#}. Reply YES to add the upgrade. |
| Promotional | Offers, sales and marketing to anyone | Blocked for DND numbers; sent only in the permitted daytime window | Weekend sale: up to {#var#}% off. Shop now: {#url#} |
Some providers report that the service explicit category is being merged into promotional, so check your DLT portal's current options before you plan new templates around it. Since 6 May 2025, operators also add a suffix to the header the customer sees: -P for promotional, -S for service, -T for transactional and -G for government. The suffix is added automatically from your template category, so choosing the wrong category now also shows the customer the wrong label.
Format rules that decide approval
- Fixed text must match exactly. Spaces, punctuation and capital letters in the fixed part are compared character by character. Adding a word, or changing "Rs." to "INR", breaks the match.
- Use variables only for data that changes. Names, amounts, dates and order numbers are variables. The brand name and the core message are not. A template made mostly of variables is usually rejected, because it could carry any content.
- Keep each variable short. DLT portals cap the length of the value in each placeholder. Do not use a single variable to carry a whole sentence.
- Pre-tag every variable. TRAI's direction of 18 November 2025 requires each variable to be tagged at registration with its purpose, such as a URL ({#url#}), an app download link or a callback number. Existing templates had 60 days to be modified, and messages on untagged templates are rejected.
- Whitelist links and numbers. Since September 2024, SMS carrying URLs, APK links, OTT links or callback numbers that are not whitelisted on DLT are not permitted. For links with a fixed and a variable part, the fixed part must be whitelisted.
- One template, one header. TRAI's August 2024 direction says a content template must not be linked to more than one header. Register a separate template for each sender ID.
Why templates get rejected or blocked
- Wrong category. An offer registered as service implicit is the most common reason. It is also the costliest, because under the August 2024 direction, five templates blacklisted for the wrong category can lead to a one-month suspension of the sender, or longer until all its templates are reverified.
- Header and template mismatch. For example, a bank header with an e-commerce template, or a template linked to a header from a different entity.
- Vague content. Templates such as "{#var#} {#var#} {#var#}" or "Dear customer, {#var#}" give the scrubber nothing to check.
- Links and numbers that are not whitelisted or tagged. The template may be approved, but the message fails at sending time.
- A broken telemarketer chain. From November 2024, messages whose telemarketer chain is undefined or mismatched are rejected. Bind your entity to your SMS provider's telemarketer ID.
A short approval checklist
- Write the message as it will actually be sent, then mark only the changing parts as variables.
- Choose the category by purpose, not by what is easier to get approved.
- Tag every variable by type, and whitelist every domain and callback number.
- Name your templates clearly (for example, "ORDER_SHIPPED_v2") and record each template ID in your sending system.
- Test each template with real values before a campaign, and watch the delivery reports for scrubbing failures.
- Review your templates every quarter and retire the ones you no longer use.
If OTPs are your main SMS traffic, it is also worth reading WhatsApp vs SMS for OTP to plan a second channel. If you plan to sell SMS to your own clients, see how to start a bulk SMS business.
How Voxvalley helps
The Voxvalley Messaging API sends India traffic on DLT-registered routes, with per-message delivery reports that show where a message failed, including scrubbing rejections. The same API carries WhatsApp and RCS, and reaches 180 countries, including 10DLC-compliant throughput in the US. Our team can help you choose the right template categories and set up the entity-to-telemarketer binding before you go live. Resellers can run the platform under their own brand through our bulk SMS reseller programme. To get started, write to sales@voxvalley.com.