How to Automate Maintenance Requests for a Small Property Manager
A leaking sink arrives by text. A broken gate comes in by voicemail. A photo of a ceiling stain lands in your email with no address. You're not short on effort. You're short on one reliable path from "something's wrong" to "this is handled."
Tools and features last checked October 2026.
The manual version
You ask the resident for the unit, photos, permission to enter, and a better description. Then you call a vendor, leave a message, copy the details into another text, and make a note to check back. The resident asks for an update while you're still waiting on the vendor.
Urgent and routine requests share one inbox, so every notification demands a judgment call. Proving the work got done is hard later, because the date, invoice, photos, and resident confirmation live in different threads.
What it costs you
About 12–25 hours a month
That's for roughly 30–75 units and 10–25 requests a month: getting missing details, triage, coordinating vendors, status replies, follow-up, and records. A storm or an older building can blow well past that.
The automated version
The automated version gives residents one clear way to report a problem, tells them how to report emergencies, collects what you need to triage, creates a trackable request, and sends status updates when a person changes the stage. It organizes decisions. It doesn't diagnose hazards.
Google Forms and Sheets
Enough for basic intake and tracking on a small portfolio. Alerts, permissions, and resident updates take careful setup.
Buildium
Resident portals and maintenance workflows for small and mid-size portfolios. AI intake comes from add-on services.
AppFolio
Built-in AI that can triage and dispatch maintenance end to end. There's a 50-unit minimum and a monthly minimum spend, so it suits bigger portfolios.
Plans and features change often. Check what your current plan includes before you buy or upgrade anything.
Where AI fits now
Property software went furthest with AI. AppFolio's Realm-X Maintenance Performer can reply to residents, look at their photos, troubleshoot simple problems, prioritize emergencies, create the work order, and dispatch a vendor, all on its own. Buildium users can add similar AI intake from outside services. Used well, that clears a huge share of the inbox. Used carelessly, it sends a vendor to the wrong problem, or treats a gas smell as a routine ticket.
What AI can handle
- Answering residents at any hour and collecting unit, photos, and access details
- Walking residents through simple fixes, like a tripped breaker or a clogged drain, when you've approved that
- Creating the work order and suggesting priority and vendor
- Sending status updates and following up with vendors
What stays with you
- Real emergencies: gas, fire, flooding, no heat in winter, security. Those go to a phone number that rings a person
- Deciding when the AI may dispatch a vendor on its own, and the spending limit it can approve
- Residents who are vulnerable, displaced, frightened, or reporting the same problem again
What setup really involves
Decide the emergency path before anything goes live. A tidy ticket list is only useful if residents still know exactly what to do when there's immediate danger.
-
Publish emergency instructions first
What counts as an emergency, which number to call, and what to do when there's immediate risk. Show it before and after the request form, and make the AI assistant say it too.
-
Build a complete request form
Property and unit, contact details, category, description, photos, permission to enter, pets or entry notes, and when it started. Don't ask residents to diagnose the problem.
-
Set triage rules and owners
Categories, response targets, which vendor or staff member owns each, and who reviews new requests. Words like 'gas,' 'smoke,' 'flood,' or 'sparks' alert a person immediately.
-
Put limits on what the AI can do
Decide what it can troubleshoot, which vendors it can dispatch, the dollar limit it can approve, and what always needs you. Start with drafts and suggestions, and widen its permissions as it earns trust.
-
Keep status updates plain
A few clear stages: received, reviewing, scheduled, waiting on a part, completed. Tell residents what changed and what happens next.
-
Close with proof
Completion notes, date, vendor, invoice, and photos, then ask the resident to say if the problem's still there. Review open and recently closed work every week.
When not to automate it
- Don't send emergencies through a queue that might wait until morning, whether it's a form or an AI assistant.
- Don't let anything dispatch a vendor automatically when the request could involve safety, access, warranty, or who's responsible for the repair.
- Don't replace a real conversation when a resident is vulnerable, displaced, frightened, or reporting the same unresolved problem again.
Find the automation worth doing first.
The Automation Audit will help you compare request intake with vendor follow-up and inspections. If emergencies and exceptions make the process messy, get in touch and I'll help you map the safe handoffs first.