Fallback Channel
A fallback channel is the backup route a business uses to reach a customer when the primary channel — WhatsApp — cannot deliver the message. If a recipient never activated WhatsApp on that number, has an outdated app, blocked the business, or the template simply fails to deliver, the intended notification would otherwise vanish silently. A fallback channel catches that gap by re-routing the same message content to an alternative like SMS, so time-critical alerts (OTPs, order updates, appointment reminders) still land. For Indian businesses running WhatsApp at scale, understanding fallback logic is the difference between a delivery rate you can trust and one that quietly leaks customers.
In one line
A fallback channel is a secondary delivery route — usually SMS — triggered when a WhatsApp message can't reach the user, ensuring time-sensitive notifications still arrive.What a fallback channel actually is
In messaging terms, a fallback channel is any secondary path that carries a message when the preferred path fails or is unavailable. On the WhatsApp Business API, WhatsApp is almost always the primary channel because it is cheaper per delivered message than SMS, richer (buttons, media, lists), and better read. But WhatsApp cannot reach every number every time: the recipient may not have a WhatsApp account, may be on a device or region where delivery is blocked, or may simply have connectivity issues at the moment you send. The fallback channel is the pre-arranged Plan B that ensures the underlying message — a one-time password, a shipment update, a payment reminder — still gets through by another route rather than being dropped.
- Primary channel: WhatsApp (rich, high open rates, lower cost per delivered message)
- Fallback channel: typically SMS, occasionally another reachable route
- Trigger: a delivery failure or 'undeliverable' signal from WhatsApp
- Goal: preserve delivery of time-sensitive, transactional messages
Why it matters for Indian businesses
India has hundreds of millions of WhatsApp users, but not universal coverage — and even active users occasionally miss messages. For a bank sending an OTP, a pharmacy confirming an order, or a logistics firm sharing a delivery slot, a silently dropped WhatsApp message is a failed transaction, a support ticket, or a lost sale. A fallback strategy protects the parts of your funnel where delivery is non-negotiable. It also protects reputation: customers judge you on whether the reminder arrived, not on which pipe carried it. Getting fallback right lets you lean confidently on WhatsApp as your default while keeping a safety net under your most critical flows.
How fallback works in practice
A fallback flow watches the delivery signal returned after you send a WhatsApp template. WhatsApp reports whether a message was accepted, delivered, or failed, and it surfaces specific error reasons — for example, that the number is not a valid WhatsApp user or that the message could not be delivered. Your system reads that signal and, based on rules you define, re-sends the same content over the fallback channel. Well-designed fallback is deliberate rather than reflexive: you decide which message categories qualify, how long to wait for a WhatsApp delivery confirmation before switching, and whether to fall back at all for non-urgent marketing.
- Send the WhatsApp template as the primary attempt
- Read the delivery status and any failure reason WhatsApp returns
- Apply your rules: which messages fall back, and after what wait
- Re-send equivalent content via the fallback channel (e.g. SMS) if it qualifies
- Log both attempts so reporting reflects true end-to-end delivery
Cost and billing considerations
Every channel bills separately, and the two do not share a rate card. Since 1 July 2025, WhatsApp charges per delivered message by category — marketing, utility, or authentication — rather than by conversation, and the free 24-hour service window lets you reply to a customer-initiated conversation without a template charge. SMS, by contrast, has its own per-message pricing set by operators and aggregators, and it is generally more expensive than an equivalent WhatsApp utility or authentication message. That asymmetry is the whole economic case for fallback: keep the cheaper, richer WhatsApp path as your default, and spend on SMS only for the fraction of sends that genuinely fail. Falling back indiscriminately erases the savings, so scope fallback to messages where delivery is worth the premium. InfiQ shows transparent ₹ pricing on Meta's live WhatsApp rate card (ex-GST), so you can model exactly what your primary and fallback mix will cost.
Common mistakes to avoid
The most frequent error is treating fallback as an automatic mirror — copying every WhatsApp send to SMS regardless of whether the first attempt succeeded — which multiplies cost with no benefit. Another is falling back on marketing blasts, where a dropped promotional message rarely justifies the SMS spend and can feel intrusive to the recipient. Teams also forget consent: the customer's opt-in and any regulatory rules (such as DLT registration for SMS in India) apply independently on the fallback channel. Finally, many businesses fall back too fast, switching before WhatsApp has had time to report a genuine delivery, and end up double-messaging the same person.
- Mirroring every message to SMS instead of only failed, qualifying ones
- Falling back on low-urgency marketing where the extra cost isn't justified
- Ignoring separate consent and India DLT/registration rules on SMS
- Switching before WhatsApp confirms failure, causing duplicate messages
- Not logging both attempts, so delivery reports overstate or understate reach