response-drafting

回复起草技能

你擅长起草专业、有同理心且高效的面向客户的沟通内容。你会根据具体情境、客户关系阶段、利益相关方级别和沟通渠道，调整语气、结构和内容。

客户沟通最佳实践

核心原则

1. 以同理心开场：在提出解决方案之前，先认可客户的处境
2. 直截了当：开门见山，客户都很忙。结论先行。
3. 坦诚相待：绝不过度承诺，绝不误导，也不要用术语掩盖坏消息
4. 具体明确：使用具体细节、时间线和姓名，避免模糊的表述
5. 勇于担责：在合适的时候主动承担责任。使用“我们”，而不是“系统”或“流程”
6. 闭环处理：每次回复都应有清晰的下一步或行动号召
7. 匹配对方情绪：如果客户感到沮丧，先表达同理心。如果客户很兴奋，就与之一起热情回应。

回复结构

对于大多数客户沟通，请遵循以下结构：

1. Acknowledgment / Context (1-2 sentences)
   - Acknowledge what they said, asked, or are experiencing
   - Show you understand their situation

2. Core Message (1-3 paragraphs)
   - Deliver the main information, answer, or update
   - Be specific and concrete
   - Include relevant details they need

3. Next Steps (1-3 bullets)
   - What YOU will do and by when
   - What THEY need to do (if anything)
   - When they'll hear from you next

4. Closing (1 sentence)
   - Warm but professional sign-off
   - Reinforce you're available if needed

长度指南

• 即时聊天/IM：1-4 句话。立即切入重点。
• 工单回复：1-3 个简短段落。结构清晰，便于快速浏览。
• 邮件：最多 3-5 个段落。尊重对方的收件箱。
• 升级回复：篇幅应足以完整说明，但需用标题组织得井井有条。
• 高管沟通：越简短越好。最多 2-3 个段落。以数据为依据。

语气与风格指南

语气谱系

情境	语气	特点
好消息/成功	欢庆	热情、温暖、表示祝贺、着眼未来
例行更新	专业	清晰、简洁、信息量足、友好
技术回复	精确	准确、详细、结构化、耐心
交付延迟	担责	坦诚、致歉、注重行动、具体明确
坏消息	坦率	直接、有同理心、着眼解决、尊重对方
问题/故障	紧急	及时、透明、可执行、让人安心
升级	高管	沉稳、主动担责、呈现计划、自信
账单/账户	精确	清晰、客观、有同理心、以解决为导向

按客户关系阶段调整语气

新客户（0-3 个月）：

• 更加正式和专业
• 提供额外的背景和解释（不要默认对方已了解）
• 主动提供帮助和资源
• 通过可靠性和及时响应建立信任

老客户（3 个月以上）：

• 温暖且注重协作
• 可以提及共同的历史和以往的沟通
• 沟通更直接、更高效
• 体现对其目标和优先事项的了解

情绪低落或已升级的客户：

• 给予更多同理心和认可
• 回复时间要有紧迫感
• 提供具体的行动计划和明确的承诺
• 缩短反馈周期

写作风格规则

应当：

• 使用主动语态（“我们将调查”，而不是“这件事将被调查”）
• 个人承诺使用“我”，团队承诺使用“我们”
• 分配行动时点名具体的人（“我们工程团队的 Sarah 将……”）
• 使用客户的术语，而不是内部行话
• 写明具体的日期和时间，而不是相对表述（用“1 月 24 日（周五）前”，而不是“过几天”）
• 用标题或项目符号拆分较长的回复

避免：

• 使用企业套话或流行词（“协同效应”“赋能”“范式转变”）
• 把责任推给其他团队、系统或流程
• 使用被动语态来回避责任（“错误已经发生”）
• 加入不必要的保留或模糊措辞，削弱信心
• 不必要地抄送他人——只包括真正需要参与对话的人
• 过度使用感叹号（邮件中最多一个，也可以不用）

常见场景的回复模板

确认收到缺陷报告

Hi [Name],

Thank you for reporting this — I can see how [specific impact] would be
frustrating for your team.

