conversation-resurrection
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseConversation Resurrection
对话复活
You are an expert in building sales bots that intelligently revive stalled conversations. Your goal is to help developers create systems that re-engage prospects with contextually relevant hooks long after initial contact went cold.
你是构建智能复活停滞对话的Sales Bot专家。你的目标是帮助开发者创建能够在初次联系冷却很久之后,通过上下文相关的钩子重新触达潜在客户的系统。
Why Resurrection Matters
为何复活至关重要
The Dormant Opportunity
沉睡的机遇
Reality of sales pipelines:
- 80% of leads don't convert on first sequence
- Average prospect needs 8-12 touches
- Timing is often wrong, not interest
- Circumstances change over months
Dead doesn't mean dead forever.销售管线的现实:
- 80%的线索不会在首次跟进序列中转化
- 潜在客户平均需要8-12次触达
- 通常是时机不对,而非没有兴趣
- 数月内情况可能发生变化
停滞并不意味着永远失去。The Resurrection Advantage
复活的优势
Well-timed revival:
- Lower competition (others gave up)
- Circumstances may have changed
- New budget cycles, new priorities
- Previous awareness reduces friction
"Hey, we talked 6 months ago about X.
Given [relevant trigger], thought it might
be worth reconnecting."时机恰当的复活:
- 竞争更少(其他人已经放弃)
- 情况可能已发生变化
- 新的预算周期、新的优先级
- 之前的认知降低了沟通阻力
"您好,我们6个月前聊过关于X的话题。
鉴于[相关触发因素],我认为或许值得重新联系。"Resurrection Triggers
复活触发因素
Time-Based Triggers
基于时间的触发因素
Calendar milestones:
- 30 days since last contact (warm revival)
- 90 days since last contact (quarterly check-in)
- 6 months (new budget cycle potential)
- 12 months (annual review, new year)
- Anniversary of their signup/trial
"It's been a few months since we connected.
A lot can change in a quarter—wanted to
check if [problem] is still on your radar."日历里程碑:
- 上次联系后30天(温和复活)
- 上次联系后90天(季度回访)
- 6个月(潜在新预算周期)
- 12个月(年度回顾、新年)
- 他们注册/试用的周年纪念日
"距离我们上次联系已经过去几个月了。
一个季度里可能发生很多变化——想了解一下[问题]是否仍在你的关注范围内。"Event-Based Triggers
基于事件的触发因素
External signals:
- Company funding announcement
- New executive hire
- Expansion news
- Competitor mention in news
- Industry regulation change
- Product launch from them
"Congrats on the Series B! When we talked
in March, scaling was a future concern.
Guessing it's more urgent now?"外部信号:
- 公司融资公告
- 新高管入职
- 扩张新闻
- 新闻中提及竞争对手
- 行业法规变更
- 他们发布新产品
"恭喜获得B轮融资!我们3月聊的时候,规模化还是未来的担忧。
猜测现在这已经更紧迫了?"Behavioral Triggers
基于行为的触发因素
Re-engagement signals:
- Visited website again
- Opened old email
- Downloaded new content
- Engaged on social media
- Colleague from company engaged
"Noticed you were back on our site—timing
might be better now than when we last talked?"重新互动信号:
- 再次访问网站
- 打开旧邮件
- 下载新内容
- 在社交媒体上互动
- 公司同事进行了互动
"注意到你再次访问了我们的网站——现在的时机可能比上次我们聊天时更好?"Internal Triggers
基于内部的触发因素
Your side changes:
- New feature launched (addresses their objection)
- Price change (if they had budget concerns)
- New case study (their industry/size)
- Integration added (their tech stack)
"When we talked in Q2, you mentioned needing
[feature]. Just launched it—thought you'd
want to know."我方的变化:
- 推出新功能(解决他们的异议)
- 价格调整(如果他们有预算顾虑)
- 新案例研究(他们所在行业/规模)
- 添加集成(他们的技术栈)
"我们第二季度聊的时候,你提到需要[功能]。我们刚刚推出了该功能——觉得你会想了解。"Context Retention
上下文留存
What to Remember
需要记住的内容
From original conversation:
- Their stated pain points
- Objections raised
- Why they went cold
- Key stakeholders mentioned
- Timeline they shared
- Budget context
Store structured:
{
"prospect_id": "12345",
"last_contact": "2024-01-15",
"conversation_summary": "Interested but budget locked until Q2",
"pain_points": ["manual reporting", "Salesforce integration"],
"objections": ["timing", "budget"],
"dormant_reason": "asked to reconnect after Q1",
"revival_hooks": ["Q2 budget", "reporting feature"]
}来自原始对话的信息:
- 他们提出的痛点
- 提出的异议
- 对话冷却的原因
- 提到的关键利益相关者
- 他们分享的时间线
- 预算背景
结构化存储:
{
"prospect_id": "12345",
"last_contact": "2024-01-15",
"conversation_summary": "感兴趣但预算要到第二季度才解锁",
"pain_points": ["manual reporting", "Salesforce integration"],
"objections": ["timing", "budget"],
"dormant_reason": "要求第一季度后重新联系",
"revival_hooks": ["Q2 budget", "reporting feature"]
}Context Application
上下文应用
Generic revival (bad):
"Hi! Just checking in to see if you're
still interested in our product."
Contextual revival (good):
"Hi Sarah—when we talked in January, you
mentioned budget was locked until Q2 and
reporting was your biggest pain. Now that
we're in Q2 and you're probably planning,
is it worth a fresh look?"
Reference their specific situation.通用复活(不佳):
"您好!只是想确认您是否仍对我们的产品感兴趣。"
上下文相关的复活(优秀):
"您好Sarah——我们1月聊的时候,您提到预算要到第二季度才解锁,且报告是您最大的痛点。现在已经到第二季度了,您可能正在做规划,是否值得重新了解一下?"
参考他们的具体情况。Revival Message Frameworks
复活消息框架
The "Relevant Update" Framework
“相关更新”框架
Structure:
1. Reference previous conversation
2. Share relevant update
3. Connect to their stated need
4. Low-pressure ask
Example:
"Hi [Name], we spoke in [month] about
[their pain point]. Since then, we've
[relevant update that addresses their need].
Given what you shared about [specific detail],
thought it might be worth a quick look.
Worth 15 minutes to see what's changed?"结构:
1. 提及之前的对话
2. 分享相关更新
3. 关联他们的明确需求
4. 低压力请求
示例:
"您好[姓名],我们[月份]聊过关于[他们的痛点]的话题。从那以后,我们[解决他们需求的相关更新]。
鉴于您分享的[具体细节],我认为或许值得快速了解一下。
是否能抽出15分钟看看有哪些变化?"The "Trigger Event" Framework
“触发事件”框架
Structure:
1. Acknowledge the event
2. Connect to previous conversation
3. Explain relevance
4. Offer value
Example:
"Saw the news about [company event]—congrats!
When we talked earlier this year, [scaling/growth]
was on the horizon. Guessing that's more
front-and-center now?
Happy to share how [similar company] handled
this same transition if it would help."结构:
1. 提及事件
2. 关联之前的对话
3. 解释相关性
4. 提供价值
示例:
"看到关于[公司事件]的新闻——恭喜!
我们今年早些时候聊的时候,[规模化/增长]即将提上日程。猜测现在这已经是重中之重了?
如果有帮助的话,我很乐意分享[类似公司]是如何应对这一转型的。"The "Value-First" Framework
“价值优先”框架
Structure:
1. Lead with something useful
2. Reference past conversation
3. Soft reconnection
Example:
"[Name], just published a guide on [topic
related to their pain]. Given our conversation
about [their challenge], thought you might
find it useful: [link]
If things have changed since [month], happy
to catch up. If not, no worries—hope the
guide helps either way."结构:
1. 以有用的内容开头
2. 提及过往对话
3. 温和重新联系
示例:
"[姓名],我们刚刚发布了一份关于[与他们痛点相关的主题]的指南。鉴于我们之前聊过[他们的挑战],我认为您可能会觉得有用:[链接]
如果自[月份]以来情况有变化,我很乐意跟进。如果没有,也没关系——希望这份指南能帮到您。"The "Honest Check-In" Framework
“坦诚回访”框架
Structure:
1. Direct acknowledgment of time passed
2. Respect their previous position
3. Simple question
Example:
"Hi [Name]—it's been [time] since we talked.
You mentioned [reason for pause].
Curious if anything's changed, or if this
is still not the right time. Either way,
wanted to keep the door open."
Low pressure, high respect.结构:
1. 直接提及时间已过
2. 尊重他们之前的立场
3. 简单提问
示例:
"您好[姓名]——距离我们上次聊天已经过去[时间]了。您提到过[暂停的原因]。
好奇情况是否有变化,或者现在时机仍不合适。无论如何,我都想保持联系的可能性。"
低压力,高尊重。Timing Intelligence
时机智能
Optimal Revival Windows
最佳复活窗口
By dormant reason:
"Timing not right":
→ Revival at 60-90 days
→ Begin of new quarter
→ After fiscal year change
"Budget locked":
→ Revival at budget cycle start
→ Q1 for calendar-year companies
→ Ask when their fiscal year starts
"Using competitor":
→ Revival at 6-12 months
→ Contract renewal period
→ If competitor news is negative
"Not a priority":
→ Revival if trigger event occurs
→ Otherwise 6-month check-in
→ Lead with new value/content按停滞原因分类:
"时机不对":
→ 60-90天后复活
→ 新季度开始时
→ 财年变更后
"预算锁定":
→ 预算周期开始时复活
→ 日历年公司的第一季度
→ 询问他们的财年何时开始
"使用竞争对手产品":
→ 6-12个月后复活
→ 合同续约期
→ 如果竞争对手有负面新闻
"不是优先事项":
→ 发生触发事件时复活
→ 否则每6个月回访一次
→ 以新价值/内容开头Day/Time for Revival
复活的日期/时间
Best practices:
- Tuesday-Thursday (avoid Monday chaos, Friday checkout)
- Mid-morning (9-11am local)
- Mid-week of month (avoid beginning/end crunches)
Avoid:
- Holiday weeks
- Major industry events
- Their known busy periods (if logged)最佳实践:
- 周二至周四(避免周一混乱、周五收尾)
- 上午中段(当地时间9-11点)
- 月中(避免月初/月末的忙碌期)
需避免:
- 假期周
- 重大行业活动
- 已知的他们的忙碌时段(如果已记录)Sequence Design
序列设计
Revival Sequence Structure
复活序列结构
Touch 1 (Day 0): Contextual reconnection
→ Reference past conversation + new hook
→ Low-pressure, value-focused
Touch 2 (Day 5): Value add
→ Share relevant content/insight
→ No direct ask
Touch 3 (Day 12): Direct ask
→ Specific meeting request
→ Easy yes/no
Touch 4 (Day 20): Break-up
→ Close the loop
→ Leave door open
Shorter than initial outreach—they know you.触达1(第0天):上下文相关的重新联系
→ 提及过往对话 + 新钩子
→ 低压力、以价值为核心
触达2(第5天):提供价值
→ 分享相关内容/见解
→ 无直接请求
触达3(第12天):直接请求
→ 具体的会议请求
→ 简单的是/否回答
触达4(第20天):收尾
→ 闭环
→ 保持联系的可能性
比初次触达序列更短——他们已经认识你。Multi-Channel Revival
多渠道复活
Coordinate across channels:
Day 0: Email (primary revival message)
Day 3: LinkedIn (if no response, different angle)
Day 7: Email follow-up
Day 14: SMS (if opted in, brief check-in)
Day 21: Final email (break-up)
Don't use all channels at once—escalate gradually.跨渠道协调:
第0天:邮件(主要复活消息)
第3天:LinkedIn(如果无回复,换个角度)
第7天:邮件跟进
第14天:短信(如果已选择接收,简短回访)
第21天:最终邮件(收尾)
不要同时使用所有渠道——逐步升级。Handling Responses
响应处理
Positive Response
积极响应
"Actually, yeah, timing is better now."
Response:
"Great to hear! A lot's probably changed
since [month]. Would love to hear what's
shifted on your end and show you what's
new on ours.
Does [specific time] work this week?"
Move quickly—they're re-engaged.“实际上,是的,现在时机更好了。”
回复:
“很高兴听到这个消息!自[月份]以来可能发生了很多变化。我很想了解您这边的变化,并向您展示我们这边的新内容。
这周[具体时间]方便吗?”
快速行动——他们已经重新互动了。Neutral Response
中性响应
"Things are still pretty busy, but maybe soon."
Response:
"Totally understand—appreciate you letting me know.
I'll check back in [timeframe they suggest or 4-6 weeks].
In the meantime, if anything changes or a question
comes up, just reply here."
Set expectation, stay helpful.“事情还是很忙,但可能很快就会有空。”
回复:
“完全理解——感谢您告知。我会在[他们建议的时间范围或4-6周后]再次回访。
在此期间,如果情况有变化或有问题,只需回复此邮件即可。”
设定预期,保持乐于助人。Negative Response
消极响应
"We went with another solution."
Response:
"Thanks for letting me know—appreciate the closure.
How's it working out?
If things change or you ever want a second opinion,
I'm around. Best of luck with [competitor]."
Graceful, leaves door open for future.“我们选择了另一个解决方案。”
回复:
“感谢您告知——感谢您给出明确答复。
使用情况如何?
如果情况有变化或您需要第二意见,我随时都在。祝您使用[竞争对手产品]一切顺利。”
优雅,为未来保持联系的可能性。No Response
无响应
After full revival sequence with no response:
- Mark as "revival attempted"
- Set next revival for 6+ months out
- Don't over-contact
- Watch for re-engagement signals
Some prospects need multiple revival attempts
over years before converting.完整复活序列后无响应:
- 标记为“已尝试复活”
- 设置下次复活为6个月后
- 不要过度联系
- 关注重新互动信号
有些潜在客户需要多年内多次复活尝试才会转化。Metrics
指标
Revival Performance
复活表现
Track:
- Revival response rate vs initial outreach
- Response rate by dormant period length
- Conversion rate from revival to meeting
- Win rate from resurrected opportunities
Benchmarks:
- Revival response rate: 5-15% (lower than fresh leads)
- But often higher quality (pre-qualified)跟踪:
- 复活响应率 vs 初次触达响应率
- 按停滞时长划分的响应率
- 从复活到会议的转化率
- 复活机会的赢单率
基准:
- 复活响应率:5-15%(低于新线索)
- 但通常质量更高(已预筛选)Optimization Signals
优化信号
Look for:
- Which revival triggers perform best?
- Which dormant reasons respond best?
- Optimal time between initial and revival?
- Which message frameworks convert?
Use to refine:
- Trigger selection
- Timing rules
- Message templates
- Sequence length关注:
- 哪些复活触发因素表现最佳?
- 哪些停滞原因的响应最好?
- 初次触达到复活的最佳时间间隔?
- 哪些消息框架转化率最高?
用于优化:
- 触发因素选择
- 时机规则
- 消息模板
- 序列长度Edge Cases
边缘情况
Multiple Revivals
多次复活
Second revival attempt:
- At least 6 months after first revival
- New hook required (not same message)
- Consider different channel
- Lower expectations
Third+ revival:
- Annual check-in only
- Trigger-based only
- Don't harass第二次复活尝试:
- 至少在第一次复活后6个月
- 需要新钩子(不要使用相同消息)
- 考虑不同渠道
- 降低期望
第三次及以上复活:
- 仅年度回访
- 仅基于触发事件
- 不要骚扰Company Changes
公司变更
Prospect changed companies:
→ Research new role
→ If relevant, reach out at new company
→ "Saw you moved to [company]. If [problem]
is relevant there too, happy to reconnect."
New contact at same company:
→ Fresh start with new person
→ May reference previous conversation if helpful
→ "I spoke with [previous contact] last year..."潜在客户更换公司:
→ 研究新职位
→ 如果相关,联系新公司的他们
→ “看到您转到了[公司]。如果[问题]在那里也相关,我很乐意重新联系。”
同一公司的新联系人:
→ 与新联系人重新开始
→ 如果有帮助,可以提及之前的对话
→ “我去年和[之前联系人]聊过...”Objection Changes
异议变更
Original objection no longer valid:
They said: "Too expensive"
Now: You have new pricing tier
Revival: "When we talked, pricing was the sticking
point. We've since introduced a [tier] that might
fit better. Worth a fresh look?"
Address the specific blocker.原始异议不再有效:
他们曾说:“太贵了”
现在:您有了新的定价层级
复活:“我们聊的时候,价格是障碍。我们后来推出了[层级],可能更适合您。是否值得重新了解一下?”
解决具体的障碍。