Can I blast my whole list with an announcement?

No. Broad sending happens only through a flow you explicitly enable; every message remains an individual, traceable send.

How is this different from a campaign tool?

The audience is evaluated at dispatch, each recipient runs on their own clock, and the path can branch on current product state.

What if someone matches two flows at once?

Enrolment honours priority and exclusivity, so overlapping triggers don't turn into two emails in the same hour. You decide which programme wins when they collide.

Can someone get the welcome sequence twice?

Not unless you allow it. With re-enrolment off, the existence of a past run is what blocks re-entry — and those run records are kept permanently, so a contact who joined two years ago still won't be welcomed again today.

Marketing emails

Send lifecycle email from live customer behaviour. Not a stale exported list.

Segments read live attributes, events, and engagement at dispatch time. Every recipient follows their own run through the flow, so the message fits where they actually are.

Build my first lifecycle flow Read the docs

✓Every recipient gets their own run. No blasts, by construction.

Lifecycle path

Marketing emails

Context decides the send

Trial ending in 3 days

Audience

Plan is Pro

Condition

Renewal reminder

Message

Run recorded

Evidence

One recipient per dispatchInspect

[ 01 / 03 ]What you build with

Live audiences, reusable messages, real outcomes.

Target live audiences

Saved segments built from attributes, product events, and engagement — evaluated when it matters.

Compose from published templates

Branded, versioned messages with deliberate send controls rather than one-off drafts.

Measure per step

Delivery and engagement attributed to the flow step and variant that produced them.

[ 02 / 03 ]How it works

From a product event to the right message.

Define who

A segment reading live attributes, events, and engagement — not a static import.

Define when

A product event opens the run; delays, branches, and send windows shape the path.

Launch deliberately

The flow is built paused. Turning it on is a separate, explicit decision.

What runs per recipient

An individual automation run
Deterministic A/B variant assignment
Timezone-aware send windows
Suppression checked at dispatch

[ 03 / 03 ]Related

Questions people ask us

Everything else is in the docs.

Turn current customer behaviour into the next useful message.

Build one segment from real attributes, attach it to a paused flow, and watch a single run.