## Plan One Prospect's Emails

A personal sequence holds 1–3 complete emails for one prospect inside a campaign. Review the copy and schedule together, then approve once. Kit sends only those exact emails as they become eligible; it does not generate future copy under that approval.

This is an account-specific pilot. It requires an active campaign with a team mailbox and permission to manage that campaign. The prospect must have no existing messages, including unsent drafts, and no research or drafting underway. Contact restrictions can still prevent approval. If preparation is unavailable, ask your platform administrator about pilot setup.

## Prepare and Approve

1. Open the prospect in [its campaign](/outreach/campaigns) and choose **Prepare sequence**. Use **Prepare with AI** if you want help writing the emails.
2. Enter each subject and plain-text body, then check the recipient, sending mailbox and signature. Add source context through the preparation assistant when needed.
3. Set the first eligible time, time zone, permitted weekdays, daily sending window and approval expiry. Each later email waits 1–14 calendar days after the previous email's recorded mail-server acceptance. Approval expires within 30 days and may end earlier if required source context expires.
4. Choose **Save draft** to return later, or **Review & schedule** to inspect every remaining email and the full schedule. Saving, requesting review and an AI copy review do not authorize sending. Evidence labels and critic findings are assessments to check, not proof of accuracy.
5. Choose **Approve & schedule** and confirm with your own trusted passkey. The pilot requires a passkey independently verified and approved by a platform administrator; registering a new one is not enough. Review on a browser or device outside an assistant's control.

The first eligible time is not a delivery promise. Sending windows, account capacity, current reply checks and permission checks can delay or block an email. **Sent** and **Completed** record mail-server acceptance, not inbox placement.

## Track or Change the Sequence

Open [Outreach > Sequences](/outreach/prospect_sequences) to filter saved sequences by campaign or status. Open one to inspect its next email, sent count, exact copy and timeline. Prospect status and sequence status are separate.

**Pause** revokes approval for remaining emails. Use **Pause & edit** to change the remainder, then review and approve it again. Sent emails stay in history. An email already being submitted may still require an outcome review; pausing cannot recall it. Resuming the campaign does not restore a revoked sequence approval.

A recorded reply, opt-out, bounce, meeting or contact stop prevents later emails. Expired approval or source context, changed access, and a schedule missed by more than 48 hours require attention before continuing. If the pilot is disabled, authorized members can still inspect existing history and resolve retained delivery uncertainty.

## Resolve Delivery Uncertainty

Open the sequence timeline when delivery needs review. Check the recorded attempt and provider evidence, including its RFC Message-ID. Absence from a Sent folder alone does not prove an email was not sent.

- **Confirmed sent** records acceptance without another send.
- **Confirmed not sent** or **Return to draft for review**, when offered, leaves the remaining emails paused. Review and approve them separately before another attempt.
- **Close without delivery** stops the sequence.

Record the evidence and confirm with a trusted passkey. Resolving delivery never immediately retries or resumes the sequence. Removed email copy cannot be restored through recovery.

## Use an External AI Assistant

Use a separately authorized [MCP connection](/integrations/mcp/settings) with `outreach_read outreach_compose`. Ask the assistant to check `outreach_get_sequence_capabilities`, read the current version, save complete copy and evidence, and request human review. Research, writing and critic agents can coordinate through those saved revisions; version and retry keys protect concurrent edits.

Follow the response's current `sequence_url`, `review_url` when present, and `next_action`. A saved mutation receipt describes an earlier result, not current readiness. The preparation tools cannot approve, activate campaigns or send. Existing broad `outreach_write` connections keep their separate legacy powers; they are not preparation-only connections. Client compatibility must be tested, including for Grok or OpenClaw.

See the [MCP tools reference](/docs/mcp-tools-reference#exact-prospect-sequences-pilot) for the tool list, scopes and retry contract.