email-drafting
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEmail Drafting
开发信撰写
Pure reasoning skill for writing cold emails. No scripts, no tools — just frameworks, patterns, and examples from real campaigns that consistently generate replies.
Auto-loaded by during Phase 3, or standalone when the user asks for email copy directly.
cold-email-outreach用于撰写开发信的纯推理型技能。无固定脚本、无需工具——仅依靠经过验证的框架、模式和真实营销活动案例，持续提升回复率。
在「cold-email-outreach」工具的第3阶段会自动加载，或当用户直接请求邮件文案时独立启用。
When to Auto-Load
自动加载场景
Load this skill when:
- User says "write a cold email", "draft outreach", "help me with email copy", "write a sequence"
- An upstream skill reaches its email generation phase
- invokes Phase 3
cold-email-outreach
满足以下条件时加载本技能：
- 用户提出“写一封开发信”“起草外展邮件”“帮我写邮件文案”“设计邮件序列”等需求
- 上游技能进入邮件生成阶段
- 「cold-email-outreach」触发第3阶段
Phase 0: Intake
阶段0：信息收集
Collect campaign context before writing anything. Ask all questions at once, organized by category. When called from , skip questions already answered upstream.
cold-email-outreach在撰写前先收集营销活动背景信息。按类别一次性提出所有问题。若由「cold-email-outreach」调用，可跳过已在上游回答过的问题。
Campaign Context
营销活动背景
- What product/service are you selling?
- What problem does it solve? Who feels this pain most acutely?
- What's the campaign angle? (hiring signal, competitor displacement, pain-based, event-triggered, etc.)
- Is there a specific signal or trigger? (job posting, G2 review, LinkedIn engagement, funding round, etc.)
- 你推广的产品/服务是什么？
- 它解决什么问题？哪些人群受此问题困扰最深？
- 营销活动的切入点是什么？（招聘信号、竞品替代、痛点驱动、事件触发等）
- 是否有特定的触发信号？（招聘启事、G2评论、LinkedIn互动、融资消息等）
Audience
受众信息
- Who is the recipient? (title, seniority, department)
- What keeps them up at night? (daily frustrations relevant to your product)
- What objections will they have? (budget, switching cost, "we already have X", timing)
- 收件人是谁？（职位、职级、部门）
- 他们日常面临哪些困扰？（与你的产品相关的痛点）
- 他们可能提出哪些异议？（预算、转换成本、“我们已经在用X工具”、时机不合适等）
Proof & Credibility
信任背书
- What social proof do you have? (customer logos, case studies, metrics)
- Name 2-3 peer companies the recipient would recognize as similar to them
- Any hard metrics? (cost savings, speed improvement, % lift)
- 你有哪些社交证明？（客户logo、案例研究、数据指标）
- 列出2-3个收件人熟知的同行业企业
- 有哪些硬核数据？（成本节约、效率提升、转化率增长百分比等）
Tone & Style
语气风格
- What tone fits? (casual-direct, professional-sharp, provocative, empathetic)
- Who is the sender? (founder, AE, SDR — this affects voice)
- Any brand guidelines or words to avoid?
- 适合的语气是什么？（随性直接、专业干练、带有挑衅性、共情式）
- 发件人是谁？（创始人、销售代表、销售开发专员——这会影响语气）
- 是否有品牌规范或需规避的词汇？
Sequence
邮件序列
- How many touches? (default: 3)
- What's the desired CTA? (call, demo, reply, resource download)
- Email-only or multi-channel? (email + LinkedIn, email + phone)
- 计划发送多少轮邮件？（默认：3轮）
- 期望的行动号召（CTA）是什么？（电话沟通、产品演示、回复邮件、下载资源）
- 仅邮件渠道还是多渠道？（邮件+LinkedIn、邮件+电话）
Phase 1: Draft Emails
阶段1：撰写邮件
Email Structure Formula
邮件结构公式
Every cold email follows this skeleton:
Hook (1 sentence) → Evidence (1-2 sentences) → Offer (1 sentence)Word count targets:
- Cold intro (Touch 1): 50-90 words
- Follow-up (Touch 2-3): 30-50 words
- Breakup (final touch): 20-40 words
每封开发信都遵循以下框架：
钩子（1句话）→ 证据（1-2句话）→ 邀约（1句话）字数要求：
- 初次开发信（第1轮）：50-90词
- 跟进邮件（第2-3轮）：30-50词
- 收尾邮件（最后一轮）：20-40词
Frameworks
撰写框架
Pick the framework that matches the campaign angle:
| Framework | Structure | Best For |
|---|---|---|
| PAS | Problem → Agitate → Solve | Pain-based signals (complaint posts, operational friction) |
| BAB | Before → After → Bridge | Aspirational buyers (growth-stage, scaling companies) |
| AIDA | Attention → Interest → Desire → Action | Cold database outreach (no specific signal) |
| Signal-Proof-Ask | Signal → Proof → Soft ask | Signal-based campaigns (hiring, engagement, events) |
根据营销活动切入点选择对应的框架：
| 框架 | 结构 | 适用场景 |
|---|---|---|
| PAS | 问题 → 激化 → 解决方案 | 痛点触发类活动（投诉帖、运营摩擦） |
| BAB | 过去 → 未来 → 桥梁 | 有增长需求的客户（成长期、扩张型企业） |
| AIDA | 注意 → 兴趣 → 欲望 → 行动 | 无特定信号的冷触达（批量数据库外展） |
| Signal-Proof-Ask | 信号 → 证据 → 软性邀约 | 信号触发类活动（招聘、互动、事件） |
Personalization Tiers
个性化层级
Choose based on campaign size and expected ROI per lead:
| Tier | What It Means | Lead Volume | Expected Reply Rate |
|---|---|---|---|
| Tier 1 (Generic) | Merge fields only ( | 500+ leads | 1-3% |
| Tier 2 (Segment) | Industry/role-specific pain points + proof swaps. One template per segment. | 50-500 leads | 3-7% |
| Tier 3 (Deep) | Reference a specific signal (their post, comment, job posting, news). Unique per lead. | 1-50 leads | 8-20% |
根据活动规模和单线索预期ROI选择：
| 层级 | 定义 | 线索数量 | 预期回复率 |
|---|---|---|---|
| 层级1（通用型） | 仅使用合并字段（ | 500+条 | 1-3% |
| 层级2（细分型） | 针对行业/职位的特定痛点+定制化信任背书，每个细分群体使用一个模板。 | 50-500条 | 3-7% |
| 层级3（深度型） | 引用特定信号（他们的帖子、评论、招聘启事、新闻），每条线索的邮件均独一无二。 | 1-50条 | 8-20% |
Subject Line Patterns
标题模式
8 proven patterns from real campaigns:
| # | Pattern | Example |
|---|---|---|
| 1 | Signal reference | "Before you fill that [role] role" |
| 2 | Peer framing | "What TIA members are doing with AI workers" |
| 3 | Question | "Is [Company] still [doing thing product fixes]?" |
| 4 | Replacement | "Looking for a [competitor] replacement?" |
| 5 | Data hook | "$150K agency study → $8K. 48 hours." |
| 6 | Empathy | "When [event that affected them]" |
| 7 | Direct | "[Topic] for [Company]" |
| 8 | Curiosity | "How [peer company] did [interesting thing]" |
Rules for subject lines:
- Under 50 characters
- No ALL CAPS, no exclamation marks, no emoji
- No "quick question" or "touching base"
来自真实活动的8种验证有效的标题模式：
| 序号 | 模式 | 示例 |
|---|---|---|
| 1 | 信号引用 | "Before you fill that [role] role" |
| 2 | 同行参照 | "What TIA members are doing with AI workers" |
| 3 | 提问式 | "Is [Company] still [doing thing product fixes]?" |
| 4 | 竞品替代 | "Looking for a [competitor] replacement?" |
| 5 | 数据钩子 | "$150K agency study → $8K. 48 hours." |
| 6 | 共情式 | "When [event that affected them]" |
| 7 | 直接式 | "[Topic] for [Company]" |
| 8 | 好奇心驱动 | "How [peer company] did [interesting thing]" |
标题规则：
- 字数少于50字符
- 不使用全大写、感叹号、表情符号
- 避免使用“快速提问”“特此跟进”这类表述
Tone Guidance
语气指南
| Tone | When to Use | Voice Example |
|---|---|---|
| Casual-Direct | SDR sending to peers, startup-to-startup | "Hey — saw your post. We work on the same problem." |
| Professional-Sharp | Enterprise outreach, VP+ recipients | "I wanted to reach out because [specific reason]." |
| Provocative | Competitive displacement, challenger positioning | "Your current tool is costing you more than you think." |
| Empathetic | Orphan capture, pain-based outreach | "I know switching platforms mid-cycle is brutal." |
| 语气 | 适用场景 | 示例表述 |
|---|---|---|
| 随性直接 | 销售开发专员对接同行、初创企业间沟通 | "Hey — 看到你的帖子了，我们在解决同一个问题。" |
| 专业干练 | 企业级客户触达、对接VP及以上职级收件人 | "我联系您是因为[具体原因]。" |
| 带有挑衅性 | 竞品替代、挑战者定位 | "你当前使用的工具正在让你付出更高的成本。" |
| 共情式 | 潜在客户挖掘、痛点驱动型外展 | "我知道在周期中途切换平台有多痛苦。" |
Sequence Design Principles
邮件序列设计原则
| Touch | Timing | Purpose | Length | Notes |
|---|---|---|---|---|
| Touch 1 | Day 1 | Hook + proof + soft CTA | 50-90 words | The only email that can be longer |
| Touch 2 | Day 3-5 | New angle or asset | 30-50 words | Different proof point, not a "bump" |
| Touch 3 | Day 7-10 | Different proof point or social | 20-40 words | Shorter = better this late |
| Touch 4 | Day 14-21 | Breakup (optional) | 20-30 words | Remove pressure, leave door open |
Sequence rules:
- Never repeat the same CTA across touches
- Each touch needs a new reason to reply
- Later touches = shorter emails
- Never send a "just checking in" or "bumping this" — add value or stop
| 轮次 | 发送时机 | 目的 | 长度 | 注意事项 |
|---|---|---|---|---|
| 第1轮 | 第1天 | 钩子+证据+软性CTA | 50-90词 | 唯一允许较长的邮件 |
| 第2轮 | 第3-5天 | 新切入点或新素材 | 30-50词 | 使用新的信任背书，而非单纯跟进 |
| 第3轮 | 第7-10天 | 新信任背书或社交证明 | 20-40词 | 越往后的邮件越短越好 |
| 第4轮（可选） | 第14-21天 | 收尾邮件 | 20-30词 | 降低压力，为后续沟通留有余地 |
序列规则：
- 不同轮次的邮件不要重复相同的CTA
- 每轮邮件都要给收件人一个新的回复理由
- 后续邮件需更简短
- 绝对不要发送“只是跟进一下”的邮件——要么提供价值，要么停止触达
Hard Rules
硬性规则
These are non-negotiable. Every email must pass all 10:
- No filler openers. Never "I hope this finds you well", "I hope you're having a great week", "just reaching out"
- No "just checking in" follow-ups. Every touch adds a new reason to reply
- Max 4 paragraphs per email. Most should be 2-3
- Every email references something specific to the recipient. Title, company, signal, industry — never fully generic
- Exactly one CTA per email. Always low-friction (15-min call, "worth a look?", "open to chatting?")
- Never lie about how you found them. If it was a database search, don't say "I came across your profile"
- No filler words. Ban: synergy, leverage, circle back, loop in, touch base, align, ping
- Subject lines under 50 chars. No caps, no exclamation marks, no emoji
- No selling in the first sentence. Lead with them, not you
- Sign off simply. Name only, or Name + one-line title. No "Best regards", no "Looking forward to hearing from you"
以下规则不容违反，每封邮件都必须满足全部10条：
- 无冗余开场：绝对不要使用“祝您一切安好”“祝您本周愉快”“特此联系”这类表述
- 无单纯跟进邮件：每轮触达都要添加新的回复理由
- 每封邮件最多4段：大部分邮件应控制在2-3段
- 每封邮件都要引用收件人特定信息：职位、公司、触发信号、行业——绝对不能完全通用
- 每封邮件仅一个CTA：始终选择低门槛的行动（15分钟通话、“值得一看吗？”“愿意聊聊吗？”）
- 不要谎报获取渠道：如果是从数据库搜索到的，不要说“我看到了您的资料”
- 无冗余词汇：禁用：协同效应、杠杆作用、后续跟进、纳入讨论、特此联系、对齐、联系
- 标题少于50字符：不使用大写、感叹号、表情符号
- 开头不要推销：先提及收件人，而非自己的产品
- 简洁落款：仅留姓名，或姓名+一行职位。不要使用“此致”“期待您的回复”
Phase 2: Review & Refine
阶段2：审核与优化
- Present 3-5 draft variants for Touch 1 (different angles/frameworks)
- Ask user to pick a direction or combine elements
- Generate the full sequence based on chosen direction
- Iterate max 3 rounds — after that, ship it
- 提供3-5版第1轮邮件草稿（不同切入点/框架）
- 请用户选择方向或组合不同元素
- 根据选定方向生成完整邮件序列
- 最多迭代3轮——之后即可发送
Example Library
示例库
Real emails from real campaigns. Use these as structural templates — swap product, proof, and signal for the current campaign.
来自真实营销活动的邮件模板。可将其作为结构模板，替换为当前活动的产品、证据和信号。
Type 1: Signal-Based (Hiring)
类型1：信号触发（招聘）
Signal source: LinkedIn Jobs — company posting for role that product replaces
Framework: Signal-Proof-Ask
Subject: Before you fill that {role_title} role
Hi {first_name} — I noticed you're hiring for a {role_title} at {company}. Before you finalize that hire, worth a quick look at what companies like DHL, Werner, and MODE Global are doing instead — deploying AI workers for exactly this function.4x cheaper than a BPO equivalent. 10x the call capacity. Runs 24/7. Happy to send over a quick overview or jump on a 15-minute call if the timing is right.
Why it works: Opens with their specific hiring signal (proves relevance). Names peer companies (social proof). Quantifies the alternative (4x, 10x). Low-friction CTA.
信号来源：LinkedIn职位——企业发布的职位可被你的产品替代
框架：Signal-Proof-Ask
标题：Before you fill that {role_title} role
Hi {first_name} — 我注意到您正在为{company}招聘{role_title}。在您最终确定招聘人选前，不妨快速了解一下DHL、Werner和MODE Global等企业的做法——部署AI员工来完成这项工作。成本比BPO等效方案低4倍，通话容量高10倍，7*24小时运行。如果时机合适，我很乐意发送一份快速概述或进行15分钟的通话。
成功原因：以收件人特定的招聘信号开场（证明相关性），提及同行企业（社交证明），量化替代方案的优势（4倍、10倍），CTA门槛低。
Type 2: Signal-Based (Peer/Association)
类型2：信号触发（同行/协会）
Signal source: Industry association membership directory
Framework: BAB (Before → After → Bridge)
Subject: What TIA members are doing with AI workers
Hi {first_name} — as a TIA member running a serious freight brokerage, you're probably seeing the same thing we are: the best operators are rethinking how they staff carrier-facing functions.Companies like Werner, MODE Global, and Circle Logistics — TIA members you'd recognize — have already deployed AI workers for carrier calls, check calls, and load coordination. I wanted to reach out because HappyRobot works specifically with freight brokers at this scale.Worth a 15-minute call to see if it's relevant for {company}?
Why it works: Peer framing ("TIA members you'd recognize") creates belonging pressure. Names real members using the product. Positions as industry-specific, not generic.
信号来源：行业协会会员目录
框架：BAB（过去→未来→桥梁）
标题：What TIA members are doing with AI workers
Hi {first_name} — 作为TIA会员，您运营着一家专业的货运经纪公司，您可能也注意到了：顶尖运营商正在重新思考如何配置面向承运人的岗位。Werner、MODE Global和Circle Logistics等您熟知的TIA会员企业，已经部署AI员工来处理承运商呼叫、核查呼叫和装载协调工作。我联系您是因为HappyRobot专门为这个规模的货运经纪公司提供服务。值得花15分钟了解一下是否适用于{company}吗？
成功原因：同行定位（“您熟知的TIA会员”）带来归属感压力，提及真实使用产品的会员，定位为行业专属而非通用服务。
Type 3a: Signal-Based (Competitor Engagement — Liker)
类型3a：信号触发（竞品互动——关注者）
Signal source: LinkedIn Sales Navigator — engaged with competitor company page content
Framework: Signal-Proof-Ask
Subject: The other side of freight AI
Hi {first_name} — I noticed you've been following the freight AI space and wanted to reach out. HappyRobot is the other side of that conversation — we're the platform 8 of the top 10 US freight brokers including DHL and Werner run for AI carrier calls.If you're evaluating options in this space, I'd love to show you what enterprise-grade looks like. 15 minutes?
Why it works: Acknowledges their research without calling out the competitor by name in email (saves that for LinkedIn). "Other side of that conversation" is intriguing. Proof point (8 of top 10) is specific and strong.
信号来源：LinkedIn Sales Navigator——关注竞品企业主页内容
框架：Signal-Proof-Ask
标题：The other side of freight AI
Hi {first_name} — 我注意到您一直在关注货运AI领域的动态，特此联系。HappyRobot是这场对话的另一方——我们的平台被包括DHL和Werner在内的美国前10大货运经纪公司中的8家用于AI承运商呼叫。如果您正在评估该领域的方案，我很乐意向您展示企业级服务的标准。15分钟可以吗？
成功原因：认可收件人的研究行为，但未在邮件中提及竞品名称（留到LinkedIn沟通时再说）。“对话的另一方”颇具吸引力，具体的信任背书（前10大中的8家）说服力强。
Type 3b: Signal-Based (Competitor Engagement — Commenter)
类型3b：信号触发（竞品互动——评论者）
Signal source: Same as 3a but lead left a comment (higher intent)
Framework: Signal-Proof-Ask with comment reference
Subject: Re: your comment on freight AI
Hi {first_name} — I saw your comment on {competitor}'s post about {topic}. That's exactly the problem we work on. HappyRobot powers AI carrier calls for DHL, Werner, and 8 of the top 10 US freight brokers.If you're actively looking at this, worth 15 minutes to see the other option?
Why it works: References their exact comment (Tier 3 personalization). "Actively looking at this" matches their behavior. Even shorter than 3a because higher-intent leads need less convincing.
信号来源：与3a相同，但线索留下了评论（意向更高）
框架：Signal-Proof-Ask（引用评论）
标题：Re: your comment on freight AI
Hi {first_name} — 我看到您在{competitor}关于{topic}的帖子下的评论。这正是我们解决的问题。HappyRobot为DHL、Werner和美国前10大货运经纪公司中的8家提供AI承运商呼叫服务。如果您正在积极关注这个领域，值得花15分钟了解另一种选择吗？
成功原因：引用收件人的具体评论（层级3个性化），“积极关注这个领域”匹配其行为，比3a更简短，因为高意向线索无需过多说服。
Type 4: Pain-Based (Commenter)
类型4：痛点驱动（评论者）
Signal source: LinkedIn post search for pain-language keywords
Framework: PAS (Problem → Agitate → Solve)
For commenters (wrote about the pain):
Hi {first_name}, saw your comment on the {source} post about {pain_topic}. "{comment_snippet}..." — that resonated.We've been working with brokers who had the same issue. HappyRobot handles {relevant_task} so your team doesn't have to.Worth a quick look?
For reactors (liked/reacted to pain content):
Hi {first_name}, noticed you've been following the conversation around {pain_topic} on LinkedIn.If {company} is dealing with {specific_pain}, we might be able to help. HappyRobot automates {relevant_task} for freight brokers — no extra headcount needed.Open to a quick chat?
Why it works: Quotes their own words back to them (strongest personalization). Empathetic tone — no hard sell. Short. The reactor version is lighter-touch because the signal is weaker.
信号来源：LinkedIn帖子搜索——含痛点关键词的内容
框架：PAS（问题→激化→解决方案）
针对评论者（曾提及痛点）：
Hi {first_name}，我看到您在{source}关于{pain_topic}的帖子下的评论。“{comment_snippet}...”——我深有同感。我们一直在与有同样问题的经纪公司合作。HappyRobot可以处理{relevant_task}，让您的团队无需再为此费心。值得快速了解一下吗？
针对互动者（点赞/互动过痛点内容）：
Hi {first_name}，我注意到您一直在LinkedIn上关注{pain_topic}相关的讨论。如果{company}也在面临{specific_pain}的问题，我们或许能提供帮助。HappyRobot为货运经纪公司自动化处理{relevant_task}——无需额外招聘人员。愿意快速聊聊吗？
成功原因：引用收件人自己的话（最强的个性化方式），语气温和——无强硬推销，篇幅简短。互动者版本更轻量化，因为信号强度较弱。
Type 5: Competitive Displacement
类型5：竞品替代
Signal source: G2 reviews (1-star), public complaints, known competitor customers
Framework: PAS
Subject: UserTesting alternatives in 2026
{first_name} — I'll keep this short. If you've run into participant quality issues with UserTesting, you're not alone. HubSpot and Glassdoor both moved to Outset after hitting the same wall.We use Prolific-verified participants instead of a general panel. Different quality tier entirely. Worth 20 minutes to compare?
Why it works: Validates their frustration without bashing the competitor. Names companies they'd respect. Explains the "why" behind the switch (Prolific-verified participants). CTA is specific (20 minutes, comparison framing).
信号来源：G2评论（1星）、公开投诉、已知竞品客户
框架：PAS
标题：UserTesting alternatives in 2026
{first_name} — 我长话短说。如果您在使用UserTesting时遇到了参与者质量问题，您并不孤单。HubSpot和Glassdoor都在遇到同样的问题后转向了Outset。我们使用Prolific认证的参与者，而非普通面板。质量层级完全不同。值得花20分钟对比一下吗？
成功原因：验证收件人的挫败感但不贬低竞品，提及他们认可的企业，解释切换的原因（Prolific认证参与者），CTA具体（20分钟，对比定位）。
Type 6: ABM / Enterprise
类型6：ABM / 企业级
Signal source: Target account list, vertical-specific research
Framework: AIDA
Touch 1:
{first_name} — WeightWatchers cut their per-study research cost from $150K to $8K using Outset's AI-moderated interviews. They run 3x the studies they used to, in half the time.I put together a quick breakdown of what this could look like for {company}'s {vertical} research. Worth 20 minutes?
Touch 3 (Day 7):
Following up with something concrete — built a rough ROI model using {industry} benchmarks. Even conservative numbers show a 6-8x reduction in per-study cost.Happy to walk through the math. 15 minutes?
Touch 5 (Day 14):
Last note from me. If research cost or speed isn't a priority right now, totally understand. But if it is — the WeightWatchers and HubSpot numbers are worth seeing.Open to a quick benchmark call? No demo, just data.
Why it works: Leads with a specific customer story and hard numbers. Each touch adds new value (case study → ROI model → benchmark offer). Breakup touch removes pressure. CTA evolves: overview → walk-through → benchmark.
信号来源：目标客户列表、垂直领域专项研究
框架：AIDA
第1轮：
{first_name} — WeightWatchers使用Outset的AI主持访谈，将每项研究的成本从15万美元降至8000美元。他们现在能运行的研究数量是之前的3倍，时间缩短一半。我为{company}的{vertical}研究整理了一份快速分析，展示了类似方案的效果。值得花20分钟了解吗？
第3轮（第7天）：
跟进并提供具体内容——我使用{industry}基准数据构建了一个粗略的ROI模型。即使是保守计算，也能将每项研究的成本降低6-8倍。我很乐意带您过一遍计算过程。15分钟可以吗？
第5轮（第14天）：
这是我最后一次联系您。如果目前研究成本或速度不是优先事项，我完全理解。但如果它成为您的关注点，WeightWatchers和HubSpot的数据值得一看。愿意进行一次快速基准对比通话吗？无产品演示，仅分享数据。
成功原因：以具体的客户案例和硬核数据开头，每轮邮件都添加新价值（案例研究→ROI模型→基准对比邀约），收尾邮件降低压力，CTA逐步演变：概述→演示→基准对比。
Type 7: Follow-Up Patterns (Touch 2+)
类型7：跟进邮件模式（第2轮及以后）
New angle (not a bump):
{first_name} — different angle from my last email. {Peer company} just published results from their first quarter using {product}: {specific metric}. Thought it might be relevant given {company}'s {situation}.
Asset-led:
Put together a one-page breakdown of {topic relevant to them}. No pitch — just data. Want me to send it over?
Social proof drop:
Quick update — {new customer} just went live with us last week. Similar setup to {company}. Happy to share what their onboarding looked like.
Breakup:
I'll keep this short — if the timing isn't right, no worries at all. But if {problem} comes back up, I'm an easy call away. Cheers.
新切入点（非单纯跟进）：
{first_name} — 这是与上一封邮件不同的切入点。{Peer company}刚刚发布了使用{product}第一季度的成果：{specific metric}。考虑到{company}的{situation}，我认为这可能与您相关。
素材驱动：
我整理了一份与您相关的{topic}的单页分析。无推销内容——仅数据。需要我发给您吗？
社交证明更新：
快速更新——{new customer}上周刚刚启用我们的服务，他们的情况与{company}类似。我很乐意分享他们的入职流程。
收尾邮件：
我长话短说——如果时机不合适，完全没问题。但如果{problem}再次出现，您可以随时联系我。顺颂商祺。
Type 8: Re-engagement (90-Day)
类型8：重新触达（90天后）
Signal source: Outreach log — leads contacted 90+ days ago with no reply, or leads who filled the role your product replaces
Framework: Signal-Proof-Ask
Hi {first_name} — we chatted about 3 months ago when you were hiring for {role}. Curious how it's going. If you're still feeling the pain on {problem}, a few things have changed on our end worth seeing.15 minutes to catch up?
Why it works: References the original conversation and signal. Acknowledges time has passed. "A few things have changed" creates curiosity without overselling.
信号来源：外展记录——90天前联系过但无回复的线索，或已招聘了你的产品可替代的职位的线索
框架：Signal-Proof-Ask
Hi {first_name} — 大约3个月前我们聊过，当时您正在招聘{role}。我很好奇进展如何。如果您仍然在{problem}上感到困扰，我们这边有一些新变化值得了解。花15分钟聊聊近况可以吗？
成功原因：提及最初的对话和信号，承认时间已过去，“一些新变化”引发好奇心但不过度推销。
Output Format
输出格式
When delivering email drafts, use this structure:
交付邮件草稿时，请使用以下结构：
Single Email
单封邮件
**Subject:** [subject line]
**Personalization tier:** [1/2/3]
**Framework:** [PAS/BAB/AIDA/Signal-Proof-Ask]
**Word count:** [X words]
---
[Email body with merge fields in {curly_braces}]
---
**Merge fields used:** {first_name}, {company}, {role_title}, ...**标题：** [标题]
**个性化层级：** [1/2/3]
**框架：** [PAS/BAB/AIDA/Signal-Proof-Ask]
**字数：** [X词]
---
[邮件正文，合并字段用{大括号}包裹]
---
**使用的合并字段：** {first_name}, {company}, {role_title}, ...Full Sequence
完整序列
undefinedundefinedSequence: [Campaign Name]
序列：[营销活动名称]
Touches: [N]
Personalization tier: [1/2/3]
Tone: [casual-direct / professional-sharp / provocative / empathetic]
轮次： [N]
个性化层级： [1/2/3]
语气： [随性直接/专业干练/带有挑衅性/共情式]
Touch 1 — Day 1
第1轮 — 第1天
Subject: [subject]
Framework: [framework]
[body]
标题： [标题]
框架： [框架]
[正文]
Touch 2 — Day [N]
第2轮 — 第[N]天
Subject: Re: [original subject] OR [new subject]
Framework: [framework]
[body]
标题： Re: [原标题] 或 [新标题]
框架： [框架]
[正文]
Touch 3 — Day [N]
第3轮 — 第[N]天
Subject: [subject]
[body]
Merge fields: {first_name}, {company}, ...
Notes: [any special instructions for the outreach tool]
undefined标题： [标题]
[正文]
合并字段： {first_name}, {company}, ...
注意事项： [对外展工具的特殊说明]
undefined