Complaints on WhatsApp: half resolve themselves, 40% need a person

The numbers from a real operation

At a building management firm handling its complaints over WhatsApp with Alumbra, the monthly operation looks like this: around 312 conversations and about 4,137 messages exchanged, of which 1,247 come in and 2,890 go out.

Of those conversations, around 50% resolve with no person involved and around 40% escalate to someone on the team. This is data from our own platform on that operation, not a projection.

The reading people usually get wrong is treating that 40% as a failure. In complaint handling on WhatsApp it is the reverse: it is the part you protect.

Why half resolve themselves

Complaints in a building repeat with a regularity that surprises you when you see it written down. Leaks, noise, elevators, maintenance. And around each one, the same questions: has it been reported, what is the status, when is the technician coming, who pays for it.

That block does not need judgment. It needs to be available at eleven on a Sunday night, which is exactly when something breaks and nobody on the team is watching their phone.

That is where the automatic reply comes in: it takes the complaint as it arrives, logs it, and gives the resident something better than silence. And because the system has permanent memory of every contact, the owner who already complained about the same thing last month does not have to tell the whole story again.

Why 40% has to escalate

The other block shares one trait: it needs coordination with the physical world or a decision that costs money.

• A technician has to be sent and a supplier coordinated.
• There is a dispute between neighbors.
• Someone has to decide who pays.
• There is a tone that needs a person on the other end.

None of those get solved by answering well. They get solved by doing something outside the chat.

An escalated complaint is not a lost conversation. It is a conversation that arrived organized to the right person, with everything already asked and answered sitting above it.

Where the line falls, and who draws it

The question that matters is who decides what gets automated.

At Alumbra the handoff rules are configurable: you define the topics you would rather handle yourself and the system steps aside. Prices, sensitive complaints, special cases, whatever you do not want answered automatically in your operation.

When a conversation needs a person, an email alert goes out with the handoff reason and a direct link to the chat. No need to watch an inbox in case something urgent showed up.

And so that none of this is a black box, the actions that matter are written into the conversation as private notes: order creation, past order lookup, audio transcription, and the handoff with its reason. Your team sees them, the resident does not. We wrote about that in what you can see and what you cannot.

The mistake of aiming for 100%

It is tempting to look at that 50% and want to push it to 80. Worth flagging what trying costs.

Every point you take off the escalation rate you are taking off the hard category, which is exactly where a rushed answer does damage. A badly handled leak complaint is not a lost query: it is a resident who now has two problems.

The metric worth watching is a different one: how long first contact takes and how many complaints get lost without being logged. A resident waiting three days for a confirmation does not complain that a machine answered them. They complain that nobody did.

How to start organizing complaints that arrive loose today

Three steps that require changing nothing about the channel:

1. Write down the list of what repeats. If you do not have it, pull it from the last 50 messages. It will be shorter than you think.
2. Mark what you never want answered automatically. That list is your handoff rules.
3. Separate who is who. Owner, tenant, supplier and neighbor do not complain about the same things or expect the same answers. With contact attributes and tags, that distinction stops living in the head of whoever is on duty.

Key takeaways

• In a real building management operation, around 50% of complaints resolve with no involvement and around 40% escalate.
• What resolves on its own is the repetitive part and the part that needs to be available after hours.
• What escalates shares one cause: it needs physical coordination or a decision that costs money.
• You draw the line between the two with handoff rules. The system does not decide it.
• Every handoff arrives by email with the reason and the link to the chat, and is logged in the conversation.
• Aiming for 100% automation pushes the error precisely toward the cases where it costs most.