Fluent Start speaking

Workplace situation · Clients and negotiation

Handling a client complaint

Calm an angry client without groveling, and turn a complaint into a plan.

Case study: Ramesh and the Monday outage

A retail client in Dallas lost four hours of online orders when a release from Ramesh's Hyderabad team broke the checkout page. Their Head of IT called, furious. Ramesh panicked and said, "Sorry, sorry, actually the issue was from the client side config also." The call got louder. His colleague Divya took the next call. She let the client finish, said, "You lost a morning of sales. That's serious and I'm sorry," then gave three things: the fix was live, a root cause report would arrive by Wednesday, and a rollback check was now in the pipeline. The client's tone dropped in two minutes.

Takeaway: Angry clients need to feel heard first, then see a specific plan with dates. Blame, even partly true, comes last or not at all.

We often apologize repeatedly or explain the technical cause too early, which sounds like an excuse. Global clients want one sincere apology, ownership, and a concrete next step with a date.

Calming the client (you are Vendor delivery lead)

Goal: Lower the temperature, own the problem, and end the call with a plan and dates the client accepts.

Step by step

  1. Listen fully. Let them vent without interrupting. Take notes.
  2. Acknowledge the impact. Name what it cost them in their words: sales, time, trust.
  3. Own it once. One clear apology. No 'but', no blame.
  4. Act with dates. What's fixed now, what happens next, and when they'll hear from you.
  5. Follow up in writing. Send a short summary the same day.

Say this, not that

I hear you. Please go ahead, I want to understand the full picture.Sir, please calm down.Telling someone to calm down makes them angrier.
You lost four hours of orders. That's a real hit to your business, and I'm sorry.Sorry, sorry, very sorry for the inconvenience.One specific apology beats five vague ones.
That's on us. Here's what we've done and what happens next.Actually the issue was from your side also.Even if it's partly true, blame now ends the conversation.
You'll have a root cause report from me by Wednesday, five p.m. your time.
I'll send a written summary of this call within the hour.

Model conversation

Mark
This is the second time this quarter. We lost a whole morning of orders. What is going on over there?
You
I hear you, Mark. Please tell me everything, I want the full picture.
Mark
Our checkout was down from eight to noon. My CEO is asking me why we're paying you.
You
Four hours of lost orders, and you're the one answering for it. That's serious, and I'm sorry. It's on us.
Mark
Okay. So what are you doing about it?
You
The fix has been live since twelve fifteen. By Wednesday you'll have a root cause report, and we've added an automatic rollback check to every release.
Mark
Fine. I need that report before my Thursday board meeting.
You
You'll have it Wednesday by five your time. I'll also send a summary of this call within the hour.

Rehearse this side out loud

Complaining as client (you are Client project owner)

Goal: Make the problem and its cost unmistakable, stay professional, and leave with committed fixes and dates.

Step by step

  1. State the facts. What happened, when, and how often. No adjectives needed.
  2. Name the impact. Money, time, users, or reputation lost.
  3. Say what you need. The specific outcome you expect, not just 'improve'.
  4. Set a deadline. Agree on a date and an owner before you hang up.

Say this, not that

I need to raise a serious issue about last week's delivery.We are very much disappointed with your people.Start with the issue, not the insult.
The build failed three times in two weeks, and each time we lost a day of testing.Facts and numbers are hard to argue with.
This isn't acceptable for us, and I need it to change.Kindly do the needful.Firm and plain beats polite and vague.
What I need is a stable build by Friday and a named person I can call.
Who owns this on your side, and when will I hear back?Please look into it.'Look into it' has no owner and no date.

Model conversation

You
Deepak, I need to raise a serious issue about the last two sprints.
Deepak
Of course. I'm listening.
You
The staging build broke three times in two weeks. Each time, my QA team lost a full day.
Deepak
I'm sorry about that. The team was dealing with some dependency changes.
You
I understand things happen, but this is costing us our release date. I need it to stop.
Deepak
That's fair. What would you like us to do?
You
A stable build by Friday, a short root cause note, and one person I can call when it breaks.
Deepak
Done. I'll be your contact, and you'll have the note by Thursday.

Rehearse this side out loud

Practice it out loud

Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.

Practice both sides

Related situations