> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enroll Existing Subscribers

> Add subscribers who already match your sequence trigger to an automation

# Enroll Existing Subscribers

When you create a sequence with a trigger (tag, list, or event), it only starts for **new** matches going forward. But what about subscribers who already match the criteria?

## The Problem

Imagine this scenario:

1. You have 500 subscribers with the tag `past-due`
2. You create a new "Past Due Recovery" sequence triggered by that tag
3. The sequence only runs for **future** subscribers who get the tag

Those 500 existing subscribers won't receive your recovery emails.

## The Solution

Use the **Enroll Existing Subscribers** feature to retroactively add matching subscribers to your sequence.

### How to Use It

1. Open your sequence in the editor
2. Click the **people icon** in the header toolbar
3. Review the count of matching subscribers
4. Optionally exclude specific subscribers from enrollment
5. Click **Enroll** to add them to the sequence

### What You'll See

The enrollment modal shows:

* **Matching criteria** - The trigger condition being matched
* **Subscriber count** - How many subscribers are eligible
* **Subscriber list** - Paginated list of matching subscribers
* **Exclusion controls** - Remove specific subscribers before enrolling

### Excluding Subscribers

You can exclude specific subscribers from batch enrollment:

1. Click the **X** button next to any subscriber
2. They'll be marked as excluded (shown with strikethrough)
3. Click **Undo** to re-include them
4. The count updates to reflect exclusions

This is useful when you want to enroll most subscribers but skip a few specific ones.

## Trigger-Specific Behavior

### Tag Added (`tag_added`)

Matches all active subscribers who currently have the specified tag.

### Contact Added (`contact_added`)

* **With specific list**: Matches subscribers in that list
* **Any list**: Matches subscribers in any list

### Event Received (`event_received`)

Matches subscribers who received the event in the **last 30 days**.

<Note>
  Events older than 30 days are not included. This prevents accidentally
  enrolling subscribers based on very old activity.
</Note>

## Enrollment Mode

The enrollment respects your sequence's enrollment mode setting:

| Mode        | Behavior                                              |
| ----------- | ----------------------------------------------------- |
| `one_time`  | Excludes anyone who previously completed the sequence |
| `unlimited` | Only excludes those currently active in the sequence  |

## Sequence Status

You can enroll subscribers even when the sequence is in **draft** or **paused** state:

* Subscribers will be added to the sequence
* They'll start processing once the sequence is **activated**
* A warning is shown if the sequence isn't active

## Common Use Cases

### New Sequence for Existing Tags

You've been tagging customers as `churned` for months. Now you want to create a win-back sequence:

1. Create the sequence with trigger: `tag_added: churned`
2. Use **Enroll Existing Subscribers** to add all currently churned customers
3. New churned customers will automatically enter going forward

### Onboarding Sequence Launch

You're launching a new onboarding sequence for your product:

1. Create the sequence with trigger: `tag_added: signed-up`
2. Enroll existing signed-up users who haven't completed onboarding
3. Exclude users who are already paying customers

### Re-engagement Campaign

Starting a re-engagement sequence for inactive users:

1. Create the sequence with trigger: `event_received: session_started` (inverted logic via tag)
2. Or use: `tag_added: inactive-30d`
3. Enroll all currently inactive subscribers

## Enroll at a Specific Step

Sometimes subscribers finish a sequence, and you later add new steps. You can re-enroll those subscribers starting at a specific step — skipping the steps they've already completed.

### How to Use It

1. Open your sequence in the editor
2. **Hover** over the step where you want to enroll subscribers
3. Click the **Enroll** button that appears on the left side of the node
4. Choose from **Finished** subscribers (who already completed the sequence) or **Search** for any subscriber
5. Select subscribers and click **Enroll**

### How Filtering Works

The "Finished" tab automatically filters subscribers based on their progress:

* Only subscribers who **haven't already passed** the selected step are shown
* Subscribers with an **active** enrollment in the sequence are excluded (shown as "Already active")
* This prevents accidentally re-running steps a subscriber has already completed

### Example

You have a 3-step welcome sequence. 15 subscribers completed it. You add steps 4 and 5:

```
Step 1: Welcome Email     ✓ (15 completed)
Step 2: Delay 3 days      ✓ (15 completed)
Step 3: Tips Email         ✓ (15 completed)
Step 4: Feature Email      ← NEW (hover → click Enroll)
Step 5: Delay 7 days       ← NEW
```

When you click "Enroll" on Step 4, those 15 finished subscribers appear in the modal. They'll start at Step 4 and continue through Step 5, skipping the steps they already received.

### Notes

* This bypasses the enrollment mode (`one_time` vs `unlimited`) — it's an explicit manual action
* If the sequence is paused or draft, subscribers will be queued until the sequence is activated
* You cannot enroll subscribers at the trigger node

## Best Practices

1. **Review before enrolling** - Check the subscriber list to ensure you're targeting the right people
2. **Start with draft mode** - Create and configure your sequence fully before enrolling
3. **Use exclusions wisely** - Exclude VIP customers or special cases that need manual handling
4. **Check enrollment mode** - Decide if subscribers should be able to re-enter the sequence
5. **Use step-specific enrollment for additions** - When adding new steps to an existing sequence, enroll finished subscribers at the new step rather than restarting from the beginning
