Auto-Enrollment
A cadence can name the event that ought to put somebody into it and then fill itself. The refusals matter more than the additions, and every route into the cadence 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.
The event is chosen on the cadence
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.
The event fires beside the save, not on an interval
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 guards, read on every route 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 enrolment
- 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 enrolled
- 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 afterwards 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 webhooks that act without being asked.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
Branch on whether they opened, clicked or replied, and on how the last call was dispositioned - so the next step answers what actually happened.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
Drop a call step into a sequence and it raises an assigned task on the lead's owner, with the outcome the rep logs coming back as a branchable answer.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Twenty-six behaviours attach to wrap-up codes, and twenty codes ship already pointing at one, so ending a call the right way books the follow-up.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
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