Business Domain Connect
Crack the Delivery Interview · Episode 8 · DM #06

How do you handle a client escalation?

Your phone rings. It’s your CEO. The client has just escalated to them, about your account. What do you do in the first hour?

Delivery Manager interviewFree

Watch Episode 8

What the interviewer is really testing

  • Composure. When the pressure is on and senior people are watching, do you stay calm and think clearly?
  • Ownership. Do you take responsibility, or do you start explaining whose fault it was?
  • Root-cause thinking. Do you just put out this fire, or do you fix whatever keeps starting fires?

The weak answer vs the strong answer

Here's the weak answer: "I explain to the client why it wasn't our fault."

Even if you're right, the client hears one thing: you're not listening. And the escalation goes one level higher.

The strong answer shows you can calm the situation, take ownership, and make sure it doesn't happen again: respond within hours, bring the facts and a plan with dates, and stop the next escalation before it starts.

The 5-step answer

Here's how I handle a client escalation, step by step.

  1. Acknowledge fast. I call the client within hours, even before I have all the answers. Something like: "I've seen this, I'm personally on it, and you'll have an update from me by end of day." Silence is what turns an escalation into a crisis.
  2. Listen, don't defend. I ask what this is costing their business. Is it members, money, a regulator, or their own boss? Until you understand who is impacted and how, you can't fix the right thing.
  3. Get the facts and own it. With the team, I establish what happened, why it happened, and what we'll do. If we got something wrong, I say so plainly. Ownership calms people down faster than any explanation.
  4. Share an action plan with dates. Short-term fixes and long-term fixes, each with an owner and a date. Then I close the loop: I tell the client as each action is done, without waiting to be asked.
  5. Fix the pattern. One escalation can be bad luck. Repeated escalations usually mean the client doesn't have visibility. So I fix that: a regular status update, a simple dashboard of actions, owners and dates, and a single point of contact.
Say it like this

“An escalation is a request for visibility. Give it before they ask.”

A real example

Here's a real example. I'll keep the client anonymous.

On a US healthcare payer account, a claims processing batch was delayed two days in a row. The client's VP of operations escalated directly to our leadership.

I called the client within two hours. I didn't defend. I listened, and learned the delay was holding up provider payments. By end of day we had the root cause, a failed data load that nobody was alerted to, and I shared a recovery plan with dates. And I owned it.

Then we fixed the pattern. The client had heard about the problem from their own team, not from us. So we set up a daily batch-status email after every run, a simple dashboard, and one named contact for any issue.

The result: the backlog was cleared in three days, the escalation was closed within a week, and there were no repeat escalations for the rest of the year.

And the client's feedback changed. They told us they now heard about problems from us first. That's the real fix.

Follow-up questions to expect

What if the escalation is unfair?

I acknowledge it first, then address the facts calmly, with data in hand. But I still ask the client what we could have done better in communication, because they felt strongly enough to escalate.

How do you stop repeat escalations?

A proactive weekly status, a clear owner for every issue, and a fixed meeting cadence set by severity, so the client never has to chase us.

All 40 questions, answered: the Interview Kit

Delivery, Project, Program and QA Manager questions, 10 of each, with the weak answer, the strong answer, the line to say and the follow-ups. A 24-page PDF for ₹999, or $15 outside India.