Email Sequences
Every lead holds their own place in the cadence and moves at their own pace. Nobody loses that place when the platform updates underneath them, and nobody is ever sent the same message twice.
One enrolment, one cursor, one claim before each send
the claim comes before the render- current node
- send_intro
- version
- v3, frozen at publish
- steps taken
- 4
- next run at
- now
- status
- active
- active
- waiting
- completed
- exited
- blocked
- suppressed
- holdout
Product figures from the platform’s own defaults - not customer averages
How it works.
Everybody's place is written down, not remembered
It stores which box they are standing on, which frozen version they are running, how many steps they have taken and when they are due back. None of that lives in memory, so a deploy in the middle of a cadence costs nothing at all.
Every minute, it picks up whoever has come due
A repeating job looks across every workspace for runs whose time has arrived under a sequence that is still live, then walks each one until it parks, ends, or is stopped. A hundred boxes is the ceiling for one pass; reaching it marks that run blocked instead of spinning.
Nobody gets sent the same message twice
Ahead of composing anything the engine inserts a row keyed on the run, the box, the version and the step counter. Where that row already exists the insert does nothing and the message is skipped. Because the counter moves, a genuine loop back around does legitimately send again.
Pausing stops the people already inside it
The sweep only picks up runs whose parent is live, and the single-run path checks a second time before acting. Pause it and everyone mid-flight stands still where they are. Set it live again and they resume from the identical box.
Two moments in every run.
Every run passes through the same seven. Email Sequences is the lit ones, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- Run states
- Active, waiting, completed, exited, blocked, suppressed, and held back for a control group. Twenty characters of text with no constraint behind it, so the set is a convention the engine keeps rather than one the database enforces
- Sequence states
- Draft, awaiting approval, live, paused, archived. Only a live one accepts people or moves them, and archiving takes a finished cadence out of the list without disturbing the runs it left behind
- Sweep
- Once a minute, every workspace in turn, from the shared job runner
- Against duplicates
- A unique row on run, box, version and step counter, taken before anything is composed
- Step ceiling
- One hundred boxes per pass. Beyond that the run is marked blocked and the reason written down
- One place per sequence
- The same person cannot be put on the same sequence twice. A second attempt is dropped in silence
- With no outgoing server set
- The step is still recorded and the walk still proceeds. The row simply says it was not delivered
- Not the same as
- This is the walk itself. Drawing the shape it walks is the Sequence Builder
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
12 capabilitiesSequences, dispositions and outside triggers that act without being asked.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
The next step answers something the person actually did, not something your floor guessed. Opened, clicked, replied, or how the last call was dispositioned.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See email sequences on your own floor.
Thirty minutes, your numbers and your data. We will set email sequences up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included