How to Automate Tenant Maintenance Requests for a Small Property Management Business

A maintenance request arrives as a text at half past nine on a Sunday saying the boiler is making a noise. By Tuesday there are four more, two of them about the same building, and the only record of any of them is in one person's phone, alongside a photograph of a radiator.

Small property managers rarely lose requests because nobody cares. They lose them because a request can arrive on six channels, and none of those channels has a status. Nothing is assigned, nothing is closed, and the tenant chases because chasing is the only way to find out whether anyone saw it.

This guide gives every request one front door, sorts it by urgency before a person reads it, and turns the approved ones into a contractor instruction with the access details already attached. Budget about half a day to build.

What you are building

One intake form that every request is funnelled into, an AI triage step that summarises the problem and proposes an urgency band, a human decision where money is involved, and a dispatch message to the right trade. Plus a status the tenant can see moving, because most chasing messages are really requests for an update.

Tools: a form tool, a spreadsheet or the property software you already use, an automation tool such as Zapier, Make or n8n, an AI assistant such as ChatGPT or Claude, and your email or SMS.

Step 1: one front door, and a short form

Publish one link and put it everywhere a tenant might look: the tenancy pack, the email signature, the voicemail greeting, the noticeboard in the communal hall. When a request arrives any other way, reply with the link rather than with a fix.

Keep the form short enough to complete standing in a kitchen holding a phone.

• ·Property address and unit number, chosen from a list rather than typed.
• ·What is wrong, in their own words, with a photo or short video if they can.
• ·When it started and whether it is getting worse.
• ·Whether anything is unsafe, leaking, without heat or without power right now.
• ·Best times for access, and whether there is a pet, an alarm code or a key safe.
• ·A phone number the contractor can actually ring.

The access question saves the most time later. A contractor who arrives at a flat nobody is in has cost you the visit, the call afterwards, and the tenant's patience.

Step 2: the triage prompt

Triage is not a decision. It is a first read that arrives already sorted, so the person on the desk spends their attention on the borderline cases rather than on reading forty descriptions of a dripping tap.

The instruction not to diagnose matters more than it looks. A model will happily tell you a boiler needs a new diverter valve on the strength of one sentence and a photograph, and that guess has a way of turning into an instruction by the time it reaches a contractor.

Step 3: keep a person between triage and money

Everything up to this point can run on its own. The dispatch cannot, unless you have decided in advance where the line sits.

The workable version is a standing authority with a number attached: routine work under an agreed limit goes straight to the contractor, anything above it waits for the landlord, and anything marked NEEDS A HUMAN DECISION goes to a person immediately with the tenant's phone number in the notification. Agree that limit with each landlord in writing when you take the property on, and record it against the property so the automation can read it.

Step 4: the dispatch message

A contractor instruction that has to be followed up with three texts is not a saving. Write it once, with everything a van needs.

Step 5: wire it up

1. 1Trigger on a new form submission.
2. 2Send the tenant an immediate confirmation with a reference number, what happens next, and the emergency number again.
3. 3Call the assistant with the triage prompt and write the result into a sheet, one row per request, with a status column holding new, approved, dispatched, booked or done.
4. 4Route by urgency. NEEDS A HUMAN DECISION notifies a person with the phone number attached. Anything above the landlord authority limit sends an approval request to the landlord. Everything else moves to approved.
5. 5On approval, pick the contractor for that trade and that area from a simple lookup table, and send the dispatch message.
6. 6Send the tenant a short update every time the status changes, and one message the day before an attendance once a date is confirmed.
7. 7Chase anything still sitting in dispatched with no confirmed date after two working days.

That last step quietly does the most work. A request does not usually fail at the point it is raised. It fails in the gap between a contractor saying yes and nobody checking whether a date was ever agreed.

Step 6: what the record is for

One row per request, kept properly, answers questions that are otherwise expensive. Which property eats the most call-outs. Which contractor confirms within a day and which needs chasing every time. Whether the boiler in flat four has now been attended three times for the same noise, which is a replacement conversation rather than a fourth repair.

It is also the record you will want if a tenant ever says a request was ignored. Dates, who was told, when a contractor attended, all in one place, without reconstructing anything from somebody's phone.

What changes

Tenants get an answer within minutes instead of wondering whether anybody saw their message. Contractors get an instruction they can act on without three follow-up texts. And the person on the desk spends the morning on the two requests that need judgement rather than sorting the forty that did not.

Connecting a form, a sheet, an assistant and your contractor list like this is exactly the kind of build in Workflow 05: Build Automation Workflows, the AutomateFirst module about wiring the tools you already pay for so repetitive work runs in the background. This guide is one complete build from it, free. The playbook has seven workflows for one payment of $297, with a 30 day refund.