The person closest to the problem and the fix should own the decisions during a customer escalation, inside limits agreed before the escalation started. Senior leaders set the outcome and the level of risk they will accept. The escalation owner makes the calls inside those limits.
When ownership is settled during the crisis instead of before it, it defaults to the most senior person on the call, and the response slows down to brief them.
Ownership by type of decision
A single owner for the whole escalation is too blunt. Different decisions belong to different people, and the split works best when it is written down in advance. A typical split looks like this:
| Decision | Who owns it |
|---|---|
| The technical path to resolution | The incident commander or technical lead running the response |
| What the customer hears, and when | One named owner of customer communication, on a fixed schedule |
| Commercial concessions such as credits | The account owner, up to a limit set in advance |
| Changing the goal or the risk you will accept | The executive sponsor |
| Bringing in more senior leaders | The escalation owner, against the written entry rule |
Your table will differ. What matters is that every row has one name and a limit, and that the people named have seen it before the next escalation.
Why rank should not take command
Emergency response settled this decades ago. The Federal Emergency Management Agency (FEMA) teaches two rules inside the Incident Command System. Unity of command: every individual has one designated supervisor. And a transfer of command begins with a briefing. Command can move. It moves explicitly and on the record. It does not move because someone with a bigger title joined the call.
Google's guidance for managing incidents makes the same point for technology teams: everyone involved should know their role and not stray onto someone else's turf.
So when a leader more senior than the executive sponsor joins a live escalation, they set the outcome and the risk appetite. The commander keeps command of the response. Rank gives the right to change the objective. It does not make anyone fluent in the last six hours, and fluency is what command requires.
Written limits beat case-by-case approval
Economists tested this in a randomized experiment with 600 public procurement officers, published in the Quarterly Journal of Economics in 2021. One group needed approval for every purchase. The other got a written limit they could act within on their own. The officers working to a written limit paid 9 percent less for the same items, and the gain showed up where the approver had been the one holding things up.
A limit agreed in a calm week beat judgment applied under pressure.
We inspect the system before we blame the person.
Sources: FEMA, Incident Command System 200, Lesson 2. Google SRE, "Managing Incidents," sre.google/sre-book/managing-incidents. Oriana Bandiera, Michael Best, Adnan Khan and Andrea Prat, "The Allocation of Authority in Organizations: A Field Experiment with Bureaucrats," Quarterly Journal of Economics 136(4), 2021.