Omnichannel Messaging

Omnichannel messaging is not simply supporting many channels; it is treating them as one continuous conversation with a user, choosing the right channel per message and falling back gracefully when one doesn't deliver. The user experiences a coherent thread, not disconnected silos.

The motivation is that no single channel is best everywhere. SMS reaches everyone but is plain; WhatsApp and RCS are rich but require the user to be reachable there; voice and email serve different moments. Orchestration picks the best available option for each message and each market.

Doing this well means a shared identity for the user across channels, a policy for which channel to try first, and consistent branding and content so the conversation feels unified regardless of the transport.

SMS is the universal baseline: near-total reach, plain text, no rich media, and the encoding and segment rules covered elsewhere in the Academy. It is the natural fallback because it works when nothing else does.

WhatsApp Business supports rich media, buttons, and read receipts, but is governed by strict rules on when you may message a user and requires pre-approved templates for business-initiated conversations. RCS (Rich Communication Services) brings rich cards, suggested replies, and verified sender branding to the native messaging app, with SMS as its fallback.

Voice and email complete the picture — voice for OTP fallback and urgent alerts, email for longer-form or attachment-bearing content. Each channel's rules, not just its features, decide when it is eligible in an orchestration.

WhatsApp distinguishes user-initiated from business-initiated messaging. When a user messages your business, a 24-hour customer-service window opens during which you may reply with free-form messages. Outside that window, business-initiated messages must use pre-approved template messages.

This rule shapes both cost and design. Conversations are priced by category, and templates must be submitted and approved before use, so an omnichannel flow has to know whether the window is open before choosing WhatsApp for a given message.

Practically, this means tracking the last inbound message time per user and treating the window as a routing input: inside it, free-form WhatsApp is available; outside it, only a template — or a different channel — will deliver.

RCS upgrades the native SMS app with rich cards, carousels, suggested actions, and typing indicators, delivered under the GSMA RCS Universal Profile. For businesses, the standout feature is the verified sender: a branded, checkmarked identity that raises trust versus an anonymous short code.

Because RCS availability depends on the user's device, carrier, and settings, it is designed to fall back to SMS when RCS isn't available. A message can be authored once and delivered as rich RCS where possible and plain SMS otherwise.

That fallback behaviour makes RCS a natural fit for omnichannel: you gain richness and verified branding where the ecosystem supports it, without losing the universal reach of SMS where it doesn't.

A fallback waterfall is an ordered sequence of channel attempts with rules for escalation. For a notification you might try RCS, then WhatsApp, then SMS; for verification you might try flash call, then SMS, then voice. Each step should be time-boxed and confirmed by a delivery signal before deciding it succeeded.

The waterfall must respect each channel's eligibility rules — the WhatsApp window, RCS availability, sender-ID registration — and must avoid duplicate delivery of the same content across channels, which wastes money and confuses the user.

Instrument the whole thing: delivery rate, latency, and conversion per channel and per market feed the orchestration so it learns which order works where. A platform that unifies these channels behind one API — such as BroadNet's omnichannel product — is what makes this practical to operate.