Auto-sync: 2026-04-21 04:02
This commit is contained in:
53
wiki/concepts/Support-Tiers.md
Normal file
53
wiki/concepts/Support-Tiers.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: support-tiers
|
||||
title: "Support Tiers"
|
||||
type: concept
|
||||
tags: [customer-service, support, escalation]
|
||||
sources: [support-support-responder.md]
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
支持层级(Support Tiers),分层客户服务架构,根据问题复杂度和客户类型将请求分配到不同专业级别的支持团队。
|
||||
|
||||
## Tier Structure
|
||||
|
||||
### Tier 1 — General Support
|
||||
**Capabilities**:
|
||||
- Account Management:账户创建、修改、恢复
|
||||
- Basic Troubleshooting:常见问题诊断和解决
|
||||
- Product Information:产品功能和使用指导
|
||||
- Billing Inquiries:账单查询和基本计费问题
|
||||
|
||||
**Escalation Criteria**:
|
||||
- 技术复杂度超出基础知识范围
|
||||
- 政策例外请求需要管理层批准
|
||||
- 客户表达不满且一线无法解决
|
||||
|
||||
### Tier 2 — Technical Support
|
||||
**Capabilities**:
|
||||
- Advanced Troubleshooting:复杂技术问题诊断
|
||||
- Integration Support:API 和系统集成支持
|
||||
- Custom Configuration:定制化配置指导
|
||||
- Bug Reproduction:问题复现和日志分析
|
||||
|
||||
**Escalation Criteria**:
|
||||
- 需要工程团队介入的代码级别问题
|
||||
- 安全相关问题需要安全团队
|
||||
- 数据恢复需要 DBA 支持
|
||||
|
||||
### Tier 3 — Specialist Support
|
||||
**Capabilities**:
|
||||
- Enterprise Support:企业级客户专属支持
|
||||
- Custom Development:定制开发需求评估
|
||||
- Security Incidents:安全事件响应
|
||||
- Data Recovery:重大数据恢复操作
|
||||
|
||||
**Escalation Criteria**:
|
||||
- C-Level 管理层涉及
|
||||
- 法律咨询需求
|
||||
- 需要产品团队深度协作
|
||||
|
||||
## Connections
|
||||
- [[Multi-Channel Support Framework]] — 层级嵌入的框架
|
||||
- [[Support Responder]] — 层级执行的主体
|
||||
Reference in New Issue
Block a user