Single-Flow Multi-Step Campaign Orchestration
The choice ExpertFlow made
ExpertFlow authors an entire outbound campaign as a single multi-step, omnichannel flow in Conversation Studio — the same flow-authoring environment that defines inbound IVR, bot, and routing logic — rather than as a dialer configuration wired out to separate IVR, bot, and message-dispatch subsystems. Each step branches on any call-progress outcome (live answer, answering machine, busy, no-answer) and routes that outcome to the right next action: invoke a bot/voicebot (for example, leave a personalised voicemail and log a callback request), escalate to a live human agent on live answer, or emit a follow-up on a different channel (an SMS or email with a renewal link). Bot-or-human is a per-step decision inside one flow, and every step writes to the same unified conversation object (see [[axiom-00009]]) linked to the contact record and the originating campaign — so the campaign journey is one authored artifact and one reportable record, not an outcome reconstructed by joining across tools.
The alternative (who made it and why it exists)
The prevailing outbound architecture composes a campaign from several distinct subsystems. Cisco Outbound Option supports sequential dialing (up to ten numbers per record) and a VRU/IVR-transfer mode, but the unattended path runs in CVP/IP-IVR scripts authored separately from the agent-reservation script, and there is no native digital follow-up step — SMS/email is a bolt-on. Genesys Cloud classifies the call with a call-analysis response set and can hang up on an answering machine or transfer a live answer into an Architect "outbound flow" — but the bot, the dialer, and any SMS/email dispatch are separate products stitched together, and the agentless and agent-assisted paths are configured apart. The broad CCaaS suites (Five9, Avaya, Zoom, 8x8) treat outbound as one module among hundreds, optimised for predictive-dial throughput rather than for authoring a branching bot-or-human-or-digital journey as a single artifact. The split persists because outbound grew up as a telephony-pacing discipline (predictive dialing, call-progress analysis) and the omnichannel and bot layers were added later as adjacent products — it was rarely worth refolding them into one campaign-flow authoring model.
The scenario where our choice wins
A multi-touch campaign that must adapt per contact and per outcome across channels: an insurance renewals programme against 10 000 policyholders where live answer routes to a human agent, answering machine triggers a voicebot that leaves a personalised message and books a callback, and no-answer sends an SMS with a renewal link — defined once and changed in one place. With a stitched architecture, inserting or reordering a step (adding an email before the SMS, swapping the voicemail bot) means coordinating changes across the dialer config, the IVR/flow tool, the bot, and the message dispatcher — each with its own model, its own reporting, and its own failure modes — and the campaign outcome is reconstructed by joining across systems. ExpertFlow's single-flow model lets a supervisor author and revise the whole journey in Conversation Studio and read per-step outcome breakdowns against one conversation object in real time. The edge is operational agility and unified per-step reporting on multi-step omnichannel campaigns — not raw dial throughput, where a dedicated predictive dialer may still lead.
The one-sentence axiom claim
"ExpertFlow authors an entire outbound campaign as one multi-step, omnichannel flow in Conversation Studio — the same engine that defines inbound IVR, bot, and routing — so any branch (live answer, answering machine, busy, no-answer) can invoke a bot, route to a live human, or emit a follow-up on another channel (SMS/email) as a first-class campaign step over one unified conversation object, unlike Cisco Outbound Option (separate agent-reservation and CVP/IP-IVR-transfer scripts, no native digital step), Genesys Cloud (a call-analysis response set transferring to a separate Architect outbound flow, with bot and message dispatch as distinct products), or broad CCaaS suites (Five9, Avaya, Zoom, 8x8) where outbound is a throughput-optimised module among hundreds — which means a contact centre running multi-touch, bot-or-human, cross-channel campaigns authors and revises the whole journey in one place and reports per-step outcomes against a single conversation object, instead of stitching and reconciling a dialer, an IVR flow tool, a bot, and a message dispatcher."
Competitors for the relevant solution pattern(s)
| Competitor | Their approach | Where our axiom creates an edge |
|---|---|---|
| Cisco Outbound Option | Sequential dialing (up to 10 numbers/record) + a VRU/IVR-transfer mode; the unattended path lives in CVP/IP-IVR scripts authored separately from the agent-reservation script; no native digital follow-up step | EF authors live-answer→human, machine→voicebot, no-answer→SMS as one flow; Cisco needs separate scripts per path and a bolt-on for the digital step, with no single conversation object across them |
| Genesys Cloud | Call-analysis response set hangs up or transfers a live answer into a separate Architect outbound flow; bot and SMS/email dispatch are distinct products, and agentless vs. agent paths are configured apart | EF folds bot-or-human and cross-channel follow-up into one campaign flow over one conversation object; Genesys reconstructs the journey across subsystems and configures the two paths separately |
| Broad CCaaS suites (Five9, Avaya, Zoom, 8x8, …) | Outbound is one module among hundreds, optimised for predictive-dial throughput; multi-step omnichannel journeys are assembled from separate channel and bot tools | EF treats bot-or-human-or-digital branching as native campaign authoring with single-artifact revision and per-step reporting; suites lead on raw pacing, EF on multi-touch orchestration agility |