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

# Enroll a reviewed email-sequence batch

> Review a complete lead selection and reconcile its enrollment receipt.

**Unreleased backend.** Parent transaction/authentication, approval policy and recovery integration are complete locally. Screens, actual signed approval UX, independent review and release validation remain required. There is no new public API endpoint or availability claim.

An organization administrator with CRM, settings and current lead access chooses one active sequence, an available From mailbox and 2–50 explicit leads. The read-only preview names every lead and recipient and shows the actual From address, sequence/version and complete sending window, including its name, revision, organization timezone, weekdays and local hours. Inaccessible, closed, archived, suppressed or already enrolled leads make the complete selection unavailable. Two leads sharing the same normalized recipient are refused; nothing is silently merged. Preview does not reserve a place or promise delivery.

One human decision approves the complete named batch. The dedicated assistant action requires approval even in Auto, and cannot be wrapped in generic bulk actions. Web, mobile and staff WhatsApp use the same trusted-current-actor service and current authorization. Browser actions also refuse acting sessions. Support and partner sessions cannot enroll batches.

Admission checks every record again in one database transaction. Changed names, addresses, sender, sequence/version or sending window require another complete review. A failed member, unsubscribe or concurrent enrollment causes the entire transaction to roll back. Enrollment itself sends nothing; the existing worker decides when to attempt each message and applies the existing reply, booking, suppression, subscription, lifecycle and sending-window stop rules. A provider request already underway may finish.

Keep the original batch UUID and exact reviewed input until the result is known. With current authorized administrator access, an exact replay returns its original minimal receipt, including after completion, stop or source deletion; changed input cannot reuse that UUID. If the connection drops while committing, use reconciliation with that same UUID/input. Reconciliation only reads the outcome and never starts enrollment. An absent receipt is not permission for an automatic retry. Do not create a fresh batch ID to work around an uncertain result.

Receipts retain only the input hash, count, timestamp and nullable enrollment references. They do not store names, recipients, message bodies or reusable approval input. Deleting a lead or sequence can clear references without erasing the receipt. Restoring stopped enrollment history does not reconnect cleared references, recreate authorization or restart outreach. Tenant closure controls final receipt purge.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.