The Complaint That Never Arrives

The restaurant manager asks whether everything was all right. The customer smiles, says yes and never returns.

On paper, the evening was a success. The bill was paid. Nobody demanded a refund. No complaint interrupted the next morning’s meeting. Only the customer knows that the relationship has ended, and the customer has other things to do.

A business can lose an argument without ever hearing it.

The cost of speaking up

Complaining is work. Someone must explain what happened, decide how strongly to object and risk an uncomfortable exchange. For a disappointing lunch, the easiest remedy may be to have the next one elsewhere.

In his 1970 book, Exit, Voice, and Loyalty, Albert Hirschman distinguished between leaving an organisation and trying to improve it by speaking up. For a business, those responses provide very different kinds of information. [1]

Consider an imaginary hotel guest whose room is clean but whose arrival is needlessly difficult. The booking instructions are vague, the entrance is hard to find and nobody answers the first call. Once inside, the guest may decide that explaining all this would only prolong the inconvenience.

The hotel sees a completed stay. The guest remembers an avoidable ordeal. Neither account is invented; one is simply much more useful for understanding the next booking.

An invitation with a preferred answer

“Was everything perfect?” sounds attentive. It also makes disagreement socially expensive. The customer must interrupt a pleasant exchange to announce that, actually, it was not.

A more useful question might be: “Was anything harder than it should have been?” It gives the customer permission to mention a small difficulty without presenting themselves as an angry person. A venue could ask whether the booking instructions were clear. A supplier could ask whether anything caused extra work when the order arrived.

These are questions to test, not magic wording. Their advantage is specificity. “Any feedback?” asks the customer to design the conversation. A concrete question gives it a starting point.

Timing matters too. A restaurant can ask while there is still time to replace a dish. A business supplier may learn more after the customer has unpacked the order than immediately after taking payment. The moment that suits the reporting calendar is not necessarily the moment when the customer knows the answer.

A complaint is not a referendum

Listening does not require accepting every interpretation or granting every request. One person’s preference is not automatically the market’s instruction. A hotel should not rebuild its breakfast around the loudest guest.

But a complaint can contain two separate things: the remedy the customer wants and the difficulty that produced the request. The proposed remedy may be unreasonable while the underlying difficulty is real. A demand for a refund could reveal confusing instructions, an expectation the website created or a handover that nobody owned.

That distinction gives a small business room to act intelligently. Record what went wrong, where it happened and whether it has appeared before. Look for patterns across conversations, returns and repeat orders. Several different complaints may point to the same poorly explained step.

The aim is to learn enough to fix a cause. Turning every objection into a negotiation over compensation can obscure it just as effectively as dismissing every objection.

Beware the improving dashboard

Suppose a business makes contacting support easier. Complaints rise. Has service deteriorated, or has the business finally begun hearing about problems that were already there?

The count alone cannot tell us. It should be read alongside order volume, the nature of the problems, resolution times and repeat purchasing over a sensible period. A fall in complaints might reflect better service. It might also reflect a form that nobody can find.

Nor should every missing customer be diagnosed as dissatisfied. People move, budgets change, projects end and purchasing cycles differ. A monthly café visit and an annual equipment order cannot share the same definition of “lost”. Silence is a reason to investigate, not a verdict.

A modest experiment is enough to begin. Offer a short, optional opportunity for feedback at one relevant moment. Give someone responsibility for reading it and dealing with recurring problems. Compare what you learn with what customers subsequently do. There is little point opening a suggestion box if it is merely another place to store things nobody intends to change.

When a specific problem has been fixed, a brief explanation can close the loop. The business demonstrates that speaking was useful. The customer does not have to be recruited into an unpaid advisory committee.

A quiet inbox is pleasant. It is not, by itself, evidence of a healthy relationship.

The customer who complains may still be deciding whether to stay. The one who says nothing may already have decided.