Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Skeptic
Journeys are real and cross-channel — behavioural triggers from views, carts, wishlists and price-drop alerts, plus SMS keyword replies that start an email, a push, a segment or a suppression, are all documented. But none of the captures shows branching, waits, goals, or what happens when one contact qualifies for several journeys at once, and the Agentic AI module offers to build the workflow without showing what a workflow can contain. That sits between a triggered sequence and a documented builder. 1 3 5