On this page6 sections
No. You do not register WhatsApp Business templates on DLT. TRAI's TCCCPR, and the DLT system it requires, govern commercial SMS and voice calls carried by licensed telecom operators, while WhatsApp messages run on Meta's platform. Consent duties still apply through WhatsApp's own policy and the DPDP Act, and DLT returns the moment you send an SMS.
This post describes what the regulations say, with links to the text, as of 20 October 2026. It is not legal advice. If you are a bank, NBFC, insurer or other regulated entity, confirm your position with counsel and your sector regulator.
What TCCCPR and DLT actually regulate
The Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR) were notified by TRAI on 19 July 2018. TRAI's consolidated text defines a commercial communication as a voice call or message "using telecommunication services" whose main purpose is to advertise or solicit business.
The duties land on Access Providers, which the regulations define as the licensed basic, cellular, unified access and universal access service providers plus virtual network operators. Regulation 3 tells every Access Provider to ensure that commercial communication on its network uses only registered headers or numbers from the special series set aside for it.
DLT (distributed ledger technology) is how operators meet that duty. A business registers as a principal entity, then registers its headers, content templates and telemarketer chain, and every message is scrubbed against those records and the recipient's preferences before delivery. InfiQ's glossary covers the mechanics of DLT registration and the history of TCCCPR.
One detail settles the scope question. The preference schedule lets a subscriber block commercial communication by mode, and the modes listed are voice calls, SMS, auto-dialer calls and robo-calls. There is no mode for messages inside an app.
Why WhatsApp business messages sit outside DLT
A WhatsApp Business message carries no DLT header, no content template ID and no telemarketer chain, and it does not pass through an operator's scrubbing step. It reaches the customer inside the WhatsApp app over a data connection. The system DLT was built to police never sees it.
That has two practical consequences:
- There is nothing to register. You do not need a principal entity ID, header or content template for WhatsApp. Your templates go through Meta's review instead.
- DND does not filter WhatsApp. Preferences on the DND registry are checked during DLT scrubbing. On WhatsApp, the customer is protected by the opt-in rule and by the block and report buttons.
TRAI has amended TCCCPR twice since early 2025. The Second Amendment, dated 12 February 2025, treats any message that mixes promotional content into a transactional or service message as promotional, and gives subscribers seven days to complain. The Third Amendment, announced in TRAI's press release of 18 September 2026, adds AI/ML-based spam detection by operators, rules for application-to-person calls and an appeal route for consumers. All of it is framed around misuse of telecom resources, and none of it moves WhatsApp business messages onto DLT.
What still applies when you message on WhatsApp
Being outside DLT does not mean being outside the rules. A different set of rulebooks applies, and the consequences of breaking them are just as real.
| Rulebook | Applies to WhatsApp business messages? | What it asks of you |
|---|---|---|
| TCCCPR and DLT | No, for messages sent on WhatsApp | Nothing on WhatsApp; full compliance for your SMS and calls |
| WhatsApp Business Messaging Policy | Yes | Contact only people who gave you their number and opted in; honour opt-out requests made on or off WhatsApp; never impersonate another business |
| Meta's opt-in requirements | Yes | Name your business in the opt-in; comply with applicable law |
| DPDP Act, 2023 | Yes, to the personal data you process | Notice, consent, withdrawal and security duties, most of them from 13 May 2027 |
| Your sector regulator's rules | Check with your regulator | Content and conduct rules that may not depend on the channel |
The WhatsApp Business Messaging Policy is explicit on the first two rows. You may contact people only if they gave you their phone number and opted in, and you must respect requests to block, discontinue or opt out, whether they arrive on WhatsApp or elsewhere. Meta's opt-in guidance adds that the opt-in must clearly state the name of the business the person is opting in to hear from.
Enforcement looks different too. Under TCCCPR, operators act against your telecom resources: suspension, disconnection and blacklisting. Under WhatsApp's policy, WhatsApp may limit or remove your access to its business products, and a termination for policy violations can bar your organisation from future use. People can block or report you, and messaging limits may follow.
The DPDP Act sits across both channels. Its notice, consent and security duties come into force eighteen months after the Gazette notification of 13 November 2025 (G.S.R. 843(E) in the e-Gazette), which on a plain count is 13 May 2027. InfiQ's guide to WhatsApp opt-in under the DPDP Act covers how to collect and record consent that satisfies both Meta and the Act.
Where DLT comes back into a WhatsApp programme
Most WhatsApp programmes in India still touch SMS or voice somewhere. Each of those touchpoints is fully under TCCCPR.
- SMS fallback. If an OTP, delivery update or payment reminder falls back to SMS when WhatsApp delivery fails, the SMS needs a registered header, a content template in the right category and a defined telemarketer chain. A fallback channel is only as reliable as its DLT registrations.
- SMS that carries a link to your WhatsApp. TRAI's direction of 30 August 2024 told Access Providers not to permit traffic containing URLs, APKs or OTT links that are not whitelisted, with effect from 1 October 2024. Whitelist every link before it goes into an SMS template, including a click-to-chat link to your WhatsApp number.
- SMS invitations to join WhatsApp. An order-update SMS that also pitches offers on WhatsApp mixes promotional content into a service message, and since the Second Amendment such a message is treated as promotional. Send the invitation as its own template in the right category.
- Calls that follow a WhatsApp lead. TRAI's press release names the 140xx series for regulated promotional calls and the 1600xx and 1601xx series for service and transactional calls. Under the Third Amendment, any business placing automated application-to-person calls must declare them and the numbers it will use to its telecom provider in advance.
- Follow-ups based on an enquiry. The Third Amendment lets a sender contact a customer on the basis of the customer's enquiry for seven days from that enquiry, provided the enquiry was made in writing or digitally and is kept in a verifiable form. If the enquiry came in on WhatsApp, keep the chat, and ask counsel whether it meets that standard.
The Third Amendment was announced on 18 September 2026. Before you change your SMS or calling set-up, check the notified text on trai.gov.in for the date each provision applies.
Keep one consent record for two rulebooks
The cleanest set-up treats WhatsApp and telecom consent as two entries in one register, not two registers that drift apart.
- Record channel and purpose for every consent. A WhatsApp opt-in for order updates is not consent for promotional SMS, and it is not recorded on the operators' DLT consent register.
- Make one opt-out stop everything it should. WhatsApp's policy counts requests made off WhatsApp, so a STOP sent by SMS or said to a call-centre agent should reach your WhatsApp suppression list too.
- Keep promotional lines out of service messages on both channels. On SMS it changes the legal category; on WhatsApp it changes the template category Meta assigns.
- Put a date in the diary after every TRAI amendment. Re-check SMS templates, headers, whitelisted links and calling series each time the regulations change.
You can draft compliant opt-in and opt-out wording with InfiQ's opt-in message generator.
Where InfiQ fits
InfiQ runs on the official WhatsApp Business API, so your templates go through Meta's review, not DLT. Every plan includes opt-in link pages, QR codes and per-contact consent records, and opt-out keywords such as STOP are enforced at platform level with a suppression log. The readiness check on our compliance hub walks through six consent basics in a few minutes.

