Interactive guide
Which messaging channel fits your message?
Answer four short questions to see which channel to start with and which to keep as fallback. It is a starting point built on how the channels differ, not a quote or a promise about coverage.
The short version
The rules behind the guide
The same rules as a table, for when you would rather read than click.
| Your situation | Start with | Fallback |
|---|---|---|
| One-time passcodes, urgent alerts, or anything that must reach everyone | SMS | None needed |
| Order, delivery and booking updates | SMS, or RCS where you want buttons and branding | SMS |
| Promotions with images and buttons to customers who have opted in | RCS | SMS |
| Ongoing conversations with customers who use WhatsApp and have opted in | SMS |
Use the rules as a starting point. The right mix depends on your countries, on which channels your recipients use and have opted in to, and on what the message needs to contain. In the API you set one primary channel and any fallback channels; ZafeConnect’s routing then selects the best available route for each message.
Try it
Answer four questions
The recommendation appears when all four are answered.
The picker needs JavaScript. The table above has the same rules.
FAQ
Questions about choosing a channel
Can I use more than one channel for the same message?
Yes. In the API you set a primary channel and fallback channels in order; if the primary fails, the next one is tried.
Who decides which channel a customer gets?
You choose the primary channel and the fallbacks. ZafeConnect’s routing then selects the best available route and, where RCS or iMessage can reach the customer, the most cost-efficient delivery method.
Is RCS available everywhere?
No. RCS depends on the device, the operator and the country, and support is expanding. That is why SMS is usually kept as the fallback.