---
name: email-sequence
description: "Prepare email copy, subjects, timing and branching plan; no sending. Use for this workflow with supplied business information."
---

# Email sequence

## Inputs and purpose

Use this workflow to prepare: Email copy, subjects, timing and branching plan; no sending.

Start with: Purpose, audience, offer, voice and desired timing.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Define the audience, purpose, entry condition, desired action and any supplied consent or communication rules.

2. Plan each message's distinct purpose and timing, including when the sequence should stop or move to a human response.

3. Draft subjects and messages using verified offer details. Avoid repeating the same request without adding useful information.

4. Return copy and a branching plan. Keep drafted messages separate from sending, contact enrollment and automated scheduling.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve messaging and campaign choices.

Possible success measures: Qualified inquiries, conversion, contribution after advertising. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).