Back to Details

email-sequence

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Sequence

邮件序列

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Design and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.
若你看到不熟悉的占位符或需要查看已连接的工具，请参阅CONNECTORS.md。
为任何生命周期或营销活动场景设计并起草包含完整文案、发送时机、分支逻辑及性能基准的完整邮件序列。

Trigger

触发条件

User runs 
/email-sequence
or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.
当用户运行
/email-sequence
命令，或请求创建、设计、搭建或起草邮件序列、drip campaign、培育流程或用户引导系列时触发。

Inputs

输入信息

Gather the following from the user. If not provided, ask before proceeding:
  1. Sequence type — one of:
    • Onboarding
    • Lead nurture
    • Re-engagement
    • Product launch
    • Event follow-up
    • Upgrade/upsell
    • Win-back
    • Educational drip
  2. Goal — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)
  3. Audience — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)
  4. Number of emails (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below
  5. Timing/cadence preferences (optional) — desired spacing between emails (e.g., "every 3 days", "weekly", "aggressive first week then taper off")
  6. Brand voice — if configured in local settings, apply automatically and inform the user. If not configured, ask: "Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone."
  7. Additional context (optional):
    • Specific offers, discounts, or incentives to include
    • CTAs or landing pages to link to
    • Content assets available (blog posts, case studies, videos, guides)
    • Product features to highlight
    • Competitor differentiators to reference
从用户处收集以下信息，若用户未提供，需先询问再继续：
  1. 序列类型 — 以下类型之一：
    • 用户引导
    • 线索培育
    • 用户重激活
    • 产品发布
    • 活动跟进
    • 升级/交叉销售
    • 赢回流失用户
    • 教育类 drip
  2. 目标 — 该序列需要达成的结果（例如：激活新用户、将线索转化为客户、降低用户流失率、提升活动参与度、升级至更高套餐）
  3. 受众 — 接收该序列的人群、所处阶段及任何相关细分信息（职位、行业、行为触发条件、生命周期阶段）
  4. 邮件数量（可选）— 若用户未指定，则根据序列类型，参考下方「序列类型模板」部分的模板推荐合适的数量
  5. 发送时机/节奏偏好（可选）— 邮件之间的理想间隔（例如：「每3天一封」、「每周一封」、「首周密集发送，之后放缓」）
  6. 品牌语调 — 若本地设置中已配置，则自动应用并告知用户。若未配置，询问用户：「你是否有品牌语调指南需要我遵循？如果没有，我将使用清晰、口语化的专业语调。」
  7. 额外上下文（可选）：
    • 需要包含的特定优惠、折扣或激励措施
    • 需要链接的CTA（行动号召）或落地页
    • 可用的内容资产（博客文章、案例研究、视频、指南）
    • 需要突出的产品功能
    • 需要提及的竞品差异化优势

Process

执行流程

1. Sequence Strategy

1. 序列策略

Before drafting any emails, define the overall sequence architecture:
  • Narrative arc — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last?
  • Journey mapping — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion)
  • Escalation logic — how does the intensity, urgency, or value of each email build on the previous one?
  • Success definition — what specific action signals that the sequence has done its job and the recipient should exit?
在起草任何邮件之前，先定义整体序列架构：
  • 叙事脉络 — 整个序列要讲述怎样的故事？从第一封邮件到最后一封，情感和逻辑上的递进是怎样的？
  • 旅程映射 — 将每封邮件对应到购买者或用户旅程的某个阶段（认知、考虑、决策、激活、拓展）
  • 升级逻辑 — 每封邮件的强度、紧迫感或价值如何在前一封的基础上递进？
  • 成功定义 — 哪些具体行为标志着序列已完成目标，收件人应退出序列？

2. Individual Email Design

2. 单封邮件设计

For each email in the sequence, produce:
针对序列中的每封邮件，生成以下内容：

Subject Line

主题行

  • Provide 2-3 options per email
  • Vary approaches: curiosity, benefit-driven, urgency, personalization, question-based
  • Keep under 50 characters where possible; note preview behavior on mobile
  • 每封邮件提供2-3个选项
  • 采用不同策略：引发好奇心、突出利益、制造紧迫感、个性化、提问式
  • 尽可能控制在50字符以内；标注移动端预览显示效果

Preview Text

