email-sequence

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Sequence Designer

邮件序列设计工具

Designs complete email automation sequences with strategic timing, persuasive copy, and conditional logic.
设计包含策略性时间安排、有说服力的文案和条件逻辑的完整邮件自动化序列。

Quick Reference

速查指南

Sequence TypeEmailsDurationBest For
Welcome Series4-614 daysNew subscribers
Nurture6-106-10 weeksEducation, engagement
Re-engagement3-528 daysInactive subscribers
Abandoned Cart33 daysE-commerce recovery
Post-Purchase4-630 daysCustomer experience
Review Request1-21-24 hoursSocial proof
CustomVariableVariableSpecific goals
序列类型邮件数量时长适用场景
欢迎系列4-614天新订阅用户
用户培育6-106-10周教育、用户互动
重新激活3-528天沉睡订阅用户
购物车遗弃召回33天电商订单挽回
售后跟进4-630天客户体验维护
评价请求1-21-24小时社交口碑积累
自定义序列可变可变特定目标场景

Execution Protocol

执行流程

Step 1: Load Context

步骤1:加载上下文

Read the business profile for context:
  • email-profile.md
    (project root)
Load reference files for frameworks and benchmarks:
  • references/copy-frameworks.md
  • references/benchmarks.md
读取业务档案获取上下文信息:
  • email-profile.md
    (项目根目录)
加载框架和基准参考文件:
  • references/copy-frameworks.md
  • references/benchmarks.md

Step 2: Gather Sequence Requirements

步骤2:收集序列需求

Ask the user:
  1. Sequence type: welcome, nurture, re-engagement, abandoned-cart, post-purchase, review-request, or custom
  2. If custom: goal, trigger event, desired email count, preferred cadence, tone
Confirm business context from profile:
  • Industry
  • Target audience
  • Brand voice
  • Primary offer/product
向用户确认:
  1. 序列类型:欢迎、培育、重新激活、购物车遗弃召回、售后跟进、评价请求或自定义
  2. 若为自定义序列:目标、触发事件、期望邮件数量、偏好发送节奏、语气风格
从业务档案中确认以下信息:
  • 行业
  • 目标受众
  • 品牌调性
  • 核心产品/优惠

Step 3: Design Sequence Architecture

步骤3:设计序列架构

Based on sequence type, define:
  • Total number of emails
  • Timing between emails
  • Framework assignment per email
  • Conditional logic rules
  • KPI targets
根据序列类型定义:
  • 邮件总数
  • 邮件间隔时间
  • 每封邮件对应的框架
  • 条件逻辑规则
  • KPI目标

Step 4: Generate Each Email

步骤4:生成单封邮件内容

For each email in sequence, create:
  1. Position and timing: Email X, Day Y or Hours after trigger
  2. Subject lines: 3 variants with scores (60-100)
  3. Preheader text: 30-80 characters
  4. Email body: Full copy following assigned framework
  5. CTA: Button text and link placeholder
  6. Conditional logic: What happens based on engagement
为序列中的每封邮件创建以下内容:
  1. 定位与时间:第X封邮件,触发后第Y天/小时发送
  2. 主题行:3个变体及评分(60-100分)
  3. 预头文本:30-80字符
  4. 邮件正文:遵循指定框架的完整文案
  5. CTA:按钮文字及链接占位符
  6. 条件逻辑:基于用户互动的后续动作

Step 5: Add Implementation Guidance

步骤5:添加实施指导

Include:
  • Platform setup notes
  • A/B test recommendations
  • KPI benchmarks for this sequence type
  • Segment considerations
包含以下内容:
  • 平台设置说明
  • A/B测试建议
  • 该序列类型的KPI基准
  • 用户分群考量

Sequence Type Templates

序列类型模板

1. Welcome Series (4-6 emails, 14 days)

1. 欢迎系列(4-6封邮件,14天)

Standard Timeline:
  • Email 1: Immediate (welcome + deliver lead magnet)
  • Email 2: Day 1 (brand story)
  • Email 3: Day 2 (best content/resource)
  • Email 4: Day 4 (social proof)
  • Email 5: Day 7 (soft offer)
  • Email 6: Day 14 (stronger CTA or segmentation)
Framework Assignment:
  • Email 1: BAB (Before-After-Bridge)
  • Email 2: BAB (Before-After-Bridge)
  • Email 3: FAB (Features-Advantages-Benefits)
  • Email 4: 4Ps (Picture-Promise-Prove-Push)
  • Email 5: AIDA (Attention-Interest-Desire-Action)
  • Email 6: PAS (Problem-Agitate-Solution)
