Templates registered with the old generic {#var#} must be moved to the new typed tags. Operators are phasing in enforcement, first logging mismatches and then rejecting them, so update your templates before your messages start failing.
Step 1: List your templates that have variables #
Export or list your templates from your DLT portal and mark every template that contains {#var#}. Prioritise the ones you send most, such as OTPs and order updates.
Step 2: Map each variable to a tag #
For every {#var#}, decide what it actually carries and choose the tag: {#numeric#}, {#alphanumeric#}, {#url#}, {#urlott#}, {#cbn#} or {#email#}. See What are DLT variable tags, and which one should I use?
Step 3: Whitelist the CTAs #
For any variable tagged {#url#}, {#urlott#} or {#cbn#}, make sure the links or numbers are whitelisted on your DLT portal first.
Step 4: Update the template on the DLT portal #
Submit the tagged version and wait for approval. Some portals issue a new Template ID for the updated template. Note it down.
Step 5: Update the template in your SMS Gateway Center account #
- Add or update the template under your message templates with the new tagged text and the correct DLT Template ID.
- If you send through the API or SMPP, update the Template ID in your application too.
Step 6: Check your data #
Send a test to your own number, then check that live values match their tags. The most common failures are an OTP field with a space in it, a customer name containing a link, and a callback number that includes “+91”.
Official source: TRAI Direction on variable tagging, 18 Nov 2025.