Early Access: under active development, stable for demos, improving weekly.
Back to guides

Understand the Contact Enrollment Lifecycle

Outreach Sequencer Team5 min read
contactsenrollmentcampaignslifecycle

Most confusion about the app comes down to one thing: not knowing what state a contact is in. Every contact moves through a small, predictable set of states, and once you can read them, the app stops feeling mysterious. You always know why someone is or isn't in your queue, and what your next move is.

Here is a simple way to think about the full lifecycle.

1. Pending — added, not in a campaign

When you first add a contact (capture from LinkedIn, manual add, or bulk import), they are pending. They exist in your contacts list, but no sequence is running, so they never appear in your queue.

Pending is a holding state. Nothing happens automatically. The next move is yours: enroll them in a campaign.

2. Enroll — put them into a campaign

Enrolling starts a sequence. You pick the campaign yourself — nothing is ever pre-selected for you — and the contact begins at step 1 with a status of active.

A contact runs one sequence at a time, and the app enforces it: the Enroll action is disabled for someone already active or paused, and you cannot double-enroll them in the same campaign. The one exception is nurture. A warm contact is in their sequence and a repeating nurture cadence at once, because those are two different jobs.

3. Which campaigns will accept this contact

Campaigns aren't interchangeable. Each one needs something different from the contact, and the app tells you which before you commit:

  • Needs connection — the sequence messages people on LinkedIn but never sends a request, so it only takes someone you're already connected to. Pick it for a stranger and the app refuses: you can't message someone who hasn't accepted you.
  • Connection-first — step 1 is the connection request, so this is the one for people you don't know yet. It refuses someone you're already connected to, because that first step would fire a pointless request. The Chrome extension sends the request and reports back when it's accepted; until then the contact stays out of your queue on purpose.
  • No connection needed — email, phone, in person. Takes anyone, LinkedIn URL or not.
  • Nurture — a repeating check-in. Takes anyone.

The rule is checked when you save, not when you opened the form, so it's still right even if the extension marked someone connected a minute ago.

4. Active and paused — the running states

  • Active means a step is due (or coming due) and the contact shows up in your queue.
  • Paused means the enrollment is still alive but no step is currently due, so they stay out of the queue until you resume.

This is where the daily work happens. For the operating rhythm — how to clear these without rushing or hoarding — see Work a Daily Outreach Queue Well. From the queue, a due contact gives you the working options:

  • Complete the step — logs the touch and advances to the next step.
  • Skip step — move past this step without logging a touch.
  • Snooze — push the due date out to later.
  • Pause / Resume — stop or restart the whole sequence.
  • Log touch, Reply, Log sale, Set warm — record what actually happened.

5. Close — end the campaign

When you're done with a sequence — they replied, they bought, they're not interested, whatever — you close the enrollment with a reason. Closing ends the active run. The contact drops out of the queue and is no longer in a running campaign.

Important: closing does not delete anything. Their touch history and outcomes stay on the record. "Out of a campaign" means closed, not erased.

6. Change campaign — move them without starting over

Picked the wrong sequence, or the relationship moved on? Open the contact and use Change Campaign. The current sequence closes as superseded, the new one starts fresh at step 1, and every touch you already logged stays on the record attached to the sequence it happened in.

This works in every direction: sequence to sequence, sequence to a nurture cadence, and one cadence to another when monthly is too often or not often enough. The same connection rules from section 2b apply, so a change can be refused for the same reasons an enrollment can.

Two things it won't do: pick the campaign the contact is already in, and touch the other enrollment a warm contact has. Only the sequence shown on the contact is changed.

The short version

Pending → Enroll → Active/Paused → Close, with Change Campaign available the whole way through.

One sequence per contact, plus a nurture cadence once they're warm. You always pick the campaign; the app only refuses when the sequence needs a LinkedIn connection you don't have, or sends a request to someone you already know. Closing keeps history, and so does changing. Deleting is separate — it removes the contact from your active list entirely while keeping their touch log.

Put the guide into practice inside the app

Use these playbooks alongside the queue, campaigns, prompts, and tracking flows so the operating ideas turn into daily reps.

Read More Guides