> ## Documentation Index > Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Enrolling people > The five ways to add people to a sequence, what the preview checks, why someone is refused, and how enrollment runs work. Open a sequence and click **Add people**. Every path goes through the same preview, so you see who will be enrolled, who will be skipped and why, before anything starts. ## Where people can come from | Source | What it means | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CRM list** | A named HubSpot list or Salesforce report. | | **CRM: my contacts** | Every contact whose CRM owner is you. | | **CRM: my call queue** | The contacts behind your due tasks in the CRM. This is your task queue, not your ownership; the two are different sets. | | **Salesfinity contact list** | Any list from the dialer. | | **Contacts** | People picked one at a time from the contacts directory. | | **CSV or paste** | Rows you upload or paste. Column headers are matched to contact fields; unmatched columns can be mapped to custom fields, which merge fields can then use. | 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. | Refusal | Cause | What to do | | ------------------ | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | Policy | A rules-of-engagement scenario blocked it, for example an open deal or a CRM opt-out. The rule name is shown. | Fix the record, or change the rule if it is wrong. | | Suppressed | The email, domain or phone is on the do-not-contact list. | Check **Sequencer › Suppression**. Entries added by unsubscribe, bounce or complaint should stay. | | Already enrolled | The person has a live enrollment in this sequence. A person can only be in a sequence once at a time. | Finish the existing enrollment first if you want to restart them. | | Throttle: capacity | The sequence is at its active-people cap. | Raise the cap on the sequence, or wait for enrollments to finish. | | Throttle: daily | The sequence has hit its adds-per-day cap. | Try again tomorrow or raise the cap. | | Contact not found | The row could not be matched or created as a contact, usually a missing email and phone. | Fix the row and re-import. | Refusals are recorded on the sequence's **enrollment attempts** list, so a manager can see who was kept out and why after the fact. Rules of engagement are evaluated against fresh CRM facts (owner, open deals, opt-out, CRM fields). If a preview looks stale, it is usually the CRM facts cache; the enrollment itself refreshes them within the age limit set on the policy. ## 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](/ari/approvals-and-permissions). ## Enrollment states | State | Meaning | | --------- | --------------------------------------------------------------------------------------------------------- | | Pending | Enrolled but not started: held for approval, or waiting for the sequence to be enabled. | | Active | Working through the steps. | | Paused | Stopped with a reason (rep paused, reply action, sequence disabled, rule) and, optionally, a resume date. | | Finished | Done: ran out of steps, or finished by a reply, an outcome, a rule or a rep. | | Bounced | An email hard-bounced; no further steps run. | | Opted out | The prospect unsubscribed; they are also added to suppression. | | Failed | The engine could not continue; the reason is on the enrollment. Use **Retry** after fixing the cause. | Open an enrollment to see its full event timeline: every send, open, click, reply, bounce, task, approval, rule that applied, and outcome.