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 drag-and-drop editor with behaviour and tag triggers, configurable waits, linkable multi-step automations and twenty-plus prebuilt journeys is documented, and the tier pages show where automation starts (one automation in the free tier, unlimited in the paid one). We found no public information on branching, goals and exit conditions, or what happens when a contact qualifies for several journeys — and the captured help page states that bulk REST transfers deliberately do not start a tag-triggered chain, which would silently break CRM-driven onboarding flows. 1 4 5 11