Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cbrock84/escalation-management
Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.
Passed 22 of 23 test cases with the skill, and 19 of 23 without it.
and 2 more in the full report
3 fixed19 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Following the resolution of a Sev-1 escalation for FinServe Corp, the team is conducting an internal post-incident review. Beyond technical bug analysis, what fundamental question must be evaluated regarding support process health?
| Checked | Without skill | With skill |
|---|---|---|
| Requires analyzing what caused the normal path to fail. | Missed | Passed |
The instructions your model reads when the skill loads.
An escalation is a signal that the normal path failed. Handling it well matters; the more useful question afterward is why it was needed.
Severity is what it costs them, not how alarming it looks internally. A cosmetic bug blocking a regulated filing is severe. A total outage of a feature nobody uses is not.
Ask: what can they not do, how many people, is there a workaround, and is there a deadline attached. That last one converts a medium into a critical more often than anything technical.
Own it visibly. One named person, introduced to the customer, who does not disappear. Escalations get worse when ownership is ambiguous — the customer starts re-explaining, which is its own insult.
Communicate on a stated cadence, and hold it even when there is nothing new. "No update yet, next update at three" preserves trust; silence destroys it faster than bad news does. Customers escalate again because they heard nothing, far more often than because of the underlying issue.
Separate acknowledgment from explanation. Acknowledge the impact immediately, in their terms. Explanation comes when you actually know. Leading with a cause you have not confirmed means retracting it later, and the retraction is what they remember.
Do not over-promise to end the conversation. Every commitment made under pressure to a frustrated customer is a commitment someone has to keep, and failing a recovery promise ends the relationship.
When a customer reaches your leadership, the relationship is already damaged — the escalation is the symptom.
Brief the executive properly before the call: what happened, what we have done, what we are committing to, and what not to promise. An executive walking in uninformed makes commitments the delivering team learns about afterward.
test cases passed, vs 19 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.