International·USD
English
Start free

6 min read · 2026-10-20

From a 40-person WhatsApp group to one request queue

Why maintenance requests get lost in group chats, and a seven-day plan to move them into one queue where every request has an owner and a deadline.

Most buildings don’t decide to run maintenance through WhatsApp. It just happens. A manager creates a group for the technicians, another for security, residents get the duty phone number, and within a year every request lives somewhere in a chat.

It works — until it doesn’t. These are the signs that it has stopped working:

  • A resident asks “any update?” and nobody in the group knows who took the job.
  • The same request is answered twice, or not at all, because everyone assumed someone else had it.
  • A technician leaves the company and his half-finished jobs leave with his phone.
  • An owner asks what was done in his apartment last year, and someone spends an evening scrolling.

None of this is a people problem. It is a missing rule: every request needs exactly one owner and one deadline, visible to everyone who needs to see it. A group chat cannot hold that rule. A queue can.

Day 1: list what you actually receive

Before changing anything, write down a week of requests. For each one: where it came from (call, WhatsApp, the guard, e-mail), the unit, what it was about, who handled it and how long it took to close. You will usually find that 70 to 80 percent of requests fall into six or seven categories: AC, plumbing, electrical, lifts, cleaning, keys and access, noise.

Day 2: decide who covers what

For each category, write down who may do the job (skill), when they work (shifts) and who is on duty at night. This is the part people skip, and it is the part that matters most. A request system is only as good as the answer to “who should get this at 21:00 on a Thursday?”

Day 3: give every unit an address

Make a list of your units and common areas with consistent numbers: 402, not “4th floor left”. If you use a spreadsheet for tenants or a booking system for stays, export it. This becomes the backbone everything else hangs on.

Day 4: put a front door on every unit

Residents need one obvious way to report. A QR code in each unit and lobby works because it needs no app and no phone number to remember. Keep WhatsApp too — but on your business number, connected to the queue, not to a group.

Day 5: run one complaint end to end

Pick a real or test request and follow it: reported, understood, assigned, accepted, fixed, confirmed by the resident. Time each step. If any step depends on someone remembering, fix that step before you go live.

Day 6: tell residents, once and clearly

One short message in each resident’s language: “From Monday, scan the code on your kitchen door or write to this number. You’ll get a job number and updates until it’s fixed.” Put the same words on the lobby poster.

Day 7: close the groups for requests

Keep the groups for chat if you like, but stop taking requests in them. When someone posts a request there, reply with the link to the queue. It takes two or three weeks for habits to change. Be consistent and they will.

What changes after a month

You will be able to answer three questions you couldn’t before: how many requests you get a week, how long they take to close, and which units and machines keep coming back. That last one is where the money is — see our guide on repeat repairs.

UnitVO was built around exactly this rule: one owner and one deadline for every request, from the QR code to the resident’s confirmation. You can start the free trial and try the whole week above on one building.

Add UnitVO as a preferred source on Google

All guides