email-sequence

Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Audience permission and automation limits

This is draft strategy/copy, not an ESP integration or permission to send, enroll contacts or change billing. Verify recipient eligibility, lawful marketing basis and channel preferences under the actual jurisdictions; signup, purchase, invitation or NPS score alone does not authorize every promotional sequence. Preserve unsubscribe/suppression state and separate essential service notices from marketing. Do not re-enroll opted-out contacts through win-back campaigns or cancellation surveys.

Define entry/exit conditions, per-person frequency caps across overlapping sequences, duplicate-event handling, quiet hours/time zones and stop conditions after conversion, cancellation, payment recovery or a support issue. Keep invitations bounded and avoid revealing account details to an unverified address. Personalization needs approved data, safe fallbacks and HTML/URL escaping; never invent usage savings, prior achievements, testimonials, scarcity, sender identity or guarantees. Confirm actual billing/renewal dates and secure self-service links. Timings, lengths and benchmarks are hypotheses, not universal requirements. Use conversions/deliverability with explicit denominators and a planned test horizon; open-rate differences alone do not establish lift. No contacts accessed, message sent or automation configured here.