Handle a customer on fire with a runbook, not a scramble.
“Our biggest customer just emailed the CEO, and nobody knows who owns this. What do we do first?”
Triage severity, name owners and comms cadence, draft the customer message, and set the post-mortem.
What this skill does
Takes a live customer escalation and turns panic into a sequence. It grades how bad this actually is, assigns the internal owners, sets how often everyone hears an update, drafts the message the customer receives, and schedules the post-mortem that prevents the same fire twice. A calm customer is not a lucky customer. It is a managed one.
Inputs
- Works today with: what is happening, in your words. What broke, since when, who is affected, what the customer has said, and how big the account is. Paste the thread or describe it.
- More powerful connected to a CRM: pulls the account value, the renewal date, and the owner, so the severity reflects the stakes.
- Sharper with a meeting or email tool: reads what was already promised and when the customer last heard from you.
- Sharper with a support or product tool: adds the ticket history and whether this issue is a repeat.
How it works
- 1Severity triage
Grade the escalation on two axes: how much is broken and how many it hits. A full outage on a top account is not the same as a cosmetic bug for one user. Assign a severity and state the reason in one line. The severity sets the cadence and the owners. Everything downstream follows from this call.
- 2Owners and RACI
Name the people, not the departments. Who drives the fix, who talks to the customer, who decides, who just needs to know. One accountable owner per escalation. A fire with two owners has none.
- 3Comms cadence
Set the heartbeat. How often the customer hears from you and how often the internal room syncs, both keyed to severity. Silence is what turns a bug into a churn risk. An update that says "still working it, next update at 3pm" beats a fix delivered in silence.
- 4Customer-facing message
Draft what the customer actually reads. Acknowledge, own it without over-promising, state what you know, state the next update time. No blame, no jargon, no false certainty. Give them the next checkpoint, not a guess at the finish.
- 5Post-mortem that prevents a repeat
Schedule the review before the fire is even out. Capture the root cause, the timeline, what the customer experienced, and the one change that stops a recurrence. An escalation you do not learn from is one you have agreed to have again.
Output format
ESCALATION RUNBOOK
Severity: SEV1 (core workflow down, top-20 account, renewal in 60 days)
Owners
Drive fix: Eng on-call
Customer comms: the CSM
Decision: Support lead
Informed: Exec sponsor
Cadence: customer update every hour, internal sync every 30 min
Customer message (draft):
"We are aware the X workflow is failing for your team and we have
engineers on it now. This is our top priority. Next update by 2:00pm
your time, whether or not it is resolved by then."
Post-mortem: scheduled within 5 business days. Owner: the CSM.
Prevent-a-repeat: add a monitor on the workflow that failed silently.
(Details are illustrative.)
Tips
- No severity grade without the one-line reason behind it.
- Exactly one accountable owner. Named, not a team.
- The customer message states a specific next-update time, never "soon."
- Every resolved escalation has a scheduled post-mortem before it closes.
- No blame language in anything the customer sees.
Turn account data into a QBR that earns the renewal.
Value delivered, adoption vs stated goals, risks named first, the roadmap, and one outcome-tied expansion ask.
Build the plan that predicts the renewal a year out.
Translates the customer's goals into measurable outcomes, time-to-value milestones, and the leading indicators that flag risk early.