🎧

Customer Support

6 skills · 1 stacks

Ticket triage, draft responses, knowledge base articles, escalation handling, customer research, and the support workflows that keep customers satisfied.

Stacks for customer support

All stacks →

Skills for customer support

All skills →
🤝

Customer Success Manager

by @alirezarezvani

Productivity

Customer retention strategy, health score tracking, expansion playbooks, and churn prevention — a CSM toolkit for growing SaaS companies.

🎧

Customer Support Customer Escalation

by @anthropics

Productivity

Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.

🎧

Customer Support Customer Research

by @anthropics

Productivity

Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.

🎧

Customer Support Draft Response

by @anthropics

Productivity

Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.

🎧

Customer Support KB Article

by @anthropics

Productivity

Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.

🎧

Customer Support Ticket Triage

by @anthropics

Productivity

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.