Tells tenants and owners where a job has actually got to, at the points that matter, and answers the chasing call before anybody makes it.
An AI agent for repair status updates keeps both audiences of a work order informed while it runs: it tells the tenant when a job is raised, assigned, scheduled and completed, tells the owner when their money is involved or a decision is theirs, answers a status question at any hour by reading the job record, and flags to the office when a job has gone quiet. Maintenance complaints are usually about information rather than speed. A tenant who knows a part is on order and the engineer returns Thursday will wait. The same tenant, told nothing for a week, assumes the job has been forgotten and starts ringing daily — which consumes exactly the coordinator time that would have moved the job forward.
Closes the information gap that generates the chasing.
Confirms to the tenant that a job is raised and what happens next
Updates both sides at assignment, scheduling and completion
Answers status questions at any hour from the live job record
Explains delays honestly, including when a part is on order
Tells the owner when a decision or a cost is theirs
Flags jobs with no movement so the office sees them before the tenant does
Every chasing call is a piece of work the agency created for itself by not saying something earlier. The call is expensive twice over: it interrupts the coordinator, and it arrives with an emotional charge that a proactive update would never have carried, because by the time somebody rings for the third time they are not asking for information, they are complaining. There is also a harder benefit. A system that has to report status continuously makes stalled jobs visible, and stalled jobs are otherwise invisible by definition — nobody has an alert for the absence of progress. The office ends up seeing its own backlog for the first time, which is uncomfortable and useful in roughly equal measure.
A three-step flow around the life of a work order.
When a job is raised, assigned, scheduled, delayed or completed, the agent tells whoever is waiting on that stage, in the channel they used.
A tenant or owner asking for progress gets the live position from the job record — not a template, and not a promise nobody made.
Jobs with no state change inside your expected window are reported to the coordinator, so the stall is found internally rather than externally.
A boiler repair that needs a part ordered.
Scenario: an office was updating tenants only when they rang, and was fielding several chasing calls a day. An engineer attends a boiler fault on Monday, diagnoses a failed pump and orders the part. The agent tells the tenant that afternoon what was found, that a part is on order, and that the engineer will return once it arrives — with a note that she will hear again by Thursday either way. On Wednesday the supplier confirms delivery for Friday, and she is told. The owner gets a separate message, because the part is chargeable and the cost sits within his standing authority so no decision is needed, only a record. On Thursday the tenant asks whether she should be at home Friday; the agent reads the job, confirms the window and the engineer's name. She has been kept whole for four days without a single call reaching the coordinator, who spent that time on jobs that were actually stuck.
Anybody whose phone rings because somebody is waiting.
Chasing calls interrupt exactly the work that would end the chasing.
Repair communication is what tenants judge the agency on.
Complaint volume tracks information gaps far more closely than repair times.
One communal job generates the same question from many residents.
Owners hearing about their own property from the tenant is how agencies get replaced.
Most inbound volume is a status question that the record already answers.
Reads the job, tells the people waiting, watches for stalls.
Holds the work order and its state history, which every update is read from.
Carries tenant updates and answers status questions in the same thread.
Sends owner updates and keeps a written record on the property file.
Answers callers asking for progress instead of sending them to voicemail.
Builds the stalled-jobs report the coordinator reviews each morning.
Raises jobs with no movement and any message that reads as a complaint.
The moments where silence turns a wait into a complaint.
Questions about keeping people informed without adding headcount.
An AI agent for repair status updates keeps both audiences of a work order informed while it runs: it tells the tenant when a job is raised, assigned, scheduled and completed, tells the owner when money or a decision is theirs, answers status questions from the job record at any hour, and flags jobs that have gone quiet.
At every real state change, plus a holding update if nothing has changed inside the window you promised. The second one matters more. An update saying the part has not arrived yet is unwelcome but acceptable; a week of silence is what produces the complaint.
It reads the live record, which is the difference that makes it worth having. A template saying your repair is progressing when nothing has happened for eight days damages trust more than saying nothing at all, because the tenant can tell, and now they know you are automating rather than working.
Then it will confidently tell people something untrue, at scale. This is worth being blunt about internally: the quality of the updates is capped by the discipline of updating work orders after site visits, and no agent compensates for a system nobody keeps current.
No. The tenant needs to know when somebody is coming and what to expect; the owner needs to know what it costs and what is being decided. Sending both the same update means one of them is reading something irrelevant, and people stop opening messages that are usually irrelevant.
It compares time since last state change against what you expect for that stage. This tends to be the most uncomfortable output at first, because the backlog was always there and simply had nobody counting it. That discomfort is the feature.
It reduces the complaints caused by not knowing, which in most offices is the larger share. It does nothing about a genuinely slow repair — a tenant told promptly and honestly that the wait is three weeks is still going to be unhappy about three weeks, and should be.
Tells tenants and owners where a job has actually got to, at the points that matter, and answers the chasing call before anybody makes it.