cs-analytics
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCustomer Service Analytics
客户服务分析
Framework
框架
IRON LAW: Measure Satisfaction AND Efficiency — Never Just One
High CSAT with terrible resolution time = unsustainable (agents spend
too long per ticket). Fast resolution with low CSAT = cutting corners.
Both dimensions must be tracked and balanced.IRON LAW: Measure Satisfaction AND Efficiency — Never Just One
High CSAT with terrible resolution time = unsustainable (agents spend
too long per ticket). Fast resolution with low CSAT = cutting corners.
Both dimensions must be tracked and balanced.Key Metrics
核心指标
Satisfaction Metrics
| Metric | What It Measures | How to Collect | Benchmark |
|---|---|---|---|
| CSAT | Satisfaction with specific interaction | Post-interaction survey (1-5 scale) | > 4.0/5 |
| NPS | Likelihood to recommend | "How likely to recommend?" (0-10) | > 30 |
| CES | Effort required to resolve | "How easy was it to resolve?" (1-7) | > 5.0/7 |
Efficiency Metrics
| Metric | Formula | Benchmark |
|---|---|---|
| First Contact Resolution (FCR) | Resolved on first contact / Total contacts | > 70% |
| Average Handle Time (AHT) | Total handle time / Total contacts | 5-8 min (varies by industry) |
| Average Response Time | Time from ticket creation to first response | < SLA target |
| Backlog | Open tickets / Daily throughput | < 1 day |
| Escalation Rate | Escalated tickets / Total tickets | < 20% |
| Reopen Rate | Reopened tickets / Resolved tickets | < 5% |
Operational Metrics
| Metric | Formula | Use |
|---|---|---|
| Ticket Volume | Tickets per day/week/month | Staffing planning |
| Channel Mix | % by channel (email, chat, phone, LINE) | Resource allocation |
| Peak Hours | Volume by hour-of-day | Shift scheduling |
| Category Distribution | % by issue type | Process improvement priority |
满意度指标
| 指标 | 衡量内容 | 收集方式 | 基准值 |
|---|---|---|---|
| CSAT | 特定交互的满意度 | 交互后调查（1-5分制） | > 4.0/5 |
| NPS | 推荐意愿 | “您有多大可能推荐我们？”（0-10分） | > 30 |
| CES | 问题解决所需的精力 | “解决问题的难易程度如何？”（1-7分） | > 5.0/7 |
效率指标
| 指标 | 计算公式 | 基准值 |
|---|---|---|
| First Contact Resolution (FCR) 首次联系解决率 | 首次联系解决工单量 / 总联系量 | > 70% |
| Average Handle Time (AHT) 平均处理时长 | 总处理时长 / 总联系量 | 5-8分钟（因行业而异） |
| 平均响应时间 | 工单创建到首次回复的时间 | < 服务水平协议（SLA）目标 |
| 工单积压量 | 未结工单量 / 每日处理量 | < 1天 |
| 升级率 | 升级工单量 / 总工单量 | < 20% |
| 重开率 | 重开工单量 / 已解决工单量 | < 5% |
运营指标
| 指标 | 计算公式 | 用途 |
|---|---|---|
| 工单量 | 每日/每周/每月工单数量 | 人员配置规划 |
| 渠道占比 | 各渠道占比（邮件、在线聊天、电话、LINE） | 资源分配 |
| 高峰时段 | 按小时统计的工单量 | 班次调度 |
| 问题类别分布 | 各问题类型占比 | 流程改进优先级排序 |
Analysis Workflows
分析流程
1. Top Contact Reason Analysis
- Categorize all tickets by reason (auto-tag or manual)
- Pareto chart: top 5 reasons usually account for 60-80% of volume
- For each top reason: can it be self-served? Automated? Eliminated at source?
2. Text Mining on Tickets
- Extract frequent keywords/phrases from ticket descriptions
- Cluster into topics (LDA, BERTopic, or simple TF-IDF)
- Identify emerging issues (new topics appearing in recent weeks)
- Sentiment analysis on customer messages
3. Staffing Optimization
Required Agents = Peak Hour Volume × AHT / (60 × Utilization Target)
Example: 50 tickets/hour × 8 min AHT / (60 × 0.75 utilization) = 8.9 → 9 agentsAdd buffer for breaks, meetings, and training (~15-20%).
4. Agent Performance
| Metric | Compare | Action |
|---|---|---|
| Individual CSAT vs team avg | Identify coaching needs | Training for below-average |
| Individual AHT vs team avg | Identify efficiency gaps | Shadow high-performers |
| FCR by agent | Identify knowledge gaps | Knowledge base improvements |
1. 主要联系原因分析
- 按原因对所有工单进行分类（自动打标签或手动分类）
- 帕累托图：前5大原因通常占工单总量的60-80%
- 针对每个主要原因：能否实现自助服务？能否自动化？能否从根源消除？
2. 工单文本挖掘
- 从工单描述中提取高频关键词/短语
- 聚类为主题（LDA、BERTopic或简单TF-IDF算法）
- 识别新出现的问题（近几周出现的新主题）
- 对客户消息进行情感分析
3. 人员配置优化
Required Agents = Peak Hour Volume × AHT / (60 × Utilization Target)
Example: 50 tickets/hour × 8 min AHT / (60 × 0.75 utilization) = 8.9 → 9 agents需为休息、会议和培训预留缓冲空间（约15-20%）。
4. 客服人员绩效
| 指标 | 对比对象 | 行动 |
|---|---|---|
| 个人CSAT vs 团队平均值 | 识别辅导需求 | 为低于平均值的人员提供培训 |
| 个人AHT vs 团队平均值 | 识别效率差距 | 让效率低的人员观摩高绩效员工 |
| 按客服人员统计的FCR | 识别知识缺口 | 优化知识库 |
VOC (Voice of Customer) Tracking
客户声音（VOC）跟踪
| Signal | Source | Frequency |
|---|---|---|
| Emerging complaints | Ticket text mining | Weekly |
| Feature requests | Tagged tickets + surveys | Monthly |
| Churn signals | "Cancel" intent tickets, low CSAT patterns | Weekly |
| Praise patterns | High CSAT + positive comments | Monthly (share with team) |
| 信号 | 来源 | 频率 |
|---|---|---|
| 新出现的投诉 | 工单文本挖掘 | 每周 |
| 功能需求 | 打标签的工单 + 调查 | 每月 |
| 流失信号 | 包含“取消”意图的工单、低CSAT模式 | 每周 |
| 表扬模式 | 高CSAT + 正面评价 | 每月（与团队分享） |
Output Format
输出格式
markdown
undefinedmarkdown
undefinedCS Analytics Report: {Period}
CS Analytics Report: {Period}
Summary Dashboard
Summary Dashboard
| Metric | Current | Prior | Target | Status |
|---|---|---|---|---|
| CSAT | {X}/5 | {X}/5 | >4.0 | 🟢/🟡/🔴 |
| FCR | {%} | {%} | >70% | 🟢/🟡/🔴 |
| Avg Response Time | {hrs} | {hrs} | <{X}hrs | 🟢/🟡/🔴 |
| Ticket Volume | {N} | {N} | — | ↑/↓ |
| Metric | Current | Prior | Target | Status |
|---|---|---|---|---|
| CSAT | {X}/5 | {X}/5 | >4.0 | 🟢/🟡/🔴 |
| FCR | {%} | {%} | >70% | 🟢/🟡/🔴 |
| Avg Response Time | {hrs} | {hrs} | <{X}hrs | 🟢/🟡/🔴 |
| Ticket Volume | {N} | {N} | — | ↑/↓ |
Top Contact Reasons (Pareto)
Top Contact Reasons (Pareto)
| # | Reason | Volume | % | Self-Servable? |
|---|---|---|---|---|
| 1 | {reason} | {N} | {%} | Y/N |
| # | Reason | Volume | % | Self-Servable? |
|---|---|---|---|---|
| 1 | {reason} | {N} | {%} | Y/N |
Emerging Issues
Emerging Issues
{New topics detected in text mining this period}
{New topics detected in text mining this period}
Staffing
Staffing
- Current agents: {N}
- Required (based on volume): {N}
- Gap: {over/under-staffed by N}
- Current agents: {N}
- Required (based on volume): {N}
- Gap: {over/under-staffed by N}
Recommendations
Recommendations
- {highest-impact improvement}
undefined- {highest-impact improvement}
undefinedGotchas
注意事项
- CSAT response bias: Only 10-20% of customers respond to surveys, usually the very happy and very unhappy. The silent majority's experience is unknown. Supplement with behavioral data (repeat contact, churn).
- NPS is strategic, CSAT is tactical: NPS measures overall brand loyalty (long-term). CSAT measures specific interaction quality (short-term). Don't use NPS to evaluate individual agents.
- AHT optimization can hurt quality: Pressure to reduce AHT may cause agents to rush, reducing FCR and CSAT. Optimize FCR first, then look at AHT.
- Ticket categorization drift: Categories become outdated as products evolve. Review and update the category taxonomy quarterly.
- Correlation ≠ causation in CS data: "Agents who use more templates have higher CSAT" might mean templates help, OR that experienced agents (who happen to use templates) are just better.
- CSAT回复偏差：仅10-20%的客户会回复调查，通常是非常满意或非常不满意的客户。沉默大多数的体验未知。需要补充行为数据（重复联系、客户流失）。
- NPS是战略指标，CSAT是战术指标：NPS衡量整体品牌忠诚度（长期）。CSAT衡量特定交互质量（短期）。不要用NPS评估单个客服人员。
- 优化AHT可能影响服务质量：施压缩短AHT可能导致客服人员敷衍了事，降低FCR和CSAT。应先优化FCR，再考虑AHT。
- 工单分类偏差：随着产品迭代，分类会过时。需每季度审核并更新分类体系。
- 客服数据中的相关性≠因果性：“使用更多模板的客服人员CSAT更高”可能意味着模板有用，也可能是经验丰富的客服人员（恰好使用模板）本身更优秀。
References
参考资料
- For NPS survey design, see
references/nps-methodology.md - For text mining on support tickets, see
references/ticket-text-mining.md
- 关于NPS调查设计，请查看
references/nps-methodology.md - 关于工单文本挖掘，请查看
references/ticket-text-mining.md