Compliance

DLT templates: what to write and what gets rejected

5 min read

In India, every commercial SMS is sent against a template registered on the DLT platform. The template fixes the wording; variables mark the parts that change from message to message. If the text you send does not match an approved template, the message can be blocked, however correct the rest of your setup is.

Why templates exist

TRAI introduced the DLT system so that operators can verify who is sending a message and what it says before it reaches a customer. Registering a template gives the operator a record to compare each message against. This is how unregistered or altered messages, including many scam texts, are filtered out. For a legitimate business it means the approved wording is part of your delivery infrastructure, not a formality.

Parts of a template

  • Fixed text, which must match exactly what is sent
  • Variables for the changing parts, such as a code, a name or an amount
  • A category: OTP or transactional, service, or promotional
  • A sender ID (header) it is linked to
  • A template ID, issued on approval, which your messages must reference

Writing a template step by step

  • List the exact message you want to send, with a real example
  • Replace each changing part with the variable placeholder, and leave everything else fixed
  • Choose the category by the purpose of the message, not by what is convenient
  • Remove anything promotional from a transactional message
  • Check the length with the longest realistic variable values
  • Submit one template per message type

Examples by category

These are illustrative formats only. Register your own wording and keep it consistent with your brand.

  • Transactional (OTP): “{#var#} is your OTP for {#var#}. It expires in {#var#} minutes. Do not share it with anyone.”
  • Service (reminder): “Reminder: your appointment is on {#var#} at {#var#}. Call {#var#} to reschedule.”
  • Promotional: “{#var#}, enjoy {#var#} off this weekend at {#var#}. Reply STOP to opt out.”

How matching works when you send

When you send through an API, the request carries the template ID and the values for each variable. The platform assembles the final text and the operator checks it against the registered template. If you edit the wording in your code without updating the template, or add a space or punctuation mark that is not in the registered text, the check can fail. Treat the registered text as the single source of truth and generate messages from it.

Common reasons for rejection

  • Promotional wording in a transactional template
  • Variables that are too open-ended, so the message could say anything
  • A link or phone number that is not allowed for that category
  • A sender ID that is not linked to your entity
  • Wording that closely imitates a bank, government body or well-known brand

If a template is rejected

Read the reason, change only what it points to, and re-submit. Resubmitting the same text unchanged wastes days. If the reason is unclear, ask your compliance contact before trying again, and look for the same issue in your other templates, because the same wording often appears in several.

Links and phone numbers

Links in messages are checked more closely than the rest of the text. Use a consistent domain that belongs to you rather than a public shortener, keep the link in a template of a category that allows it, and confirm the current rules for link registration before filing. Phone numbers follow similar caution.

Working as a team

Templates become a shared asset once several people send messages. Keep a single register listing each template ID, its exact text, category, owner and the systems that use it. Require that any change to wording goes through the owner and is filed on DLT before it is deployed. Without this, developers edit strings in code and marketing teams ask for “small tweaks”, and messages quietly stop matching their templates.

Planning seasonal and campaign templates

Promotional templates for festivals, sales and launches should be filed well before the campaign date. Prepare the copy, the variable list and the opt-out wording in advance, and reuse a well-approved structure where you can, changing only the variable values. A tested structure is more likely to be approved the first time than a new layout written in a hurry.

Good habits

  • Register one template per message type, not one general template
  • Keep promotional and transactional wording separate
  • Keep a copy of every approved template next to the code that sends it
  • Give each template an owner on your team, and review the list every quarter
  • Plan new campaigns early, because new templates take time to approve

Requirements change over time, so confirm current rules with your compliance contact before filing. For the full registration order, see our DLT registration process guide, and for naming rules see how sender IDs are approved. Our DLT registration service can prepare and file templates for you.

Related services