All Fixes Damage Control
A Client Is Unhappy And It's Not Entirely Your Fault — AwkwardFix Guide 016
GUIDE 016

When A Client Is Upset, But It's Not Entirely Your Fault

The exact response for six versions of shared-fault client blowups -- without over-apologizing or throwing anyone under the bus.

Ready before today's conversation 6 exact responses 36 pushback branches Includes follow-up plan Instant access

You read the email twice before you even process what it's actually asking.

Somewhere between the first line and the last, you already know they're blaming you for something that wasn't only yours -- and you're not sure yet whether to apologize for all of it or push back on any of it.

The honest answer is neither. You can own your part completely and still refuse to own the rest -- in the same message, without sounding defensive.

Here's the part most people don't realize: a blanket apology feels safer in the moment, but it quietly rewrites what actually happened into a version where you're fully at fault -- and you're the one who'll have to live with that version later.

But 'they sat on their approval' and 'a vendor's outage caused this' and 'we each understood the brief differently' all need a completely different opening line -- so winging it means guessing which of six situations you're actually in, and hoping the right balance of ownership and honesty shows up in the moment. This gives you the version that's actually happening, and the exact words that hold both truths at once.

Step 1 — Here's What You Get

6 ready-to-use responses for the 6 ways a client blames you for something that wasn't only yours.

This isn't one apology, it's six. A slipped deadline caused by their own approvals needs a different opening line than a vendor outage you had no control over. Each response already includes the likely pushbacks worked out.

Most people say
So sorry about this, we'll get it sorted as soon as we can.
This fix gives you
The Vendor Outage Response
Word for word: 'You didn't sign up to work with our vendor, you signed up to work with us -- so I'm not going to hand you a link to their outage page and call it done.' Then the exact plan you give them next.
Page 18

That's one of the six responses inside. Because the first sentence is rarely the hard part.

Actual page. no crop. no blur.
Actual interior page from A Client Is Unhappy And It's Not Entirely Your Fault -- The Vendor Outage Response, Page 18
Page 18 from the guide you'll download today.

Every response was rewritten until it sounded like something you'd actually send -- not something you'd reread three times and soften before pressing Send.

And here's what happens a page later, once they push back --
Them
You said this would be done Friday and it's Wednesday and it's still not here.
You
I want to get you a clear answer on the delay, not just an apology.
Them
We sent our feedback back right away, this delay isn't on us.
You
Let me pull up the exact timeline and confirm -- I want to make sure I've got this right before we go further.
This is where most people back down. The guide gives you the next line -- and 5 more branches if they keep pushing.

Which one sounds like your situation?

Inside this fix
The Delayed Approval Response
When the deadline slipped because they sat on approvals, not because of you.
The Teammate's Mistake Response
When someone else on your team caused the error, but you're the one they're blaming.
The Requested Change Response
When the scope change they asked for is the actual cause of the problem.
The Different Understanding Response
When you both did what you thought was agreed, and the result missed the mark.
The Vendor Outage Response
When a third-party tool or vendor failure caused the visible problem.
The Escalation Threat Response
When they're furious and threatening to leave over something manageable.

One PDF. Six situations. A Quick Deployment page if the email needs an answer in the next ten minutes. Open it on your phone and go.

BONUS
The After Plan — Covers the next 48 hours: writing down what was actually agreed, flagging the real cause to your team privately, and deciding in advance where your own line is before the next version of this happens. Following it turns one calm response into an actual fix instead of a moment of relief that fades the next time they email. Most guides give you the words for the moment. This one gives you what to do after.
Step 2 — Here's What It Does For You

You held the line without losing the client. Here's what that actually gets you.

Because you named what was actually true instead of absorbing blame or getting defensive, which is what most people do instead.

You don't rewrite what actually happened. The client's version of events includes the full picture, not a blanket apology you'll have to quietly walk back in three weeks.
You don't sound defensive or dismissive. The same message that names the shared cause also names your part clearly enough that nobody reads it as excuse-making.
You stop being the default explanation. Handling this once, clearly, means the next slipped deadline or vendor issue doesn't automatically land on your desk as your fault by default.
Step 3 — Here's What To Do Next

What happens if you just apologize and move on

Right now this is one calm, specific email. Let a blanket apology stand instead, and in three months you're the default explanation for anything that goes wrong on this account, whether you caused it or not -- a much bigger conversation, from a weaker position. $7 for the exact words to a conversation you're already having anyway, either clearly this week or defensively later. If today's the day you finally send the real version, that's cheaper than every future version of this that gets blamed on you by default.

This gets you the words that hold the line honestly -- it can't make a client who's decided to blame you regardless actually hear it; the guide covers that case too, so you're not stuck if they don't.

If this isn't quite your situation
AwkwardFix Guide 016
Stop rewriting what happened in your head. Send the real version.
Get the fix. Use it today.
$7
✓ One-time payment
✓ 26-page PDF, instant download
✓ Works on your phone, tablet, or desktop
✓ No subscription. Ever.
✓ Swap it if it's not right
🔒 Secure checkout via PayPal.
Instant access to your download.
The AwkwardFix Promise — Not the right fix for your situation? Email us at hello@awkwardfix.co and tell us what you're dealing with. We'll find the guide that fits and swap it out. No questions. We'd rather find you the right words than keep your money.

P.S. If you skipped to the bottom -- you've got an unhappy client and a version of events in your head that isn't quite the one you're about to send. Picture the moment right after you hit send on the honest version instead of the over-apology: the relief of not having anything to quietly walk back later. $7. Instant download. 6 responses, 36 pushback branches, and the After Plan for closing this out properly once the reply's sent. If it's not the right fit, we'll swap it.

Know Exactly What to Say Today →
≡ Browse all Damage Control fixes
Scroll to Top