cs-sop
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCustomer Service SOP
客户服务SOP
Framework
框架
IRON LAW: Tier the Support, Not the Customer
Every customer deserves quality service. But not every issue needs a
senior specialist. Route by ISSUE COMPLEXITY, not by customer "importance."
L1 handles 70-80% of volume (simple, repeatable)
L2 handles 15-20% (requires expertise)
L3 handles 5% (requires engineering or management)铁律：对支持服务分层，而非对客户分层
每位客户都应获得优质服务。但并非每个问题都需要资深专员处理。按问题复杂度分配，而非按客户“重要性”。
L1处理70-80%的咨询量（简单、重复性问题）
L2处理15-20%的咨询量（需要专业知识）
L3处理5%的咨询量（需要工程师或管理层介入）Three-Tier Support Model
三层支持模型
| Tier | Handles | Skills Required | Resolution Target |
|---|---|---|---|
| L1 (Basic) | FAQ, order status, password reset, simple returns | Script-following, product basics, empathy | < 5 minutes, first-contact resolution |
| L2 (Specialist) | Technical issues, billing disputes, complex returns, product defects | Deep product knowledge, judgment, negotiation | < 24 hours |
| L3 (Expert) | System bugs, legal/compliance, executive escalations, crisis | Engineering, legal, or management involvement | < 72 hours, case-by-case |
| 层级 | 处理范围 | 所需技能 | 解决目标 |
|---|---|---|---|
| L1（基础层） | 常见问题、订单状态查询、密码重置、简单退货 | 遵循脚本、产品基础知识、共情能力 | < 5分钟，首次联系解决 |
| L2（专业层） | 技术问题、账单争议、复杂退货、产品缺陷 | 深厚的产品知识、判断能力、协商能力 | < 24小时 |
| L3（专家层） | 系统漏洞、法律/合规问题、高管升级投诉、危机事件 | 工程师、法务或管理层介入 | < 72小时，视具体情况而定 |
Case Categorization
案例分类
| Category | Examples | Priority | SLA (First Response) |
|---|---|---|---|
| Critical | Service outage, security breach, safety issue | P1 | < 15 minutes |
| High | Payment failure, account locked, order error | P2 | < 1 hour |
| Medium | Product question, feature request, general complaint | P3 | < 4 hours |
| Low | Feedback, suggestion, general inquiry | P4 | < 24 hours |
| 分类 | 示例 | 优先级 | SLA（首次回复） |
|---|---|---|---|
| 紧急 | 服务中断、安全漏洞、安全问题 | P1 | < 15分钟 |
| 高优先级 | 支付失败、账户锁定、订单错误 | P2 | < 1小时 |
| 中优先级 | 产品疑问、功能需求、一般投诉 | P3 | < 4小时 |
| 低优先级 | 反馈、建议、一般咨询 | P4 | < 24小时 |
Complaint Handling: LAST Framework
投诉处理：LAST框架
- Listen: Let the customer express fully without interrupting
- Apologize: Acknowledge their frustration sincerely ("I'm sorry this happened")
- Solve: Offer a concrete solution or next step
- Thank: Thank them for bringing it to your attention
- 倾听（Listen）：让客户充分表达，不打断
- 致歉（Apologize）：真诚认可客户的不满（“很抱歉发生了这样的事情”）
- 解决（Solve）：提供具体解决方案或下一步措施
- 感谢（Thank）：感谢客户将问题告知我们
Escalation Rules
升级规则
| Trigger | Escalate To | Timeline |
|---|---|---|
| L1 can't resolve in 15 min | L2 | Immediate warm handoff |
| Customer requests supervisor | L2 or Team Lead | Within 5 minutes |
| Issue involves refund > NT$X | L2 (approval authority) | Same interaction |
| Legal threat or media mention | L3 + Legal + PR | Immediate |
| Repeat contact (3+ on same issue) | L2 + investigation | After 3rd contact |
| 触发条件 | 升级至 | 时间要求 |
|---|---|---|
| L1在15分钟内无法解决 | L2 | 立即无缝转接 |
| 客户要求对接主管 | L2或团队负责人 | 5分钟内 |
| 涉及退款金额超过NT$X | L2（拥有审批权限） | 本次沟通内 |
| 涉及法律威胁或媒体提及 | L3 + 法务 + 公关 | 立即 |
| 同一问题重复联系3次及以上 | L2 + 调查团队 | 第3次联系后 |
Response Template Structure
回复模板结构
[Greeting] Hi {name}, thank you for contacting us.
[Acknowledge] I understand you're experiencing {issue}.
[Action] Here's what I've done / Here's what we'll do:
1. {specific action}
2. {timeline}
[Next steps] {what the customer should expect / do next}
[Close] Is there anything else I can help you with?[问候语] 您好{name}，感谢您联系我们。
[确认问题] 我了解您遇到了{issue}问题。
[行动措施] 以下是我已采取的措施/我们将采取的措施：
1. {具体行动}
2. {时间安排}
[下一步] {客户可预期的内容/需采取的行动}
[结束语] 还有其他我可以协助的吗？Output Format
输出格式
markdown
undefinedmarkdown
undefinedCustomer Service SOP: {Business}
客户服务SOP: {业务名称}
Support Tiers
支持层级
| Tier | Scope | Team Size | Tools |
|---|---|---|---|
| L1 | {scope} | {N people} | {tools} |
| L2 | {scope} | {N} | {tools} |
| L3 | {scope} | {N} | {tools} |
| 层级 | 范围 | 团队规模 | 工具 |
|---|---|---|---|
| L1 | {范围} | {N人} | {工具} |
| L2 | {范围} | {N人} | {工具} |
| L3 | {范围} | {N人} | {工具} |
SLA Targets
SLA目标
| Priority | First Response | Resolution | Escalation |
|---|---|---|---|
| P1 | {time} | {time} | {to whom} |
| P2 | ... | ... | ... |
| 优先级 | 首次回复 | 解决时间 | 升级对接 |
|---|---|---|---|
| P1 | {时间} | {时间} | {对接对象} |
| P2 | ... | ... | ... |
Top 10 Contact Reasons
十大咨询原因
| # | Reason | Volume % | Resolution | Template? |
|---|---|---|---|---|
| 1 | {reason} | {%} | L1/L2 | Y/N |
| 序号 | 原因 | 占比 | 解决层级 | 是否使用模板 |
|---|---|---|---|---|
| 1 | {原因} | {%} | L1/L2 | 是/否 |
Escalation Flowchart
升级流程图
{Decision tree for when to escalate}
{升级决策树}
Quality Metrics
质量指标
| Metric | Target |
|---|---|
| First Contact Resolution | > 70% |
| CSAT | > 4.2/5 |
| Avg Response Time | < {X} hours |
| Escalation Rate | < 20% |
undefined| 指标 | 目标 |
|---|---|
| 首次联系解决率 | > 70% |
| 客户满意度（CSAT） | > 4.2/5 |
| 平均回复时间 | < {X}小时 |
| 升级率 | < 20% |
undefinedGotchas
注意事项
- SLAs must be MEASURABLE: "Respond quickly" is not an SLA. "First response within 1 hour for P2 tickets" is. If you can't measure it, you can't manage it.
- Warm handoff > cold transfer: When escalating, the L1 agent should brief L2 before transferring. Forcing the customer to repeat their story destroys satisfaction.
- Empower L1 with resolution authority: If L1 must escalate every refund, 70% of volume goes to L2 unnecessarily. Give L1 authority for refunds under a threshold (e.g., NT$500).
- Templates are starting points, not scripts: Robotic copy-paste responses feel worse than no response. Agents should personalize templates to the specific situation.
- Taiwan CS expectations: Taiwan customers expect fast LINE response (within minutes during business hours), polite and apologetic tone, and willingness to go the extra mile. The bar for "good service" is high.
- SLA必须可衡量：“快速回复”不是SLA。“P2工单首次回复在1小时内”才是。无法衡量的标准，就无法管理。
- 无缝转接优于冷转接：升级时，L1客服应在转接前向L2简要说明情况。让客户重复叙述问题会严重影响满意度。
- 赋予L1解决权限：如果L1每次退款都必须升级，那么70%的咨询量会不必要地流向L2。应赋予L1一定金额以下的退款权限（例如NT$500）。
- 模板是起点，而非脚本：机械地复制粘贴回复比不回复更糟糕。客服应根据具体情况个性化调整模板内容。
- 台湾地区客服期望：台湾客户期望LINE快速回复（工作时间内几分钟内）、礼貌致歉的语气，以及愿意额外付出的服务态度。“优质服务”的标准很高。
References
参考资料
- For CSAT/NPS survey design, see the cs-analytics skill
- For chatbot-human handoff design, see the cs-chatbot-design skill
- 关于CSAT/NPS调查设计，请参考cs-analytics技能
- 关于聊天机器人-人工转接设计，请参考cs-chatbot-design技能