A clinic that has run SMS appointment reminders in India has almost certainly done a DLT registration, entity registration, sender ID, and every template filed and approved with a telecom operator before a message would go out. So when the same clinic moves reminders to WhatsApp, the question comes up automatically: do I need to register my WhatsApp templates for DLT too? As of August 2026, checked against TRAI's own regulation text and current reporting rather than a vendor blog's summary of it, the answer is no. WhatsApp Business API messaging is not part of TRAI's DLT framework. It runs under a separate compliance regime, Meta's own WhatsApp Business Policy, plus India's DPDP Act for how patient data is handled. This post lays out what DLT actually is, why it does not reach WhatsApp today, what does apply instead, and one thing worth watching: TRAI has an open consultation on regulating OTT messaging platforms like WhatsApp, so this is current fact, not a permanent one.
The confusion is reasonable, not a sign anyone did anything wrong. DLT registration is a real, mandatory, sometimes painful process for commercial SMS in India, and a clinic that has been through it once tends to assume every other bulk messaging channel works the same way. SMS/bulk-messaging vendors sometimes reinforce this by folding "compliance" into a reason to stay on SMS rather than move to WhatsApp. It is worth separating the two channels cleanly, because they are regulated by entirely different bodies under entirely different laws.
DLT stands for Distributed Ledger Technology, the blockchain-style record TRAI uses to administer the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR). It is TRAI's anti-spam mechanism for commercial communication sent over India's telecom network, meaning SMS and voice calls placed through telecom operators. The regime has been mandatory for commercial A2P (application-to-person) SMS since it was phased in from 2019, and TRAI has kept tightening it since, most recently with amendments in 2025 that standardised sender-ID headers and tightened consent rules further. A business sending commercial SMS or making commercial calls without completing DLT registration risks having those messages silently blocked by the telecom operator.
That is the regime clinics are remembering when they ask about WhatsApp. It is a real, three-step, TRAI-administered process, and it is specific to telecom SMS and voice, by design and by the regulation's own text.
WhatsApp messages sent through the official WhatsApp Cloud API do not travel over telecom SMS or voice routes, they travel as data over Meta's own platform. TRAI's jurisdiction under TCCCPR attaches to telecom resources, numbering, SMS routes, and voice, not to an app-layer messaging platform, and this is exactly why the DLT registry has no field for a WhatsApp sender at all. What actually governs a clinic's WhatsApp messaging is Meta's own WhatsApp Business Policy, structured around three mechanisms: prior patient opt-in before a business can message someone, template pre-approval by Meta for every message category before it can be sent, and a per-number quality rating that Meta tracks based on how patients respond to a business's messages.
The template-category system is also where CuraVerto's own published rates come from, already covered in detail on the utility-vs-marketing post linked below: Meta bills utility templates, an appointment reminder or a payment confirmation tied to something the patient already did, at ₹0.15 per message, and marketing broadcasts, promotional content the clinic chooses to send, at ₹0.88 per message. That category split is Meta's pricing model for the WhatsApp Business Platform, a completely separate mechanism from TRAI's DLT template registration, even though both involve pre-approving a message format before it ships. On the data-protection side, India's DPDP Act 2023 governs how a clinic collects consent and handles patient data over any channel including WhatsApp, that obligation is covered in full on CuraVerto's DPDPA post linked below rather than repeated here.
None of this means WhatsApp messaging has no compliance step at all, and it is worth being precise here so this post does not overcorrect into "no rules apply." Getting a clinic's WhatsApp Business number verified and connected to the Cloud API still requires Meta's own business verification: PAN or GST-type documents, a registered business name, and a verified phone number, broadly similar in spirit to DLT's entity KYC. The difference is what this verification is for and how often it happens. DLT registration is a per-template, TRAI-administered filing that recurs every time a clinic wants to send a new SMS format. Meta's business verification is a one-time platform onboarding step for the WhatsApp number itself, not a filing repeated per message template with a telecom regulator.
The practical failure mode clinics run into on SMS is well documented: a template that has not cleared DLT registration, or an entity that has not completed onboarding, gets blocked by the telecom operator at the point of sending, sometimes mid-campaign, with no message reaching the patient and no obvious error to the clinic. WhatsApp reminders sent through the official Cloud API, the connection CuraVerto uses without a BSP markup layer sitting in between as already covered on the Cloud-API cost post linked below, are not exposed to that specific telecom-DLT blocking mechanism, because they were never inside that regulatory pipe to begin with. That is not a claim that WhatsApp messaging has zero failure modes, Meta's own template approval and quality-rating system is a real gate of its own, only that the specific "unregistered sender gets silently blocked by a telecom operator" failure that DLT exists to enforce on SMS does not apply to a channel that TRAI's DLT framework does not currently reach.
Regulation in this space is genuinely moving. TRAI has an open, multi-year consultation process on regulating OTT communication platforms, WhatsApp, Telegram, and similar apps, with telecom operators and their industry body pushing for WhatsApp to be brought under a comparable framework, and software-industry bodies opposing new rules for communication platforms. As of August 2026, that remains a consultation and policy debate, not an enacted regulation, TRAI's recent 2026 amendments to the Telecom Consumer Protection Regulations have addressed tariff and voucher structure, not OTT messaging apps, and no rule has brought WhatsApp Business API messaging under DLT registration. Clinics should treat the answer in this post as accurate today and worth re-confirming periodically, the same way any regulatory question deserves revisiting, rather than as a fact that can never change.
No. CuraVerto's WhatsApp reminders, confirmations, and prescription delivery run on the official Meta WhatsApp Cloud API, which is governed by Meta's WhatsApp Business Policy and template approval, not TRAI's DLT framework. TRAI's DLT registration applies to commercial SMS and voice calls sent over India's telecom network under TCCCPR 2018, a separate regulatory regime that WhatsApp messaging is not currently part of. There is no DLT filing for a clinic to complete before sending WhatsApp reminders through CuraVerto.
DPDP compliance is a real, separate obligation from DLT, and it applies to WhatsApp the same way it applies to any channel a clinic uses to communicate with patients: consent, purpose limitation, and data-handling practices under India's DPDP Act 2023. CuraVerto's dedicated DPDPA post covers the eight binding obligations for clinics in full, including how WhatsApp fits into a clinic's consent and privacy notice.
Meta bills WhatsApp business-initiated template messages by category, fixed when the template is approved, not chosen per message. On CuraVerto, utility templates, reminders, confirmations and digital prescription delivery tied to something the patient already did, are metered at ₹0.15 per message. Marketing broadcasts, promotional content the clinic chooses to send outside a specific patient interaction, are metered at ₹0.88 per message. Neither rate has anything to do with TRAI's DLT registration, it is entirely Meta's own category pricing for the WhatsApp Business Platform.
Only if the clinic also sends commercial SMS or makes commercial voice calls over the telecom network, those channels remain governed by TRAI's TCCCPR and require DLT registration regardless of what messaging platform the clinic uses elsewhere. A clinic that runs its reminders, confirmations and prescriptions entirely through WhatsApp has no DLT obligation for that traffic.
It is a live policy question, not a settled one. TRAI has an open consultation process on regulating OTT communication platforms including WhatsApp, and telecom operators have pushed for it, but as of August 2026 no regulation has brought WhatsApp Business API messaging under TRAI's DLT framework. This reflects the current, verified position; clinics evaluating this long-term should treat it as current fact rather than a permanent guarantee.
CuraVerto connects clinics to the official Meta WhatsApp Cloud API, utility templates metered at ₹0.15 per message, no DLT registration, no BSP markup layer, included from the Essential plan at ₹9,999 per year excluding GST.