Short answer: Most DLT template rejections come down to three things the regulations actually specify: more than three variables without a justified requisition, less than thirty per cent fixed content, and one template linked to more than one header. Fix those and the registrar’s seventy-two-hour discrepancy loop usually ends. The expensive failure is not rejection at all.

A rejected template is annoying. In regulatory terms it is also the cheapest thing that can go wrong. From 17 December 2026 a template approved in the wrong category carries a far worse penalty than one never approved at all. What follows works from the gazetted regulations and one operator’s DLT documentation, read on 16 October 2026.

The three rules that are actually written down

Schedule-I of the Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025 — gazetted 12 February 2025 — tells Access Providers what to do about content templates. Item 4(3) decides whether yours passes.

Three variables is the default ceiling. The Access Provider may allow more than three only “in special circumstances and on requisition with reasons and proper justification from Principal Entity”. More than three is not forbidden — it is an exception you must ask for, in writing, with reasons. Submitting a five-variable template through the ordinary route is the commonest self-inflicted rejection.

Thirty per cent of the characters must be fixed. That exception carries conditions, one being “minimum thirty percent characters in the Content Template shall be fixed content”. It is a condition on the more-than-three case, not a universal rule, but it decides whether your requisition can be granted. On a 160-character template, thirty per cent is 48 fixed characters, leaving 112 for every variable combined.

One template, one header. The Access Provider must “ensure that one Content Template is not linked with more than one Header”. The same body under a promotional and a transactional header is two registrations. That is a structural rejection; rewording will not fix it.

Two operational provisions sit alongside. Access Providers must “designate a separate executive specially for the purpose of carrying out approval of Content Template registration” — a named human in the loop, which is why turnaround varies by registrar — and must “temporarily deactivate unused Content Templates” after ninety days. A template last used on 16 October 2026 can be deactivated from 14 January 2027: not a rejection, but identical from the sending end.

What one operator adds on top

Vodafone Idea’s VILpower DLT FAQ, read 16 October 2026, gives the turnarounds the regulations do not: content template verification “within 60 minutes”, discrepancy notifications “within the defined 72-hour TAT”. Templates registered from 11 October 2020 should carry the brand name and “could be rejected if the same is not incorporated while registering”. After registration only the variable part can be changed; regional-language templates must also be whitelisted; headers inactive beyond ninety days return to the pool. No fee is stated for content template registration, which matters: a rejection costs calendar time, not money. Our DLT registration guide covers the entity and header side, where fees do apply.

Three sources, three header formats

One contradiction is worth publishing rather than smoothing over, because anyone building a header to match a template will hit it. Three published descriptions of header length disagree, all read 16 October 2026.

SourceWhat it says a header is
TCCCPR Second Amendment, Schedule-I item 2(1), gazette 12 Feb 2025“SMS Header for sending Transactional SMS, Service SMS, Promotional SMS and Government SMS from 11-character alphanumeric string”
VILpower DLT FAQ, first definitiona “unique 6-digit string”
VILpower DLT FAQ, second definition on the same pagea “6-digit alpha string”

We will not say which is right, because we cannot source it. Check the format in your own registrar’s portal, and keep the screenshot.

The gazette is unambiguous about the suffix — “by suffixing ‘-P’, ‘-S’, ‘-T’, and ‘-G’ for Promotional, Service, Transactional, and Government Messages, respectively”, so that “the type of Commercial Communication can be identified by Recipients from the Header structure”. Category is not a tick-box buried in a form. It is printed on every message you send.

The expensive failure is approval in the wrong category

The Third Amendment to the TCCCPR, gazetted 18 September 2026, inserts a proviso into regulation 25(4)(d)(ii). Where a complaint arises “due to registration of content template in wrong category”, “the content template shall be blacklisted by the OAP”. And if “five content templates of such Sender are blacklisted for registration under wrong category during the last ninety days”, then “the OAP shall suspend the services of the Sender, for one month” — “or till the time all the content templates of the Sender are reverified for registration under proper category, whichever is later”.

Read that last clause slowly. The suspension does not end after a month; it ends when every template on the account has been re-verified correctly, if that takes longer. A sender with four hundred templates faces a floor of one month and a ceiling nobody has published. A rejection costs three days.

The incentive has inverted. Pushing a promotional message through as transactional to dodge DND scrubbing was a tactic with a compliance risk attached; from 17 December 2026 it is five complaints from taking the account down. Our note on utility versus marketing categorisation on WhatsApp shows the same pattern on Meta’s platform, where the penalty is a price rather than a suspension.

Three dates, and only one of them is close

Regulation 1(3) says the regulations come into force “after thirty days from the date of their publication in the Official Gazette except” — “(a) regulation 4, regulation 6, regulation 8(a) and regulation 18, which shall come into force after sixty days; and (b) the amendments listed in Annexure, which shall come into force after ninety days”. Counting from 18 September 2026:

CommencesDays from 16 Oct 2026What landsBearing on templates
18 October 20262The general rule — everything not exceptedNothing specific to content templates
17 November 202632Regulations 4, 6, 8(a) and 188(a) is the header and content-template misuse regime
17 December 202662The Annexure amendments, including regulation 11Wrong-category blacklisting and the five-in-ninety-days suspension

The 17 November tranche is the one most senders have not read. Regulation 8(a) covers misuse of a header or template — use by anyone other than the registered sender, through compromise, theft, leakage, cloning or impersonation. The Originating Access Provider must suspend it “immediately upon noticing the misuse, but not beyond six hours”, across all Access Providers. If credential compromise is established, the registrar “shall mandatorily de-register all Headers and Content Templates of such Sender” within five business days — every template, not just the compromised one. If you are found not at fault, templates are restored “within two business days of such determination”; the regulation sets no deadline for the determination itself.

