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 Solution Architect
A visual journey builder, event-triggered campaigns from the unified profile, cross-channel next-best-step decisioning and a smart frequency policy are all on the record, which is more orchestration surface than most vendors publish. We found no public information on waits and goals, entry and exit conditions, per-contact journey state, versioning of a live journey, or what happens when several journeys claim the same person — the collision case that decides whether a programme survives contact with reality. 1 2 3 4 8