WhatsApp for building management: 312 conversations a month without losing one

How much WhatsApp a building manager actually handles

More than fits in one person's head, and less than would justify hiring another.

At one of our customers, a building management company, WhatsApp for building management means, measured: about 312 conversations and 4,137 messages a month. Of those messages, 1,247 come in and 2,890 go out.

That is around ten new conversations a day, every day, about different things: a leak, a lift, a noise complaint, a service charge nobody understands.

"I wrote three days ago and nobody answered"

That is the verbatim sentence of an owner in one of the buildings that customer manages.

It does not say the manager works badly. It says something harder to fix: the message arrived, somebody read it in the middle of something else, and it sank under twenty others. There was never a decision not to reply.

It is the typical failure mode of a WhatsApp that is also the channel where suppliers, the accountant and the family come in.

Why a building complaint is different

Because the person writing is not a customer who can go elsewhere.

An owner lives with the problem and with the answer. On top of that, the activity is regulated: in the City of Buenos Aires, Law 941 governs building administration and created the Public Registry of Administrators, with concrete obligations for whoever manages a building. Most jurisdictions have their own version of that duty.

That changes the standard. Not replying is not a lost sale, it is a complaint that escalates upwards.

Half resolve on their own, 40% need a person

The numbers from the same case, measured over those 312 monthly conversations.

What happens to the issue	Share
Resolved in the conversation, with no intervention	~50%
Escalated to somebody on the team	~40%
Rest	one-off queries and follow-up

That 50% is not the hard complaints. It is the ones that repeat: opening hours, the status of a job, who is responsible for what, how to request an authorisation.

What can be answered with nobody stepping in

Everything already written down somewhere that nobody can find.

• The building rules and what they allow or forbid: moves, pets, works, quiet hours.
• The status of an issue already logged, instead of "I'll check and let you know".
• Operational details: when the lift service comes, what day pest control is due.
• Who has to pay for what, when the answer is in the rules and not in an interpretation.

All of that comes out of your own documents. It is not invented: it is answered with the paragraph that says it.

What has to reach a person, no exceptions

Anything that involves coordinating with somebody in the physical world.

A leak needs somebody to call the plumber and agree a time. A stopped lift needs the maintenance company. A conflict between neighbours needs judgement, not information.

That is the 40%, and it is right that it should be. Escalation is not the system failing: it is the system working.

What happens after the handoff

Here is the detail that pays off most in this particular case.

When the issue passes to a person, the conversation keeps being read. It does not switch off: it follows the thread, so when the issue is resolved it can pick the follow-up back up without anybody having to reread everything from the start.

For a complaint that lasts four days and passes through three people, that is the difference between a case with a history and twenty loose messages.

How to start without changing how the team works

The first thing is not to automate. It is to stop losing messages.

1. Connect the channel and work in the inbox, with automated replies switched off. That alone stops conversations living on one phone.
2. Upload the building rules and the how-to sheets. That is half of the 50% that resolves itself.
3. Start gradually, tagging which conversations get answered automatically.
4. Mark the topics that are off limits and go straight to a person.

Key takeaways

• A real building manager moves 312 conversations and 4,137 messages a month over WhatsApp.
• Around 50% of issues resolve in the conversation and 40% escalate to a person.
• What can be answered automatically is what is already written: rules, hours, the status of a job.
• What needs coordinating with a supplier or resolving a conflict goes to a person.
• After the handoff the conversation keeps being read, so the case does not get cut in half.
• The first step that pays off most is using the inbox with automation switched off.