KPI Targets:
  • Average open rate: 40-60%
  • Average click rate: 3-8%
  • Conversion rate: 2-5%
标准时间线:
  • 邮件1:即时发送(欢迎语+交付引流赠品)
  • 邮件2:第1天(品牌故事)
  • 邮件3:第2天(优质内容/资源)
  • 邮件4:第4天(社交证明)
  • 邮件5:第7天(软性优惠)
  • 邮件6:第14天(更强CTA或用户分层)
框架分配:
  • 邮件1:BAB(Before-After-Bridge)
  • 邮件2:BAB(Before-After-Bridge)
  • 邮件3:FAB(Features-Advantages-Benefits)
  • 邮件4:4Ps(Picture-Promise-Prove-Push)
  • 邮件5:AIDA(Attention-Interest-Desire-Action)
  • 邮件6:PAS(Problem-Agitate-Solution)
KPI目标:
  • 平均打开率:40-60%
  • 平均点击率:3-8%
  • 转化率:2-5%

2. Nurture Sequence (6-10 emails, 6-10 weeks)

2. 用户培育序列(6-10封邮件,6-10周)

Cadence: 1-2 emails per week
Content Mix:
  • 80% value (education, tips, resources)
  • 20% promotion (offers, CTAs)
Framework Rotation: PAS -> FAB -> BAB -> 4Ps -> AIDA -> repeat
Progressive Profiling: Gather data over time through link clicks, survey questions
KPI Targets:
  • Average open rate: 25-35%
  • Average click rate: 2-5%
  • Conversion rate: 1-3%
发送节奏:每周1-2封
内容比例
  • 80%价值内容(教育、技巧、资源)
  • 20%推广内容(优惠、CTA)
框架轮换:PAS -> FAB -> BAB -> 4Ps -> AIDA -> 循环
渐进式用户画像:通过链接点击、调查问卷逐步收集用户数据
KPI目标:
  • 平均打开率:25-35%
  • 平均点击率:2-5%
  • 转化率:1-3%

3. Re-engagement / Win-Back (3-5 emails, 28 days)

3. 重新激活/赢回序列(3-5封邮件,28天)

Trigger: 90 days no click engagement (not opens, due to Apple MPP)
Standard Timeline:
  • Email 1: Day 0 (friendly check-in)
  • Email 2: Day 5-7 (value reminder)
  • Email 3: Day 10-14 (incentive offer)
  • Email 4: Day 21 (last chance)
  • Email 5: Day 28 (final goodbye)
Framework Assignment:
  • Email 1: BAB (Before-After-Bridge)
  • Email 2: 4Ps (Picture-Promise-Prove-Push)
  • Email 3: AIDA (Attention-Interest-Desire-Action)
  • Email 4: PAS (Problem-Agitate-Solution)
  • Email 5: Direct
After sequence: Remove non-responders from active list to protect sender reputation
KPI Targets:
  • Average open rate: 15-25%
  • Average click rate: 1-3%
  • Re-engagement rate: 5-10%
触发条件:90天无点击互动(因Apple MPP限制,不统计打开行为)
标准时间线:
  • 邮件1:第0天(友好问候)
  • 邮件2:第5-7天(价值提醒)
  • 邮件3:第10-14天(激励优惠)
  • 邮件4:第21天(最后机会)
  • 邮件5:第28天(最终告别)
框架分配:
  • 邮件1:BAB(Before-After-Bridge)
  • 邮件2:4Ps(Picture-Promise-Prove-Push)
  • 邮件3:AIDA(Attention-Interest-Desire-Action)
  • 邮件4:PAS(Problem-Agitate-Solution)
  • 邮件5:直接式
序列结束后:将未响应用户从活跃列表中移除,保护发件人信誉
KPI目标:
  • 平均打开率:15-25%
  • 平均点击率:1-3%
  • 重新激活率:5-10%

4. Abandoned Cart (3 emails, 3 days)

4. 购物车遗弃召回(3封邮件,3天)

Standard Timeline:
  • Email 1: 1 hour (reminder, no discount)
  • Email 2: 24 hours (address objections, social proof)
  • Email 3: 48-72 hours (incentive offer)
Framework Assignment:
  • Email 1: Direct
  • Email 2: PAS (Problem-Agitate-Solution)
  • Email 3: AIDA (Attention-Interest-Desire-Action)
