Auto-Enrollment
Nobody builds the list by hand. The cadence names the event that ought to put somebody in it and then fills itself. The refusals matter more than the additions, and every route in reads the same ones.
Three ways in, and every one reads the same guards
perCompanyDedupe- Lead createdraised at the save
- Stage changedraised at the save
- Tag addedraised at the save
- a suppressed address
- a cadence that is not live
- anybody already on this one
Product figures from the platform’s own defaults - not customer averages
How it works.
You name the moment; it does the adding
A picker offers created, stage changed and tag added, with a field for which stage or which tag it must be. When that event happens, every live cadence naming it is looked up and each is offered the person in turn.
It starts filling now, not at the top of the hour
Creation raises its event once the row exists, and never in a way that could hold up the write. A stage moving and a tag landing raise theirs alongside their own save, so a cadence set to one of them begins filling the moment it goes live rather than at the top of the next hour.
Four ways to say no, read on every way in
Skip anyone already active on a different cadence. Skip a second person from the same company. Skip anyone written to inside the last so many days. Hold a percentage back as a control group, kept as a run that never advances. The same four are read whether somebody arrives by hand, in bulk, or from the event.
Three more that hold whatever you ticked
A suppressed address, a cadence that is not live, and anybody already on this one. Those sit underneath the four you configure, so they still refuse an add on a cadence where every guard is switched off.
Two moments in every run.
Every run passes through the same seven. Auto-Enrollment 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- Events offered
- Lead created, stage changed, tag added, or off entirely
- When it fires
- Inline with the save that caused it, so nothing has to be waited out between the change and the enrolllment
- Guards
- Already on another cadence, a colleague from the same company, written to in the last N days, and a control percentage
- Where they bite
- Every route in. One at a time from the sequence screen, the list-wide bulk action, and the automatic add
- Applied every time regardless
- A suppressed address, a cadence that is not live, and anybody already on this one
- Order
- The three unconditional checks, then your four guards, then the run row. Nobody is ever half enrollled
- Control group
- A percentage chosen by hashing the person, so somebody is always in or always out and never sometimes
- Not the same as
- This decides who goes in. What happens to them afterward is Email Sequences
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.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
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.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
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.
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 auto-enrollment on your own floor.
Thirty minutes, your numbers and your data. We will set auto-enrollment up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included