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 captured pages document a visual drag-and-drop flow builder with real-time behaviour triggers, conditional splits and custom waits, webhook steps that POST to any API endpoint with a testable request, and A/B testing of flow logic with revenue tracked per flow. The question that decides real programmes — what happens when one contact qualifies for several flows at once — goes unanswered: I found no public information on frequency capping, suppression across flows, per-step reporting or safe editing of a live flow. 10 11 14 12