AI for Property Maintenance Operations

1. 01Maintenance is the highest-volume workflow most PMCs run. It is the right first AI workflow because the pain is daily, the cycle times are measurable, and the after-hours load is real.
2. 02A real ticket touches the resident, the PM, the vendor, the owner, the accounting ledger, and the visibility layer. Single-system AI cannot run it. Cross-system orchestration is the bar.
3. 03An AI maintenance operation does specific jobs: pre-ticket troubleshooting, classification, vendor dispatch, owner approval gating, photo verification, invoice intake, closeout, owner reporting.
4. 04Done right, a one-ticket workday for the PM collapses to a few one-tap confirmations. The agent does the typing and the chasing. Humans gate the judgment calls.
5. 05Verification is non-negotiable. Photo comparison and structured email parsing are what stop a vendor-said-done from closing a ticket where the work did not actually happen.

01

After-hours coverage

A meaningful share of resident maintenance contact happens outside business hours. A live PM means a paged manager or a delayed reply. An AI agent picks up the moment the chat opens.

02

Triage time per ticket

Categorize, set priority, suggest a vendor, write the summary, link the unit and lease, post the resident chat as context. Minutes per ticket times daily volume.

03

Drafting + sending comms

Every ticket fires off at minimum a resident scheduling email, a vendor dispatch, an owner approval, a vendor confirmation, an invoice reminder, and a resident closeout. Six drafts the PM no longer types.

04

Reading vendor replies

Vendor reply hits the inbox. Someone has to read it, extract the dollar amount, find the schedule date, decide if owner approval is needed, and update the right columns.

05

Photo review

Pre-work and post-work photos sit on the ticket. Confirming the right fixture, spotting safety hazards, comparing before-and-after, is human work unless the agent does it.

06

Owner reporting

Final PDF report. Cover page, problem, triage history, pre/post photos, closeout, full activity log. Manual assembly takes hours per ticket.

1. 01

   Resident contact

   Resident opens the maintenance chat on the portal. The agent picks up before a work order exists, classifies the issue, walks through the known fix attempts for that class of issue, and either resolves it or escalates with the full context preserved.

2. 02

   Ticket creation, already triaged

   Item appears on the maintenance board. Classification, priority, linked unit, linked lease, the original problem, the troubleshooting log, and the full chat transcript are all pre-filled. The form-path triage agent skips when the chat-path agent has already handed off.

3. 03

   First resident reply

   Status moves to awaiting resident info. The comms agent drafts and sends a scheduling email asking for availability windows and access notes, in your voice. The same message is posted as an update on the item.

4. 04

   Vendor dispatch

   Status moves to initial dispatch. The comms agent drafts and sends the vendor email with property, unit, resident contact, what the resident reported, what was already tried, and the ask for estimate plus earliest schedule date.

5. 05

   Inbound parse

   Vendor replies. The inbound-email agent matches the reply to the right work order, classifies the sender, extracts the dollar amount and the schedule date, writes them to the columns, and flags the suggested next status.

6. 06

   Owner approval gate

   If the amount exceeds the property's reserve, the comms agent drafts the owner approval email but holds the send. The draft sits on the item as a gated update for a human to confirm with one word or one tap.

7. 07

   Approval relay

   PM confirms. The coordinator agent fires the gated email. Owner replies. The inbound parser reads the reply, sets the owner-approval column, and the comms agent fires the vendor-proceed email.

8. 08

   Verification

   Vendor arrives, takes a pre-work photo, uploads it. The photo agent validates fixture and condition. Vendor completes the work, uploads the post-work photo. The photo agent compares pre and post, confirms the fix, checks for new damage.

9. 09

   Closeout

   Invoice arrives. Inbound parser ticks the invoice-available column and suggests closed status. PM confirms. The comms agent sends the resident closeout. The photo agent assembles the owner PDF and emails it. Item collapses into the closed-tickets view.

01

Time to first resident response

Submission to first reply the resident sees. Agent-handled chat collapses this from hours (or overnight) to seconds.

02

Time to vendor dispatch

Triage to first outbound message to the vendor. Comms drafted + sent on status change, no waiting for a human to find the right template.

03

Time to resolution

First triage to a verified completion. The bottleneck shifts from PM availability to vendor schedule.

04

First-touch resolution rate

