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 Sales Ops Manager
Real-time event triggers off the unified customer view, a visual journey builder, and a decisioning layer that picks the next best step across web, SMS and ads — with purchase-based ad suppression and an engagement-based frequency policy — are all on the public pages. We found no public information on versioning of a live journey, per-contact journey state, holdout groups, or what happens when two journeys want the same contact beyond that frequency policy. 1 2 4 8