How property managers can automate maintenance requests

Most property management offices do not have a maintenance problem. They have a maintenance message problem. A tenant texts a photo of a wet ceiling at 9 p.m., another emails "the dishwasher is making a noise," and a third calls the office and leaves a voicemail with no unit number. Someone then spends the next morning turning those messages into work orders that a vendor can act on.

This guide is for owners and operations leads at small and mid-sized property management companies who are ready to fix that. It covers what to automate, what to keep with people, and what the software you already pay for can and cannot do. We read the current Buildium Open API reference on 2026-10-24 for the work order and webhook details below. The steps also apply if you run AppFolio, Rent Manager, or Yardi, with the differences noted.

An AI should not decide who fixes the boiler. The goal is that four routine jobs stop depending on someone reading every message by hand:

1. 1Intake. Every request, from the portal, a text line, email, or a voicemail transcript, lands in one queue and is matched to a tenant and unit.
2. 2Screening. Real emergencies are pulled out first and go to a person right away.
3. 3Completing the ticket. The system asks the tenant the follow-up questions a technician always needs, then writes the work order.
4. 4Keeping everyone posted. The vendor gets the job, the tenant gets a status, and the manager sees anything that is stuck.

Your team still owns the decisions that cost money or carry risk: who pays, whether to approve a large repair, and anything involving safety.

Sit down with whoever runs maintenance and write the list of words and situations that skip the queue. Gas smell, smoke, sparking, carbon monoxide alarms, active water coming through a ceiling, sewage backup, no heat in freezing weather, and lockouts are common starting points. Your list should match your properties and your on-call setup.

For the most dangerous items, the tenant should get a fixed, pre-approved safety message (for example, leave the unit and call the gas company or 911) and your on-call person should be paged at the same moment. Do not let a language model write that message on the fly. Use a plain keyword rule that runs before any AI step, so the safest path never depends on a model reading the text correctly.

Test the list against real messages from the last few months. If a past emergency would not have been caught, fix the list before you go live.

Ask your vendors what they always have to call back about. The answer is usually the same handful of things: which room, what the problem looks like, how long it has been happening, a photo, whether pets are in the unit, and whether the tech can enter if nobody is home.

Those answers map straight onto fields your software already has. In Buildium, for example, the create work order call needs a vendor and an entry permission value (yes, no, or unknown), and also takes a title, work details, entry notes, vendor notes, priority, due date, and the tenant to contact about entry. If your intake does not collect entry permission, your work orders will keep going out as "unknown," and the vendor will keep calling.

Write your list of required answers down. That list becomes the script for the follow-up questions in the next step.

This is where AI helps the most. Instead of a coordinator texting back and forth, the system asks the tenant short questions one at a time, in plain language, until it has the answers from Step 2. It can also sort the request by trade (plumbing, electrical, HVAC, appliance, pest, general) and suggest a priority.

Keep a few limits on it:

• Cap the number of follow-up questions. If the tenant stops answering, create the work order anyway and flag it as incomplete.
• Offer self-help only for fixes your team has approved, such as resetting a tripped outlet, and always give the tenant a way to skip it and ask for a technician.
• Send anything the system is unsure about to a person instead of guessing.

Here the setup depends on what you run.

• Buildium. The Open API needs a Premium subscription. It has endpoints to create and update resident requests and work orders, and webhooks that fire when a work order or task is created, updated, or deleted. That means the automation can write the ticket and also hear back when your team or a vendor changes it. Buildium limits API clients to 10 concurrent requests per second, which is plenty for maintenance volume at most companies. See our Buildium integration notes.
• AppFolio. API access is limited to approved partners in its Stack program, so many teams cannot write work orders directly. A common fallback is to build the complete ticket in a review screen and have a coordinator submit it with one click. See our AppFolio integration notes.
• Rent Manager and Yardi. Both have API options for maintenance data, but access and cost depend on your plan and agreement, so confirm before you scope anything.

If you cannot get API access at all, the automation can still do intake, screening, and follow-up questions, then hand a finished ticket to your team. That alone removes most of the back and forth.

Once the work order exists, the rest is rules your office already follows but tracks by hand:

• A preferred vendor per trade and property, with a backup.
• A not-to-exceed amount per job, and an owner approval step above a set threshold.
• A confirmation to the tenant with the vendor name and appointment window, and a reminder the day before.
• An entry notice that follows your state and local rules.
• A "is this fixed?" text when the vendor marks the job done. A "no" reopens the ticket.
• An alert to the manager when a ticket sits too long in one status, or when the same unit has the same problem twice in a short window.

This is where webhooks matter. When the work order changes in your software, the automation should react to that change, not check every few minutes. Our post on webhooks vs polling explains why.

If you hired us to build this, a typical first version would include:

• One text number and one email address that feed the same queue, plus your existing portal.
• The emergency keyword rule and on-call paging, tested against your past messages.
• The follow-up question flow, sorting by trade, and a suggested priority.
• Work order creation through the Buildium API, or a one-click review screen where API access is not available.
• Vendor rules, approval thresholds, and tenant updates.
• A short weekly summary: open tickets by age, repeat issues by unit, and vendor response times from your own data.

Workflow automation projects start at $2,500 with a fixed-price quote, and we would pilot on one property first, with a coordinator reading every conversation for the first couple of weeks. More detail on how this fits property management offices is on our property management page.

• Wrong unit matching. Tenants text from new numbers. Decide what happens when a message cannot be matched to a lease, and make sure it goes to a person.
• Language. If your tenants write in more than one language, test the follow-up questions in each one.
• Fair housing and privacy. Apply the same rules to every tenant, and keep photos and messages inside systems you control.
• Vendor buy-in. If vendors still ignore the work order and call the office, the process has not changed. Ask them what they need in the ticket.
• Upkeep. Rules drift as vendors and properties change. Our post on automation maintenance costs covers what ongoing care looks like.

If you manage a small number of units and one person already handles maintenance well in your software's portal, a project like this may not pay back. Start by turning on your software's own request form and notifications, and revisit when message volume grows. Our post on whether to hire or automate walks through that decision.

It is also not worth automating a process nobody agrees on. If your team cannot say who approves a repair over a certain amount, write that down first.

Pull the last 30 days of maintenance messages and count how many needed at least one follow-up before a vendor could be sent. That number tells you how much coordinator time this would free up. If you want a second opinion, our free automation audit looks at your current tools and messages and tells you what we would build first, or whether you should build anything at all. You can also see what workflow automation projects include.