Issues resolved during the initial chat without ever creating a vendor work order. Every one is a vendor dispatch you did not pay for.

05

Percent of comms auto-drafted

Resident scheduling, vendor dispatch, owner approval (gated), vendor confirmation, invoice reminder, resident closeout. Six drafts per ticket the PM no longer types.

06

Owner approval cycle time

Owner email sent to approval received. Single-click approve buttons in the owner email cut this from days to minutes.

07

Verification catches

Times the photo or invoice check caught a vendor-said-done that did not match the photo. Quiet quality control on every closeout.

08

After-hours queue depth

Tickets accumulated overnight that needed a human first thing. With an agent on the chat, this collapses toward zero.

01

Hours per ticket reclaimed

A typical maintenance ticket consumes 20 to 60 minutes of PM time across triage, drafting, reading replies, chasing vendors, owner comms, and closeout. The agent compresses that to roughly the time it takes to read a draft and tap confirm.

02

First-touch resolutions you do not pay for

Every issue resolved during the resident chat saves the vendor truck-roll cost and the PM coordination time. Common cases: tripped breakers, reset disposals, filter replacements walked through, faucet aerator fixes.

03

After-hours coverage without a human

Friday-evening leaks, weekend lockouts, holiday outages: the agent handles intake, classification, and (gated) dispatch. The PM looks at a queue Monday morning instead of getting paged Friday night.

04

Owner reports out the door

PDF reports assemble themselves on closeout and email to the owner from your maintenance address. The PM stops cobbling them together at month end.

1. 01

   Sending owner emails without a gate

   Owner approval emails carry weight. An agent firing them on its own erodes the trust you spent years building. The gate is non-negotiable on day one and removed only when the confidence data supports it.

2. 02

   Letting the photo step be optional

   Skipping photo verification gives the vendor unilateral say-so on whether the work happened. Photo compare catches the quiet failures (wrong unit, wrong fixture, original problem still visible) that erode owner trust.

3. 03

   Generic templates instead of your voice

   Generic vendor and resident comms read like a chatbot. Comms drafted in your voice, using your phrasing on the kinds of issues you handle, are what keep the agent invisible to residents and owners.

4. 04

   Triage without classifier confidence

   Classifications without a confidence score get routed to the wrong vendor and burn truck-rolls. The classifier should be willing to admit it does not know, and route to a human in that case.

5. 05

   Acting on parsed amounts without confirmation

   Inbound emails can be ambiguous (parts vs labor vs total, schedule dates with no year). The parser writes the amount and proposes the next status; the human still confirms on the gated calls.

6. 06

   Closing tickets without verifying completion

   Vendors mark themselves done. Closing on that signal alone misses the cases where the work did not match the report. Verification requires either a photo compare verdict, an invoice that matches the work, or a resident confirmation.

7. 07

   Black-box agent runs

   If the agent did the work but the PM cannot see what it did, when, or why, the agent is not trusted. Every send, parse, and status change has to post as a readable update on the same item the team already opens.

Pre-ticket troubleshooting

The phase before a work order exists, where an agent chats with the resident and either resolves the issue or escalates with the classification and history preserved.

Form-path triage

The fallback triage path for any ticket that does not come through the chat: form submission, inbound email, voicemail. Categorization, priority, suggested vendor, summary.

Inbound parser

The agent that watches the maintenance mailbox, matches every reply to the right work order, classifies the sender, and extracts the structured information (amounts, dates, completion signals, owner intent) into the right columns.

Gated comms

Comms the agent has drafted and holds until a human confirms. Used for owner emails, large dispatches, and any send where the cost of being wrong is high.

Approval gate threshold

The dollar amount above which a vendor estimate requires owner approval before work can proceed. Encoded per client, usually tied to the property's on-site reserve.

Photo verification

Comparing pre-work and post-work photos to confirm the right fixture was worked on, the original problem is gone, and no new damage was introduced. Used as the gate on automatic closeout.

Suggested next status

A column on the work order that the inbound parser writes when it has enough confidence to recommend an action but the agent will not move the ticket without a human tap.

Owner PDF report

The closeout artifact assembled on completion: cover page, original problem, triage history, pre and post photos, closeout note, chronological activity log. Emailed to the owner from the maintenance address.

13 / How we do it

How LaunchEngine runs maintenance operations