cs-escalation-brief
$
npx mdskill add mohitagw15856/pm-claude-skills/cs-escalation-briefProduce 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.
SKILL.md
.github/skills/cs-escalation-briefView on GitHub ↗
--- name: cs-escalation-brief description: "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." --- # 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 escalation, legal, or press | CCO / Legal / Comms | Immediate | ## Output Format --- # Escalation Brief: [Account Name] **Escalation level:** L[1/2/3/4] — [Label] **Date raised:** [Date] **Raised by:** [CSM name] **Escalation owner:** [Name of exec or senior stakeholder now leading response] --- ## Account at a Glance | Field | Detail | |---|---| | ARR | £/$/€[X] | | Tier | Enterprise / Mid-Market / SMB | | Customer since | [Date] | | Renewal date | [Date] — [N] days away | | Renewal risk (pre-escalation) | Green / Amber / Red | | Renewal risk (current) | Green / Amber / Red | | Customer contact who escalated | [Name, role, seniority] | | Executive sponsor (customer) | [Name, role — active / passive / vacant] | | Executive sponsor (vendor) | [Name, role] | --- ## What Happened — Summary [3–5 sentences. State the facts plainly. What the customer experienced, how they reacted, and how we learned about the escalation. No editorialising. No blame.] --- ## Timeline List in chronological order. Each entry: `[Date / time] — [What happened. Who did what.]` Include: - When the original issue or trigger event occurred - When the customer first raised concerns (informally) - When it escalated (formal escalation or exec involvement) - Actions taken since escalation --- ## Root Cause **Primary cause:** [One clear sentence. What specifically went wrong.] **Contributing factors:** - [Factor 1 — be honest about internal failures as well as external ones] - [Factor 2] **Is this a systemic issue or isolated?** [ ] Isolated to this account [ ] Pattern seen in other accounts — details: [_______] [ ] Product or process gap that needs fixing --- ## Customer's Stated Position **What the customer says happened:** [Their version of events — fair and unfiltered] **What they are asking for:** [Their explicit ask — compensation, fix by date, exec call, SLA credit, exit clause] **Sentiment of escalating contact:** [Frustrated but constructive / Angry / Seeking exit / Unknown] **Risk of public escalation:** Low / Medium / High — [evidence if Medium or High] --- ## Business Impact | Impact type | Detail | |---|---| | ARR at risk | £/$/€[X] | | Potential churn probability | [X]% | | Reputational risk | Low / Medium / High | | Reference / case study status | [Was a reference — now at risk / Not a reference] | | Expansion pipeline at risk | £/$/€[X] | --- ## What Has Been Done So Far 1. [Action taken — by whom — date — outcome] 2. [Action taken — by whom — date — outcome] 3. [Action taken — by whom — date — outcome] **Has a formal apology or acknowledgement been issued?** Yes / No --- ## Proposed Resolution Plan **Immediate actions (next 24–48 hours):** | Action | Owner | By when | |---|---|---| | [Action] | [Name] | [Date] | | [Action] | [Name] | [Date] | **Medium-term actions (next 2–4 weeks):** | Action | Owner | By when | |---|---|---| | [Action] | [Name] | [Date] | **What we are NOT offering:** [Be explicit about what is not on the table — avoids misaligned expectations] **Success criteria:** [How will we know the escalation is resolved? What does the customer need to confirm they are satisfied?] --- ## Decision Required from Escalation Owner [State clearly what decision or resource the escalation owner needs to provide. Be specific — do not make them ask. E.g.: "We need approval to offer a 20% service credit for Q2" or "We need an exec call with [name] within 48 hours."] --- ## Communication Plan | Audience | Message | Channel | Owner | By when | |---|---|---|---|---| | Escalating customer contact | [Summary of message] | Email / Call | [Name] | [Date] | | Customer exec sponsor | [Summary] | Call | [Name] | [Date] | | Internal CS team | [Summary] | Slack / Meeting | CS Manager | [Date] | --- ## Quality Checks - [ ] Root cause is specific — not "communication breakdown" or "product gap" without detail - [ ] Customer's position is stated fairly — not minimised or dismissed - [ ] A clear decision is requested from the escalation owner — brief does not end with "what do you think?" - [ ] ARR at risk is quantified - [ ] Communication plan has owners and dates — not "TBD" - [ ] Language is professional and blameless toward individuals
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.