Show cart items: Include product images, names, prices in email body
Target recovery rate: 5-15%
KPI Targets:
  • Email 1 open rate: 40-50%
  • Email 2 open rate: 30-40%
  • Email 3 open rate: 25-35%
  • Total recovery rate: 10-18%
标准时间线:
  • 邮件1:1小时后(提醒,无折扣)
  • 邮件2:24小时后(解决顾虑,社交证明)
  • 邮件3:48-72小时后(激励优惠)
框架分配:
  • 邮件1:直接式
  • 邮件2:PAS(Problem-Agitate-Solution)
  • 邮件3:AIDA(Attention-Interest-Desire-Action)
显示购物车商品:邮件正文中包含产品图片、名称、价格
目标挽回率:5-15%
KPI目标:
  • 邮件1打开率:40-50%
  • 邮件2打开率:30-40%
  • 邮件3打开率:25-35%
  • 总挽回率:10-18%

5. Post-Purchase (4-6 emails, 30 days)

5. 售后跟进序列(4-6封邮件,30天)

Standard Timeline:
  • Email 1: Immediate (order confirmation)
  • Email 2: Shipped (shipping notification)
  • Email 3: Delivered (delivery confirmation + tips)
  • Email 4: Day 7 (value-add content)
  • Email 5: Day 14 (review request)
  • Email 6: Day 30 (cross-sell/upsell)
Framework Assignment:
  • Email 1: Direct
  • Email 2: Direct
  • Email 3: FAB (Features-Advantages-Benefits)
  • Email 4: BAB (Before-After-Bridge)
  • Email 5: PAS (Problem-Agitate-Solution)
  • Email 6: AIDA (Attention-Interest-Desire-Action)
KPI Targets:
  • Average open rate: 50-70%
  • Average click rate: 5-12%
  • Review request response: 5-15%
  • Cross-sell conversion: 3-8%
标准时间线:
  • 邮件1:即时发送(订单确认)
  • 邮件2:发货时(发货通知)
  • 邮件3:送达时(送达确认+使用技巧)
  • 邮件4:第7天(增值内容)
  • 邮件5:第14天(评价请求)
  • 邮件6:第30天(交叉销售/向上销售)
框架分配:
  • 邮件1:直接式
  • 邮件2:直接式
  • 邮件3:FAB(Features-Advantages-Benefits)
  • 邮件4:BAB(Before-After-Bridge)
  • 邮件5:PAS(Problem-Agitate-Solution)
  • 邮件6:AIDA(Attention-Interest-Desire-Action)
KPI目标:
  • 平均打开率:50-70%
  • 平均点击率:5-12%
  • 评价请求响应率:5-15%
  • 交叉销售转化率:3-8%

6. Review Request (1-2 emails)

6. 评价请求序列(1-2封邮件)

Timing varies by business type:
  • Restaurant/food: within 24 hours
  • Salon/spa/service: same day or next day
  • Home services: 24-48 hours
  • Retail (simple products): 1-2 days
  • Shoes/clothing: 1-2 weeks
  • Courses/coaching: 1+ week
  • Medical/dental: 24 hours
Framework: PAS (Problem-Agitate-Solution) - position review as helping others
Include:
  • Direct link to review platform
  • Multiple platform options if applicable
  • Incentive (optional): discount on next purchase
KPI Targets:
  • Open rate: 50-70%
  • Review completion: 10-25%
发送时间因业务类型而异:
  • 餐饮:24小时内
  • 美容/SPA/服务类:当天或次日
  • 家庭服务:24-48小时
  • 零售(简易产品):1-2天
  • 鞋服:1-2周
  • 课程/培训:1周以上
  • 医疗/牙科:24小时内
框架:PAS(Problem-Agitate-Solution)——将评价定位为帮助他人
包含内容:
  • 评价平台直接链接
  • 若适用,提供多个平台选项
  • 激励(可选):下次购买折扣
KPI目标:
  • 打开率:50-70%
  • 评价完成率:10-25%

7. Custom Sequence

7. 自定义序列

For custom sequences, ask user:
  1. Goal: What should this sequence accomplish?
  2. Trigger event: What starts this sequence?
  3. Email count: How many emails?
  4. Cadence: How often should emails send?
  5. Tone: Formal, casual, urgent, educational?
Design sequence architecture based on responses.
针对自定义序列,向用户确认:
  1. 目标:该序列需达成什么效果?
  2. 触发事件:什么会启动这个序列?
  3. 邮件数量:需要多少封邮件?
  4. 发送节奏:发送频率是多少?
  5. 语气风格:正式、随意、紧急、教育性?
根据回复设计序列架构。

Conditional Logic Rules

