Skip to content
The InfiQ GlossaryFeature

CPaaS & channels

Omnichannel Orchestration

Choosing the best channel for each user, message and moment across WhatsApp, SMS, RCS, email and voice while keeping one customer context.

Also called: Channel orchestration · Cross-channel orchestration · Journey orchestration · Multichannel orchestration

InfiQ Glossaryreviewed Practitioner

What is omnichannel orchestration?

Omnichannel orchestration is the decision layer that chooses which channel — WhatsApp, SMS, RCS, email, push or voice — carries each message to each customer, and when, while every channel reads from and writes to one customer profile. Instead of marketing blasting SMS while support answers WhatsApp separately, an orchestration engine looks at the person, the message and the moment and picks the channel most likely to achieve the goal at an acceptable cost.

The inputs are concrete. Consent and preference: which channels has this person opted into, and which did they last reply on? Reachability: is the number on WhatsApp, is the handset RCS-capable, did the last email bounce? Content: a PDF invoice, a carousel or reply buttons rule out plain SMS. Urgency and cost: an OTP needs the fastest reliable channel, while a newsletter can wait for the cheapest channel the person actually reads. The engine then sequences: send on one channel, wait for a delivered or read status, and escalate to SMS or a call only if the goal is still open.

It is wider than a fallback channel, which is a single failover rule triggered by a failed or undelivered message, and different from an omnichannel inbox, which is where agents answer conversations from many channels. Orchestration sits upstream of both. It plans the whole journey across channels, cancels messages already made pointless by a reply elsewhere, and makes sure a customer who answered on WhatsApp is not then chased by SMS and email about the same thing.

Key takeaways

  • Omnichannel orchestration decides, per user and per message, which channel to use and when, while every channel shares one customer context.
  • Its inputs are consent, preference, reachability, what the content needs, urgency and cost per delivered message.
  • A fallback rule such as "WhatsApp, then SMS after 15 minutes" is one tactic inside orchestration, not the whole strategy.
  • Consent is per channel: a WhatsApp opt-in does not cover promotional SMS, which needs DLT-recorded consent and DND checks in India.
  • Measure each journey's outcome — paid, booked, resolved — and its cost, not opens per channel.

Figure 1

Ten messages, five channels: which goes where?

10 / 10

Only agents with the required skill are eligible; the least busy of them wins.

Incoming · 0 left

  1. All 10 conversations have been routed.

Conversation 10 of 10 · Skills-based

Kavya · rate your order(needs Buttons)goes toWhatsApp

Skills: needs Buttons; of WhatsApp and RCS, WhatsApp is least busy.

  • WhatsApp

    3 of 4 open

    • Rich media
    • Buttons
    • OTP
    • Invoice PDF
    1. Kavya · order shippedneeds Rich media
    2. Mohan · login OTPneeds OTP
    3. Kavya · rate your orderneeds Buttons

  • SMS

    2 of 2 open

    Full
    • Feature phone
    • OTP
    1. Madhu · payment dueneeds Feature phone
    2. Madhu · reminderneeds Feature phone

  • RCS

    2 of 2 open

    Full
    • Rich media
    • Buttons
    1. Kavya · arriving todayneeds Buttons
    2. Meena · new offerneeds Rich media

  • Email

    2 of 3 open

    • Invoice PDF
    • Prefers email
    1. Arjun · invoiceneeds Invoice PDF
    2. Arjun · statementneeds Prefers email

  • Voice

    1 of 2 open

    • Prefers calls
    • Feature phone
    1. Lakshmi · appointmentneeds Prefers calls

Waiting · 0

  1. Nobody waiting: every conversation found an agent.
Same 10 conversations, each strategy
StrategyRoutedWaitingSkill mismatches
Skills-based1000
Sticky1001
Round-robin1007
Channels stand in for agents, each message's deciding need for a skill. Skills-based routing matches each need to a capable channel; sticky keeps a customer on their last channel; round-robin rotates blindly.

Conversation 10 of 10, Kavya · rate your order: Skills: needs Buttons; of WhatsApp and RCS, WhatsApp is least busy.

Why it matters

Why does omnichannel orchestration matter?

Each channel is strong at something and weak at something else, and they cost very different amounts per delivered message. Using one channel for everyone either overpays — WhatsApp marketing templates at ₹0.94 each to people who never read them — or under-delivers — SMS links to people who would have tapped a WhatsApp button. Orchestration lowers cost per outcome and stops the duplicate, cross-channel nagging that drives opt-outs and blocks.

Example: Report-ready notices at a diagnostics lab

