Design an Email Funnel and Sequence

Turn an offer or lifecycle goal, audience context, and supplied assets into a multi-step email funnel with triggers, message roles, sequencing logic, CTAs, and review checkpoints.

Context → structured prompt → explicit AI handoff

Runs in this browser. No upload by this page. External AI handoff is explicit. Review before sharing.

Prompt workbenchConfigure → review → use

Configure task

Setup

Funnel goal and offerRequiredDescribe the lifecycle or business goal, the offer/action, and what the sequence should help an eligible recipient do next.

Audience context and entry stateRequiredDescribe who enters the sequence, what they already know, why they may be interested, and any known objections or decision context.

Prompt style

Additional options

Existing assets, consent context, and constraintsPaste existing messages/assets and note user-verified permission context, timing limits, platform assumptions, exclusions, or brand constraints.

Sequence type

Sequence length

Message style

What you’ll need

Funnel goal or offer plus audience context and any existing messages or assets
Funnel goal and offer
Audience context and entry state

What you’ll get

Funnel objective and entry criteria
Trigger and exit assumptions
Sequence map
Per-email purpose, subject angle, key points, and CTA
Timing rationale

Prompt preview

Editable

Review or edit the generated prompt before you copy it or explicitly open an AI chat.

Export

ChatGPT opens with the current prompt prepared. Gemini copies the current prompt, then opens Gemini so you can paste it. Keep secrets and sensitive information out of URL-carried prompts.

Task referenceExamples, expected output, boundaries, and routing.

Examples

1. Lead nurture sequence

Context: A consultant has an opt-in guide, a verified service description, and a user-supplied permission context.

Goal: Design five nurture emails that progress from education to a consultation CTA.

Useful output: Sequence map, message roles, CTA progression, personalization fields, verification checklist, and test ideas.

2. Product onboarding

Context: A software team supplies onboarding milestones and existing help resources.

Goal: Create a three-email activation sequence without inventing platform automation behavior.

Useful output: Entry assumption, three-email flow, verified resource references, CTA logic, and implementation questions.

3. Re-engagement planning

Context: A creator wants a seven-email concept for inactive subscribers but has not provided current consent-policy details.

Goal: Plan message progression while flagging permission/compliance verification.

Useful output: Sequence structure, subject angles, conservative timing suggestions, explicit verification items, and no fake results.

Expected output

Funnel objective and entry criteria
Trigger and exit assumptions
Sequence map
Per-email purpose, subject angle, key points, and CTA
Timing rationale
Personalization fields
Consent/compliance verification checklist
Testing ideas and uncertainties
Next implementation steps

Truth boundary

Do not invent consent status, recipient facts, deliverability results, conversion rates, platform automation capabilities or legal compliance. User must verify permission and applicable messaging rules.

Overlap guard: Owns multi-message lifecycle architecture and progression. Use the other email tasks when the job is one specific message or a recurring editorial newsletter rather than a funnel.

Privacy and handoff

Runs in this browser. No upload by this page. Copy/download locally or explicitly open ChatGPT or Gemini. Source files are attached in the chosen AI service, not uploaded by Mycelgrid. Review the generated prompt and AI output before using or sharing it.

Browse GPT Tasks Open Workspace