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
A visual journey builder covering email, SMS, push and in-app from a single studio, triggered by real-time behaviour with journeys that pivot when a user stalls, plus A/B testing at each workflow stage — that is real orchestration. What I could not find is the arbitration layer: nothing on waits, goals or exit conditions, frequency capping, or what happens when the same contact qualifies for two journeys at once, which is exactly where my pipeline reports start lying to me. 1 3 6 8