预览文本

  • 40-90 characters that complement (not repeat) the subject line
  • Should add context or intrigue that increases open likelihood
  • 40-90字符，补充（而非重复）主题行内容
  • 应增加上下文或吸引力，提升邮件打开率

Email Purpose

邮件目的

  • One sentence explaining why this email exists and what it moves the recipient toward
  • 用一句话说明该邮件的存在意义，以及它能推动收件人达成什么目标

Body Copy

正文文案

  • Full draft ready to use
  • Clear hierarchy: hook, body, CTA
  • Short paragraphs (2-3 sentences max)
  • Scannable formatting with bold key phrases where appropriate
  • Personalization tokens where relevant (e.g., first name, company name, product used)
  • 可直接使用的完整草稿
  • 清晰的层级结构：钩子、正文、CTA
  • 短段落（最多2-3句话）
  • 可扫描的格式，必要时对关键内容加粗
  • 相关的个性化标记（例如：名字、公司名称、使用的产品）

Primary CTA

主CTA

  • Button text and destination
  • One primary CTA per email (secondary CTA only if appropriate for the sequence stage)
  • 按钮文本及跳转目标
  • 每封邮件仅设置一个主CTA（仅在序列阶段合适时添加次要CTA）

Timing

发送时机

  • Days after the trigger event or after the previous email
  • Note if timing should adjust based on engagement (e.g., "send sooner if they opened but did not click")
  • 触发事件发生后或上一封邮件发送后的天数
  • 标注是否应根据用户互动调整时机（例如：「若用户已打开但未点击，则提前发送」）

Segment/Condition Notes

受众细分/条件说明

  • Who receives this email vs. who skips it
  • Any behavioral or attribute-based conditions (e.g., "only send to users who have not completed setup")
  • 哪些人会收到这封邮件，哪些人会跳过
  • 任何基于行为或属性的条件（例如：「仅发送给未完成设置的用户」）

3. Sequence Logic

3. 序列逻辑

Define the flow control for the sequence:
  • Branching conditions — alternate paths based on engagement. For example:
    • "If opened email 2 but did not click CTA, send email 2b (softer re-ask) instead of email 3"
    • "If clicked CTA in email 1, skip email 2 and go directly to email 3"
  • Exit conditions — when a recipient converts (completes the desired action), remove them from the sequence. Define what "conversion" means for this sequence.
  • Re-entry rules — can someone re-enter the sequence? Under what conditions? (e.g., "if a user churns again 90 days later, re-enter the win-back sequence")
  • Suppression rules — do not send if the recipient is already in another active sequence, has unsubscribed from marketing, or has contacted support in the last 48 hours
定义序列的流程控制规则：
  • 分支条件 — 根据用户互动设置不同路径。例如：
    • 「若用户打开了邮件2但未点击CTA，则发送邮件2b（更温和的再次请求）而非邮件3」
    • 「若用户点击了邮件1的CTA，则跳过邮件2，直接发送邮件3」
  • 退出条件 — 当收件人完成期望操作（转化）时，将其从序列中移除。明确该序列中「转化」的定义。
  • 重新加入规则 — 用户能否重新加入序列？在什么条件下可以？（例如：「若用户在90天后再次流失，可重新加入赢回序列」）
  • 排除规则 — 若收件人已在其他活跃序列中、已退订营销邮件，或在过去48小时内联系过客服，则不发送邮件

4. Performance Benchmarks

4. 性能基准

Provide expected benchmarks based on the sequence type so the user can set targets:
MetricOnboardingLead NurtureRe-engagementWin-back
Open rate50-70%20-30%15-25%15-20%
Click-through rate10-20%3-7%2-5%2-4%
Conversion rate15-30%2-5%3-8%1-3%
Unsubscribe rate<0.5%<0.5%1-2%1-3%
Adjust benchmarks based on industry and audience if the user has provided that context.
根据序列类型提供预期基准，帮助用户设定目标：
指标用户引导线索培育用户重激活赢回流失用户
打开率50-70%20-30%15-25%15-20%
点击率10-20%3-7%2-5%2-4%
转化率15-30%2-5%3-8%1-3%
退订率<0.5%<0.5%1-2%1-3%
若用户提供了行业和受众相关信息，可调整上述基准。

Sequence Type Templates

序列类型模板

