The first hour
Escalations are rarely about the original fault. They are about what the customer concluded from how the first hour went.
The rule this article follows
Acknowledge before you understand. A customer who hears "we have seen this, Priya owns it, she will update you by 4pm" within the hour is a customer waiting. One who hears nothing for a day is a customer escalating.
Four things, in order:
Acknowledge, fast. Even with nothing useful to say. Confirm you have seen it, that it is being looked at, and when you will next make contact.
Assign one named owner. Not a team, not an inbox. A person whose name the customer knows, who owns communication and the timeline whether or not they own the technical fix.
Establish what actually happened. Separately from what the customer believes happened, which may be an accurate report or a reasonable misinterpretation. Both matter, and confusing them sends you fixing the wrong thing.
Assess the real impact. Whether work has stopped, whether their customers are affected, whether there is a deadline in play. Impact rather than fault decides urgency.
Structuring the response
Separate the stop-the-bleeding fix from the real cause
The immediate priority is getting the customer working again, which is often a workaround rather than a solution.
Do not let the root-cause investigation delay the workaround. They run in parallel and confusing them keeps customers broken while you are being thorough.
Parallel, not sequentialGive a timeline you can meet, not one they want
An optimistic estimate you miss does more damage than a conservative one you beat. Under-promise deliberately.
If you genuinely do not know, say so and commit to an update time instead of a fix time. A committed update time is something you can always keep.
Commit to updates, not fixesKeep the customer informed on your schedule, not theirs
If they are chasing you for updates, you have already lost control of the escalation. Get ahead of it with a fixed cadence.
Daily for a serious issue, more often if work is stopped. Send the update even when it says nothing has changed.
Never let them chaseBring in someone senior once, early
A short message from a founder or a lead, acknowledging the problem and confirming who owns it. Two sentences.
Disproportionately effective, and only works if it is early. Senior involvement that appears after a week reads as damage control rather than care.
Two sentences, earlyConfirm resolution with the customer, not with yourself
"We believe this is fixed, can you confirm it is working for you?" Do not close an escalation because your side looks healthy.
Closing something the customer still considers open is one of the fastest ways to turn a resolved issue into a lost account.
They close it, not you
What to say while it is unresolved
The hardest messages are the ones with no news. Three rules make them work.
Say what is actually happening. "Two people are working on it, we have ruled out the integration, we are now looking at the import" tells them progress is real. "We are looking into it" for the third day tells them nothing and reads as a holding pattern.
Never speculate about blame in writing. Especially about a third party. It ages badly and it frequently turns out to be wrong.
Keep every commitment, including small ones. If you said you would update at 4pm, update at 4pm even to say there is nothing new. Missing a small commitment during an escalation confirms the fear that caused the escalation.
After it is fixed
The escalation is not over when the problem is. Two things remain.
Tell them what happened and what changes. A short written summary: what went wrong, why, what you did, what you are changing so it does not recur. Customers who receive this are measurably more forgiving than customers who receive silence after a fix.
Decide about compensation separately, afterwards. If it was serious, offer something without being asked. Doing it after resolution reads as accountability; doing it during reads as purchase.
Then look at the account honestly. A serious escalation shifts a customer's risk profile, and it is worth a deliberate check-in a month later rather than assuming the relationship reset.
Preventing the next one
Log every escalation with a cause from a fixed list. Free text cannot be counted, which is the same principle that governs loss reasons in win/loss analysis. After a dozen entries the pattern is usually obvious and usually not what people assumed.
Look for the process, not the person. Most escalations trace to a handover where context was lost, an expectation set during the sale, or a step that only one person knew how to do. Our guides to documenting a process and the sales to delivery handoff cover the two most common of those.
Fix one cause per quarter. Not all of them. The same discipline that makes retrospectives work applies here: one completed change beats five identified ones.
Write down the playbook itself. Who acknowledges, who owns, what the update cadence is, when someone senior gets involved. During an escalation nobody has time to invent a process, and a one-page document is the difference between a coordinated response and three people messaging the customer separately.
Frequently asked questions
- How quickly should you respond to an escalation?
- Acknowledge within an hour during working hours, even if you have nothing to report. The acknowledgement is not the fix, it is the thing that stops the customer escalating further because they think nobody is listening.
- Who should own an escalation?
- One named person, and never a team inbox. The owner does not have to be the person who fixes it, but they own the customer communication and the timeline. Shared ownership is how customers end up chasing three people.
- Should a founder get involved in escalations?
- For significant accounts, once, early, and briefly. A short message from someone senior acknowledging the problem is disproportionately effective. Taking over the day-to-day handling is usually counterproductive.
- What do you say when you have no update?
- That you have no update, what is being worked on, and when you will next make contact. Silence is what turns a problem into a relationship issue, and customers judge you far more on the communication than on the elapsed time.
- Should you offer compensation?
- Sometimes, and after the fix rather than during. Offering money during an escalation reads as buying silence. Offering it afterwards, unprompted, reads as taking responsibility.