DLT variable pre-tagging: #numeric#, #url#, #cbn# and the rest

· BharatCaller team

For years a DLT content template could mark every changing part with the same placeholder, {#var#}, and put almost anything in it. That is how fraudsters slipped unregistered links and phone numbers into otherwise approved messages. Since TRAI's Direction of 18 November 2025, every variable must say what it holds, and messages that put the wrong thing in it are rejected.

The rule and its dates

TRAI's Direction of 18 November 2025 tells operators to make sure that each variable field in every SMS content template is pre-tagged with a label for its content type, purpose and validation rules. TRAI's press release the same day explains why: without tags, operators couldn't check whether a link, app link or callback number inserted into a template came from the sender's whitelist, and investigations showed the gap was routinely used for phishing.

The Direction set four clocks, all counted from 18 November 2025:

  • After 10 days (from about 28 November 2025): new templates are registered only if their variables are tagged.
  • Within 30 days (by about 18 December 2025): operators start checking tagged variables against senders' whitelisted URLs, OTT and APK links and callback numbers.
  • Within 60 days of that checking starting: existing templates must be modified to use tags.
  • For the first 60 days of checking, messages that fail are delivered in "logger mode" with fault messages. After that, any message failing variable-tag validation is rejected outright.

Each operator set its own switch-over dates within those limits, so if you see different dates quoted, that's why. An operator that started checking on the 30-day deadline would have finished its logger period around mid-February 2026.

This rule is older than it looks

TRAI first asked for it in 2023. The November 2025 Direction recites a Direction of 16 February 2023 limiting templates to two variables (a third only in exigency, with reasons recorded) and requiring variables to be non-contiguous, and one of 12 May 2023 requiring pre-tagging whenever more than three variables are allowed. The Second Amendment of 12 February 2025 wrote the pre-tagging condition into the regulations. TRAI said in November 2025 that the 2023 directions had not been implemented. The tag list itself came from the operators' association COAI on 5 September 2025, and all operators agreed to it on 17 September 2025.

The six tags

Annexure I of the Direction lists these tags and how operators validate them:

  • #number# or #numeric#: numeric values. Digits only; no letters or special characters.
  • #url#: a web link, for example "Track order: #url#". It must match a link you registered as a call-to-action (CTA), as a static, dynamic or short URL.
  • #urlott#: an app or OTT link, for example "Download app". It must match a CTA you registered under OTT or APK.
  • #cbn#: a callback number, for example "Call #cbn# for support". It must match a number you registered (mobile, landline or toll-free).
  • #email#: an email address, checked against a valid email pattern.
  • #alphanumeric#: mixed values such as ticket or booking IDs. Letters and numbers are allowed, length is checked, and scrubbing allows no more than 40 characters. The annexure's line on special characters is ambiguous, so keep these values to letters and digits where you can.

The list has no separate tag for names, dates or amounts. An amount such as "1,250.00" is not digits only, so it won't pass as #numeric#. Some portals may offer more tags than the official six, so check yours before you choose.

How the tags look on portals

The Direction writes tags as #url#. Portals vary in where you put them. MSG91, an SMS provider, says Airtel, Jio, Vi and BSNL take the tag inside the template, as {#numeric#}, while SmartPing and Tata tag variables in a separate section of the form. Follow your portal's own examples.

Before and after

An old-style template:

Your order {#var#} has shipped. Track: {#var#} Call {#var#} for help - BRAND

The same template, tagged:

Your BRAND order {#alphanumeric#} has shipped. Track it at {#url#}. For help, call {#cbn#}. - BRAND

Each variable now says what it holds, the variables are separated by fixed words, and the link and number will be checked against your whitelist. Register the tracking domain and the helpline number as CTAs before you send. Our guide to URL, APK and callback number whitelisting covers that step.

Mistakes that now get messages rejected

  • The wrong tag for a link. An app download link belongs in #urlott#, not #url#.
  • Formatting inside #numeric#. Spaces, plus signs, commas and hyphens aren't digits. Put phone numbers in #cbn#.
  • Long values. More than 40 characters in #alphanumeric# fails scrubbing, and the 2025 rules refer to a 30-character limit for a variable.
  • A correctly tagged but unregistered value. A new short-link domain or a new helpline number in an old template fails until you whitelist it.
  • Variables side by side. TRAI's 2023 rule says variables must not be contiguous or separated only by a space, comma or other special character.
  • Untagged legacy templates. Once your operator's logger period ended, a template still using {#var#} is at risk. Check its status on your portal.

How to fix a template

  1. List every template that still uses an untagged placeholder.
  2. For each variable, decide what it really carries and choose the matching tag.
  3. Whitelist every domain, app link and callback number the template will carry.
  4. Edit or re-register the template on your portal, keeping the brand name and fixed text.
  5. Send a test through your provider and check the delivery report before switching live traffic.

OTP templates need the same care: the code goes in #numeric#. We cover which category an OTP belongs in, under the 2026 definitions, in is your OTP SMS transactional or service.

Quick answers

Can I still use {#var#}?

Not under the Direction, which requires every variable field in every SMS content template to be pre-tagged.

Which tag do I use for a customer's name?

The official list has no name tag. If you don't need the name, leaving it out is simplest. If you do, ask your portal which tag it accepts.

Is callback number checking really on?

For tagged variables, yes: the Direction tells operators to validate #cbn# values against registered numbers. Whitelist every number you send.

How many variables can a template have?

Keep to two or three. More than three needs written justification under the 2025 rules.

Last checked: 6 November 2026. Sources: TRAI Direction of 18 November 2025 (with Annexure I) and press release No. 133 of 2025; TRAI's Second Amendment 2025; MSG91 on portal syntax; MediaNama (19 November 2025). Each operator set its own switch-over dates; check your DLT portal.