Use these as starting frameworks. Adapt length and content based on the user's goal and audience.
Onboarding (5-7 emails over 14-21 days): Welcome and set expectations -- Quick win to demonstrate value -- Core feature deep dive -- Advanced feature or integration -- Social proof and community -- Check-in and feedback request -- Upgrade prompt or next steps
Lead Nurture (4-6 emails over 3-4 weeks): Value-first educational content -- Pain point identification -- Solution positioning with proof -- Social proof and results -- Soft CTA (trial, demo, resource) -- Direct CTA (buy, book, sign up)
Re-engagement (3-4 emails over 10-14 days): "We miss you" with a compelling reason to return -- Value reminder highlighting what they are missing -- Incentive or exclusive offer -- Last chance with clear deadline
Win-back (3-5 emails over 30 days): Friendly check-in asking what went wrong -- What is new since they left -- Special offer or incentive to return -- Feedback request (even if they do not come back) -- Final goodbye with door open
Product Launch (4-6 emails over 2-3 weeks): Teaser or pre-announcement -- Launch announcement with full details -- Feature spotlight or use case -- Social proof and early results -- Limited-time offer or bonus -- Last chance or reminder
Event Follow-up (3-4 emails over 7-10 days): Thank you with key takeaways or recordings -- Resource roundup from the event -- Related offer or next step -- Feedback survey
Upgrade/Upsell (3-5 emails over 2-3 weeks): Usage milestone or success celebration -- Feature gap or limitation they are hitting -- Upgrade benefits with proof -- Limited-time incentive -- Direct comparison of plans
Educational Drip (5-8 emails over 4-6 weeks): Introduction and what they will learn -- Lesson 1: foundational concept -- Lesson 2: intermediate concept -- Lesson 3: advanced concept -- Practical application or exercise -- Resource roundup -- Graduation and next steps
将以下内容作为初始框架，根据用户的目标和受众调整长度及内容。
用户引导（14-21天内发送5-7封邮件）： 欢迎并说明预期 -- 快速展示价值的小成就 -- 核心功能深度解析 -- 高级功能或集成介绍 -- 社交证明与社区 -- 跟进并请求反馈 -- 升级提示或后续步骤
线索培育（3-4周内发送4-6封邮件）： 以价值为核心的教育内容 -- 痛点识别 -- 带证明的解决方案定位 -- 社交证明与成果 -- 温和CTA（试用、演示、资源）-- 直接CTA（购买、预约、注册）
用户重激活（10-14天内发送3-4封邮件）： 「我们想念你」并给出回归的诱人理由 -- 价值提醒，突出用户错过的内容 -- 激励措施或专属优惠 -- 最后机会，明确截止日期
赢回流失用户（30天内发送3-5封邮件）： 友好跟进，询问问题所在 -- 用户离开后新增的内容 -- 专属优惠或回归激励 -- 请求反馈（即使用户不回归）-- 最终告别，保留未来合作可能
产品发布（2-3周内发送4-6封邮件）： 预告或预公告 -- 发布公告及完整详情 -- 功能亮点或使用场景 -- 社交证明与早期成果 -- 限时优惠或福利 -- 最后机会提醒
活动跟进（7-10天内发送3-4封邮件）： 致谢并提供关键要点或录播内容 -- 活动相关资源汇总 -- 相关优惠或后续步骤 -- 反馈调研
升级/交叉销售（2-3周内发送3-5封邮件）： 使用里程碑或成功庆祝 -- 用户遇到的功能缺口或限制 -- 升级后的好处及证明 -- 限时激励 -- 套餐直接对比
教育类Drip（4-6周内发送5-8封邮件）： 介绍及学习内容预告 -- 第1课：基础概念 -- 第2课：中级概念 -- 第3课：高级概念 -- 实际应用或练习 -- 资源汇总 -- 结业及后续步骤

Tool Integration

工具集成

If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io)

若已连接邮件营销工具（如Klaviyo、Mailchimp、Customer.io）

  • Reference how to set up the sequence as a flow or automation in the platform
  • Note any platform-specific features to use (e.g., smart send time, conditional splits, A/B testing)
  • Map the branching logic to the platform's visual flow builder concepts
  • 说明如何在平台中将序列设置为流程或自动化任务
  • 标注可使用的平台特定功能（例如：智能发送时间、条件拆分、A/B测试）
  • 将分支逻辑映射到平台的可视化流程构建器概念

If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo)

