Omnichannel Orchestration
What the domain covers
Omnichannel orchestration coordinates messages across email, SMS, push, web, and other channels so a contact receives a coherent, timely sequence rather than disconnected blasts. The candidate must understand journey design (entry criteria, steps, waits, branches, exits), channel selection, frequency and fatigue management, and cross-channel coordination to avoid duplicate or conflicting outreach.
Concepts to master
- Entry and exit criteria: who enters, and what removes them (conversion, opt-out, or a competing journey).
- Wait steps and timing: delays between touches, and time-zone or send-window rules.
- Branching logic: splitting on behavior or attributes mid-journey.
- Channel fallback: email, then SMS, then push, based on preference and engagement.
- Frequency caps and suppression: preventing over-contact across journeys.
- Goal and conversion tracking: measuring journey success at the step and journey level.
Traps in questions
Frequent traps: assuming a contact can be in two conflicting journeys at once (priority and suppression usually prevent this), and forgetting that exit criteria should fire on conversion so a buyer stops receiving nurture. Another trap is ignoring frequency caps when adding a new channel - more channels can mean more fatigue, not more reach. Watch for questions that treat a wait step as optional or that ignore send-window rules.
Worked example
A welcome journey: entry = new signup; step 1 email immediately; wait 2 days; branch - if opened, send SMS offer; if not, send reminder email; exit on first purchase or unsubscribe. Rule of thumb: always define the exit before the steps. If the contact converts after step 1, the journey ends and no SMS is sent, even if the branch condition was met.
Key points
- Define entry and exit criteria before designing steps.
- Conversion should end a nurture journey.
- Branch on behavior or attributes mid-journey.
- Frequency caps prevent cross-journey over-contact.
- More channels can increase fatigue without coordination.
- Send windows and time zones affect timing.