Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning 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 a journey a colleague can read months later without a diagram.
The Skeptic
A drag-and-drop builder with multi-branch journeys, event triggers like price-drop and back-in-stock, frequency caps and A/B testing of entire journey flows — the middle of the ladder is genuinely evidenced. But we found no public information on waits, entry and exit conditions, where a contact currently sits, versioning a live journey, or priority when a person qualifies for several journeys; the collision handling that decides whether this survives production is not shown on any public page. 3 4 8