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 Sales Ops Manager
Orchestration is the best-evidenced area: branching on real-time behaviour and attributes, exit criteria the moment a contact converts, versioning with post-launch edits, testing at journey, step and message level, and frequency capping on or across channels. What pushed it high is programme-level control — priority rules set once and applied across every campaign and Canvas, plus global control groups for uplift measurement. I held back a point because per-contact journey state and per-step reporting appear only as a generic analytics statement. 2 3 4 8