若已连接营销自动化或CRM工具（如HubSpot、Marketo）

  • Reference lead scoring data to inform segmentation and exit conditions
  • Use lifecycle stage data to tailor messaging per segment
  • Note how to set enrollment triggers based on CRM properties or list membership
  • 参考线索评分数据，指导受众细分和退出条件设置
  • 利用生命周期阶段数据，为不同细分群体定制消息
  • 说明如何基于CRM属性或列表成员身份设置加入触发条件

If no tools are connected

若未连接任何工具

  • Deliver all email content in copy-paste-ready format
  • Include a setup checklist the user can follow in any email platform:
    1. Create the automation or flow
    2. Set the enrollment trigger
    3. Add each email with the specified delays
    4. Configure branching and exit conditions
    5. Set up tracking for the recommended metrics
  • 提供可直接复制粘贴的所有邮件内容
  • 包含用户可在任何邮件平台中遵循的设置清单：
    1. 创建自动化或流程
    2. 设置加入触发条件
    3. 添加每封邮件并设置指定延迟
    4. 配置分支和退出条件
    5. 为推荐指标设置跟踪

Output

输出内容

Present the complete sequence with the following sections:
按以下板块呈现完整序列：

Sequence Overview Table

序列概览表

#Subject LinePurposeTimingPrimary CTACondition
序号主题行目的发送时机主CTA条件

Full Email Drafts

完整邮件草稿

Each email with subject line options, preview text, purpose, body copy, CTA, timing, and segment notes.
每封邮件包含主题行选项、预览文本、目的、正文文案、CTA、发送时机和受众细分说明。

Sequence Flow Diagram

序列流程图

A text-based diagram showing the email flow, branching paths, and exit points. Use a clear format such as:
[Trigger] --> Email 1 (Day 0)
                |
          Opened? --Yes--> Email 2 (Day 3)
                |              |
                No        Clicked CTA? --Yes--> [EXIT: Converted]
                |              |
                v              No
          Email 1b (Day 2)     |
                |              v
                +--------> Email 3 (Day 7)
                               |
                               v
                          Email 4 (Day 10)
                               |
                          [EXIT: Sequence complete]
基于文本的流程图，展示邮件流程、分支路径和退出点。使用清晰格式，例如：
[Trigger] --> Email 1 (Day 0)
                |
          Opened? --Yes--> Email 2 (Day 3)
                |              |
                No        Clicked CTA? --Yes--> [EXIT: Converted]
                |              |
                v              No
          Email 1b (Day 2)     |
                |              v
                +--------> Email 3 (Day 7)
                               |
                               v
                          Email 4 (Day 10)
                               |
                          [EXIT: Sequence complete]

Branching Logic Notes

分支逻辑说明

Summary of all conditions, exits, and suppressions in a reference list.
汇总所有条件、退出规则和排除规则的参考列表。

A/B Test Suggestions

A/B测试建议

  • 2-3 recommended A/B tests (subject lines, CTA text, send time, email length)
  • What to test, how to split, and how to measure the winner
  • 2-3个推荐的A/B测试（主题行、CTA文本、发送时间、邮件长度）
  • 测试内容、分组方式及获胜标准

Metrics to Track

需跟踪的指标

  • Primary conversion metric for the sequence
  • Per-email metrics: open rate, CTR, unsubscribe rate
  • Sequence-level metrics: overall conversion rate, time to conversion, drop-off points
  • Recommended review cadence (e.g., "Review performance weekly for the first month, then monthly")
  • 序列的主转化指标
  • 单封邮件指标：打开率、点击率、退订率
  • 序列级指标：整体转化率、转化时长、流失节点
  • 推荐的复盘频率（例如：「首月每周复盘效果，之后每月复盘」）

After the Sequence

序列完成后

Ask: "Would you like me to:
  • Revise the copy or tone for any specific email?
  • Add a branching path for a specific scenario?
  • Create a variation of this sequence for a different audience segment?
  • Draft the A/B test variants for the subject lines?
  • Build a companion sequence (e.g., a post-purchase follow-up after this lead nurture converts)?"
询问用户：「你是否需要我：
  • 修改某封邮件的文案或语调？
  • 为特定场景添加分支路径？
  • 为不同受众细分群体创建该序列的变体？
  • 起草主题行的A/B测试变体？
  • 构建配套序列（例如：线索培育转化后的售后跟进序列）？」