Working Web skill
Design an email nurture sequence
Design a consent-aware email sequence around useful recipient progress and branching.
Help recipients take the next useful step without manufacturing pressure.
Procedure
- Define the eligible audience, consent source, purpose, current state, desired progress, and exit conditions.
- Map recipient questions, barriers, risks, decisions, and relevant product or service events.
- Choose sequence length, timing, timezone behavior, frequency cap, and event-based branches.
- Give each message one purpose, evidence-backed promise, primary action, and clear sender identity.
- Write subject, preview, body, link, alternative path, and accessibility requirements.
- Add suppression for conversion, ineligibility, complaint, bounce, opt-out, risk, support escalation, and contradictory messages.
- Define personalization from necessary verified fields only, with safe fallbacks.
- Test rendering, links, tracking, consent, unsubscribe, localization, branching, duplication, and interrupted journeys.
- Measure delivery, useful action, progress, complaint, opt-out, support burden, and downstream outcome.
- Start with a bounded audience, review qualitative feedback, and stop or revise harmful branches.
Guardrails
- Do not repurpose consent, hide unsubscribe, or use sensitive inference for personalization.
- Avoid false deadlines, shame, or escalating frequency after nonresponse.
- Never continue promotional nurture during an unresolved safety, billing, or support problem.
- Keep transactional and promotional purposes appropriately separated.
--- name: design-an-email-nurture-sequence category: web description: Design a consent-aware email sequence around useful recipient progress and branching. Use when onboarding, education, evaluation, renewal, event, or re-engagement messages need coordinated timing, content, evidence, and measurement. --- # design-an-email-nurture-sequence Help recipients take the next useful step without manufacturing pressure. ## Procedure 1. Define the eligible audience, consent source, purpose, current state, desired progress, and exit conditions. 2. Map recipient questions, barriers, risks, decisions, and relevant product or service events. 3. Choose sequence length, timing, timezone behavior, frequency cap, and event-based branches. 4. Give each message one purpose, evidence-backed promise, primary action, and clear sender identity. 5. Write subject, preview, body, link, alternative path, and accessibility requirements. 6. Add suppression for conversion, ineligibility, complaint, bounce, opt-out, risk, support escalation, and contradictory messages. 7. Define personalization from necessary verified fields only, with safe fallbacks. 8. Test rendering, links, tracking, consent, unsubscribe, localization, branching, duplication, and interrupted journeys. 9. Measure delivery, useful action, progress, complaint, opt-out, support burden, and downstream outcome. 10. Start with a bounded audience, review qualitative feedback, and stop or revise harmful branches. ## Guardrails - Do not repurpose consent, hide unsubscribe, or use sensitive inference for personalization. - Avoid false deadlines, shame, or escalating frequency after nonresponse. - Never continue promotional nurture during an unresolved safety, billing, or support problem. - Keep transactional and promotional purposes appropriately separated. ## Done - A sequence map records audience, consent, timing, message purpose, branches, and exits - Claims, links, personalization, and suppression logic are verified - End-to-end test evidence covers delivery, rendering, unsubscribe, and duplicate prevention - Outcome and harm measures have review owners