## Overview

**Enrolling** means placing a contact inside a cadence. Each enrollment is the run of the sequence
for that contact: it pins the published version, advances step by step on schedule, and stops on its
own when an exit rule is met. ConversaLabs offers **several ways to enroll**, from a manual click to
an automatic trigger.

The platform avoids messaging the same person twice: there is at most **one active (or paused)
enrollment per contact in each sequence** (the conversation is taken into account too). Repeated
attempts are safely ignored.

## Prerequisites

- A **published** and active sequence.
- For event/inactivity/AI enrollment: the matching **trigger** configured on the sequence.
- For automation, macro or flow enrollment: the **Automation/Flow** module available.
- For AI enrollment: the **Maestro** enabled on the account.

## Step by step

1. Choose the **enrollment method** that best fits the case (see the options below).
2. Confirm the sequence **target** (contact, conversation, deal, appointment or charge).
3. For automatic triggers, configure the condition (event or inactivity time) on the sequence.
4. Enroll (manual) or let the trigger act; the enrollment starts as **active**.
5. Track the enrollment in the **enrollments** list, with its state and history.

## Settings & options

### Enrollment methods

| Method | How it happens |
|--------|----------------|
| **Manual** | You enroll one contact (or many, in bulk) directly from the interface. |
| **Automation** | An automation rule runs the enroll action when its conditions match. |
| **Macro** | An agent runs a macro that includes the enroll-into-cadence action. |
| **Flow** | A Flow Builder node enrolls the contact in the middle of a flow. |
| **Event** | A system event (stalled deal, overdue charge, appointment no-show, conversation resolved, etc.) triggers enrollment automatically. |
| **Inactivity** | Conversations idle for more than X minutes are enrolled automatically. |
| **AI** | The Maestro evaluates the conversation and decides whether to start the follow-up now. |
| **API** | An external system enrolls contacts programmatically. |

### Event-based enrollment

Configure the sequence with an **event** trigger and choose the event (for example, overdue charge,
inactive deal, appointment no-show or conversation resolved). When the event happens, the platform
enrolls the contact — provided the sequence target matches what the event carries.

### Inactivity-based enrollment

Configure the sequence with an **inactivity** trigger and set the **time limit in minutes** and which
**conversation statuses** count (by default, open and pending). Conversations idle beyond the limit
are enrolled — each conversation is processed only once per sequence.

### AI-based enrollment (proposed)

With an **AI** trigger, the Maestro analyzes the conversation and answers whether a follow-up makes
sense now. If the Maestro is unavailable, enrollment is not blocked: the cadence proceeds by the
normal rules.

## Use cases

- **Manual in bulk**: select several contacts from a list and enroll them in a reactivation campaign.
- **Event**: every overdue charge automatically enters the billing cadence.
- **Inactivity**: conversations unanswered for 60 minutes enter a recovery cadence.
- **Automation**: new leads from a specific channel enter the welcome sequence.

## Tips, limits & best practices

- Match the sequence **target** to the enrollment method (a billing cadence has a charge target).
- Don't try to enroll the same contact twice in the same sequence — the duplicate is ignored.
- For inactivity triggers, tune the time limit to your business so it doesn't fire too early.
- Use AI enrollment when you want a relevance filter before the cadence begins.

## Troubleshooting

- **The contact wasn't enrolled by an event**: check the sequence is active, published and has the
  right trigger/target.
- **Inactivity didn't fire**: review the time limit and the conversation statuses the sequence counts.
- **I enrolled and nothing showed up**: there was probably already an active/paused enrollment for
  that contact in that sequence (one per target limit).

## See also

- [Follow-ups and cadences overview](/hc/ajuda/articles/follow-ups-overview-en)
- [Sequences, steps, channels and composition](/hc/ajuda/articles/follow-ups-sequencias-passos-canais-composicao-en)
- [Cadence funnel and exit rules](/hc/ajuda/articles/follow-ups-funil-e-saida-en)
- [AI with human approval](/hc/ajuda/articles/follow-ups-ia-com-aprovacao-humana-en)