cs-escalation-brief

Solid

Write a structured escalation brief for an at-risk customer account. Use when an account has escalated, when a customer is threatening churn, when a P1 customer issue needs executive attention, or when preparing an internal save play. Produces a crisp escalation brief with account context, timeline, root cause, business impact, and a clear resolution plan.

AI & Automation 915 stars 165 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Customer Escalation Brief Skill Produce a clear, concise escalation brief that gives internal stakeholders — VP CS, CCO, product leadership, or the CEO — everything they need to understand the situation, make decisions, and act fast. A good escalation brief is not a complaint. It is a professional document that states the facts, assigns accountability honestly, and proposes a specific resolution plan. ## Required Inputs Ask for these if not already provided: - **Account name**, tier, and ARR - **CSM name** and account owner - **Nature of the escalation** — what happened, what the customer is saying - **Timeline** of events leading to escalation - **Customer contact** who escalated (name, role, influence level) - **What the customer wants** — their stated ask - **What we believe the root cause is** - **What has already been done** to address the situation - **Renewal date** and current renewal risk assessment ## Escalation Levels Calibrate urgency and audience based on escalation level: | Level | Trigger | Audience | Response time | |---|---|---|---| | L1 — Account Risk | Customer expressing dissatisfaction; renewal at risk | CSM + CS Manager | 24 hours | | L2 — Executive Escalation | Customer escalated to their exec; requesting vendor exec involvement | VP CS + Account Exec | 4 hours | | L3 — Churn Risk | Customer has issued notice or is in active churn conversation | CCO / CEO + Revenue leadership | 1 hour | | L4 — Public Risk | Customer threatening public escalatio...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

customer-escalation

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.

2 Updated yesterday
nota-america
AI & Automation Listed

customer-escalation

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.

15 Updated yesterday
charlieviettq
AI & Automation Solid

escalation-workflow

Automated escalation path determination and workflow execution

1,034 Updated today
a5c-ai
AI & Automation Solid

cs-health-scorecard

Build a customer health scorecard for a specific account. Use when asked to score account health, assess renewal risk, build a health dashboard, or evaluate an account's likelihood to renew or expand. Produces a structured health scorecard with a RAG status, dimension scores, key risks, and recommended actions.

915 Updated 3 days ago
mohitagw15856
AI & Automation Listed

human-escalation

An agent that knows the boundary of its own authority and competence - pausing to involve a human when decisions carry risk, when requirements are ambiguous, or when the task exceeds what autonomous execution should handle. Without this skill, agents make irreversible decisions, introduce security risks, or silently build the wrong thing.

2 Updated today
varunk130