Skip to content
Adoptiv

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.

See pricing

Three ways in, and every one reads the same guards

perCompanyDedupe
The event a cadence may name
  • Lead createdraised at the save
  • Stage changedraised at the save
  • Tag addedraised at the save
One at a time, from the sequence screen
reads the same four
The list-wide bulk action
reads the same four
Raised by the event the cadence names
reads the same four
The order somebody is walked through
the three unconditional checksthenyour four guardsthenthe run row
The row is the last thing written, so nobody is ever half enrolled.
Applied every time, whatever you ticked
  • a suppressed address
  • a cadence that is not live
  • anybody already on this one
One person per company name, so a cadence does not land on a whole switchboard. It is read when you add one person from the sequence screen, when a list adds hundreds at once, and when the event fills the cadence with nobody watching. One guard, one place it is written down, three routes obeying it.
0
events that can put somebody in without a rep
0
reasons to refuse an add that you set yourself
0
refusals nobody can switch off

Product figures from the platform’s own defaults - not customer averages

The mechanism

How it works.

01

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.

02

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.

03

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.

04

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.

Where it sits

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.

  1. 01
    Trigger

    the thing that happened first

  2. 02
    Enrol

    how somebody gets onto it

  3. 03
    Wait

    the pause, and what governs its length

  4. 04
    Branch

    the fork, and which side is taken

  5. 05
    Act

    the mail, the text, the task that goes out

  6. 06
    Measure

    what counts as it having worked

  7. 07
    Exit

    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

More in Automation & Flows

12 capabilities

Sequences, dispositions and outside triggers that act without being asked.

Sequence Builder

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.

Branch Logic

The next step answers something the person actually did, not something your floor guessed. Opened, clicked, replied, or how the last call was dispositioned.

A/B Split Testing

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.

Wait & Timing

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.

Sending Windows

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.

Call Tasks in Sequences

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.

Goal Tracking

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.

Disposition Behaviors

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.

Workflow Actions

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.

Conditional Logic

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.

SMS in Sequences

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.

REST API

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.

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.

See pricing

14-day trial · no card · migration included