Maintenance triage and approval.

Maintenance is the single biggest comms drain on a rent roll, so it's the obvious place to start. The good news is that most of a repair job is a fixed chain of steps that happen the same way every time. Pull that chain apart and you can see exactly which links a machine should run, and which two or three belong firmly with a person. Get that split right and a property manager goes from running fifty jobs by hand to supervising fifty jobs that mostly run themselves.

The chain, link by link

A routine repair walks through a predictable sequence. Lay it out and the automation almost designs itself:

• Triage. The request comes in. Is it urgent, like a burst pipe or no hot water in winter, or routine, like a sticking door? Is it the owner's responsibility or the tenant's? What detail is missing? This is the sorting step.
• Owner approval. Routine work inside the owner's agreed spend limit can proceed. Anything above it, or anything unusual, goes to the owner for a yes.
• Book a tradie. Send the job to a suitable contractor from your panel, with the details and photos already attached.
• Coordinate access. Line up a time that suits the tenant and the tradie, and confirm it to both.
• Follow up. Check the work was done, close the job, and update the owner and tenant.

That's the 8-to-12-message marathon from lesson one. Every link except triage and the approval decision is pure relaying, and relaying is what automation does best.

What AI handles, and what stays with you

Picture a tenant logging a repair through your portal. An AI layer can take it from there: ask the clarifying questions, request a photo, sort urgent from routine, and draft the owner approval request. If it's routine and inside the owner's limit, it can book a tradie from your panel, propose access times to the tenant, confirm the booking, and chase the tradie to mark it complete. The property manager sees a tidy summary and steps in only where judgement is needed.

And judgement is needed in clear places. An urgent safety issue, gas, electrical, flooding, a security risk, gets flagged to a person immediately, never left to a queue. A spend above the owner's limit waits for a human decision. An angry tenant, a dispute over who pays, or anything out of the ordinary lands on a property manager's desk. The rule is simple: automate the routine chain, and keep every call that carries risk or needs a head firmly with your team.

Owner approval is the safe dividing line

The cleanest way to make this safe is the owner's spend limit, agreed up front. Many owners are happy to pre-authorise routine repairs up to a set figure, say a couple of hundred dollars, so a blocked toilet doesn't sit waiting on a phone call. Below the limit, the flow proceeds and the owner is simply kept informed. Above it, or for anything that isn't clearly routine, the flow pauses and asks. That single number does most of the work of keeping automation sensible: it tells the system exactly where "just handle it" ends and "ask a human" begins.

The AU platforms that run this

You don't build this from scratch. PropertyMe and Console Cloud, the two dominant Australian platforms, both have maintenance and owner-approval workflows at their core, including job creation, owner approval requests and contractor dispatch. Newer platforms like Ailo and ManagedApp lean hard into streamlined tenant and owner communication too, and Re-Leased serves the commercial side. The job here isn't to switch platforms, it's to use the workflow tools you already have, then layer AI on the parts that still land in your inbox: the triage questions, the chasing, the status updates. Getting those pieces talking to each other is the heart of our systems integration work. A photo of a problem and a few words from a tenant should be most of the way to a booked, approved job before you've touched it.