Design or improve the support operating model: contact taxonomy, routing, waiting-state clocks, authority, and quality loops. Use for the system, not for answering one ticket.
Installs into .claude/skills of the current project.
Are you the author of Operate Customer Support?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-operate-customer-support)
---
name: operate-customer-support
description: "Design or improve the support operating model: contact taxonomy, routing, waiting-state clocks, authority, and quality loops. Use for the system, not for answering one ticket."
---
# Operate Customer Support
Every waiting state has an owner and a next update time. Money, identity, and deletion stay with those owners. A queue without a clock is not an operating model.
Open [support operations patterns](references/support-ops-patterns.md) when routing, clocks, or quality loops need depth.
Use `resolve-customer-support-case` for one ticket.
