You already have a facilities system. Why is everyone still chasing on WhatsApp?

The following is a fictional working day at a managing agent responsible for three commercial properties. It illustrates a coordination problem, not a Wisbid customer case.

At 8.15am, a tenant sends the site manager a photo of a loading-bay shutter that will not open. “Can someone come before the deliveries arrive?”

The manager calls the maintenance contractor, then gets pulled into a problem at another property. She plans to enter the request when she gets back.

The team already has a facilities management system. It holds the asset register, planned maintenance and work orders. Yet, for the next few hours, the most current account of this fault will be spread across a phone call, two WhatsApp conversations and an email.

By lunchtime, three people have three different answers

The receptionist knows the tenant is waiting. The site manager knows a technician has been dispatched. The administrator checking the system cannot find the job, so she messages the manager to ask whether anyone has taken responsibility.

A second tenant emails about the same shutter. Without the first request in front of her, the administrator starts entering another report. She pauses to check whether the two messages describe the same entrance.

Meanwhile, the contractor sends “Attended, motor needs replacement” to the manager. The quotation goes to the office by email. The tenant receives neither update and calls reception again.

No one has ignored the fault. Several people have acted. But each person has only enough information to answer part of the next question. The system catches up when someone finds time to copy everything into it.

That person is now doing a second job alongside coordination: remembering which conversations still need to become records.

The afternoon question is about a promise

At 2.30pm, the portfolio manager asks, “Are we meeting the service target, and when will the loading bay reopen?”

The team needs to establish when the fault was first reported, when the contractor attended and what was promised next. The time the administrator finally entered the job cannot answer all of that. The relevant contract may distinguish an attendance target from a repair target, so someone needs to check the terms before giving an assurance.

The replacement motor also raises a practical question: does the maintenance contract cover it, or does additional spending need approval? The person able to decide needs the contractor’s findings and quotation. Asking the site manager to resend both interrupts another piece of work.

With three properties to watch, the portfolio manager cannot keep every conversation in mind. A job described simply as “waiting” gives little help in deciding where to intervene. Waiting for a part calls for a different conversation from waiting for the building owner to approve the expense.

What this day has already cost

The receptionist has handled repeat calls. The administrator has checked and copied the same details more than once. The site manager has stopped work to supply updates she thought she had already given. A planned inspection has slipped while she reconstructs the history.

The loading-bay disruption has its own consequences for tenants and deliveries. Better coordination would not manufacture a replacement motor, but the team could have explained the position earlier and got the approval question to the right person sooner.

At 4.45pm, a colleague takes over. Her first question is the one the administrator asked that morning: “Who is dealing with this?”

That repeated question is worth noticing. It shows how much the operation depends on the availability and memory of particular people. An absence, shift change or additional property makes that dependence harder to manage.

What would make tomorrow easier?

For this team, a useful improvement would let the covering colleague pick up the unfinished repair without phoning everyone again. The tenant would get an update grounded in the latest information, and the manager would know which decision still needed attention.

Wisbid’s maintenance platform can keep the original request, related work and completion records together, with visibility of responsibility and service targets. That helps a manager follow the whole repair, including work still outstanding after a contractor’s first visit.

Wisbid also supports WhatsApp enquiries in a shared facilities workspace and conversations attached to work orders. Its AI assistance can help find relevant job information and prepare an update using the records it can access. Your team chooses which actions need approval. The intended benefit is fewer repeated searches, copied updates and interruptions during the working day.

If a client requires an existing system, include that requirement in the discussion. Ask to see how the proposed arrangement would reduce the team’s total work, including any entries that still have to be made there.

Try the handover test on one open repair

Choose a recent job that involved several people. Ask a colleague who was not handling it to explain what the occupant is waiting for, what has already happened and who needs to act next.

Notice where the colleague gets stuck. Do they need someone’s phone? Is the latest contractor answer missing? Does “completed” describe a visit while the original fault remains open?

Then ask the team which repeated task it most wants to stop doing. Our maintenance work order checklist can help review a handover, but the useful starting point is the actual interruption your people keep facing.

Tomorrow’s loading-bay fault may still need a technician, a part and a spending decision. The team should be able to carry that work into the next shift without rebuilding the story from scratch.