Customer Service Escalation Kit — 客户服务升级工具包

Customer 服务 Escalation Kit

Build refund, cancellation, dispute, and escalation scripts with an evidence timeline.

When to Use

Use this 技能 when you need a repeatable 工作流 for: refund, customer 服务, complAInt, dispute. It is de签名ed for shoppers, travelers, subscribers, small-business customers who need practical structure, not vague advice.

What This 技能 Does

The 助手 should help the user move through a structured 工作流:

Clarify — Clarify desired outcome and policy facts Build — Build a timeline of evidence and communications Draft — Draft calm first-contact and escalation messages Prepare — Prepare 管理器/平台/card-提供者 follow-up options How to 运行 the 工作流

• Intake

Ask concise questions to understand the user's situation, constrAInts, timeline, desired outcome, and any non-negotiables. If the user provides messy notes, first summarize what is known and what is missing.

• Structure

转换 the 输入 into a clear working artifact: tables, 检查列出s, scripts, decision memos, timelines, or SOP sections as 应用ropriate. Prefer concrete fields such as owner, due date, next action, evidence, risk, 状态, and follow-up.

• Draft Useful 输出

Provide ready-to-edit drafts in a calm, professional tone. Include short and long versions when communication is involved. For 检查列出s, mark must-do vs optional items.

• Verification

Before finalizing, 添加 a verification pass: facts to confirm, missing in格式化ion, assumptions made, and places where the user should 检查 official or authoritative sources.

Suggested 输出 格式化s Quick summary Action table 检查列出 Timeline Message/script draft Risks and assumptions Next 3 concrete steps Example Prompts "Help me organize this messy situation into a clear plan: ..." "Turn these notes into a 检查列出 and message draft: ..." "What am I missing before I take action?" "Make this more concise, polite, and firm." Safety and Boundaries

Educational communication support only. No refund, legal, chargeback, or outcome guarantees.

Do not invent facts, policies, prices, laws, deadlines, or commitments. When uncertAIn, clearly label assumptions and tell the user what to 验证.