条件逻辑规则

Apply these rules to every sequence:
所有序列均需应用以下规则:

Engagement-Based Branching

基于互动的分支

If opened previous email but didn't click:
  • Emphasize CTA more strongly
  • Add social proof elements
  • Simplify the ask
If clicked previous email:
  • Move faster in sequence
  • Skip reminder emails
  • Advance to stronger offer
If no engagement on 2+ consecutive emails:
  • Slow down cadence
  • Change subject line approach
  • Test different framework
If unsubscribed:
  • Stop sequence immediately
  • Remove from all active lists
若打开了上一封邮件但未点击:
  • 更突出CTA
  • 添加社交证明元素
  • 简化行动要求
若点击了上一封邮件:
  • 加快序列推进速度
  • 跳过提醒邮件
  • 直接推送更优惠的活动
若连续2+封邮件无互动:
  • 放缓发送节奏
  • 更换主题行策略
  • 测试不同框架
若用户退订:
  • 立即停止序列
  • 从所有活跃列表中移除

Time-Based Branching

基于时间的分支

If cart value is high (e.g., over $200):
  • Extend abandoned cart sequence
  • Add personal outreach email
If first purchase:
  • Trigger post-purchase sequence
  • Add to VIP nurture track
If repeat customer:
  • Skip welcome emails
  • Go straight to loyalty sequence
若购物车金额较高(如超过200美元):
  • 延长购物车遗弃召回序列
  • 添加个性化跟进邮件
若首次购买:
  • 触发售后跟进序列
  • 加入VIP培育轨道
若重复购买用户:
  • 跳过欢迎邮件
  • 直接进入忠诚度序列

Output Format Template

输出格式模板

undefined
undefined

Email Sequence: [Sequence Type]

Email Sequence: [Sequence Type]

Business: [from email-profile.md] Industry: [from profile] Trigger: [what starts this sequence] Total Emails: X Duration: X days/weeks Goal: [primary objective]
Business: [from email-profile.md] Industry: [from profile] Trigger: [what starts this sequence] Total Emails: X Duration: X days/weeks Goal: [primary objective]

Sequence Timeline

Sequence Timeline

Day 0 -> Email 1 (immediate) Day 1 -> Email 2 Day 4 -> Email 3 Day 7 -> Email 4 [visual timeline]

Day 0 -> Email 1 (immediate) Day 1 -> Email 2 Day 4 -> Email 3 Day 7 -> Email 4 [visual timeline]

Email 1: [Descriptive Title] (Day 0 / Immediate)

Email 1: [Descriptive Title] (Day 0 / Immediate)

Purpose: [what this email accomplishes]
Subject Lines:
#SubjectScoreReason
1[subject line]85[why this scores high]
2[subject line]80[why this scores high]
3[subject line]78[why this scores high]
Preheader: [30-80 character preview text]
Framework: [PAS/AIDA/BAB/FAB/4Ps/Direct]
Body:
[Full email copy with proper formatting, following the selected framework structure]
CTA: [Button text] -> [link placeholder or description]
Conditional Logic:
  • If opened: Proceed to Email 2 at scheduled time
  • If not opened: Wait 24h, resend with subject line variant #2
  • If clicked CTA: [action - skip email, advance sequence, tag subscriber]
  • If no engagement: [fallback action]
A/B Test Recommendation: [specific element to test for this email]

[Repeat full structure for each email in sequence]

Purpose: [what this email accomplishes]
Subject Lines:
#SubjectScoreReason
1[subject line]85[why this scores high]
2[subject line]80[why this scores high]
3[subject line]78[why this scores high]
Preheader: [30-80 character preview text]
Framework: [PAS/AIDA/BAB/FAB/4Ps/Direct]
Body:
[Full email copy with proper formatting, following the selected framework structure]
CTA: [Button text] -> [link placeholder or description]
Conditional Logic:
  • If opened: Proceed to Email 2 at scheduled time
  • If not opened: Wait 24h, resend with subject line variant #2
  • If clicked CTA: [action - skip email, advance sequence, tag subscriber]
  • If no engagement: [fallback action]
A/B Test Recommendation: [specific element to test for this email]

[Repeat full structure for each email in sequence]

Implementation Notes

Implementation Notes

Platform Setup:
  • [Automation trigger setup instructions]
  • [Segmentation requirements]
  • [Tag/field requirements]
Recommended A/B Tests:
  1. [Test for Email 1]
  2. [Test for Email 3]
  3. [Overall sequence test]
