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 Solution Architect
A visual builder with split and branching paths, triggers on contact-field states, segment moves, deal-stage changes and site events, and goals that trigger follow-up campaigns when missed is all documented, plus event-driven entry from over 900 external apps and API and webhooks on every plan. Goal tracking is documented as showing who moves through the funnel and where people drop off, with business goals capped per plan at 15 to 200 active. What we never found is arbitration: we found no public information on what happens when a contact qualifies for several journeys at once, on frequency capping or suppression across journeys, or on safe editing and testing of a live journey. 4 5 2