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 Skeptic
The flow builder is real and documented: Event and Segment Event triggers on a visual canvas, if/else Check Condition steps on field values, End Flow exits, and a Receive Webhook trigger that lets outside systems start a flow. Waits are implied by trial-expiration and inaction-triggered follow-ups rather than named as a step. What we found no public information on is the discipline between journeys — frequency capping, priority when a contact qualifies for several at once, and safe editing of a live flow. 1 4 9