A property manager responsible for seventeen apartment blocks wakes up on a Monday morning in September to twenty-five fault reports that arrived overnight. One email says only "the lift isn't working" with no building or flat number. Three messages came via his personal WhatsApp from residents who got his number second-hand. And eleven voicemails on the official fault line. Before he can call the first contractor, he spends an hour reconstructing which report belongs to which building.
Revtek · 8 September 2026
To act on a fault report, a property manager needs a handful of basics: the building and flat number, a description of the problem, when it started, and a contact number for follow-up. Phone calls and voicemails almost always miss at least one of those. Personal WhatsApp threads scatter the context across separate conversations. Emails usually arrive without a flat number.
The result is a callback for additional information. For a routine repair request, that costs ten minutes. For an emergency outside office hours, it becomes an escalation. In every case, the resident waits without knowing their report has been received, and the manager still lacks the full picture to brief a contractor.
September is a particularly vulnerable period. When heating systems fire up for the first time after the summer break, boiler faults, leaking connections and unresponsive radiators come in simultaneously. Technical building management covers precisely these situations, but most property organisations have no structured intake channel for the surge.
The practical fix is one WhatsApp number per building, managed by a bot that handles the first round of questions automatically. The resident sends a message to the building's number, the bot asks for the flat number and a brief description, then confirms receipt with a reference number. The manager sees a structured entry in their dashboard: building, flat, timestamp, description and contact number.
Residents change little in their behaviour: WhatsApp is already on virtually every phone. There is no new app to download, no account to create, no guide to read. Anyone who previously reported via whatever channel came to hand can now message the one number they have for the building.
Once the report arrives, the manager decides whether it is urgent. A water leak, a lift that has stopped entirely, or no heating during cold weather requires immediate action. A broken external light or a dripping tap in a shared corridor can wait for the next working day. For urgent reports, the system sends a message directly to the on-call contractor with the structured data: building, flat number, description, timestamp and the resident's contact number. The contractor no longer needs to call back for the basics before attending.
For non-urgent reports the entry joins the queue for regular scheduling, and the resident receives an automated message once an appointment is confirmed, without the manager having to communicate it separately.
Technical building management goes beyond resolving incidents. Every report is also data on the condition of the building. If the same boiler fails three times in two heating seasons, that is a signal to bring its replacement forward in the long-term maintenance plan (MJOP). A system that logs every report with timestamp, fault type and location generates that input automatically, without the manager maintaining a parallel spreadsheet.
Liability is a factor too. If a resident claims water damage and says the first report was made weeks earlier with no action taken, a complete log of reports and responses with timestamps is the only way to reconstruct the facts. A voicemail or a message buried in a personal WhatsApp thread does not provide that certainty. A centralised channel with automatic registration does.
Maintenance reports contain personal data: name, flat number, contact details, and sometimes information about conditions inside the home. Processing them requires a legal basis, a retention period matched to the purpose, and a data processing agreement with the channel provider. If you currently receive reports via personal WhatsApp or via a member of staff who uses their own number, the processing agreement is likely absent. Communication through the official WhatsApp Business API falls under a regulated processor relationship. This is general information, not legal advice; consult a specialist for your specific situation.
A manager responsible for fifty buildings cannot run fifty separate WhatsApp numbers. The solution is one number per organisation, where residents specify their building in the first message. The bot records this and routes the report to the right person. A report for a building in central Amsterdam reaches a different manager than one for a property in the suburbs. The resident notices no difference.
For larger organisations with multiple managers per region, reports can also be categorised by type: lift, heating, leak, electrical, shared spaces. Each category can have its own on-call contact, so a heating specialist is not called out for a broken intercom.
The WhatsApp channel does not replace your existing management software; it sits in front of it. Reports that come in via WhatsApp are forwarded to your own system, or to the email of the responsible contractor, depending on how your organisation currently works. For residential buildings that also want to automate parking, the combination with ANPR parking management for apartment complexes is available as an integrated package.
The building management platform page explains how Revtek sets this up for property managers and institutional landlords, including options for fault management, visitor registration and access control from one system.
Book a free demo and see what Revtek can do for your situation.
Book a demoOr email info@revtek.nl