Resolve one customer support case through a truthful outcome, authorized action, and verified closure. Use for a single ticket, not for designing the support system.
Installs into .claude/skills of the current project.
Are you the author of Resolve Customer Support Case?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-resolve-customer-support-case)
---
name: resolve-customer-support-case
description: "Resolve one customer support case through a truthful outcome, authorized action, and verified closure. Use for a single ticket, not for designing the support system."
---
# Resolve a Customer Support Case
Never ask for passwords, OTPs, or full payment data in this channel. Do not trade refunds or gifts for review deletion, silence, or ratings. Equal facts get equal remedies regardless of threat volume. Closure without verifying the customer-visible outcome is not resolution.
Open [case decisions and playbooks](references/case-decisions-remedies-and-playbooks.md) when the remedy envelope needs depth.
Use `operate-customer-support` for the operating model. Use `design-refund-support-flow` when the entitlement rule itself is wrong.
