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 Demand Gen Lead
The builder is real: drag-and-drop workflows with split and branching paths, entries on contact-field state, segment moves, deal-stage change and website actions, and goal tracking that shows who moves through the funnel and where they drop out. Entry from external systems is documented too, with webhooks and over nine hundred apps triggering automation actions. I found no public information on frequency capping, suppression across journeys, priority handling when a contact qualifies for several, or safe editing of a live journey — and Starter's cap of five actions per automation means usable orchestration starts a rung up. 4 5 7 2