Property Management: Every Maintenance Request Answered, Dispatched and Tracked to Close
Maintenance is the reason owners hire a manager and the reason they leave one. This is how request intake, vendor dispatch, resident updates and the owner report run in one Kylon room, with spend and escalation still approved by a person.
Maintenance is the service, whatever the contract says
Owners do not hire a manager for the listing photos. Buildium's 2026 industry report found 56 percent of owners say maintenance support is the main reason they hired a property manager, and that it is their number one source of stress (Buildium, 2026 State of the Property Management Industry Report, checked 21 September 2026).
The volume is steady and rising. Hemlane's analysis of more than 193,000 first-party maintenance requests across eight years and all fifty states puts 2024 at 3.30 requests per unit per year, up from 2.93 in 2020 (Hemlane, rental property maintenance requests, checked 21 September 2026). On a 400-unit book that is roughly 1,300 requests a year, arriving without regard for who is on leave.
And they sit. In the same dataset, the all-category median repair closes in 13.1 days, while requests handled by a coordinating service close in a median of 10.1 days against 14.7 days when the landlord manages them directly (Hemlane, repair resolution benchmarks, checked 21 September 2026). The gap is not craftsmanship. It is who is holding the thread between the resident, the vendor and the approval.
Most companies know the tooling exists. Buildium recorded AI adoption jumping from 20 percent in 2024 to 58 percent in 2025, while only 8 percent of companies had fully automated any process (Buildium, 2026 State of the Property Management Industry Report, checked 21 September 2026). Adoption is easy. Finishing a workflow is the hard part, and it is hard because somebody still has to approve the spend.
One room for maintenance, one record per request
The company keeps a Kylon room for maintenance operations and a Database App behind it. Every request is a record: property, unit, resident, category, reported symptom, urgency, access instructions, the vendor assigned, the approval state of the spend, and every message sent about it.
That last field is the one that changes the week. When the owner calls about unit 14, the answer is in the record rather than in three people's memories.
- Request records carrying category, urgency, access notes and the approval state
- Vendor records with trade, coverage area, insurance expiry and typical response time
- Owner approval thresholds written as a rule, not as a habit
- Room guidelines setting what an agent may send to a resident without review
What arrives, what gets prepared, who decides
Maintenance has a hard boundary that most workflows blur: money. An agent can carry a request the whole way and still never approve a dollar of it.
| What arrives | What is prepared for you | What a person decides |
|---|---|---|
| A resident texts that the kitchen is flooding | The request logged as an emergency, with the property, unit, access notes and an immediate acknowledgement drafted | Whether it is an emergency, and which vendor goes tonight |
| A vague request that says the heating is weird | Three clarifying questions drafted to the resident, and the category held open until answered | Whether it needs a diagnostic visit |
| A request that needs a trade you use often | A dispatch email drafted to the right vendor with the unit, access window and scope | The vendor, and the send |
| A quote comes back above the owner threshold | An owner approval request drafted with the quote, the symptom and the consequence of waiting | Nothing moves until the owner answers |
| Four days of silence from a vendor | The stall surfaced with its age, the last message and a chase drafted to the vendor | Whether to chase or reassign |
| The month ends | An owner report drafted from the records: what came in, what closed, what is open and why, spend against approvals | Every figure before it goes to the owner |
Intake, triage and the first reply
Most of the damage happens in the first hour, and it is reputational rather than physical. A resident who gets no reply assumes nothing is happening and calls again, then calls the owner.
In the room, a request arriving by email, form or message becomes a record with an acknowledgement drafted against it. Categorisation matters here because the mix is predictable: plumbing alone is 25.4 percent of all requests, and the top four categories account for 71 percent of everything residents report (Hemlane, maintenance gap analysis, checked 21 September 2026). A small number of well-described categories covers most of the inbox, which is exactly the condition under which drafted triage is reliable.
Emergencies are the exception that proves the rule. The agent flags them and drafts the acknowledgement, and a coordinator makes the call, because the cost of a wrong emergency dispatch at 11pm is not recoverable.
See it in action
The agent reports the quote and the threshold, the manager asks what waiting costs, and the owner request comes back written with nothing booked behind it.
The spend approval is the whole control
Every management agreement has a number in it above which the owner has to say yes. In practice that number is enforced by whoever remembers it, which is why the awkward conversations happen after the invoice.
Writing the threshold into the room makes it structural. A quote under the limit gets a drafted dispatch. A quote over it gets a drafted owner request with the symptom, the quote, the alternative and what happens if it waits. Nothing is scheduled against the owner's money until the owner has answered in the thread, and that answer stays attached to the request.
The owner report writes itself from work that already happened
Monthly owner reporting is usually reconstruction: someone opens six screens and rebuilds a month. When each request already carries its own history, the report is a read of the record rather than a research project.
The draft covers what came in by category, what closed and how fast, what is still open and the reason, spend against approvals, and the requests that needed the owner and are still waiting on them. A person reads it and signs it. Owners notice the third month, when the answer to what happened at the property is the same answer they already read.
What has to be connected
Kylon is not a property management platform and does not hold your leases, ledgers or rent collection. It sits across the tools you run and holds the coordination between resident, vendor and owner.
- Email and messaging, so resident and vendor threads attach to the request, not to a person
- A Database App as the request, vendor and property record everyone reads
- File storage for quotes, invoices, inspection photos and insurance certificates
- Room guidelines carrying the approval thresholds and the emergency definition
- Scoped permissions, so an agent works its portfolio and nothing else
Requests that arrive across shifts need a handover as well as a record. That pattern is covered in shift handovers. For the wider property picture, see real estate use cases.
Where to start
Take one portfolio and one month. Put the request fields and your vendor list into a Database App, connect the mailbox residents already write to, and write the two rules that matter: what an agent may send to a resident without review, and the number above which the owner decides.
“The requests did not get fewer. They stopped being able to go quiet without somebody noticing.”
Your first company harness. Where humans and agents run your business together.
More Use Cases
View all
How a US Hospitality Firm Built an AI Sales Pipeline with Kylon
A US-based hospitality company used Kylon to automate 1,000-contact outreach, AI reply scoring, and lead routing.
How an AI Startup Automated Talent Sourcing with Kylon
A growing AI startup built a recruiting system where agents parse resumes, score candidates against open roles, and manage outreach, all from one room with a structured database.