Ask most Indian marketers "WhatsApp or SMS?" and they reach for open rates and cost per message. That is a fair question, and we answer it in detail in our broader WhatsApp vs SMS comparison. But there is a narrower, sharper question that decides whether a message reaches a customer at all: does TRAI's DND registry block it, does the DLT pipeline reject it, and can the channel carry the content you actually need to send? That is what this post is about.
How this is different: If you want the full 22-point feature comparison (reach, cost, ROI, CRM integration), read WhatsApp vs SMS for Business in India. If you want the marketing-campaign angle (engagement, conversion, when to run which type of campaign), read Bulk SMS vs WhatsApp Marketing. This post narrows in specifically on DND exemption, delivery guarantees, and rich media- the compliance and deliverability layer that determines whether your message legally reaches the inbox in the first place, before conversion even becomes a question.
DND scrubbing quietly removes a large chunk of any Indian promotional SMS list before it is sent. Most businesses budget for a send volume they will never actually achieve, because a meaningful share of their contact database is DND-registered and legally unreachable for promotional content. WhatsApp sidesteps this entirely- it sits outside TRAI's DND framework- but trades that exemption for a requirement that the customer has opted in, has internet access, and has an active WhatsApp account. Neither channel is a free lunch on delivery; each has a different gate.
Quick answer: WhatsApp is exempt from TRAI DND, so it can legally reach any opted-in customer regardless of their DND status- a major advantage for promotional and rich-media content. Bulk SMS has broader raw number reach but a large share of that reach is blocked for promotional messages by mandatory DND scrubbing. For guaranteed delivery, use WhatsApp for opted-in reach and compliant, DND-cleared Bulk SMS for the rest- together they cover more real, deliverable inboxes than either channel alone.
Get WhatsApp Business API- DND-exempt · Rich media · Chatbot Get Bulk SMS Service- DLT registered · DND-compliant · OTP
WhatsApp vs Bulk SMS- Delivery & Compliance Comparison
| Dimension | WhatsApp Business API | Bulk SMS |
|---|---|---|
| TRAI DND applicability | Not applicable- outside DND/TCCCPR framework | Applies- promotional SMS blocked for DND-registered numbers |
| DND scrubbing required | No | Yes- mandatory before every promotional send |
| DLT registration | Not required | Mandatory- entity, Sender ID, and template registration |
| Template/content approval | Meta template approval (non-TRAI) | DLT template approval per telecom operator |
| Sender verification | Green Tick- Meta business verification | 6-character alphanumeric Sender ID |
| Consent requirement | Explicit opt-in mandatory for all sends | Not required for DND-cleared promotional or transactional sends |
| Reachable without opt-in | No | Yes- non-DND numbers, subject to DLT compliance |
| Delivery dependency | Internet connectivity + active WhatsApp account | Telecom network coverage- works without internet |
| Rich media in delivered message | Images, video, PDF, carousels, interactive buttons | Text only- 160 characters per SMS segment |
| Delivery to feature phones | No | Yes |
| Transactional/OTP delivery | Supported, DND-exempt by nature | Supported, exempt from DND for transactional category |
| Time-of-day restrictions | None | Promotional SMS restricted to 9 AM-9 PM |
| Rejection risk before send | Meta template rejection (policy violation) | DLT template mismatch rejection (content vs registered template) |
| Operator-level filtering | Not applicable | Possible- operator spam/content filters can block sends |
| Message thread continuity | Two-way, persistent conversation thread | One-way per message- replies open a new thread |
| Delivery confirmation granularity | Sent, delivered, read, clicked | Delivered/failed only (basic delivery report) |
The DND Reality- How Many Numbers Are Actually Reachable
Numbers make this concrete. Here is a worked example for a business with a 1,00,000-number Indian consumer contact list running a promotional campaign:
| Step | Bulk SMS (promotional) | WhatsApp (opted-in) |
|---|---|---|
| Total numbers in database | 1,00,000 | 1,00,000 |
| DND-registered numbers | ~55,000-65,000 (typical Indian consumer list) | Not applicable- WhatsApp is DND-exempt |
| Numbers blocked before send | ~55,000-65,000 (removed by mandatory DND scrubbing) | 0 (DND status irrelevant) |
| Numbers legally eligible for send | ~35,000-45,000 | Depends entirely on opt-in rate |
| WhatsApp opt-in rate (typical) | Not applicable | ~30-50% of database, depending on collection effort |
| Numbers eligible to receive message | ~35,000-45,000 | ~30,000-50,000 |
| Further delivery loss (filtering, inactive numbers, no internet) | ~5-10% additional loss | ~5-10% additional loss (no internet/inactive account) |
| Approximate numbers actually reached | ~31,500-42,750 | ~27,000-45,000 |
What this shows: promotional SMS looks like it should reach all 1,00,000 numbers, but DND scrubbing alone removes more than half the list before compliance even allows a send attempt. WhatsApp's reachable number depends on opt-in rather than DND status, so a business that invests in opt-in collection can often reach a comparable or larger number of real customers on WhatsApp- with the added benefit of rich media- than it can on promotional SMS once DND is factored in. Neither number is "guaranteed"- both are net-of-filtering estimates, which is exactly why understanding each channel's specific delivery gate matters more than a headline reach figure.
1. Reaching DND-registered customers with promotional content
A large share of Indian mobile numbers are DND-registered. For these customers, promotional Bulk SMS is not legally deliverable at all- no send strategy, budget, or Sender ID reputation fixes this. If your customer base skews toward DND-registered numbers (common for urban, higher-income, digitally aware segments), Bulk SMS structurally cannot reach them with promotional content, no matter how compliant your DLT setup is.
2. Delivering to customers without internet or WhatsApp
SMS delivers over the telecom network directly- no internet, no app, no account required. For customers in low-connectivity areas, on feature phones, or temporarily offline, SMS remains deliverable when WhatsApp physically cannot reach the device. This is a hard technical floor, not a compliance question.
3. Transactional and OTP delivery where speed and universality matter
Transactional SMS is DND-exempt by category and delivers in seconds across any network. For OTPs, payment confirmations, and fraud alerts where 100% universal deliverability is non-negotiable, SMS remains the dependable fallback- it does not depend on the recipient's WhatsApp account being active or online at that moment.
4. Simple, one-line alerts with no content richness needed
When the message is a single fact- "your balance is X," "your recharge is due"- there is no compliance or delivery advantage to rich media. SMS delivers the same information with a simpler, cheaper, more predictable delivery path, and DND exemption for transactional content means it reaches the full base.
5. Regulatory or statutory notices that specify SMS delivery
Some regulatory frameworks and internal compliance policies specifically mandate SMS as the notice channel for certain alerts. In these cases, the delivery guarantee that matters is not technical- it is that the message was sent via the legally specified channel, which SMS satisfies by default.
Where WhatsApp's Delivery & Compliance Model Wins
1. Reaching DND-registered customers who have opted in
This is the core structural advantage. Any customer who has opted in to WhatsApp communications can be legally messaged with promotional content regardless of their DND status. For businesses with a large DND-registered customer base that still wants to run promotions, WhatsApp is often the only compliant channel available- SMS is legally closed off for that exact segment.
2. Avoiding DLT template rejection risk
DLT template approval requires the sent message to match the registered template exactly, including variable placeholders- mismatches cause silent rejections at the operator level, sometimes discovered only after a failed campaign. WhatsApp's Meta template approval is a one-time review per template with a more forgiving mismatch tolerance for approved variable content, reducing last-mile rejection risk once a template is live.
3. Delivering rich media that carries more information per message
A DND-exempt delivery channel is only useful if it can carry the content you need. WhatsApp delivers images, PDFs, videos, carousels, and interactive buttons in a single message- content that simply cannot exist in a 160-character SMS. For product catalogues, payment receipts with attached invoices, or document verification flows, WhatsApp is the only channel that can deliver the full package in one message.
4. Consistent delivery guarantees without time-of-day restrictions
Promotional SMS delivery is legally restricted to 9 AM-9 PM. WhatsApp carries no such restriction, allowing time-sensitive or international-hours communication (shipment updates, support responses, appointment confirmations) to be delivered whenever relevant, not only within a compliance-mandated window.
5. Verified sender identity that reduces filtering risk
WhatsApp's Green Tick verification and Meta business verification give customers and Meta's own spam systems a verified identity to check messages against, reducing the odds of legitimate messages being caught in filtering. SMS Sender IDs are more easily approximated or filtered by operator-level spam systems, which can quietly suppress delivery even for DLT-compliant templates.
Use-Case Recommendation Matrix- Deliverability Focus
| Use case | Best channel for guaranteed delivery | Why |
|---|---|---|
| OTP / authentication | SMS primary, WhatsApp OTP as secondary | SMS is DND-exempt for transactional category and needs no internet |
| Promotional offer to DND-registered customers | WhatsApp (opted-in) | Only legally compliant channel for DND-registered numbers |
| Promotional offer to non-DND, non-opted-in customers | Bulk SMS | Legally deliverable without WhatsApp opt-in |
| Regulatory/statutory alerts | SMS or both | Some frameworks specify SMS as the compliant notice channel |
| Rich-media catalogue or document delivery | SMS cannot carry images, PDFs, or interactive content | |
| Rural or low-connectivity customer base | Bulk SMS | Delivers without internet or app installation |
| Payment/shipping confirmation with attached proof | Rich media (invoice PDF, tracking button) not possible in SMS | |
| Full-database awareness campaign (mixed DND status) | Bulk SMS first, WhatsApp for opted-in overlap | SMS reaches DND-cleared numbers; WhatsApp covers DND-registered opt-ins |
| Time-sensitive alert outside 9 AM-9 PM | No time-of-day restriction, unlike promotional SMS | |
| High-value customer with WhatsApp opt-in | DND-exempt, rich media, verified sender- fewer delivery gates | |
| Feature phone or offline customer | Bulk SMS | Only channel that reaches the device at all |
TRAI DLT vs Meta Template Compliance
| Compliance factor | TRAI DLT (Bulk SMS) | Meta Template Approval (WhatsApp) |
|---|---|---|
| Governing body | TRAI (Telecom Regulatory Authority of India) | Meta (WhatsApp Business Platform policies) |
| Registration scope | Entity + Sender ID + every message template | Business account verification + each message template |
| Registration required with | Each telecom operator (Vi, Airtel, Jio, BSNL) via DLT portal | Meta Business Manager, once per template |
| Typical approval time | Template approval: hours to a few days per operator | Template approval: typically 24-48 hours |
| Rejection risk | High if sent content deviates from registered template variables | Moderate- policy violations or promotional content misclassified as utility |
| DND enforcement | Enforced at scrub stage before send- mandatory | Not applicable- no DND concept in WhatsApp compliance |
| Ongoing compliance risk | Sender ID or template suspension for non-compliance | Messaging quality rating drop or number ban for policy violations |
| Consent record requirement | Implicit for non-DND numbers; explicit for promotional DND exceptions | Explicit opt-in record required for every contact, always |
Recommended Strategy- A Combined Delivery Waterfall
Neither channel alone maximises guaranteed delivery. The strategy that gets the most compliant messages into the most inboxes combines both, sequenced by delivery gate rather than by cost or preference:
- Attempt WhatsApp first for opted-in customers. No DND restriction applies, rich media improves engagement, and delivery confirmation (sent/delivered/read) gives you real-time visibility into whether the message landed.
- Fall back to compliant Bulk SMS for DND-cleared, non-opted-in numbers. This covers customers who have not opted in to WhatsApp but are legally reachable via DLT-registered SMS templates.
- Use transactional SMS as the universal fallback for anything time-critical. OTPs, payment confirmations, and fraud alerts should always have an SMS path, since it is DND-exempt by category and does not depend on internet connectivity.
- Track DND and opt-in status at the contact level, not the campaign level. A contact database that flags DND status and WhatsApp opt-in per number lets you route each customer to their legally reachable channel automatically, instead of guessing at campaign time.
GCM unified platform: Get Click Media runs WhatsApp Business API and Bulk SMS from a single platform, with per-contact DND and opt-in status tracked automatically. We handle DLT registration and Meta template approval end-to-end, and configure waterfall routing- WhatsApp first for opted-in reach, compliant SMS for DND-cleared broader reach- so you get the maximum number of guaranteed, compliant deliveries from a single contact list.
Frequently Asked Questions- WhatsApp vs Bulk SMS
Does TRAI DND block Bulk SMS delivery in India? Yes. Promotional Bulk SMS legally cannot be delivered to any mobile number registered on TRAI's Do Not Disturb (DND) / NCPR list. A large share of Indian mobile subscribers are DND-registered, so a promotional SMS campaign sent to a full customer database is scrubbed against the DND list before it goes out- the DND-registered numbers are simply never delivered, regardless of budget. Transactional and service SMS are exempt from DND, but promotional content is not.
Is WhatsApp Business API affected by TRAI DND rules? No. WhatsApp Business API sits entirely outside TRAI's DND/TCCCPR framework because it is an OTT messaging channel, not a telecom SMS channel. A business can message any customer who has opted in to WhatsApp communications, regardless of whether that customer's mobile number is DND-registered. This is the single biggest structural delivery advantage WhatsApp holds over promotional SMS in India.
Which channel actually guarantees message delivery- WhatsApp or Bulk SMS? Neither guarantees 100% delivery, but the failure modes differ. Bulk SMS can fail due to DLT template mismatch rejections, operator-level filtering, and mandatory DND scrubbing that removes a large portion of a promotional list before sending. WhatsApp delivery is generally high for opted-in, active numbers but requires the recipient to have internet connectivity and an active WhatsApp account. In practice, SMS reaches more raw numbers but blocks a large share of them for promotional content due to compliance filtering, while WhatsApp reaches fewer total numbers but with fewer artificial delivery blockers for its opted-in base.
What is the compliance difference between Bulk SMS and WhatsApp in India? Bulk SMS requires mandatory TRAI DLT registration- entity registration, Sender ID approval, and per-template approval with each telecom operator- before any commercial message can be sent. WhatsApp Business API instead requires Meta template approval, a separate process that has nothing to do with TRAI or DLT. A business running both channels needs to manage two independent compliance pipelines.
Can WhatsApp replace Bulk SMS for DND-registered customers? Yes, for customers who have opted in to WhatsApp. If a customer is DND-registered and cannot legally receive promotional SMS, WhatsApp is often the only compliant channel left to reach them with promotional content. This is why businesses with a large DND-registered customer base increasingly route promotional messaging through WhatsApp first and use SMS only for transactional or DND-cleared sends.
How much of a Bulk SMS list is typically lost to DND scrubbing? This varies by database, but it is common for a significant portion of an Indian consumer mobile list to be DND-registered, meaning that share is unreachable for promotional SMS regardless of send volume or budget. Businesses often discover their real reachable promotional SMS audience is meaningfully smaller than their total contact list once DND scrubbing is applied- which is why WhatsApp's DND-exempt status matters so much for total addressable reach.
Should I use WhatsApp or Bulk SMS for guaranteed delivery of a promotional campaign? Use both in combination. Send to opted-in customers on WhatsApp first, since it is unaffected by DND and supports rich media that improves engagement. Then send compliant Bulk SMS to the DND-cleared, non-WhatsApp-opted-in portion of your list for broader reach. This waterfall approach maximises the number of customers who actually receive a legally compliant message, rather than relying on a single channel with its own delivery gaps.
Get Started
If DND exemption, delivery guarantees, and rich media are the deciding factors for your business, the right answer is rarely "just one channel." Get Click Media sets up WhatsApp Business API for DND-exempt, rich-media reach to your opted-in base, and Bulk SMS with full DLT compliance for your DND-cleared and transactional sends- on one platform, with per-contact routing handled automatically. For the broader feature-by-feature and cost picture, see our WhatsApp vs SMS comparison.
Get WhatsApp Business API- DND-exempt · Rich media · Chatbot Get Bulk SMS Service- DLT registered · DND-compliant · OTP
Frequently Asked Questions
Yes. Promotional Bulk SMS legally cannot be delivered to any mobile number registered on TRAI's Do Not Disturb (DND) / NCPR list. A large share of Indian mobile subscribers are DND-registered, so a promotional SMS campaign sent to a full customer database is scrubbed against the DND list before it goes out- the DND-registered numbers are simply never delivered, regardless of budget. Transactional and service SMS are exempt from DND, but promotional content is not.
No. WhatsApp Business API sits entirely outside TRAI's DND/TCCCPR framework because it is an OTT messaging channel, not a telecom SMS channel. A business can message any customer who has opted in to WhatsApp communications, regardless of whether that customer's mobile number is DND-registered. This is the single biggest structural delivery advantage WhatsApp holds over promotional SMS in India.
Neither guarantees 100% delivery, but the failure modes differ. Bulk SMS can fail due to DLT template mismatch rejections, operator-level filtering, and mandatory DND scrubbing that removes a large portion of a promotional list before sending. WhatsApp delivery is generally high for opted-in, active numbers but requires the recipient to have internet connectivity and an active WhatsApp account. In practice, SMS reaches more raw numbers but blocks a large share of them for promotional content due to compliance filtering, while WhatsApp reaches fewer total numbers but with fewer artificial delivery blockers for its opted-in base.
Bulk SMS requires mandatory TRAI DLT registration- entity registration, Sender ID approval, and per-template approval with each telecom operator- before any commercial message can be sent. WhatsApp Business API instead requires Meta template approval, a separate process that has nothing to do with TRAI or DLT. A business running both channels needs to manage two independent compliance pipelines.
Yes, for customers who have opted in to WhatsApp. If a customer is DND-registered and cannot legally receive promotional SMS, WhatsApp is often the only compliant channel left to reach them with promotional content. This is why businesses with a large DND-registered customer base increasingly route promotional messaging through WhatsApp first and use SMS only for transactional or DND-cleared sends.
This varies by database, but it is common for a significant portion of an Indian consumer mobile list to be DND-registered, meaning that share is unreachable for promotional SMS regardless of send volume or budget. Businesses often discover their real reachable promotional SMS audience is meaningfully smaller than their total contact list once DND scrubbing is applied- which is why WhatsApp's DND-exempt status matters so much for total addressable reach.
Use both in combination. Send to opted-in customers on WhatsApp first, since it is unaffected by DND and supports rich media that improves engagement. Then send compliant Bulk SMS to the DND-cleared, non-WhatsApp-opted-in portion of your list for broader reach. This waterfall approach maximises the number of customers who actually receive a legally compliant message, rather than relying on a single channel with its own delivery gaps.
