warm-transfer-execution
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWarm Transfer Execution
暖转接执行指南
You are an expert in building seamless handoff systems for sales bots. Your goal is to help developers create transfers to human reps that feel smooth and maintain conversation momentum.
您是构建销售机器人(sales bot)无缝转接系统的专家。您的目标是帮助开发者实现流畅的人工客服转接,同时保持对话连贯性。
What Makes a Transfer "Warm"
何为「暖转接」
Cold Transfer (Bad)
冷转接(反面示例)
Bot: "Let me transfer you to a representative."
[Call connects]
Rep: "Hi, how can I help you?"
Prospect: "I was just talking to your chatbot about..."
Rep: "Can you start from the beginning?"机器人:“我将为您转接至客服代表。”
[电话接通]
客服:“您好,有什么可以帮您的?”
潜在客户:“我刚才正在和你们的聊天机器人咨询……”
客服:“您能从头再说一遍吗?”Warm Transfer (Good)
暖转接(正面示例)
Bot: "Sarah from our enterprise team will help you
from here. She knows you're looking at the 500-user
plan for Q2. One moment while I connect you."
[Transfer happens]
Rep: "Hi [Name]! I see you're evaluating our enterprise
plan for about 500 users. I also saw you had questions
about Salesforce integration. Let's dive in!"机器人:“接下来将由我们企业客户团队的Sarah为您提供帮助,她了解您正在为第二季度评估500用户规模的套餐。请稍等,我这就为您转接。”
[转接完成]
客服:“您好[姓名]!我了解到您正在评估我们的企业套餐,面向约500名用户。同时我也注意到您对Salesforce集成有疑问,我们直接切入正题吧!”Transfer Triggers
转接触发条件
When to Transfer
转接时机
Positive triggers (opportunity):
- High-value prospect identified
- Ready to buy signals
- Request for demo/meeting
- Complex questions needing expertise
- Enterprise-level inquiry
Necessary triggers (capability):
- Bot can't answer question
- Negotiation required
- Contract/legal discussions
- Escalation requested
- Language routing needed
Rescue triggers (risk):
- Frustrated prospect
- Repeated misunderstandings
- Sensitive situation
- VIP/strategic account
- Complaint in progress积极触发条件(潜在机会):
- 识别出高价值潜在客户
- 出现购买意向信号
- 请求演示/会议
- 需要专业知识解答的复杂问题
- 企业级咨询
必要触发条件(能力限制):
- 机器人无法解答问题
- 需要协商沟通
- 合同/法律相关讨论
- 用户要求升级处理
- 需要语言路由
补救触发条件(风险预警):
- 潜在客户产生不满
- 反复出现误解
- 敏感场景
- VIP/战略客户
- 正在进行的投诉Transfer Timing
转接时间点
Good timing:
- Natural conversation break
- After collecting key information
- When they ask for human
- Before conversation degrades
Bad timing:
- Mid-sentence/thought
- Before understanding their need
- Without warning
- When no human available合适的转接时机:
- 对话自然停顿节点
- 收集到关键信息后
- 用户主动要求转人工时
- 对话氛围恶化前
不适宜的转接时机:
- 用户发言中途/思路中断时
- 尚未理解用户需求前
- 未提前告知用户
- 无可用人工客服时Context Package
上下文数据包
Essential Information
核心信息
Transfer context must include:
PROSPECT INFO:
- Name
- Company
- Contact info
- Account history (if any)
CONVERSATION SUMMARY:
- How they found you
- What they asked about
- Key needs expressed
- Pain points mentioned
- Budget/timeline indicators
QUALIFICATION DATA:
- Company size
- Use case
- Decision timeline
- Budget range
- Decision maker status
SENTIMENT:
- Overall tone
- Frustration points
- Excitement points
- Specific concerns
RECOMMENDED APPROACH:
- What they respond to
- What to avoid
- Suggested next step转接上下文必须包含:
潜在客户信息:
- 姓名
- 公司
- 联系方式
- 账户历史记录(如有)
对话摘要:
- 客户来源渠道
- 初始咨询问题
- 表达的核心需求
- 提及的痛点
- 预算/时间线意向
资质评估数据:
- 公司规模
- 使用场景
- 决策时间线
- 预算范围
- 决策者身份
情感分析:
- 整体语气
- 不满点
- 兴奋点
- 具体顾虑
推荐应对方案:
- 用户的响应偏好
- 需要避免的内容
- 建议下一步动作Context Format
上下文格式
json
{
"transfer_id": "xfer_12345",
"timestamp": "2024-01-15T14:30:00Z",
"prospect": {
"name": "John Smith",
"email": "john@acme.com",
"phone": "+1-555-123-4567",
"company": "Acme Corp",
"title": "VP Sales",
"account_id": null
},
"conversation": {
"channel": "web_chat",
"duration_minutes": 12,
"messages_exchanged": 24,
"started_at": "2024-01-15T14:18:00Z"
},
"summary": {
"entry_point": "Clicked pricing page chat widget",
"initial_question": "Enterprise pricing for 500+ users",
"key_needs": [
"Salesforce integration",
"SSO/SAML support",
"Custom reporting"
],
"pain_points": [
"Current tool doesn't scale",
"Poor reporting capabilities"
],
"objections_raised": [
"Concerned about migration effort"
],
"objections_addressed": true
},
"qualification": {
"company_size": "500+ employees",
"use_case": "Sales team productivity",
"timeline": "Q2 implementation",
"budget": "Mentioned 'Enterprise budget available'",
"decision_maker": true,
"score": 85
},
"sentiment": {
"overall": "positive",
"frustration_level": "low",
"buying_intent": "high",
"notes": "Impressed by Salesforce integration depth"
},
"transfer_reason": "Ready for demo, enterprise deal",
"recommended_approach": "Focus on migration support and timeline",
"conversation_transcript": "[full transcript link or embedded]"
}json
{
"transfer_id": "xfer_12345",
"timestamp": "2024-01-15T14:30:00Z",
"prospect": {
"name": "John Smith",
"email": "john@acme.com",
"phone": "+1-555-123-4567",
"company": "Acme Corp",
"title": "VP Sales",
"account_id": null
},
"conversation": {
"channel": "web_chat",
"duration_minutes": 12,
"messages_exchanged": 24,
"started_at": "2024-01-15T14:18:00Z"
},
"summary": {
"entry_point": "Clicked pricing page chat widget",
"initial_question": "Enterprise pricing for 500+ users",
"key_needs": [
"Salesforce integration",
"SSO/SAML support",
"Custom reporting"
],
"pain_points": [
"Current tool doesn't scale",
"Poor reporting capabilities"
],
"objections_raised": [
"Concerned about migration effort"
],
"objections_addressed": true
},
"qualification": {
"company_size": "500+ employees",
"use_case": "Sales team productivity",
"timeline": "Q2 implementation",
"budget": "Mentioned 'Enterprise budget available'",
"decision_maker": true,
"score": 85
},
"sentiment": {
"overall": "positive",
"frustration_level": "low",
"buying_intent": "high",
"notes": "Impressed by Salesforce integration depth"
},
"transfer_reason": "Ready for demo, enterprise deal",
"recommended_approach": "Focus on migration support and timeline",
"conversation_transcript": "[full transcript link or embedded]"
}Transfer Flow
转接流程
Step 1: Prepare the Prospect
步骤1:提前告知潜在客户
"Based on what you're looking for, I think [Rep Name]
from our enterprise team would be perfect to help.
[He/She] specializes in [relevant expertise].
Before I connect you, is there anything else I should
let [them] know?"“根据您的需求,我认为我们企业客户团队的[客服姓名]是最适合为您提供帮助的人选,[他/她]专注于[相关领域专长]。
在为您转接前,还有其他需要我告知[他/她]的信息吗?”Step 2: Check Availability
步骤2:确认客服可用性
[Internal check]
- Is rep available?
- What's estimated wait time?
- Who else can take it?
If available:
"Perfect—[Rep] is available now. Let me connect you."
If not available:
"[Rep] is with another customer right now. You'll be
connected in about [X] minutes. Would you prefer to
wait, or should I have [them] call you back?"[内部核查]
- 客服是否空闲?
- 预计等待时长是多少?
- 还有其他可承接的客服吗?
若空闲:
“太好了——[客服姓名]现在有空,我这就为您转接。”
若不空闲:
“[客服姓名]目前正在服务其他客户,您大约需要等待[X]分钟。您是愿意等待,还是希望我安排[他/她]回电给您?”Step 3: Execute Transfer
步骤3:执行转接
To prospect:
"Connecting you now. [Rep] has the full context of
our conversation—you won't need to repeat anything."
To rep:
[Push notification with context package]
"Incoming: John from Acme Corp. 500-user enterprise
opportunity. Ready for demo. Hot lead."告知潜在客户:
“正在为您转接。[客服姓名]已获取我们的完整对话上下文——您无需重复任何内容。”
告知客服:
[推送含上下文数据包的通知]
“新转接:Acme公司的John,500用户规模的企业级机会,已准备好接受演示,高价值线索。”Step 4: Confirm Handoff
步骤4:确认转接完成
Rep acknowledgment:
"Got it—I see the context. Taking over."
Prospect confirmation:
Rep: "Hi John! I'm Sarah from the enterprise team.
I see you're looking at our solution for your 500-person
sales team, with Salesforce integration being key.
And you're hoping to have this in place by Q2, right?"客服确认:
“收到——我已查看上下文,开始承接对话。”
潜在客户确认:
客服:“您好John!我是企业客户团队的Sarah,我了解到您正在为500人的销售团队评估我们的解决方案,其中Salesforce集成是您的核心需求,并且您希望在第二季度完成部署,对吗?”Handling Transfer Scenarios
转接场景处理
Immediate Transfer (Live)
即时转接(在线)
Chat/Phone - rep available:
Bot: "Connecting you with Alex now..."
[2-3 second transition]
Rep: "Hi [Name], Alex here. I saw you were asking about
[topic]. Let me help with that!"聊天/电话 - 客服空闲时:
机器人:“正在为您转接Alex……”
[2-3秒过渡]
客服:“您好[姓名],我是Alex。我了解到您正在咨询[话题],让我来为您解答!”Queued Transfer
排队转接
Rep not immediately available:
Bot: "Our team is helping other customers right now.
You're [2nd] in queue—estimated wait is [3 minutes].
While you wait, is there anything else I can help with?
Or if you prefer, I can have someone call you back at
a specific time."
Options:
1. Wait in queue
2. Scheduled callback
3. Email follow-up客服无法即时响应时:
机器人:“我们的团队目前正在服务其他客户,您排在第[2]位,预计等待[3]分钟。
等待期间,还有其他我可以为您协助的吗?或者您更希望我安排专人在特定时间回电给您?”
可选方案:
1. 排队等待
2. 预约回电
3. 邮件跟进Async Transfer
异步转接
After hours or no availability:
Bot: "Our team isn't available right now, but I've
captured everything we discussed. [Rep Name] will
reach out first thing tomorrow.
Is email or phone better for you?"
Then send:
- Confirmation to prospect
- Full context to rep
- Calendar task for follow-up非工作时间或无可用客服时:
机器人:“我们的团队目前不在工作时间,但我已记录下我们的全部对话内容。[客服姓名]会在明天第一时间联系您。
您更希望通过邮件还是电话联系?”
随后执行:
- 向潜在客户发送确认信息
- 向客服发送完整上下文
- 在日历中创建跟进任务Failed Transfer Recovery
转接失败补救
If transfer fails:
Bot: "I apologize—we're having a technical issue
connecting you. Let me take your number and have
[Rep] call you directly within [X minutes].
What's the best number to reach you?"
Then:
- Collect callback info
- Alert rep immediately
- Log the issue
- Follow up to confirm connection made若转接失败:
机器人:“非常抱歉——我们在转接过程中遇到了技术问题。请提供您的电话号码,我会安排[客服姓名]在[X]分钟内直接致电您。
您的最佳联系电话是多少?”
随后执行:
- 收集回电信息
- 立即提醒客服
- 记录问题
- 跟进确认已成功联系Rep Enablement
客服赋能
Pre-Transfer Alert
转接前提醒
[Push notification to rep]
🔥 HOT TRANSFER INCOMING 🔥
Prospect: John Smith, VP Sales @ Acme Corp
Score: 85/100 (Enterprise)
Context: 500 users, Salesforce integration, Q2 timeline
Sentiment: Positive, ready for demo
Transfer reason: Qualified, requesting demo
[Accept] [Defer to colleague] [Schedule callback][向客服推送通知]
🔥 高价值转接提醒 🔥
潜在客户:John Smith,Acme公司销售副总裁
线索评分:85/100(企业级)
上下文:500用户规模,Salesforce集成需求,第二季度部署时间线
情感:积极,已准备好接受演示
转接原因:已通过资质审核,请求演示
[接受] [转交给同事] [预约回电]Context Display
上下文展示
Rep interface should show:
- Quick summary (scannable in 10 seconds)
- Key talking points
- Things to avoid
- Full transcript (expandable)
- Prospect profile (if in CRM)
- Suggested next steps客服界面应显示:
- 快速摘要(10秒内可浏览完毕)
- 核心沟通要点
- 需要避免的内容
- 完整对话记录(可展开)
- 潜在客户档案(若已录入CRM)
- 建议下一步动作Handoff Script Assistance
转接话术辅助
Suggested opener:
"Hi John! I'm [Rep] from the enterprise team.
[Bot name] filled me in—sounds like you're looking
to upgrade your 500-person sales team before Q2.
I'd love to help make that happen."
Key points to address:
☐ Salesforce integration details
☐ Migration support (concern raised)
☐ Q2 timeline feasibility
☐ Next step: Demo scheduling建议开场话术:
“您好John!我是企业客户团队的[客服姓名],[机器人名称]已向我同步了相关信息——听起来您希望在第二季度前为500人的销售团队完成系统升级,我很乐意为您提供帮助。”
需重点解决的问题:
☐ Salesforce集成细节
☐ 迁移支持(用户曾提出顾虑)
☐ 第二季度部署时间线可行性
☐ 下一步:安排演示Quality Assurance
质量保证
Transfer Metrics
转接指标
Track:
- Transfer completion rate
- Time to rep pickup
- Prospect satisfaction post-transfer
- Conversation continuation rate
- Conversion rate of transfers
- Context utilization by reps需跟踪的指标:
- 转接完成率
- 客服响应时长
- 转接后潜在客户满意度
- 对话延续率
- 转接线索转化率
- 客服上下文利用率Feedback Loop
反馈闭环
After transfer:
- Did rep find context helpful?
- Was anything missing?
- Did prospect have to repeat info?
- How could handoff improve?
Use feedback to improve context package.转接完成后:
- 客服是否认为上下文信息有帮助?
- 是否有缺失的信息?
- 潜在客户是否需要重复说明信息?
- 如何优化转接流程?
利用反馈优化上下文数据包。