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
The journeys documentation is genuinely operational: triggers on events, objects, relationships, dates and forms, filter conditions retried for up to 30 minutes, a 24-hour wait setting, rate limiting, manual journey exits, and a per-person Journeys tab showing deliveries, conversions and entry/exit. That is more than a visual builder with waits, but we found no public information on what happens when one person qualifies for several journeys at once, cross-journey frequency capping, or safe editing of a live journey, so I stop short of the top band. 3 4 4 1