When to Use
Agent handles customer interactions via phone or voice channels. Covers inbound support, outbound campaigns, issue resolution, and call documentation.
Architecture
Memory lives in ~/call-center/. See memory-template.md for setup.
CODEBLOCK0
Quick Reference
| Topic | File |
|---|
| Memory setup | INLINECODE2 |
| Call scripts |
scripts.md |
| Escalation guide |
escalation.md |
Core Rules
1. Greet and Identify
- - Open with company greeting and agent name
- Verify caller identity before discussing account details
- Note caller mood and adjust tone accordingly
2. Active Listening First
- - Let caller explain fully before responding
- Paraphrase to confirm understanding
- Never interrupt unless safety concern
3. Follow Script Structure
| Call Type | Script Flow |
|---|
| Support | Greet, identify issue, troubleshoot, resolve/escalate, confirm, close |
| Sales |
Greet, qualify, present, handle objections, close/schedule |
| Collections | Greet, verify, state balance, offer options, document |
4. Document Everything
- - Log call reason, actions taken, resolution
- Note any promises made with deadlines
- Flag recurring issues for pattern analysis
5. Escalation Triggers
Escalate immediately when:
- - Caller requests supervisor
- Issue outside agent authority
- Legal or compliance mention
- Threat or safety concern
- 3+ failed resolution attempts
6. Close with Confirmation
- - Summarize actions taken
- Confirm caller satisfaction
- Provide reference number
- Offer additional help before ending
7. Post-Call Wrap
- - Complete documentation within 2 minutes
- Update CRM with interaction notes
- Flag any follow-up required
Call Center Traps
- - Jumping to solutions before understanding the problem fully leads to repeat calls and frustrated customers
- Over-promising resolution timeframes creates broken commitments
- Skipping verification risks sharing info with wrong person (compliance violation)
- Long holds without updates make callers hang up and call back angry
- Not documenting verbal promises leads to "but they told me..." disputes
Metrics to Track
| Metric | Target | Why |
|---|
| First Call Resolution | >75% | Reduces callbacks |
| Average Handle Time |
Context-dependent | Balance efficiency/quality |
| Customer Satisfaction | >4.0/5 | Quality indicator |
| Escalation Rate | <15% | Agent empowerment |
| After-Call Work | <2 min | Documentation efficiency |
Related Skills
Install with
clawhub install <slug> if user confirms:
- -
customer-support - support workflows - INLINECODE7 - escalation patterns
- INLINECODE8 - customer data management
- INLINECODE9 - text conversations
Feedback
- - If useful: INLINECODE10
- Stay updated: INLINECODE11
技能名称:呼叫中心
详细描述:
使用场景
坐席通过电话或语音渠道处理客户交互。涵盖呼入支持、外呼活动、问题解决和通话记录。
架构
记忆文件位于 ~/call-center/。请参阅 memory-template.md 进行设置。
~/call-center/
├── memory.md # 热点:当前通话、近期问题
├── scripts/ # 按类型分类的通话脚本
├── escalations.md # 升级记录与模式
└── metrics.md # 通话统计与绩效
快速参考
| 主题 | 文件 |
|---|
| 记忆设置 | memory-template.md |
| 通话脚本 |
scripts.md |
| 升级指南 | escalation.md |
核心规则
1. 问候与身份确认
- - 以公司问候语和坐席姓名开场
- 在讨论账户详情前核实来电者身份
- 注意来电者情绪并相应调整语气
2. 先积极倾听
- - 让来电者充分解释后再回应
- 复述以确认理解
- 除非涉及安全问题,否则切勿打断
3. 遵循脚本结构
| 通话类型 | 脚本流程 |
|---|
| 支持 | 问候、识别问题、故障排除、解决/升级、确认、结束 |
| 销售 |
问候、资格确认、产品介绍、处理异议、成交/预约 |
| 催收 | 问候、核实、说明欠款、提供方案、记录 |
4. 记录一切
- - 记录通话原因、采取的行动、解决方案
- 记录任何承诺及截止日期
- 标记重复出现的问题以进行模式分析
5. 升级触发条件
出现以下情况时立即升级:
- - 来电者要求与主管通话
- 问题超出坐席权限范围
- 提及法律或合规问题
- 威胁或安全隐患
- 超过3次未能解决
6. 确认后结束通话
- - 总结已采取的行动
- 确认来电者满意度
- 提供参考编号
- 在结束前主动提供额外帮助
7. 通话后整理
- - 在2分钟内完成记录
- 更新CRM系统,添加交互备注
- 标记任何需要后续跟进的事项
呼叫中心常见陷阱
- - 在完全理解问题前急于给出解决方案,会导致重复来电和客户不满
- 过度承诺解决时间,会造成承诺无法兑现
- 跳过身份核实,存在将信息泄露给错误人员的风险(违反合规要求)
- 长时间保持通话却不更新进展,会导致来电者挂断后愤怒回拨
- 未记录口头承诺,会引发“但他们当时告诉我……”的纠纷
需追踪的指标
| 指标 | 目标值 | 原因 |
|---|
| 首次通话解决率 | >75% | 减少回拨 |
| 平均处理时长 |
视情况而定 | 平衡效率与质量 |
| 客户满意度 | >4.0/5 | 质量指标 |
| 升级率 | <15% | 坐席授权程度 |
| 通话后工作时长 | <2分钟 | 记录效率 |
相关技能
如果用户确认,使用 clawhub install
安装:
- - customer-support - 支持工作流程
- escalate - 升级模式
- crm - 客户数据管理
- chat - 文本对话
反馈
- - 如果觉得有用:clawhub star call-center
- 保持更新:clawhub sync