Property Example use case
Tenant repair requests logged and scheduled on WhatsApp
A tenant reports a dripping tap on WhatsApp. Ezro logs the repair, offers the plumber’s next free slot and books it once the tenant confirms.
- Channel
- Works in
- Google Sheets
- Ended
- Done by Ezro
The situation
A landlord with a few blocks of flats hears about every problem on WhatsApp. A tap drips. The security light is out. The gate remote has stopped working. The messages arrive at any hour, from numbers that are not saved in anyone’s phone, and they are mixed with rent questions and photos of other things.
The manager reads them when they can, decides which can wait, rings a plumber or an electrician for a free morning, and goes back to the tenant to check someone will be home. Nothing is written down unless the manager does it. A week later nobody can say what was reported, who was booked, or whether it was fixed.
The procedure
Written once, in plain words. This is all Ezro was given.
Steps 1–4
- 1
When a tenant reports something broken, log the repair in the repairs log with the unit and what is wrong.
- 2a
IF
There is water on the floor, a smell of gas, or no power
Assign it to the caretaker straight away with a summary.
2bELSE IF
It is a tap, a toilet or a light
Offer the next free slot from the contractor sheet.
- 3
Book the slot once the tenant confirms someone will be home.
- 4
Rent and lease questions stay with the property manager. Assign them with a summary.
What Ezro did
Each step from the run, with the record it read or wrote.
[ Run · WhatsApp ] Repair requests
- Logged “kitchen tap dripping” for Unit B4 as job #3317 Google Sheets · Repairs log, job #3317
- A dripping tap, so not an emergency. Found the plumber’s next free slot: Ben, tomorrow 10:00–12:00 Google Sheets · Contractors
- Offered the slot and asked if someone would be home. The tenant said yes
- Booked Ben for tomorrow between 10:00 and 12:00 Google Sheets · Contractors, Ben
- Confirmed the booking in the chat
Done by Ezro
Job #3317 logged and Ben booked for tomorrow morning, and the tenant has the time in the chat.
Why a procedure works here
Repair requests are all the same kind of message, and the work behind them always runs in the same order: write the repair down, find a contractor who is free, and agree a time with the tenant. The procedure follows that order. Every repair goes into the repairs log first, so the log builds up by itself, and the slot Ezro offers comes from the contractor sheet, so it never promises a time nobody has.
The landlord decides what counts as an emergency. Water on the floor, gas or no power does not wait for a slot: Ezro assigns it to the caretaker straight away, with a summary. Rent and lease questions stay with the property manager, and Ezro assigns those to them too. The slot is booked only once the tenant confirms someone will be home. The repairs log and the contractor sheet are connected to Ezro during setup, where you say what it may read and which rows it may add or book.