GenieApps Digital Solutions
Back to blog
Facilities

Why most facilities teams in Africa still run on WhatsApp — and what it costs them

GenieApps Editorial·Product & Insights·2 June 2026·6 min read

Walk into almost any facilities or operations office across Lagos, Nairobi or Accra and you'll find the same tool doing the heaviest lifting: a WhatsApp group. A tenant messages that the lift is down. A security guard sends a photo of a leaking pipe. A generator technician confirms he's on his way. It works, in the sense that information moves. It fails in almost every other sense that matters.

The core problem isn't the app — it's that a chat thread has no structure. A fault reported in a group has no owner until someone volunteers, no SLA clock until someone starts one manually, and no record that survives past the next hundred messages pushing it off screen. Ask a facilities manager how long the average repair takes and most can't answer with a number, only an impression.

That absence of structure has a cost, and it's larger than it looks. Faults that would take a technician forty minutes to fix get logged, forgotten, and rediscovered three days later when someone complains a second time — at which point it's often a bigger, more expensive job. Vendors get chosen from memory rather than performance history, because there is no performance history. And when a portfolio-level report is needed for a board meeting, someone spends two days manually reconstructing it from chat logs.

The fix isn't a stricter WhatsApp policy. It's giving every fault a structure the moment it's reported: an owner, a timestamp, a status, and a place it lives that isn't a scrolling feed. That's a small process change with a compounding effect — once every request is tracked to close, patterns become visible. Which sites raise the most reactive tickets. Which vendors miss SLAs. Which equipment is about to become a bigger problem than a work order.

None of this requires an enterprise transformation. It requires treating a fault report as a record, not a message. That's the entire premise behind how we built Facilit8 — every request becomes a tracked ticket from the moment it's raised, whether it comes in from a QR code, a mobile app, or yes, even a message someone forwards from the group chat during the transition period.

Want to talk through this on your own systems?

Get in touch