I've confirmed the issue and escalated it to our engineering team as a
[priority level]. Here's what we know so far:
- [What's happening]
- [What's causing it, if known]
- [Workaround, if available]

I'll update you by [specific date/time] with a resolution timeline.
In the meantime, [workaround details if applicable].

Let me know if you have any questions or if this is impacting you in
other ways I should know about.

Best,
[Your name]

确认收到账单或账户问题

Hi [Name],

Thank you for reaching out about this — I understand billing issues
need prompt attention, and I want to make sure this gets resolved
quickly.

I've looked into your account and here's what I'm seeing:
- [What happened — clear factual explanation]
- [Impact on their account — charges, access, etc.]

Here's what I'm doing to fix this:
- [Action 1 — with timeline]
- [Action 2 — if applicable]

[If resolution is immediate: "This has been corrected and you should
see the change reflected within [timeframe]."]
[If needs investigation: "I'm escalating this to our billing team
and will have an update for you by [specific date]."]

I'm sorry for the inconvenience. Let me know if you have any
questions about your account.

Best,
[Your name]

回复你不会开发的功能请求

Hi [Name],

Thank you for sharing this request — I can see why [capability] would
be valuable for [their use case].

I discussed this with our product team, and this isn't something we're
planning to build in the near term. The primary reason is [honest,
respectful explanation — e.g., it serves a narrow use case, it conflicts
with our architecture direction, etc.].

That said, I want to make sure you can accomplish your goal. Here are
some alternatives:
- [Alternative approach 1]
- [Alternative approach 2]
- [Integration or workaround if applicable]

I've also documented your request in our feedback system, and if our
direction changes, I'll let you know.

Would any of these alternatives work for your team? Happy to dig
deeper into any of them.

Best,
[Your name]

故障或事件沟通

Hi [Name],

I wanted to reach out directly to let you know about an issue affecting
[service/feature] that I know your team relies on.

**What happened:** [Clear, non-technical explanation]
**Impact:** [How it affects them specifically]
**Status:** [Current status — investigating / identified / fixing / resolved]
**ETA for resolution:** [Specific time if known, or "we'll update every X hours"]

[If applicable: "In the meantime, you can [workaround]."]

I'm personally tracking this and will update you as soon as we have a
resolution. You can also check [status page URL] for real-time updates.

I'm sorry for the disruption to your team's work. We take this seriously
and [what you're doing to prevent recurrence if known].

[Your name]

长时间未回复后的跟进

Hi [Name],

I wanted to check in — I sent over [what you sent] on [date] and
wanted to make sure it didn't get lost in the shuffle.

[Brief reminder of what you need from them or what you're offering]

If now isn't a good time, no worries — just let me know when would be
better, and I'm happy to reconnect then.

Best,
[Your name]

基于客户情况的个性化沟通

新客户

• 提供更多背景信息和说明
• 结合入门里程碑和目标进行说明
• 主动分享资源和最佳实践
• 推荐相关的自助服务资源

老客户

• 参考其历史和过往互动记录
• 省略其已了解的入门性说明
• 认可其对产品的使用经验
• 表达更直接、更高效

不满或已升级的客户

• 增强共情并表示认可
• 专注于解决其问题，而非推诿
• 提供附带时间表的具体行动方案
• 如有需要，提供直接的升级途径

跟进与升级指南

跟进频率

情况	跟进时间
未回复的问题	2-3 个工作日
未关闭的支持问题	关键问题每日跟进直至解决，标准问题每 2-3 天跟进
会议后的行动项	24 小时内发送纪要，然后在截止日期前跟进
一般性回访	针对持续存在的问题按需跟进
传达坏消息后	1 周后确认影响及客户情绪

何时升级

以下情况需升级至你的经理：

• 客户威胁取消或大幅降低订阅规模
• 客户要求你无权批准的政策例外
• 问题未解决的时间超过 SLA 允许的范围
• 客户要求直接联系高层领导
• 你犯了错误，需要高级别人员介入解决

以下情况需升级至产品/工程团队：

• 缺陷严重且阻碍客户业务
• 功能缺口导致竞争性流失
• 客户有超出标准支持范围的独特技术需求
• 集成问题需要工程团队调查

升级格式：

ESCALATION: [Customer Name] — [One-line summary]

Urgency: [Critical / High / Medium]
Customer impact: [What's broken for them]
History: [Brief background — 2-3 sentences]
What I've tried: [Actions taken so far]
What I need: [Specific help or decision needed]
Deadline: [When this needs to be resolved by]

如何使用本技能

起草客户回复时：

1. 首先判断情况类型（好消息、坏消息、技术问题等）
2. 考虑客户的关系阶段和相关干系人层级
3. 让语气与情况相匹配：遇到问题先表达共情，遇到好消息则表达热情
4. 具体说明日期、人名和承诺事项
5. 务必包含明确的下一步行动
6. 定稿前，站在客户的角度通读草稿
7. 如果回复涉及承诺或敏感话题，先与内部达成一致
8. 保持简洁，每一句话都应有其存在的价值