Loading…
Use Case
Property managers and facilities teams receive maintenance requests via phone, email, text, and web form. Each one requires someone to read it, classify the type, assess urgency, identify the right technician, and create a work order. For a team managing 200 units, that overhead adds up to hours per day of administrative work.
A custom AI triage system classifies the request (HVAC, plumbing, electrical, appliance), assesses urgency (emergency vs routine vs cosmetic), and routes to the right technician or vendor, reducing the overhead on office staff and ensuring emergency requests get immediate attention regardless of when they arrive.
Works across phone, email, SMS, and web form. Integrates with Appfolio, Buildium, Yardi, ServiceTitan, and custom property management systems.
Tell us about your maintenance intake process.
Six components that handle the full maintenance intake workflow — from multi-channel receipt through work order creation and tenant notification.
Maintenance requests arrive through multiple channels: phone calls (transcribed and classified), email, SMS, and web form. The intake pipeline processes all channels through the same triage logic, a request submitted by email and one submitted by phone get the same classification and routing treatment.
Each request is classified by category (HVAC, plumbing, electrical, appliance, structural, landscaping, pest, or custom categories you define) and by urgency tier: emergency (health or safety risk, structural damage, no heat in winter), urgent (significant inconvenience, potential property damage), routine (standard maintenance), or cosmetic (quality of life improvement, no timeline pressure).
Urgency classification uses explicit signals in the request text (water actively leaking, no heat, electrical smell, gas smell) combined with property metadata (e.g., winter weather increases urgency of heating issues automatically). The model is conservative on emergencies: ambiguous requests with any safety signal are classified up, not down.
Classified requests are matched to available technicians based on skill set, current workload, and geographic proximity. The routing logic is configurable: preferred vendors per property, contractor exclusivity rules, and tier-based routing (e.g., all emergency plumbing goes to a specific licensed plumber).
Classified and routed requests create work orders in your property management software: Appfolio, Buildium, Yardi, ServiceTitan, or custom systems. All classification, urgency, and assignment data is written directly to the work order. Your team does not need to re-enter information.
When a work order is created, the tenant receives an automatic acknowledgement with the classified urgency and an estimated response time. When a technician is assigned, the tenant gets the assignment confirmation and a scheduling link. Status updates are sent when the work order is updated or closed.
From request received to tenant acknowledged, the full sequence.
Request received via any channel
A tenant submits a maintenance request by calling the property office (call is transcribed), sending an email, texting, or submitting a web form. All channels feed the same intake pipeline, the triage logic does not change by channel.
Classification and urgency scoring
The request is classified by type and urgency tier within seconds of receipt. Emergency requests (anything involving safety risk, structural damage, loss of essential services, or active water damage) are flagged immediately and trigger an escalation notification to the property manager.
Technician matching
The routing engine matches the request to available technicians based on category, location, and current workload. For emergencies, the highest-priority available technician is assigned immediately. For routine requests, scheduling optimisation considers travel time across open work orders.
Work order creation
A work order is created in your property management system with all classification, urgency, and assignment data pre-populated. The property manager or maintenance coordinator reviews the work order. They confirm or adjust the assignment before it is dispatched to the technician.
Tenant acknowledgement sent
The tenant receives an automatic acknowledgement via the same channel they submitted (or email/SMS as configured): their request was received, the urgency classification, and the expected response timeline for their tier.
Status tracking and close-out
As the work order progresses (technician assigned, scheduled, on-site, completed) status updates are sent to the tenant automatically. The work order is closed in your system when the technician marks it complete. Tenant satisfaction surveys are sent post-close.
Property and facilities teams with meaningful request volume and a need to handle intake consistently across channels and hours.
Maintenance coordinators at mid-sized property management firms spend a large portion of their day triaging incoming requests, calling tenants for more information, and manually assigning work orders. AI triage handles the initial classification and routing, the coordinator reviews assignments rather than building them from scratch.
Facilities managers at multi-site companies receive maintenance requests from employees across dozens of locations. A triage system that classifies request type, assesses urgency based on the facility and season, and routes to the right contractor by location reduces the manual overhead of managing requests across sites.
Home service franchise brands that centralise intake for multiple franchisees need consistent classification and routing regardless of which franchisee's territory the request comes from. A shared triage pipeline handles intake uniformly and routes to the correct franchisee based on zip code or service area.
We’d rather decline than take a project that won’t deliver value.
Property managers who want to fully automate emergency dispatch
Emergency maintenance situations (gas leaks, structural damage, active flooding) require human confirmation before dispatch. The system classifies and escalates emergencies immediately, but a human must confirm the dispatch. We will not build a system that autonomously dispatches emergency contractors without a human in the loop. The stakes are too high.
Teams with fewer than 20 maintenance requests per week
Below a certain request volume, the overhead of an automated triage system does not justify the build cost. For very small portfolios (under 20 units or under 20 requests per week), a simpler templated intake form and a manual routing checklist is more appropriate. The economics of custom AI triage become favourable above that threshold.
Tell us your approximate monthly request volume, the channels you receive requests through, and which property management system you use. We'll reply within one business day.