WhatsApp is not a maintenance management system. It just feels like one — until something falls through the cracks.
The tenant messages you about a leaking pipe. You read it, intend to call the plumber, and get distracted. Three days later the tenant follows up. You apologise, call the plumber, who visits a week after that. The tenant is now frustrated. The repair costs more because the leak got worse. And you have no record of any of it.
This is the WhatsApp maintenance loop. Most landlords are in it. Here's how to get out.
Why WhatsApp fails as a maintenance tool
The problem with WhatsApp isn't that it's bad at communication. It's that it has no structure for work management. A message is just a message — it has no status, no assignee, no deadline, no cost field, and no way to tell whether it's been acted on.
- Messages get buried. A maintenance request from 11 days ago is now 97 messages up in the thread. You know it's there somewhere. You're not sure if it was resolved or just never followed up.
- No assignment. Who is fixing the boiler? You called the plumber, but did you confirm? Did they acknowledge? Is it on their list? WhatsApp gives you no way to know without sending another message.
- No record of cost. The job gets done. The plumber invoices you. The invoice goes to email. The original maintenance request stays in WhatsApp. These two things are never connected — so your expense records are always incomplete.
- Liability risk. A tenant reports damp. The message gets missed. The damp causes damage to their belongings. They claim you were notified and took no action. WhatsApp is not an audit trail. A maintenance log is.
What a maintenance log actually needs
A proper maintenance system has five fields that WhatsApp will never have:
- Job description — what's the issue and which unit it's in
- Priority — urgent, high, medium, or low (so you know what to action first)
- Assigned vendor — who is responsible for the repair
- Status — open, in progress, or resolved
- Cost — what the repair cost, linked to your expense records
With these five fields in place, you can answer any maintenance question at a glance: what's outstanding, what's been assigned, what's cost me this month, and what's been resolved for each property.
Log it once. Know its status, cost, and history — forever.
30-day free trial · No credit card required · Cancel anytime
Start free trial →The maintenance workflow, step by step
Step 1: Log the job immediately when it's reported
The moment a tenant reports an issue — by message, phone call, or in person — create a maintenance job. Don't wait until you've arranged a contractor. Don't screenshot the WhatsApp message and tell yourself you'll deal with it later. Log it immediately.
This takes 60 seconds and ensures nothing is ever missed. The job exists in the system, it has an open status, and it will stay visible until it's marked resolved.
Step 2: Set priority and assign a vendor
Once logged, set a priority. A burst pipe is urgent — it goes to the top of the list and gets immediate action. A squeaky door hinge is low priority — it gets scheduled when a contractor is already on site.
Then assign the job to a vendor from your contractor list. This is the person responsible for the work. Having an assigned vendor means there's no ambiguity about who should be acting on this — and you can follow up with one specific person if it stalls.
Step 3: Update status as the job progresses
Move the job from Open to In Progress when the contractor is booked. Move it to Resolved when the work is done. This takes seconds but gives you a complete picture of your maintenance queue at any time.
You no longer need to check WhatsApp to know what's been sorted. Open the maintenance log and everything outstanding is right there.
Step 4: Log the cost when the job is closed
When the invoice arrives, log the repair cost against the maintenance job. This does two things: it closes the loop on the job record, and it creates an expense entry linked to the correct property and unit. Your maintenance history and your expense records become the same data — not two separate things you have to reconcile.
The shift from reactive to proactive
WhatsApp keeps you reactive. Something breaks, someone messages, you scramble to fix it. A maintenance log lets you become proactive — you can see patterns, plan preventive work, and budget for repairs before they become emergencies.
Which properties generate the most maintenance jobs? Which units cost the most to maintain? Which contractor is slowest to respond? These questions are unanswerable from WhatsApp. From a maintenance log, they take seconds.
Managing maintenance without WhatsApp isn't about removing communication — tenants can still message you. It's about what happens after they do. The message triggers a job. The job has a status. The job has an owner. The job has a cost. And nothing falls through the cracks because there are no cracks — just a list with a status on every item.