escalation-brief-skill

Generates structured customer escalation briefs with quantified business impact for engineering and leadership.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/innFactory-AI/company-ai-stack-skills --skill escalation-brief-skill-innfactory-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: escalation-brief-skill
Source: https://github.com/innFactory-AI/company-ai-stack-skills/tree/main/de/skills/customer-success/escalation-brief-skill
Command: npx skills add https://github.com/innFactory-AI/company-ai-stack-skills --skill escalation-brief-skill-innfactory-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customer issues that need engineering or leadership attention often arrive as unstructured, emotional messages that get deprioritized. This Skill turns a customer problem into a structured escalation brief with severity classification, quantified business impact, and a concrete requested action. ## Core Features & Use Cases - Severity Assessment: Classifies issues on two dimensions — customer impact and business risk — using defined Critical/High/Medium/Low matrices. - Business Impact Quantification: Translates the problem into ARR at risk, affected users, renewal proximity, strategic value, and contractual exposure using CRM and support data. - Structured Brief Template: Produces a complete escalation brief covering account context, timeline, resolution attempts, customer expectations, requested action, and internal routing. - Use Case: A CSM has a strategic account threatening non-renewal over an unresolved integration outage. The Skill pulls ticket history from the support platform and account value from the CRM, then produces a Critical-severity brief routed to the engineering lead and executive sponsor. ## Quick Start Prepare this escalation for engineering: our enterprise account has a platform outage blocking 40 users, renewal is in 60 days, and two fix attempts have failed.

Frequently Asked Questions about escalation-brief-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a customer escalation brief for engineering?▼

Structure the brief with account context (ARR, renewal date), a problem summary, quantified customer impact, business risk, a timeline of events, resolution attempts, and one concrete requested action. This Skill generates that structure automatically from your support and CRM data.

How do I quantify business impact in a customer escalation?▼

Quantify impact using ARR of affected accounts, number of affected users multiplied by frequency, renewal proximity, strategic account value, and contractual SLA exposure. Pull actual figures from CRM and support data rather than estimating from memory.

What data sources does the escalation brief skill use?▼

It pulls ticket history and resolution attempts from support platforms like Zendesk or Intercom via MCP, account value and renewal dates from CRMs like HubSpot or Salesforce, and internal notes from companyRAG collections or uploaded files.

Can I use the escalation brief skill without a connected CRM?▼

Yes. If no MCP source is connected, provide the data directly in chat or upload relevant files, and the Skill works the same way. Missing values are marked as unknown rather than invented.

When should I not escalate a customer issue?▼

Avoid escalating low-severity issues where a workaround exists and the relationship is stable, as over-escalation undermines credibility for future cases. Use the severity matrix honestly and route low-impact issues through standard support queues.