Customer Escalation
Turn a messy support ticket into a structured escalation brief engineering or leadership can act on without losing customer context.
Overview
Customer-escalation is an agent skill most often used in Grow (also Operate, Ship) that packages support incidents into structured escalation briefs for engineering, product, or leadership.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill customer-escalationWhat is this skill?
- Structures reproduction steps, customer impact, and timeline into one escalation brief
- Routes issues to engineering, product, or leadership based on severity and pattern
- Covers multi-customer repeats, SLA breaches, and churn-threat scenarios from the description triggers
- Parses what's broken, who's affected, duration, and prior troubleshooting in step 1 (Understand the Issue)
- Slash command workflow: `/customer-escalation <issue> [customer or account]`
Adoption & trust: 1.4k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know a customer issue is serious but your agent or cofounder keeps pasting fragmented ticket notes that engineering cannot reproduce or prioritize.
Who is it for?
Indie SaaS founders handling Enterprise tickets, SLA-driven support, or repeat outages that need a clean eng handoff.
Skip if: Purely internal refactor requests with no customer impact, or cases where a Jira bug is already fully specified and assigned.
When should I use this skill?
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.
What do I get? / Deliverables
You get a single structured escalation brief with impact, repro context, and the right internal audience—ready to file or forward without another support interview.
- Structured escalation brief
- Reproduction steps and business impact assessment
- Escalation target recommendation (engineering, product, or leadership)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf on Grow → Support because the skill packages customer-facing incidents for handoff when normal support is insufficient. Support is where SLAs, churn risk, and repeat reports are triaged before routing to eng or product.
Where it fits
Three accounts report missing export rows in one week—you need one brief for eng with shared repro.
Intermittent 500s in production—you document scope and customer impact before paging on-call.
Launch-week SSO loop hits all Enterprise tenants—you escalate to product with segment-wide impact.
A flagship customer threatens churn over audit logs—you frame business impact for leadership.
How it compares
Use instead of dumping raw chat logs into #engineering when you need a deliberate escalation narrative.
Common Questions / FAQ
Who is customer-escalation for?
Solo builders and small teams who own support and must escalate bugs, product gaps, or churn-risk situations to engineering or leadership with full context.
When should I use customer-escalation?
Use it in Grow → Support when a bug needs engineering beyond normal support, multiple customers report the same issue, someone threatens to churn, or an issue missed its SLA; in Operate when production defects drive support volume; in Ship when launch-week incidents need a leader
Is customer-escalation safe to install?
Review the Security Audits panel on this Prism page and only enable connector integrations you trust, since escalations may summarize customer and account details.
SKILL.md
READMESKILL.md - Customer Escalation
# /customer-escalation > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Package a support issue into a structured escalation brief for engineering, product, or leadership. Gathers context, structures reproduction steps, assesses business impact, and identifies the right escalation target. ## Usage ``` /customer-escalation <issue description> [customer name or account] ``` Examples: - `/customer-escalation API returning 500 errors intermittently for Acme Corp` - `/customer-escalation Data export is missing rows — 3 customers reported this week` - `/customer-escalation SSO login loop affecting all Enterprise customers` - `/customer-escalation Customer threatening to churn over missing audit log feature` ## Workflow ### 1. Understand the Issue Parse the input and determine: - **What's broken or needed**: The core technical or product issue - **Who's affected**: Specific customer(s), segment, or all users - **How long**: When did this start? How long has the customer been waiting? - **What's been tried**: Any troubleshooting or workarounds attempted - **Why escalate now**: What makes this need attention beyond normal support Use the "When to Escalate vs. Handle in Support" criteria below to confirm this warrants escalation. ### 2. Gather Context Pull together relevant information from available sources: - **~~support platform**: Related tickets, timeline of communications, previous troubleshooting - **~~CRM** (if connected): Account details, key contacts, previous escalations - **~~chat**: Internal discussions about this issue, similar reports from other customers - **~~project tracker** (if connected): Related bug reports or feature requests, engineering status - **~~knowledge base**: Known issues or workarounds, relevant documentation ### 3. Assess Business Impact Using the impact dimensions below, quantify: - **Breadth**: How many customers/users affected? Growing? - **Depth**: Blocked vs. inconvenienced? - **Duration**: How long has this been going on? - **Revenue**: ARR at risk? Pending deals affected? - **Time pressure**: Hard deadline? ### 4. Determine Escalation Target Using the escalation tiers below, identify the right target: L2 Support, Engineering, Product, Security, or Leadership. ### 5. Structure Reproduction Steps (for bugs) If the issue is a bug, follow the reproduction step best practices below to document clear repro steps with environment details and evidence. ### 6. Generate Escalation Brief ``` ## ESCALATION: [One-line summary] **Severity:** [Critical / High / Medium] **Target team:** [Engineering / Product / Security / Leadership] **Reported by:** [Your name/team] **Date:** [Today's date] ### Impact - **Customers affected:** [Who and how many] - **Workflow impact:** [What they can't do] - **Revenue at risk:** [If applicable] - **Time in queue:** [How long this has been an issue] ### Issue Description [Clear, concise description of the problem — 3-5 sentences] ### What's Been Tried 1. [Troubleshooting step and result] 2. [Troubleshooting step and result] 3. [Troubleshooting step and result] ### Reproduction Steps [If applicable — follow the format below] 1. [Step] 2. [Step] 3. [Step] Expected: [X] Actual: [Y] Environment: [Details] ### Customer Communication - **Last update to customer:** [Date and what was communicated] - **Customer expectation:** [What they're expecting and by when] - **Escalation risk:** [Will they escalate further if not resolved by X?] ### What's Needed - [Specific ask — "investigate root cause", "prioritize fix", "make prod