The complaint nobody answered

Here is how a janitorial company loses a ten-site account.

On a Friday in March, a facilities manager emails: the third floor bins weren't done again. It lands in a shared inbox at 6pm. Somebody sees it on Monday, means to reply, and doesn't. In May she mentions it once more, in a sentence at the end of an email mostly about parking. In August the contract goes out to tender, and the first anyone in the office hears about a problem is a polite note saying they've decided to go another way.

Nobody ignored her. That is the part worth sitting with. Every person in that company would have fixed the bins in an afternoon if they had known it mattered. The email went to an inbox, and inboxes are where accountability goes to die.

Why complaints are different from every other message

A complaint has a property no other email has: the client is already unhappy, and is measuring you on what happens next.

That means the clock starts the moment they hit send, and it is running against a number they have in their head and you do not. Every hour that passes is evidence for a conclusion they are already half-forming — that this company does not really care about our building.

An inbox cannot help you with that, because an inbox has no state. It cannot tell you what is unanswered. It cannot tell you what has been sitting longest. It cannot tell you that the same complaint has now come in twice. It is a pile in reverse chronological order, and the oldest, most dangerous item in it is always at the bottom.

Acknowledgement is not resolution, and it is the one that matters

The instinct is to promise to fix things quickly. That is the wrong promise, because it is one you frequently cannot keep — some fixes genuinely wait for the next visit — and because it is not the one the client actually wants.

Consider two versions of the same bins complaint.

Version one. Reply within the hour: Thanks — I've got this. The crew is there Tuesday and I've asked the supervisor to check the third floor personally and report back. Fixed on Tuesday, three days later.

Version two. No reply. Fixed on Tuesday, three days later.

Identical outcome. Completely different relationship. In the first the client learns their problem reaches a person who takes it seriously; in the second they learn nothing and assume the worst, and they are right to, because silence is the only evidence they were given.

So the number to promise, publish and measure yourself on is time to acknowledge. It is the one that is always in your control, and it is the one that carries the meaning.

What a log does that an inbox cannot

Give the client somewhere to raise it that is not email, and give it three properties:

It has state. Open, acknowledged, resolved. Which means it can be sorted by "unanswered, oldest first" — the exact opposite of an inbox, and the ordering that makes it impossible to accidentally leave something for three days.

It records when you answered, not just that you did. The gap between raised and acknowledged is a number, and a number you can show. Acknowledged in 2 hours is a sentence a facilities manager will renew on.

The client can see it. This is the part that feels risky and is not. A client looking at a log of five things they raised — all acknowledged the same day, four resolved, one in progress with a note — is a client who has just been shown, in their own words, that this company is on top of their building. You will never make that argument as well as their own complaint history makes it for you.

Two details that decide whether it works

Only the client creates entries. The moment your office can file a request on a client's behalf, your response-time figures are decoration. Somebody means well, back-dates a complaint they handled on the phone, and the number stops describing anything. Let the office acknowledge and resolve. That is the whole job.

Freeze the promise at the time it was made. If you say two hours today and change it to twenty-four next year, last year's answers should not retroactively become excellent. Whatever target was in force when the client raised the issue is the one that entry is judged against, permanently.

The unglamorous truth

There is no clever feature here. The whole mechanism is: a place to put it, a state so it cannot be lost, a timestamp so the answer is measurable, and visibility so the client can see the pattern.

What it buys is the difference between a client who thinks they always sort it out and one who thinks nothing ever happens — about a company that, in both cases, fixed the bins on Tuesday.