Where people can come from
The enrollment is owned by the rep who created it unless you pick a different owner. Emails go out
from the owner’s mailbox and call tasks land in the owner’s inbox.
What the preview checks
For each person the preview reports one of:- Enrolls: no rule fired.
- Enrolls with a warning: a rule fired with the “enroll with a warning” action. The warning is shown and logged on the enrollment.
- Held for approval: a rule fired with “hold for approval”. The person is enrolled in a pending state and a manager has to approve it before any step runs.
- Refused: the person will not be enrolled. The reason is one of the following.
Refusals are recorded on the sequence’s enrollment attempts list, so a manager can see who was
kept out and why after the fact.
Enrollment runs
Adding a large set creates an enrollment run that works in the background. A run moves through queued → fetching → running → completed, or ends failed or cancelled. While it is fetching, the total is not known yet; once it is running you see progress and the skips so far.- Cancel stops a run. People already enrolled stay enrolled; nobody else is added.
- Each run keeps a label of what it was pointed at (“HubSpot · Q1 SDR list”) so it can be re-run from the sequence’s runs list.
Enrolling from the dialer and from Ari
- From a call, a rep can enroll the person in a sequence directly from the call card. The enrollment goes through the same preview and rules.
- Ari can build a list and propose an enrollment. It shows the preview and asks before anyone is enrolled; see Ari approvals.
Enrollment states
Open an enrollment to see its full event timeline: every send, open, click, reply, bounce, task,
approval, rule that applied, and outcome.