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
The visual builder is real and documented — triggers on lists, smart segments and form submissions, condition splits, delays and wait-until-filter, exit ejection, and version control with revert, plus journeys that can start from new Salesforce records and activities. What I cannot see is the collision handling: the captured pages show ejection of unsubscribed contacts but no cross-journey suppression, priority when one contact qualifies for several journeys, frequency capping, or per-step reporting — just reports and dashboards at journey level. That is a competent programme-level engine, not yet one decision layer. 3 5 6 11 12