follow-up
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWrite Follow-Up Email
撰写跟进邮件
Generate a follow-up email that re-engages prospects who didn't respond.
生成一封能够重新触达未回复潜在客户的跟进邮件。
Input
输入
Parse $ARGUMENTS for:
- Original email or context of first outreach
- Days since last email: How long ago was it sent
- Follow-up number: Is this #1, #2, or #3?
- New context (optional): News, trigger events, new value to offer
If original context is missing, ask for the key points from the first email.
解析$ARGUMENTS获取以下信息:
- 原始邮件或首次触达的背景信息
- 距离上次邮件的天数:上次邮件发送至今的时长
- 跟进次数:这是第1、第2还是第3次跟进?
- 新背景信息(可选):行业新闻、触发事件、可提供的新价值
如果缺少原始背景信息,请询问首次邮件的核心要点。
Strategy by Follow-Up Number
按跟进次数制定的策略
Follow-up #1 (3-5 days after)
第1次跟进(发送后3-5天)
- Assume they're busy, not uninterested
- Add new value or angle
- Keep it shorter than original
- 假设对方只是忙碌,而非不感兴趣
- 增加新的价值或切入角度
- 篇幅比原始邮件更短
Follow-up #2 (7-10 days after)
第2次跟进(发送后7-10天)
- Try a different approach
- Share a relevant insight or resource
- Reframe the value prop
- 尝试不同的沟通方式
- 分享相关见解或资源
- 重新阐述价值主张
Follow-up #3 (14+ days after)
第3次跟进(发送后14天以上)
- "Break-up" email or permission-based close
- Give them an easy out
- Last attempt before moving on
- “收尾”邮件或基于许可的收尾方式
- 给对方一个轻松的退路
- 转移目标前的最后尝试
Frameworks
框架模板
The Bump
提醒式模板
- Quick, friendly nudge
- "Floating this back up" energy
- Best for follow-up #1
- 简短、友好的提醒
- 以“再次提及此事”的语气
- 最适合第1次跟进
The Value-Add
增值式模板
- Share something useful (article, insight, idea)
- Shows you're thinking about their problems
- Best for follow-up #2
- 分享有用的内容(文章、见解、想法)
- 表明你在关注他们的问题
- 最适合第2次跟进
The Breakup
收尾式模板
- "Should I close your file?"
- Creates urgency without pressure
- Best for follow-up #3
- “我是否可以归档您的资料?”
- 制造紧迫感但无施压感
- 最适合第3次跟进
Hard Rules
硬性规则
- Shorter than original - Each follow-up gets shorter
- New angle: Don't just repeat the first email
- No guilt trips: "I haven't heard back" sounds needy
- No "just checking in": Empty phrase, add value instead
- Reference original: Brief callback to first email
- One CTA: Same or simplified ask
- 30-75 words max: Follow-ups should be scannable
- 比原始邮件短 - 每一次跟进的篇幅都要更短
- 新角度:不要只是重复首次邮件的内容
- 不要道德绑架:“我尚未收到回复”听起来很迫切
- 避免“只是跟进一下”:空洞的表述,应改为提供价值
- 提及原始邮件:简要回顾首次邮件的内容
- 单一行动号召(CTA):保持相同或简化的诉求
- 最多30-75词:跟进邮件应便于快速浏览
What NOT to Write
切勿撰写的内容
- "I wanted to follow up on my last email" (weak opener)
- "I'm sure you're busy but..." (apologetic)
- Resending the exact same email
- Being passive-aggressive about no response
- Multiple CTAs or new complex asks
- “我想跟进一下上次的邮件”(无力的开头)
- “我知道您很忙,但是...”(带有歉意)
- 重新发送完全相同的邮件
- 因未收到回复而表现出消极攻击的态度
- 多个行动号召或新的复杂诉求
Output Format
输出格式
Subject: Re: [original subject] or [new short subject]
[Email body]
[First name]Framework used: [which one]
What's different: [how this differs from original]
Word count: [number]
Subject: Re: [original subject] or [new short subject]
[Email body]
[First name]使用的模板:[具体模板名称]
与原始邮件的差异:[具体差异点]
词数:[具体数字]