A complaint reached the manager.
That means the system already failed.

Why a complaint reaches the manager at all

There is one metric managers rarely discuss openly: how many complaints reach them personally each week. Not the system. Not the service team. You.

Every such email is a signal: there was a moment when the situation could still have been resolved. And nobody did. This is not a question of employee bad will. It is a question of the system.

In larger organisations, the complaint path upward often looks like this: the customer encounters a problem, contacts an employee, the employee has neither the authority nor a clear procedure to resolve it, the customer is disappointed — and eventually the message ends up in the manager's inbox or publicly online.

The problem is usually not that the employee did not want to help. The problem is that they did not know what they were allowed to do. That uncertainty — when the customer watches the employee go silent, make internal calls, or say "I need to check with the manager" — is the most expensive mistake in service.

What is proactive complaints management

Proactive complaints management is the organisational ability to identify and resolve a customer problem before it becomes a formal complaint. It rests on three elements: employee empowerment, complaints data analysis, and a clear escalation procedure.

It sounds simple — and it is simple, when the system is built for it. Late delivery: the employee calls first. Produktas su defektu: komanda informuoja prieš klientui pastebint. Sutarties neatitikimas: atsakingas žmogus tai mato ir kreipiasi.

But this behaviour cannot be expected from someone who has neither the tools to notice the problem nor the permission to resolve it independently.

How to build an employee empowerment system

One practical and frequently underestimated solution is to clearly define what each employee can do independently when a problem is legitimate.

An example that works across many sectors: the employee has the right to offer a discount up to a certain threshold — say, 10% — without additional approval, if the problem is clear (delay, defect, process error). Above that threshold — escalation follows a clear procedure.

This is not giving money away. It is an investment in resolving the problem at the right moment — while the customer is still talking to you, not writing a public review.

This system requires three things:

The complaint as a diagnosis

In larger organisations, department managers often present complaints as exceptions rather than patterns. "That was a special case." "The customer was difficult." These explanations may be accurate in individual cases. But when the same explanations recur every month — these are no longer exceptions. This is the system.

Complaints data tells you what surveys often do not — because the person complaining has already reached an emotional threshold and decided it is worth speaking up. This is not a random piece of feedback. It is a signal from someone who did not yet want to leave quietly.

Reading complaints systematically does not mean knowing about them. It means categories, frequency, recurring words. If for three months in a row customers mention the same stage — that is a diagnostic data point the manager can put on the table and say: here is the structural cause, and we are removing it.

The most common mistakes in complaints management

What to do tomorrow

What's in the register

Most organisations log complaints. Few analyse them systematically — and fewer still check whether the corrective action worked. This file joins the daily entry, a cost model, a CAPA cycle and automatic analytics in one document. Nine sheets and three colours: blue columns are filled by the agent, yellow by the manager, grey ones calculate themselves.