A Delhi diagnostics lab tells patients when reports are ready. Patients with a WhatsApp opt-in get a utility template with the PDF and a "Book follow-up" button at ₹0.19 per delivered message; if no delivered status arrives within 15 minutes, a DLT-registered SMS with a whitelisted link goes out. Patients who have asked for calls get a short voice call, and corporate clients receive reports by email as their contracts require. When a patient taps the WhatsApp link, the pending SMS is cancelled, and the follow-up booking lands on the same patient record the call centre sees.

— Report-ready notices at a diagnostics lab

How does omnichannel orchestration work?

  1. Unify the profile

    Join identities — phone number, WhatsApp ID, email, app user ID — into one customer record with consent per channel, stated preferences and recent engagement.

  2. Define the goal and the guardrails

    For each journey, name the outcome (payment made, slot booked) and the constraints: allowed channels, quiet hours, frequency caps across channels and a maximum cost.

  3. Choose the first channel

    Score the eligible channels on consent, reachability, content fit, urgency, past engagement and cost, then send on the best one.

  4. Listen to statuses and replies

    Use delivered and read webhooks, link clicks and replies to decide whether the goal is met or the next step is due.

  5. Escalate or stop

    If the goal is still open when a timer runs out, move to the next channel; once it is met anywhere, cancel every pending message in the journey.

  6. Measure per journey

    Report cost per outcome and conversion by path (WhatsApp only, WhatsApp then SMS, call) and feed the results back into the scoring.

Omnichannel orchestration in code

type Channel = "whatsapp" | "rcs" | "sms" | "email" | "voice";
const CHANNELS: Channel[] = ["whatsapp", "rcs", "sms", "email", "voice"];
 
export function chooseChannel(p: Profile, m: Message): Channel | null {
  const eligible = CHANNELS.filter(
    (c) => p.consent[c] && p.reachable[c] && fits(m, c) && !inQuietHours(p, c),
  );
  if (eligible.length === 0) return null; // nobody to send to: record why
 
  const score = (c: Channel) =>
    (p.lastRepliedOn === c ? 3 : 0) +            // preference shown by behaviour
    p.engagement[c] * 2 +                        // recent read / click rate, 0–1
    (m.urgent ? SPEED[c] : 0) -                  // OTPs and alerts favour speed
    COST[c][m.category] / m.valueOfOutcome;      // cost relative to what it is worth
 
  return eligible.sort((a, b) => score(b) - score(a))[0] ?? null;
}

Eligibility first (consent, reachability, content fit), then a score that balances preference, speed and cost.

Common mistakes with omnichannel orchestration

  • Assuming one consent covers every channel

    A WhatsApp opt-in does not cover promotional SMS, which in India needs consent recorded on DLT and DND scrubbing, nor marketing email. Track consent per channel and purpose.

  • Chasing on every channel at once

    Sending the same reminder on WhatsApp, SMS and email together triples cost and irritates people. Sequence with timers and cancel the rest once the goal is met.

  • Optimising channels in isolation

    A channel's open rate says little if another channel converted the same person. Attribute outcomes to the journey and the path taken.

  • No shared context for agents

    If a customer replies on WhatsApp to an SMS campaign, the agent must see both. Write every message and reply to one timeline.

Best practices for omnichannel orchestration

  • Start with two channels and one journey; add channels once measurement works.
  • Let a reply on any channel become the preferred channel for the next message.
  • Set one frequency cap per person across all channels, not one per channel.
  • Use read statuses where they exist to avoid needless fallbacks.

Omnichannel Orchestration FAQs

What is the difference between omnichannel orchestration and a fallback channel?
A fallback channel is one rule: if a message fails or is not delivered in time, resend it elsewhere. Orchestration plans the whole journey for each person — first channel, timing, escalation and when to stop.
Is omnichannel the same as multichannel messaging?
No. Multichannel means a business uses several channels; omnichannel means those channels share one customer context, so each message knows what happened on the others.
Should WhatsApp or SMS go first?
It depends on the person and the message. WhatsApp usually suits opted-in customers and rich content; SMS reaches every phone without data and needs DLT registration in India. Let consent, past engagement and urgency decide.
Do I need a customer data platform for omnichannel orchestration?
Not necessarily, but you need a unified profile. A customer data platform is one way to build it; a CRM holding identities, consent per channel and engagement history can also work.

See InfiQ pricing

* Per-message rates for India, ex-GST: marketing, utility and authentication effective 1 July 2026; service messages ₹0.145 since 1 October 2026 (they were ₹0 until 30 September 2026). Volume commitments earn discounts — final rate is confirmed on your account; applicable GST extra. Rates for other countries differ (see the international rate table on /pricing).

Try it on the official WhatsApp Business API

InfiQ is an official Meta Business Partner. Start a 7-day free trial — no card needed — and see this running on your own number.

Start free trialBrowse all 550 terms