Omnichannel messaging is a way of running customer-facing channels so that one account, one sender identity, and one conversation timeline carry every channel — SMS, voice, email, WhatsApp, RCS, wallet passes, USSD, and web chat — instead of each channel running as its own silo. The definition has three halves, and all three must hold or the stack is multichannel, not omnichannel: one account (the channels are provisioned under a single organization, not four vendor logins), one sender identity (the same brand registration, verified number, or sender name faces the customer on every channel), and one timeline (every conversation, call, and reply lands in a single record a human or AI agent can read per customer). This guide defines the term properly, contrasts it with the multichannel posture, maps the channels and the read model that Orbit ships them on, and closes with the case for staying on one channel.
Why it differs from multichannel — routing, consent, and suppression unify
Multichannel means several channels exist; omnichannel means they coordinate. Three moves do the coordinating:
Unified routing across channels. A blended agent answers voice calls and chat threads on the same shift, so assignment has to be a cross-channel decision, not two isolated queues racing to the same person. Orbit holds that with a single reservation store — voice dispatch and digital routing reserve a slot atomically against a tenant-set blended ceiling, so two channels cannot double-book the same agent. The mechanics live in the capacity and reservation model.
Fallback that is a designed chain, not a hope. When the primary channel cannot carry a recipient — an RCS capability check, a provider pool exhausted, an unregistered OTT sender — the router advances through an organization-level ordered chain (RCS → SMS, Viber → WhatsApp → SMS) instead of failing silently. The same chain applies across every send path, from API sends through campaigns to inbox replies, per the cross-channel fallback model.
Unified consent and suppression. A customer who replies STOP to an SMS, or opts out on WhatsApp, should stop everywhere. Orbit enforces send-gating per channel against the same contact record — and the fallback compliance matrix scores each channel across the three compliance planes (registration, send windows, opt-in regime) so the next channel in a chain is one your tenant is actually permitted to use. Those controls are tenant-owned: Orbit carries the settings you set; which posture is adequate for your traffic remains your call. A vendor whose opt-outs sync overnight between channel silos is running multichannel with a batch job.
The channel map — Orbit's first-registered channels
Omnichannel is defined over capability first: a channel that exists on Orbit is wired to be reachable through the same sender identity, the same org-level chain, and the same timeline, not bolted on as a vendor integration. Per-channel reference lives under docs/channels:
- SMS — the universal reach channel and every chain's terminal hop; per the SMS docs, region registration (US 10DLC, sender IDs) is tenant-owned.
- Voice — inbound IVR through outbound campaigns, recorded and transcribed; see the voice docs.
- Email — the asynchronous long-context channel, still first-class on the same timeline; per the email docs.
- WhatsApp — the conversational opener for WhatsApp-dominant markets, templates + session windows; per the WhatsApp docs.
- RCS — the carrier-verified rich opener, capability-checked per recipient before send; per the RCS docs.
- Wallet passes — Apple and Google Wallet as a persistent-credential channel for boarding passes, coupons, and loyalty; per the wallet-passes docs.
- USSD — session-based menus where reach includes feature phones and offline handsets; per the USSD docs.
"Orbit-first-registered" means these channels are provisioned against your tenant's sender identity from day one, so the channel-selection work is a posture question, not an integration project.
Choose the opener deliberately — the channel-selection matrix
Which channel opens the conversation is a per-use-case, per-market decision — and it belongs to the tenant, not the platform. Four columns decide most opening moves: reach-dominant regions, consent regime, sender-registration burden, and the reach geography of the audience. The channel-selection matrix scores SMS, WhatsApp, RCS, Apple Messages for Business, and live chat across those columns and closes with a decision tree — the strategic sibling to the fallback matrix that governs what happens after the open.
Where the shared timeline lives — one Interactions read model
The third half of the definition is the timeline. Every conversation and every call on Orbit reads back through the Interactions surface — a unified, recency-ordered list that projects conversations and call logs onto one row shape with a channel discriminator, a contact link, and a back-link to the native surface. There is no separate storage to keep in sync; the unified list is a read projection over the two source stores, per the unified interactions model. For the operator's view, the shared omnichannel inbox is the entry-level CCaaS that works that same timeline per queue.
When not to go omnichannel
One-channel genuinely fits real traffic. A notification-only OTP lane: SMS alone suffices, declared so explicitly in the fallback matrix since there is no fallback beneath SMS. A pure inbound service desk where customers always initiate: the live-chat widget alone may answer it, per the live-chat explainer. A single-campaign, single-market SMS program: if the audience lives in one channel by definition, fabricating omnichannel is overhead, not posture. Omnichannel earns its cost when a contact's journey genuinely spans channels, or when reach, consent, or capability has to be solved per channel by a shared chain.
Frequently asked questions
What is omnichannel messaging, in one sentence?
One account, one sender identity, one conversation timeline across every channel — SMS, voice, email, WhatsApp, RCS, wallet, USSD — so a customer can move between channels and the conversation follows them.
How is omnichannel different from multichannel?
Multichannel means channels exist side by side; omnichannel means they share routing, consent and suppression, and a unified timeline. A multichannel vendor syncs records or skips suppressions across silos; an omnichannel platform resolves identity and honors the opt-out once, everywhere.
Which channels does omnichannel cover on Orbit?
All Orbit first-registered channels: SMS, voice, email, WhatsApp, RCS, wallet passes, USSD — each provisioned under one account with its own reference under docs/channels.
Where does the shared conversation timeline live?
On Orbit's Interactions surface, a unified read model that projects conversations and call logs onto one row shape — see the interactions-unified-model concept. The operator view that works it is the shared omnichannel inbox.
When should you not go omnichannel?
When one channel genuinely fits: a notification-only OTP lane is SMS alone; a purely inbound service desk may need only the live-chat widget; a single-market SMS program is fine as a one-channel posture. Omnichannel earns its cost when journeys genuinely span channels or a shared chain has to solve reach and consent per channel.