What each failure costs in days

On one scale, in business days as the regulations count them, the asymmetry is obvious. Three of the four are floors, not durations: the regulation names a minimum and no maximum.

How long each kind of DLT template failure keeps you off the network Horizontal bars showing the minimum delay, in business days as the regulations count them, for four DLT template failure modes. A rejected template costs 3 business days under the registrar’s 72-hour discrepancy turnaround. A misused template where the Sender is found not at fault is restored within 2 business days of that determination, but the determination itself carries no deadline. A credential compromise requires all headers and content templates to be de-registered within 5 business days and reviewed within 10, a floor of 15. Five wrong-category blacklists in ninety days suspends the Sender for one month, 21 business days from 17 December 2026 to 17 January 2027, or until every template is re-verified, whichever is later. Three of the four bars are hatched because they are open-ended floors, not fixed durations: only the rejected-template bar is a bounded figure. Rejection is the cheap outcome Minimum delay by failure mode, in business days as the regulations count them 0 3 6 9 12 15 18 21 24 business days 3 Template rejected discrepancy notice 2+ Misused template, Sender not at fault 15+ Credential compromise: all templates de-registered 21+ Five wrong-category blacklists in 90 days bounded figure hatched: an open-ended floor, not a fixed duration

The one-month suspension is shown as twenty-one business days — what one month comes to from the earliest day regulation 11 can bite: 17 December 2026 to 17 January 2027 is thirty-one calendar days and twenty-one business days. It is hatched because “whichever is later” makes the real figure depend on how many templates you hold.

A worked example: the restoration bill

Rejections cost time; restoration costs money, and the Third Amendment publishes the rate. Under regulation 29, service is restored “on payment of a restoration charge of rupees five thousand per resource to the Authority”, and “the total amount payable by the Sender or Telemarketer shall not exceed rupees five lakh”. For PRI or SIP trunks, “each DID number shall be treated as a separate telecom resource”. Partial restoration “shall not be less than half” of the full calculation.

Resources suspendedAt ₹5,000 eachPayable after the ₹5,00,000 capPartial restoration floor
5₹25,000.00₹25,000.00₹12,500.00
20₹1,00,000.00₹1,00,000.00₹50,000.00
50₹2,50,000.00₹2,50,000.00₹1,25,000.00
100₹5,00,000.00₹5,00,000.00₹2,50,000.00
120₹6,00,000.00₹5,00,000.00₹2,50,000.00

The cap bites at exactly one hundred resources, so beyond that another suspended DID costs nothing more. Separately, regulation 27 puts ₹1,000 “per count of such valid complaints” on the Originating Access Provider — and, in its second limb, shifts that charge to “the Access Provider that has registered such Headers and Content Templates, instead of OAP”. Your registrar now has ₹1,000 a complaint riding on your categorisation. Expect template review to get stricter.

What we could not verify

No Indian domestic per-SMS rate verified on 16 October 2026 — the provider page we normally read would not load, twice — so no per-message figure appears above and nothing was carried over. The one rate that did publish is Twilio’s India SMS price of $0.0832 per message segment, for both International Numbers and Alphanumeric Sender IDs, with a $0.001 fee on failed messages; domestic discounts are “Contact sales” and unpublished. At the European Central Bank reference rate of ₹95.06 to the dollar, dated 15 October 2026, that is ₹7.909 per segment and ₹0.0951 for the failed-message fee, 1.20% of the message price.

We also could not source, from a primary publisher, a per-SMS DLT scrubbing charge, principal-entity or header registration fees, or a dated government citation for the 18% GST rate on telecom services. All three circulate widely on vendor blogs. We are not repeating them. For the rest of the bill as far as it verifies, see the four layers of a messaging invoice, our channel cost comparison and provider markup.

Frequently asked questions

Why was my DLT template rejected when the wording looks fine?

Check the structure before the wording. More than three variables needs a justified requisition, not an ordinary submission; the template must not be linked to a second header; and it is expected to carry the brand name, per Vodafone Idea’s DLT FAQ. None is a wording problem, and rewriting the sentence clears none of them.

How long does a resubmission take?

Vodafone Idea’s FAQ gives verification as within sixty minutes and discrepancy notifications within a seventy-two-hour turnaround: a clean submission is fast, a bounced one costs about three days per cycle. The gazette sets no turnaround, which is why this varies by registrar.

Is it safer to register a promotional message as transactional?

It is about to become considerably less safe. From 17 December 2026 a complaint traced to a wrong-category template gets it blacklisted, and five such blacklistings in ninety days suspend the sender for one month or until every template is re-verified, whichever is later. This is a reading of the regulations, not legal advice.

My templates stopped working and nothing was rejected. What happened?

Unused content templates are temporarily deactivated after ninety days, and headers inactive beyond ninety days return to the header pool. Neither shows up as a rejection.

Does any of this apply to WhatsApp?

We have looked for an instrument extending DLT to WhatsApp several times and found nothing either extending or exempting it. We state that as an absence, not a conclusion. WhatsApp categorisation is a separate Meta process; see also the 140 and 1600 series.


How we verified this. Every figure, rate and regulation above was checked against a live primary source on 16 October 2026 and is dated to that reading. Regulatory text comes from the gazetted regulations themselves, not from summaries. Where two published sources disagree, we show both and explain neither. Arithmetic is computed rather than estimated. Figures we could not verify are named as unverified and left out rather than approximated. We sell a competing messaging product, which is disclosed wherever a competitor’s published figures appear. We publish no engagement or response rates of our own, and no xreach51 pricing appears in this post; our rates are on the pricing page.

Sources