A complaint and a request are handled by different machinery

Two things that arrive in the same sentence

Most conversations at a counter contain both. The bill is wrong and it took four calls to get anybody to look at it. The application was refused and nobody explained why. In ordinary speech these are one grievance with two halves, and it would be strange to separate them. Inside the organisation they are two entirely different objects, opened on different systems and closed by different people.

This is not a filing quirk. The two are answering different questions, are measured against different targets, and have different definitions of a satisfactory ending. Anybody who has watched a straightforward correction disappear for six weeks has generally watched it get attached to the wrong one of the two.

A request asks for an action; a complaint asks for a judgement

A request — including one that begins as a disagreement — is a call for something to be done: a figure corrected, a decision looked at again, a service delivered that was not. It is satisfied when the thing is done, and the person handling it needs the case, the rules and the permission to act.

A complaint asks something else. It asks the organisation to form a view about its own conduct and to say what that view is. Even where a complaint also produces a correction, the correction is not the answer to it; the answer is an account of what happened and whether it should have. Those need different work, and they very often need a different person, since somebody investigating a piece of handling should not be the person who handled it.

They are counted separately, and counting shapes handling

Complaints are recorded, categorised and reported upwards in a way that ordinary work is not. That reporting is genuinely useful — it is one of the few mechanisms by which a repeated failure at the front of an organisation becomes visible at the back of it — and it is also the reason the process around a complaint is heavier than the underlying matter usually warrants.

A consequence people find counter-intuitive is that staff will sometimes try quite hard to resolve something before it is logged as a complaint. Read cynically, that is target management. Read plainly, it is usually somebody offering to fix the thing today rather than open a case that takes a fortnight to produce a letter. Both readings occur in real life, and the useful question is simply whether the immediate fix actually resolves the matter.

The timetable belongs to the complaint, not to the underlying matter

Complaint processes carry timescales: an acknowledgement within so many days, a substantive response within so many weeks, a defined route if the response does not settle it. These are what people are reaching for when they say they want something in writing, and they are a real advantage where the handling itself is the issue.

But the timetable applies to the complaint, and not to whatever prompted it. A billing error that could be corrected in a day, once folded into a complaint, is quite likely to be answered within the complaint’s timescale rather than within the correction’s. That is the mechanism by which a formal route can slow down an outcome you actually wanted quickly.

Why the pair sent together tends to stall

When both arrive in one message, somebody has to decide which machine it belongs to, and the choice is rarely obvious. Sent to the operational team, the objection to handling gets a courteous acknowledgement and no investigation. Sent to complaint handling, the correction waits behind an investigation it did not need.

The way out is unglamorous and effective: say plainly that there are two things, name the outcome you want from each, and let them travel separately. Correct the account, and separately I would like the organisation to look at why it took four calls. Most services can run both at once perfectly well. What they cannot do is guess which one is the priority when both are described in one paragraph.

Saying which one you are making

It is worth being explicit even when it feels overly formal, because the words trigger the routing. A sentence saying that you are not making a complaint but do need a correction spares everybody a fortnight. A sentence saying that you are making a complaint and want it logged as one does the opposite, and does it deliberately.

Neither is the strong move in every situation. Where the outcome is what matters, the request is faster. Where the pattern is what matters — where the same thing keeps happening, or where the handling is the substance of the problem — the complaint is the only one of the two that leaves a mark anybody else in the organisation will ever see. Choosing between them is the decision. Making both at once, in one sentence, is the thing that reliably costs time.