Fallback Routing: SMS, WhatsApp, and RCS
Fallback Routing sends the same campaign on a backup channel when the first channel does not reach the customer the way you expect.
Example: try WhatsApp first; if the message is Failed, send SMS; if that also fails, send RCS.
Portal copy: Route failed deliveries across SMS, WhatsApp & RCS in sequence.
Portal prefix: /fallback/...
| Screen | What you do |
|---|---|
Fallback library (/ or /fallback-list) | List, search, view, delete fallback rules. See counts by SMS / WhatsApp / RCS |
| Create Fallback | Name the rule, pick primary channel, then configure each step |
Set fallback (/set-fallback) | Drag-and-drop the channel order; configure message/template per step |
This is not the same as an RCS capability check (whether the handset can receive RCS). Capability is documented on RCS. This page is campaign failover across channels.
What Fallback is
A fallback record has:
| Field | Meaning |
|---|---|
fallbackName | Display name |
primaryChannel | First channel in the sequence (SMS, WhatsApp, or RCS) |
steps | Ordered list of channels |
sms / whatsapp / rcs | Per-channel payload (gateway, sender/bot, template, message, statuses that trigger the next hop) |
You also see Active / Inactive, created date, and can View or Delete.
The rule does not send by itself. Compose still starts the primary campaign. Fallback only walks the remaining steps when a status you selected occurs.
Get ready
- The account must have the channels in the chain (SMS and/or WhatsApp and/or RCS).
- Each step needs a valid gateway / sender / bot / template for that channel — the same setup as a normal send.
- Keep wallet credits on every channel in the chain. A fallback hop is billed like a normal send on that channel. See Account.
Create a fallback
- Open Fallback Routing.
- Click Create Fallback.
- Enter Fallback Name (for example
WhatsApp → SMS failover) — stored asfallbackName. - Choose Primary Channel (
SMS,WhatsApp, orRCS) — this is step 1 (primaryChannel). - Click Proceed.
- On the next screen, tabs are the steps in order. Drag to reorder. Remove a step if it is not needed. Deleted steps can be dragged back from the trash area.
- For each step after the primary, choose when to fire (see Status triggers).
- Configure that step like a normal campaign (Configure each step).
- Save. The rule appears in the library as Active.
Status triggers
For each hop after the primary, pick the campaign statuses that should start the next channel:
Delivered, Failed, Sent, Read.
Typical pattern: trigger the next channel on Failed. Some teams also include Sent when they never receive a delivery receipt.
If the statuses you selected never occur, the next hop never sends. Example: you only selected Read, but the first hop Failed — SMS/RCS will not run.
Configure each step
| Step | What to set |
|---|---|
| SMS | Gateway, sender ID, text / unicode message, optional DLT template |
| Connected number, Approved template, variables / media | |
| RCS | Bot (botId), template (templateName), content |
Use the same quality bar as a standalone campaign. An unapproved WhatsApp or RCS template will fail that hop even if the primary send worked.
Do not put the same channel twice as the only hops (WhatsApp → WhatsApp with no SMS or RCS). A fallback is useful when the next channel is different.
Use it on compose
- Open SMS, WhatsApp, or RCS compose / broadcast.
- Turn on Enable Fallback.
- Pick the rule you created.
- Send or schedule as usual.
The platform:
- Sends the primary campaign as usual.
- Watches delivery status (Sent / Delivered / Read / Failed).
- If a status you selected occurs, sends the next channel in
stepsusing that step’s template/message. - Repeats for later hops if those statuses also match.
Blocked numbers and spam rules still apply on each hop.
Credits and reports
Each hop that actually sends deducts wallet credits for that channel. If the backup wallet is empty, the primary may succeed and the fallback hop fails. Check the header balance on Account.
Reports stay on each channel:
- SMS Message / Number report
- WhatsApp Message / Number report
- RCS Message / Number report
There is no separate “fallback report” screen. Follow the recipient across those reports using the campaign name and number.
Typical mistakes
| Situation | What to do |
|---|---|
| Fallback enabled on compose but no rule selected | Pick the Active rule from the list |
| Next-step statuses never match | Include Failed (and Sent if receipts are slow) |
| WhatsApp / RCS step not Approved | Approve the template before you rely on that hop |
| Not enough wallet on the backup channel | Recharge that currency on My Wallet |
| Primary and backup are the same channel twice | Add a different channel as the next hop |
| Confusing this with RCS capability | Capability checks the handset; this page fails over the campaign |
Next: Account for wallet and API keys, then compose on SMS, WhatsApp, or RCS.