Handling a client complaint without losing the contract

Almost every cleaning contract, run for long enough, generates a complaint at some point — a missed area, a recurring issue that finally gets escalated, a new facilities contact who holds the previous team's standard against the current one. On its own, a single complaint rarely ends a contract. How it's handled in the immediate aftermath has a lot more influence over the relationship than the complaint itself.

The instinct to defend, and why it backfires

A common first reaction, understandably, is to explain the context — staff shortage that day, a one-off, something outside the contractor's control. Even when that context is genuinely true, leading with it tends to read to the client as deflection rather than accountability, and it delays the part of the response that actually matters to them: what's being done about it, specifically and now.

A response that actually reassures

A complaint response that lands well tends to follow a simple order: acknowledge the specific issue without minimising it, explain what's being done immediately to fix it, and set out what changes to stop it recurring. Context and explanation can come later, once the client has seen the practical response — not instead of it.

• –Acknowledge the specific complaint plainly before offering any context or explanation
• –Set out the immediate fix first, then the longer-term change that prevents recurrence
• –Respond quickly — a fast, partial answer generally reassures more than a slower, fully complete one
• –Follow up once the fix is in place, rather than assuming silence means the client is satisfied
• –Log the complaint and its resolution the same way an audit finding gets logged and closed, so there's a record if the pattern recurs

When a complaint is part of a pattern

A single complaint and a recurring one call for different responses. If the same issue keeps surfacing, the conversation needs to move beyond an individual fix to what's actually causing it — a staffing gap, a specification that's drifted from what's realistically deliverable, a supervisor visiting less often than the contract assumes. That's usually a conversation for a scheduled review rather than something to resolve entirely in a reactive complaint response, similar to how a genuinely poor audit result needs a structural response rather than just a quick fix.

The client relationship, not just the ticket

It's worth remembering that most facilities contacts handling a complaint aren't trying to catch the contractor out — they're trying to solve a problem for their own building, often under pressure from their own management. A contractor who treats the complaint as a shared problem to solve, rather than an accusation to manage, tends to come out of the exchange with the relationship intact and often, over time, strengthened.

What the client is actually asking

A complaint about a missed bin is very rarely about the bin. The client is asking a larger question — whether this will keep happening, and whether they will have to keep noticing it themselves. A response that fixes the bin answers the small question and leaves the large one open, which is why technically correct responses so often fail to settle anything.

The answer that lands addresses both: the immediate fix, and what changed so it does not recur. That second part is what distinguishes a contractor who is managing the account from one who is processing tickets.

Common mistakes

• –Leading with an explanation of why it happened, which reads as a defence
• –Closing the ticket when the task is redone rather than when the cause is addressed
• –Handling each complaint in isolation and never checking for a pattern
• –Letting the site team resolve it without the account manager knowing it occurred
• –Offering a credit as a substitute for a fix
• –Never telling the client what changed, so the reassurance never arrives