conversation-summarization
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseConversation Summarization
对话总结
You are an expert in building sales bots that create clear, actionable summaries of prospect conversations. Your goal is to help developers create systems that produce summaries useful for human handoff, CRM updates, and deal continuity.
您是构建销售机器人的专家,这类机器人能够生成清晰、可执行的潜在客户对话摘要。您的目标是帮助开发者创建可生成实用摘要的系统,这些摘要可用于人工交接、CRM更新以及业务跟进。
Why Summarization Matters
为什么总结很重要
The Handoff Problem
交接问题
Without summarization:
Rep picks up conversation, asks:
"So tell me about your situation..."
Prospect: "I already explained this to your bot."
Result: Frustration, lost trust, wasted time无摘要情况下:
销售接手对话后问道:
“跟我说说你的情况……”
潜在客户:“我已经跟你们的机器人说过了。”
结果:产生不满、失去信任、浪费时间With Good Summarization
优质摘要的效果
Rep picks up conversation, says:
"I see you're looking at [product] for your
15-person marketing team, and timeline is
important because of your Q2 campaign. Let
me pick up where we left off..."
Prospect: "Exactly. Yes, let's continue."
Result: Seamless experience, trust maintained销售接手对话后说道:
“我了解到您正在为15人的营销团队评估[产品],且时间安排对您的Q2 campaign至关重要。让我们接着之前的内容继续……”
潜在客户:“没错,我们继续吧。”
结果:体验无缝衔接,信任得以维持Summary Types
摘要类型
Handoff Summary
交接摘要
Purpose: Transfer to human rep
Audience: Sales rep taking over
Length: 2-4 paragraphs
Includes:
- Prospect context (who they are)
- What they need (pain/goals)
- Where conversation ended
- Recommended next steps
- Any concerns/objections raised
- Urgency level用途:交接给人工销售
受众:接手的销售代表
长度:2-4段
包含内容:
- 潜在客户背景(身份信息)
- 需求痛点/目标
- 对话结束节点
- 建议后续步骤
- 提出的顾虑/异议
- 紧急程度CRM Update
CRM更新
Purpose: Record in CRM
Audience: Anyone viewing the contact
Length: 3-5 bullet points
Includes:
- Key facts learned
- Qualification status
- Next action required
- Important quotes
- Updated contact fields用途:记录到CRM系统
受众:查看该联系人的所有人员
长度:3-5个要点
包含内容:
- 掌握的关键信息
- 资质认定状态
- 需执行的后续动作
- 重要引用内容
- 更新后的联系人字段Meeting Prep
会议准备
Purpose: Brief before scheduled call
Audience: Rep preparing for meeting
Length: 1 page
Includes:
- Full conversation history summary
- All stated needs/pains
- Questions to ask
- Potential objections
- Suggested talking points用途:为预定通话提供简报
受众:准备会议的销售代表
长度:1页
包含内容:
- 完整对话历史摘要
- 所有明确的需求/痛点
- 需询问的问题
- 潜在异议
- 建议讨论要点Internal Log
内部日志
Purpose: Audit trail
Audience: Operations/compliance
Length: Detailed, timestamped
Includes:
- Complete interaction log
- Bot decision points
- System actions taken
- Compliance-relevant details用途:审计追踪
受众:运营/合规人员
长度:详细、带时间戳
包含内容:
- 完整交互日志
- 机器人决策节点
- 执行的系统操作
- 合规相关细节Summary Components
摘要组成部分
Prospect Profile
潜在客户档案
Extract and structure:
Contact:
- Name: Sarah Chen
- Title: VP of Marketing
- Company: TechCorp (500 employees, SaaS)
- Email: sarah@techcorp.com
- Phone: +1 415-555-1234
Context:
- Source: Inbound demo request
- First contact: Jan 15, 2024
- Total interactions: 3 emails, 1 SMS提取并结构化:
联系人:
- 姓名:Sarah Chen
- 职位:VP of Marketing
- 公司:TechCorp(500名员工,SaaS企业)
- 邮箱:sarah@techcorp.com
- 电话:+1 415-555-1234
背景:
- 来源: inbound demo请求
- 首次联系:2024年1月15日
- 总交互次数:3封邮件、1条短信Needs & Pain Points
需求与痛点
What they said they need:
Explicit:
- "We need to reduce time spent on reporting"
- "Integration with Salesforce is a must"
Implied:
- Mentioned team is overwhelmed → capacity issue
- Asked about ROI → needs to justify budget
- Mentioned boss → not sole decision maker
Prioritized:
1. Time savings (mentioned 3x)
2. Integration (mentioned as "must have")
3. Ease of use (asked about training)客户明确提出的需求:
显性需求:
- “我们需要减少报告耗时”
- “必须与Salesforce集成”
隐性需求:
- 提及团队不堪重负 → 产能问题
- 询问ROI → 需要证明预算合理性
- 提及上司 → 并非唯一决策者
优先级:
1. 节省时间(提及3次)
2. 集成能力(明确为“必备项”)
3. 易用性(询问培训相关内容)Qualification Data
资质认定数据
BANT/MEDDIC data captured:
Budget:
- Range: $20-30k annually
- Source: "We have budget allocated"
Authority:
- Champion: Sarah (VP Marketing)
- Economic Buyer: CMO (mentioned)
- Decision process: "I recommend, CMO approves"
Need:
- Primary: Reporting automation
- Secondary: Campaign tracking
Timeline:
- Target: Q2 implementation
- Driver: "New fiscal year planning"捕获的BANT/MEDDIC数据:
预算:
- 范围:每年2-3万美元
- 来源:“我们已分配预算”
决策权:
- 支持者:Sarah(营销副总裁)
- 经济决策者:CMO(提及)
- 决策流程:“我推荐,CMO批准”
需求:
- 主要需求:报告自动化
- 次要需求:营销活动追踪
时间线:
- 目标:Q2完成部署
- 驱动因素:“新财年规划”Conversation Flow
对话流程
Key exchanges summarized:
1. Initial inquiry (Jan 15):
Prospect asked about reporting features.
Bot provided overview, offered demo.
2. Follow-up (Jan 17):
Prospect asked about pricing tiers.
Bot explained options, asked about team size.
Prospect: "15 people in marketing."
3. Demo scheduling (Jan 18):
Prospect agreed to demo.
Scheduled for Jan 22, 2pm PT.
Requested Salesforce integration focus.关键交流摘要:
1. 初始咨询(1月15日):
潜在客户询问报告功能。
机器人提供概述,邀请演示。
2. 跟进(1月17日):
潜在客户询问定价层级。
机器人解释选项,询问团队规模。
潜在客户:“营销团队有15人。”
3. 演示预约(1月18日):
潜在客户同意演示。
预约时间为1月22日太平洋时间下午2点。
要求重点展示Salesforce集成。Objections & Concerns
异议与顾虑
Issues raised:
Concern: "We tried something similar before."
Context: Previous tool was hard to implement.
Status: Acknowledged, not resolved.
Recommended response: Address implementation ease.
Concern: "Price seems high for our size."
Context: Comparing to lower-tier competitors.
Status: Bot offered to discuss value/ROI.
Recommended response: ROI calculator, case study.提出的问题:
顾虑:“我们之前尝试过类似的产品。”
背景:之前的工具部署难度大。
状态:已确认,尚未解决。
建议回应:强调部署便捷性。
顾虑:“对于我们的规模来说价格偏高。”
背景:与低层级竞品对比。
状态:机器人提议讨论价值/ROI。
建议回应:提供ROI计算器、案例研究。Action Items
行动项
What needs to happen:
Immediate:
□ Demo scheduled Jan 22, 2pm PT
□ Send Salesforce integration docs
□ Assign to Enterprise AE (deal size)
Before demo:
□ Research TechCorp's current tools
□ Prepare ROI model for their size
□ Find similar customer case study
Post-demo:
□ Send proposal if positive
□ Schedule follow-up with CMO需完成的事项:
紧急事项:
□ 演示预约于1月22日太平洋时间下午2点
□ 发送Salesforce集成文档
□ 分配给Enterprise AE(根据业务规模)
演示前:
□ 调研TechCorp当前使用的工具
□ 为其规模准备ROI模型
□ 寻找类似客户案例
演示后:
□ 若反馈积极则发送提案
□ 安排与CMO的跟进会议Summary Generation
摘要生成
Template Approach
模板法
python
def generate_handoff_summary(conversation):
return f"""python
def generate_handoff_summary(conversation):
return f"""Handoff Summary
Handoff Summary
Prospect
Prospect
{format_prospect_profile(conversation.prospect)}
{format_prospect_profile(conversation.prospect)}
Situation
Situation
{summarize_needs(conversation)}
{summarize_needs(conversation)}
Conversation History
Conversation History
{summarize_key_exchanges(conversation)}
{summarize_key_exchanges(conversation)}
Qualification
Qualification
{format_qualification_data(conversation)}
{format_qualification_data(conversation)}
Open Items
Open Items
{list_concerns_objections(conversation)}
{list_concerns_objections(conversation)}
Recommended Next Steps
Recommended Next Steps
{suggest_next_actions(conversation)}
{suggest_next_actions(conversation)}
Notable Quotes
Notable Quotes
{extract_key_quotes(conversation)}
"""
undefined{extract_key_quotes(conversation)}
"""
undefinedAI Summarization
AI摘要法
python
def ai_summarize(conversation, summary_type):
prompt = f"""
Summarize this sales conversation for {summary_type}.
Conversation:
{conversation.full_transcript}
Extract:
1. Who is the prospect (name, title, company)
2. What do they need (stated and implied)
3. Key qualification info (budget, timeline, authority)
4. Any concerns or objections raised
5. Where did the conversation end
6. Recommended next steps
Format as a structured summary a sales rep can
quickly scan before taking over.
"""
return llm.generate(prompt)python
def ai_summarize(conversation, summary_type):
prompt = f"""
Summarize this sales conversation for {summary_type}.
Conversation:
{conversation.full_transcript}
Extract:
1. Who is the prospect (name, title, company)
2. What do they need (stated and implied)
3. Key qualification info (budget, timeline, authority)
4. Any concerns or objections raised
5. Where did the conversation end
6. Recommended next steps
Format as a structured summary a sales rep can
quickly scan before taking over.
"""
return llm.generate(prompt)Hybrid Approach
混合法
Best results: Structured extraction + AI synthesis
Step 1: Extract structured data
- Contact info → structured fields
- Qualification → BANT fields
- Dates/times → parsed timestamps
Step 2: AI summarize unstructured
- Conversation flow narrative
- Nuanced needs interpretation
- Tone/sentiment assessment
Step 3: Combine
- Structured data in templates
- AI narrative in summary sections
- Human-readable final output最佳效果:结构化提取 + AI合成
步骤1:提取结构化数据
- 联系人信息 → 结构化字段
- 资质认定 → BANT字段
- 日期/时间 → 解析时间戳
步骤2:AI总结非结构化内容
- 对话流程叙述
- 需求的细微解读
- 语气/情绪评估
步骤3:整合
- 结构化数据填入模板
- AI生成的叙述放入摘要章节
- 生成易读的最终输出Format Examples
格式示例
Slack/Teams Handoff
Slack/Teams交接
🔔 Hot Lead Handoff: Sarah Chen @ TechCorp
**Quick Context:**
VP Marketing at 500-person SaaS company. Inbound demo
request. Looking for reporting automation, must have
Salesforce integration.
**Qualification:**
✅ Budget: $20-30k approved
✅ Timeline: Q2 implementation
⚠️ Authority: Needs CMO sign-off
**Where We Left Off:**
Demo scheduled Jan 22, 2pm PT. Requested focus on
Salesforce integration. Previous tool failed on
implementation—address this.
**Next Step:**
Join demo, prepared with:
- Salesforce integration walkthrough
- ROI calc for 15-person team
- Implementation timeline🔔 高优先级线索交接:Sarah Chen @ TechCorp
**快速背景:**
500人规模SaaS企业的营销副总裁。主动请求演示。寻求报告自动化解决方案,必须支持Salesforce集成。
**资质认定:**
✅ 预算:已批准2-3万美元
✅ 时间线:Q2部署
⚠️ 决策权:需CMO签字批准
**对话进度:**
已预约1月22日太平洋时间下午2点的演示,要求重点展示Salesforce集成。曾因部署问题放弃过同类工具——需对此作出回应。
**后续步骤:**
参与演示,准备:
- Salesforce集成演示
- 针对15人团队的ROI计算器
- 部署时间线CRM Note
CRM笔记
CONVERSATION SUMMARY - Jan 18, 2024
Contact: Sarah Chen, VP Marketing
Company: TechCorp (500 emp, SaaS)
Key Points:
• Looking for reporting automation
• 15-person marketing team
• Budget: $20-30k range
• Timeline: Q2 implementation
• Must have: Salesforce integration
• Concern: Previous tool was hard to implement
Next Step: Demo Jan 22, 2pm PT
Assigned: Enterprise AE Team
Priority: High (hot inbound)
Quote: "We need something that actually works with
Salesforce—last tool was a nightmare to integrate."对话总结 - 2024年1月18日
联系人:Sarah Chen,营销副总裁
公司:TechCorp(500名员工,SaaS企业)
要点:
• 寻求报告自动化解决方案
• 营销团队共15人
• 预算:2-3万美元
• 时间线:Q2部署
• 必备项:Salesforce集成
• 顾虑:之前使用的工具部署难度大
后续步骤:1月22日太平洋时间下午2点演示
分配:Enterprise AE团队
优先级:高(主动高意向线索)
引用:“我们需要能真正与Salesforce配合的产品——上一个工具集成起来简直是噩梦。”Email to Rep
给销售的邮件
Subject: Handoff: Sarah Chen @ TechCorp - Demo Tomorrow
Hi [Rep],
Handing off Sarah Chen from TechCorp for your demo
tomorrow at 2pm PT.
**The Situation:**
Sarah (VP Marketing) reached out asking about our
reporting automation. She leads a 15-person team and
is frustrated with manual reporting. They tried a
competitor before that "was a nightmare to integrate
with Salesforce"—so integration is her #1 priority.
**The Opportunity:**
- Budget allocated ($20-30k range)
- Q2 implementation target
- She recommends, CMO approves
- Hot inbound lead, moving quickly
**For Your Demo:**
- Focus heavily on Salesforce integration
- Show how easy implementation is
- Prepare ROI calc for 15-person team
- Have marketing-specific case study ready
**Watch Out For:**
She mentioned past bad experience, so she'll be
skeptical of implementation promises. Be specific
about timeline and support.
Good luck!主题:交接:TechCorp的Sarah Chen - 明日演示
您好[销售代表],
现将TechCorp的Sarah Chen交接给您,您的演示时间为明日太平洋时间下午2点。
**情况说明:**
Sarah(营销副总裁)主动咨询我们的报告自动化解决方案。她领导15人的团队,对手动报告感到不满。他们曾使用过竞品,但“与Salesforce集成简直是噩梦”——因此集成是她的首要需求。
**机会点:**
- 预算已到位(2-3万美元)
- 目标Q2部署
- 她负责推荐,CMO批准
- 主动高意向线索,推进速度快
**演示准备:**
- 重点展示Salesforce集成
- 强调部署便捷性
- 准备针对15人团队的ROI计算器
- 准备营销行业相关案例
**注意事项:**
她有过糟糕的同类产品使用经历,因此会对部署承诺持怀疑态度。需明确说明时间线和支持服务。
祝顺利!Quality Standards
质量标准
Good Summary Characteristics
优质摘要特征
✓ Actionable: Reader knows what to do next
✓ Scannable: Key info jumps out quickly
✓ Complete: No critical info missing
✓ Accurate: Reflects what was actually said
✓ Contextualized: Includes relevant background
✓ Prioritized: Most important info first✓ 可执行:读者清楚下一步动作
✓ 易扫描:关键信息一目了然
✓ 完整:无重要信息遗漏
✓ 准确:如实反映对话内容
✓ 有背景:包含相关上下文
✓ 有优先级:重要信息前置Common Mistakes
常见错误
✗ Too long: Burying key info in paragraphs
✗ Too short: Missing critical context
✗ Editorializing: Adding opinions not stated
✗ Jargon: Using internal terms prospect won't know
✗ No next step: Leaving reader unclear on action
✗ Stale: Not updated with latest interaction✗ 过长:关键信息淹没在段落中
✗ 过短:缺失重要背景
✗ 主观臆断:添加未提及的观点
✗ 术语过多:使用潜在客户不懂的内部术语
✗ 无后续步骤:读者不清楚要做什么
✗ 过时:未更新最新交互内容Accuracy Checks
准确性校验
python
def validate_summary(summary, conversation):
issues = []
# Check for hallucinations
for fact in summary.extracted_facts:
if not fact_in_conversation(fact, conversation):
issues.append(f"Fact not found: {fact}")
# Check for missing critical info
if not summary.has_next_step:
issues.append("Missing next step")
if not summary.has_prospect_name:
issues.append("Missing prospect name")
# Check recency
if summary.generated_at < conversation.last_message_at:
issues.append("Summary outdated")
return issuespython
def validate_summary(summary, conversation):
issues = []
# 检查幻觉内容
for fact in summary.extracted_facts:
if not fact_in_conversation(fact, conversation):
issues.append(f"Fact not found: {fact}")
# 检查关键信息缺失
if not summary.has_next_step:
issues.append("Missing next step")
if not summary.has_prospect_name:
issues.append("Missing prospect name")
# 检查时效性
if summary.generated_at < conversation.last_message_at:
issues.append("Summary outdated")
return issuesAutomation & Integration
自动化与集成
Auto-Generation Triggers
自动生成触发条件
When to generate summary:
1. Handoff requested
→ Generate handoff summary
→ Notify assigned rep
2. Meeting scheduled
→ Generate meeting prep
→ Send to rep 1 hour before
3. Conversation ends
→ Generate CRM update
→ Push to CRM automatically
4. Daily rollup
→ Summarize all active conversations
→ Send to manager何时生成摘要:
1. 请求交接时
→ 生成交接摘要
→ 通知分配的销售代表
2. 会议预约完成时
→ 生成会议准备资料
→ 会议前1小时发送给销售代表
3. 对话结束时
→ 生成CRM更新内容
→ 自动推送至CRM
4. 每日汇总
→ 总结所有活跃对话
→ 发送给管理者CRM Integration
CRM集成
Push to CRM automatically:
Salesforce:
- Create/update Contact record
- Add to Activity History
- Update Lead Score
- Set Next Step date
HubSpot:
- Update Contact properties
- Add Timeline entry
- Update Deal stage
- Create Task for follow-up
Generic:
- API call with structured data
- Field mapping configuration
- Error handling/retry自动推送至CRM:
Salesforce:
- 创建/更新联系人记录
- 添加至活动历史
- 更新线索评分
- 设置后续步骤日期
HubSpot:
- 更新联系人属性
- 添加时间线条目
- 更新业务阶段
- 创建跟进任务
通用方式:
- 携带结构化数据的API调用
- 字段映射配置
- 错误处理/重试机制Real-Time Updates
实时更新
As conversation progresses:
After each exchange:
→ Update qualification fields
→ Append to conversation log
→ Recalculate priority score
On key events:
→ Meeting booked: Update next step
→ Objection raised: Flag for review
→ Buying signal: Alert rep
Summary stays current, not snapshot.对话进行中:
每次交互后:
→ 更新资质认定字段
→ 追加至对话日志
→ 重新计算优先级评分
关键事件触发:
→ 预约会议:更新后续步骤
→ 提出异议:标记待审核
→ 购买信号:提醒销售代表
摘要保持实时更新,而非静态快照。Privacy & Compliance
隐私与合规
Data Handling
数据处理
Summary may contain sensitive data:
Include:
- Business context
- Stated needs
- Timeline/budget ranges
Redact/mask:
- Credit card numbers
- Social security numbers
- Health information
- Passwords (if mistakenly shared)
Comply with:
- GDPR (right to access, deletion)
- CCPA (disclosure requirements)
- Industry regulations摘要可能包含敏感数据:
可保留:
- 业务背景
- 明确需求
- 时间线/预算范围
需编辑/掩码:
- 信用卡号
- 社保号
- 健康信息
- 密码(若误填)
需遵守:
- GDPR(访问权、删除权)
- CCPA(披露要求)
- 行业法规Retention
数据留存
How long to keep summaries:
Active deal: Indefinitely (until closed)
Closed won: Per company policy (usually 7 years)
Closed lost: Per policy (usually 2-3 years)
Prospect opted out: Delete per regulations
Implement:
- Automated retention policies
- Deletion workflows
- Audit logging摘要留存时长:
活跃业务:无限期(直至结束)
已赢单:按公司政策(通常7年)
已丢单:按公司政策(通常2-3年)
潜在客户退订:按法规要求删除
实施方式:
- 自动化留存政策
- 删除工作流
- 审计日志Measuring Quality
质量衡量
Summary Usefulness Metrics
摘要实用性指标
Track:
- Rep feedback ratings
- Time-to-read (are they too long?)
- Edits made by reps (missing info?)
- Conversion rates with vs without summaries
Survey reps:
- Was the summary accurate?
- Was anything missing?
- Did it help you prepare?
- Suggestions for improvement?追踪:
- 销售代表反馈评分
- 阅读时长(是否过长?)
- 销售代表修改次数(是否缺失信息?)
- 使用与不使用摘要的转化率对比
调研销售代表:
- 摘要是否准确?
- 是否有信息缺失?
- 是否有助于准备工作?
- 改进建议?Continuous Improvement
持续改进
Feedback loop:
1. Generate summary
2. Rep uses summary
3. Rep provides feedback
4. Update summary templates
5. Retrain AI models
6. Repeat
Goal: Summaries that reps love and trust.反馈循环:
1. 生成摘要
2. 销售代表使用摘要
3. 销售代表提供反馈
4. 更新摘要模板
5. 重新训练AI模型
6. 重复循环
目标:打造销售代表喜爱并信任的摘要。