KPI Targets:
MetricTargetIndustry Benchmark
Average Open RateX%X%
Average Click RateX%X%
Conversion RateX%X%
Unsubscribe Rate<0.5%<0.5%
Monitoring:
  • Check performance after 50 subscribers complete sequence
  • Adjust timing if open rates drop >20% between emails
  • Test new subject lines if Email 1 opens <30%
Segment Considerations:
  • [How to adapt for different audience segments]
  • [Mobile vs desktop considerations]
  • [Geographic/timezone notes if applicable]
undefined
Platform Setup:
  • [Automation trigger setup instructions]
  • [Segmentation requirements]
  • [Tag/field requirements]
Recommended A/B Tests:
  1. [Test for Email 1]
  2. [Test for Email 3]
  3. [Overall sequence test]
KPI Targets:
MetricTargetIndustry Benchmark
Average Open RateX%X%
Average Click RateX%X%
Conversion RateX%X%
Unsubscribe Rate<0.5%<0.5%
Monitoring:
  • Check performance after 50 subscribers complete sequence
  • Adjust timing if open rates drop >20% between emails
  • Test new subject lines if Email 1 opens <30%
Segment Considerations:
  • [How to adapt for different audience segments]
  • [Mobile vs desktop considerations]
  • [Geographic/timezone notes if applicable]
undefined

Quality Checklist

质量检查清单

Before delivering sequence, verify:
  • Each email has 3 subject line variants
  • Preheaders are 30-80 characters
  • Each email follows assigned framework structure
  • CTAs are clear and actionable
  • Conditional logic is defined for each email
  • Timing makes sense for business type
  • KPI targets are realistic
  • A/B test recommendations are specific
  • Implementation notes include platform setup
交付序列前,确认以下内容:
  • 每封邮件有3个主题行变体
  • 预头文本为30-80字符
  • 每封邮件遵循指定框架结构
  • CTA清晰且可执行
  • 每封邮件定义了条件逻辑
  • 时间安排符合业务类型
  • KPI目标合理
  • A/B测试建议具体
  • 实施说明包含平台设置内容

Framework Quick Reference

框架速查

Load
../../references/copy-frameworks.md
for detailed structures:
  • PAS: Problem -> Agitate -> Solution
  • AIDA: Attention -> Interest -> Desire -> Action
  • BAB: Before -> After -> Bridge
  • FAB: Features -> Advantages -> Benefits
  • 4Ps: Picture -> Promise -> Prove -> Push
  • Direct: Straightforward, no persuasion layer (transactional emails)
加载
../../references/copy-frameworks.md
获取详细结构:
  • PAS: Problem -> Agitate -> Solution
  • AIDA: Attention -> Interest -> Desire -> Action
  • BAB: Before -> After -> Bridge
  • FAB: Features -> Advantages -> Benefits
  • 4Ps: Picture -> Promise -> Prove -> Push
  • Direct: 直截了当,无说服层(事务性邮件)

Notes

注意事项

  • Always adapt sequence length and cadence to business context
  • B2B sequences should be longer (nurture over 8-12 weeks)
  • E-commerce can be more aggressive (faster cadence)
  • Service businesses benefit from educational content
  • Always include easy unsubscribe option
  • Test sequences with small segment before full deployment
  • Monitor sender reputation metrics (bounce rate, complaint rate)
  • Apple Mail Privacy Protection makes open tracking unreliable - focus on clicks
  • Use sunset policies: remove non-engaged subscribers after 6-12 months
  • 始终根据业务场景调整序列长度和发送节奏
  • B2B序列应更长(培育周期8-12周)
  • 电商可采用更激进的节奏(发送间隔更短)
  • 服务类企业可侧重教育内容
  • 始终提供便捷的退订选项
  • 全面部署前先在小用户群测试序列
  • 监控发件人信誉指标(退信率、投诉率)
  • Apple Mail Privacy Protection使打开率追踪不可靠,重点关注点击率
  • 采用休眠用户清理政策:6-12个月未互动用户从列表中移除

Integration with Other Skills

与其他工具集成

  • Use
    /email audit
    to verify domain deliverability before launching sequences
  • Use
    /email write
    for individual email drafts or rewrites
  • Use
    /email review
    to score and optimize each email in the sequence
  • Use
    /email plan
    to align sequences with overall marketing strategy
  • 启动序列前使用
    /email audit
    验证域名送达能力
  • 使用
    /email write
    生成单封邮件草稿或改写内容
  • 使用
    /email review
    为序列中的每封邮件评分并优化
  • 使用
    /email plan
    使序列与整体营销策略保持一致