SMS is cheap per message and universally delivered. WhatsApp is 3 to 5x more expensive per message and 5 to 6x more engaging. Both have separate compliance regimes (DLT for SMS, Meta template approval for WhatsApp). This guide breaks down the real per-message cost, deliverability, DLT and Meta rules, engagement, and the hybrid strategy we actually run in production via BookMySMS. Written for Indian founders, marketers, and product managers making the pick.
Where we land after running both channels in production across BookMySMS clients spanning D2C, BFSI, healthcare, and services.
The regulatory and vendor landscape is genuinely different in India versus the rest of the world. Skipping this section is how founders end up with a broken launch.
SMS in India runs on DLT. The Telecom Regulatory Authority of India (TRAI) mandates that every commercial SMS in India go through the Distributed Ledger Technology platform. In practice this means: register your entity (principal entity registration) with a telecom operator's DLT portal (Vilpower for Vi, Jio DLT for Jio, Tata Teleservices, Airtel, BSNL). Register your header (6-character sender ID such as VMDECPR, MPDECPR, etc). Register every template you want to send, categorised as transactional, service explicit, service implicit, or promotional. Templates with variables use %s or similar placeholders and must match exactly when sent. Non-compliant messages get blocked at the operator gateway. First-time setup takes 2 to 4 weeks including document verification.
WhatsApp Business API in India runs via BSPs plus Meta. You cannot access the WhatsApp Business API directly if you are a small or mid business. You must go through a Meta-authorised BSP (Business Solution Provider). Popular Indian BSPs: Gupshup, MSG91, Kaleyra, Karix, Interakt. International players available in India: Twilio, Wati, Vonage. The BSP handles number provisioning, template submission to Meta, and message delivery. You pay the BSP a monthly platform fee (typically Rs 2,500 to 25,000 depending on tier) plus per-conversation charges. On top of the BSP fee, Meta charges its own per-conversation rate that varies by country and template category (marketing, utility, authentication, service). The Meta charge is passed through by the BSP with a small markup.
These two systems are entirely separate. DLT registration does nothing for WhatsApp. Meta template approval does nothing for SMS. If you send both, you comply with both, independently. Budget setup time and effort for each.
Sticker rates in India as of July 2026. Actual rates vary by BSP, volume commitment, and network mix. Get quotes from three vendors before committing.
| Channel & category | Per-message cost (INR) | Includes | Notes |
|---|---|---|---|
| SMS transactional | Rs 0.15-0.25 | Aggregator plus operator charges | OTP, order updates, alerts. Requires DLT template. |
| SMS service explicit | Rs 0.15-0.22 | Aggregator plus operator | Requires prior explicit consent. |
| SMS promotional | Rs 0.10-0.18 | Aggregator plus operator | Blocked by DND. Restricted send windows. |
| WhatsApp utility conversation | Rs 0.35-0.85 | Meta rate plus BSP markup | Order confirms, delivery updates, appointment reminders. |
| WhatsApp authentication | Rs 0.14-0.35 | Meta rate plus BSP markup | Newer category specifically for OTPs and 2FA codes. |
| WhatsApp marketing | Rs 0.75-1.35 | Meta rate plus BSP markup | Promotional. Higher-priced conversation category. |
| WhatsApp service (customer-initiated) | Rs 0.35 or free tier | Meta rate | When customer messages first, reply within 24 hours. |
WhatsApp bills per 24-hour conversation, not per message. Once a conversation opens (either you send a template, or the customer messages you first), all messages within that 24-hour window are covered by one conversation charge. If you send an order confirmation, a shipping update, and a delivery notification within 24 hours, you pay one utility conversation. This is meaningfully different from SMS billing (per message) and materially changes the effective cost calculation for engagement-heavy flows.
Per-message cost tells you one thing. Effective cost per informed customer tells you what actually matters.
SMS in India in 2026. Delivery rate to reachable handsets: 92-97% for transactional. Open rate: 15-25% on average for transactional SMS. Click-through on any link: 1-4%. The delivery rate is high because SMS is delivered by the carrier and shows up in the messages inbox. But most Indian users no longer actively check SMS. It has become the "OTP inbox" for a large fraction of urban users. Rural users still check SMS more actively.
WhatsApp in India in 2026. Delivery rate: 96-99% for opt-in users with the number in their contacts or with meaningful history. Read rate (measurable via double blue tick, understated because some users disable receipts): 65-80% reported, actual likely 80-90%. Click-through on interactive buttons: 15-35% depending on flow relevance. WhatsApp shows up as a notification in a chat app that Indians open dozens of times a day. The engagement gap versus SMS is not marginal, it is roughly an order of magnitude.
The effective cost math. Consider a shipping update to 10,000 customers. SMS: 10,000 messages at Rs 0.20 = Rs 2,000 spend, 20% open rate = 2,000 informed customers, effective cost Rs 1.00 per informed customer. WhatsApp: 10,000 utility conversations at Rs 0.65 = Rs 6,500 spend, 85% read rate = 8,500 informed customers, effective cost Rs 0.76 per informed customer. WhatsApp is 3.25x more expensive per message but cheaper per informed customer. This flips the intuitive "SMS is cheaper" conclusion for most transactional flows.
Both channels have friction that only becomes obvious once you are trying to ship. Plan for it.
SMS DLT registration timeline. Principal entity registration takes 3 to 7 days assuming your documents are in order (CIN, GST, PAN, authorised signatory letter). Header registration takes 24 to 48 hours per header. Template registration takes 24 to 72 hours per template and Meta-style rejections happen when your template content does not match the declared category. Budget 2 to 4 weeks for a full first-time DLT setup with 20 to 30 templates.
SMS DND filtering. Users on India's National Do Not Call registry are blocked from receiving promotional SMS. Transactional and service-explicit SMS are delivered to DND users. If you are running promotional campaigns, roughly 25-40% of your list will be filtered by DND and never receive the message.
WhatsApp template approval timeline. Each template submitted to Meta gets reviewed in 2 to 24 hours. First-submission rejection rate is roughly 15-30% for reasons including category mismatch (promotional language in utility template), formatting issues (missing button config), or content issues (excessive URLs, promotional adjectives). Budget 2 to 3 iterations per non-trivial template. Plan template submission as a workstream a week before launch, not the night before.
WhatsApp 24-hour service window. Once a customer sends you a message, you have 24 hours to reply with any content at low cost (service conversation, often free within tier). After 24 hours, only approved templates can be sent, which incurs a paid conversation charge. Your support agents need to be aware of the window. Automated bots should hand off inside the window whenever possible.
WhatsApp business number quality rating. Meta assigns a quality rating (green, yellow, red) to each business number based on user block rate and message quality. Numbers with low quality get throttled and eventually restricted. Send only to opted-in users, do not spam, use templates as intended. Losing a green rating is painful because messaging tier limits are quality-dependent.
15-minute call. Tell us your top 3 messaging use cases and expected monthly volume. We come back with a channel recommendation per use case, an estimated monthly cost, and a rough DLT plus BSP setup checklist.
Book Free 15-min CallThe honest per-scenario recommendation based on production data across BookMySMS clients.
Universal reach (works on feature phones and users without WhatsApp), lowest friction, fastest delivery. SMS remains the standard. WhatsApp authentication templates are viable as a secondary or opt-in channel for tech-savvy users. Do not force WhatsApp OTP as primary; you will lose signups.
Rich formatting (product image, order summary, tracking button), high read rate, natural place for customer to reply with questions. This is where WhatsApp shines. Fall back to SMS for users who have not opted in or where WhatsApp delivery fails.
Multiple updates over 24-48 hours ideally sit in one thread. WhatsApp's conversation-based billing plus rich media (map link, delivery photo) makes it materially better than a series of terse SMS messages.
Read rate matters because missed appointments are expensive. WhatsApp's reminder with a confirm or reschedule button converts much better than an SMS. SMS as fallback for users without WhatsApp.
Highest ROI use case for WhatsApp marketing conversations in D2C. Read rates plus interactive buttons ("Continue checkout", "Talk to us") drive real recoveries. Send within 1-4 hours of abandonment for best conversion. Watch marketing category pricing.
Regulatory and audit context favour SMS for BFSI. Users expect payment confirmations in SMS. WhatsApp is a secondary channel for enhanced context (transaction receipt PDF, view transaction button).
Opt-in WhatsApp marketing to engaged customers: highest ROI channel we see. SMS promotional to cold lists: high DND filtering, low open rate, marginal ROI. Do not use SMS promotional as your primary marketing channel in 2026. Do use WhatsApp marketing with careful segmentation and frequency caps.
Two-way conversation is what WhatsApp is built for. Bot handles common flows inside the 24-hour window, hands off to human agent when needed, full thread history preserved. SMS support does not scale as a conversation channel.
When an IVR call is missed, an SMS with the callback link or missed-details is instant, guaranteed to arrive, and does not require WhatsApp installed. WhatsApp fallback is fine as secondary for users known to be on the channel.
Security and urgency conventions in India still centre on SMS. Users pay attention. Sending a fraud alert only on WhatsApp is risky because the user may not check for hours. Send on both, prefer SMS as the loud channel.
Every serious production system we run at BookMySMS uses both channels. The strategy is not "pick one." It is "use the right channel per use case, with fallback logic."
Layer 1: OTP and urgent security alerts on SMS. Universal reach, no app dependency, regulatory alignment. This is the always-on layer.
Layer 2: Transactional flows (order, delivery, appointment, support) on WhatsApp for opted-in users. Higher engagement, richer format, conversation-native. Fall back to SMS when WhatsApp delivery fails or user has not opted in.
Layer 3: Marketing on WhatsApp for engaged, opted-in segments only. Aggressive frequency capping. Never marketing to cold lists. SMS promotional deprecated to specific carrier or geo segments where WhatsApp reach is weaker.
Cross-channel handoff logic. If a WhatsApp message is not delivered within X minutes, send SMS. If SMS is filtered (DND), attempt WhatsApp. Track delivery, read, and click per channel per user, feed into next-channel decision for next send. This routing is standard in BookMySMS and adds materially to effective delivery rate.
Consent management as a first-class problem. Track explicit opt-in per channel per user. Store timestamp and source. Honour opt-out immediately on both channels. Under India's DPDP Act 2023 you owe the user a record of consent and a mechanism to revoke it. This is not optional. See our DPDP Act 2023 compliance guide for the details.
SMS via a primary aggregator (with fallback aggregator for network diversity) for OTP and urgent alerts. WhatsApp Business API via a Meta-authorised BSP for transactional and support flows. Unified messaging orchestrator that decides channel per message based on user preference, opt-in status, message category, and cross-channel fallback rules. Consent ledger and opt-out registry maintained per DPDP requirements.
SMS layer. Two aggregators for network redundancy. DLT-registered entity, roughly 40 active headers across client sub-brands, 300 plus registered templates. Average delivery rate 94-96%. Peak send capacity 500,000 SMS per hour.
WhatsApp layer. Meta-authorised BSP integration, 60 plus WhatsApp Business API numbers across clients, 200 plus approved templates, quality rating maintained green across all numbers. Support for interactive buttons, list messages, catalogues, and location messages.
Orchestration. Unified messaging API that clients hit with a single request; BookMySMS decides channel per message based on user preference, opt-in status, category, and fallback rules. Delivery, read, click tracked at message level and rolled up to per-user engagement scores.
Compliance. DLT registration handled per client entity. Meta template submission handled by BookMySMS team for clients. Consent ledger integrated with client's user database. DPDP-aligned data handling, breach notification workflow, opt-out honoured within milliseconds across both channels.
Typical mid-market client bill. D2C brand with 100,000 monthly active users: roughly Rs 60,000 to 1.2 lakh per month across both channels for a mix of OTP, order updates, delivery notifications, cart recovery, and support handoff. This is dramatically less than the same set of use cases on SMS-only (higher volume needed for equivalent engagement) or on WhatsApp-only (marketing conversation costs).
Questions we hear on nearly every discovery call about messaging channel choice.
Tell us your top 3 messaging use cases and expected monthly volume. We come back within 48 hours with a channel recommendation per flow, an estimated monthly cost, a DLT plus BSP setup checklist, and a launch timeline.