Maintenance handled
before the second complaint.
A property manager spends half the day routing tickets — read the email, find the right plumber, schedule access, follow up. A Loomal agent reads every maintenance request, picks the right vendor from the approved list, and schedules access in-thread before tenants get frustrated.
API Primitives used
mail_list_messagesCatch the request
Agent watches the maintenance inbox for incoming tenant complaints and triage them by urgency and category.
vault_getPull approved vendors
Vendor list with trade specialties, rates, and contact info lives in the vault, scoped per property.
calendar_createBook access window
Tenant and vendor get a coordinated access window — confirmed in-thread with both parties.
Maintenance is dispatch chaos.
A property manager handling multiple buildings gets 30 maintenance requests a week. Each one needs the right trade, the right vendor, the right access window, the right follow-up. The work is mechanical but the volume eats hours, and a missed ticket turns into an angry call to the owner.
An agent owns the dispatch layer. Tickets get categorized, vendors get assigned, access gets coordinated — with humans only stepping in for emergencies or escalations.
How to build it.
mail_list_messagesRead the request
Agent picks up incoming tenant maintenance emails, classifies the issue, and rates urgency.
vault_getPick the vendor
Agent reads the approved vendor list from the vault and picks the right trade based on issue type and property.
calendar_createCoordinate access
Agent threads tenant and vendor together, finds an access window, and creates calendar events for both.
Example prompt
“Watch maintenance@. For every request, classify the issue, pick the right vendor from our approved list, and coordinate an access window with the tenant — all in-thread.”
What property managers build.
Routine repair routing
Agent handles routine plumbing, HVAC, and electrical tickets with consistent vendor selection.
Emergency escalation
Urgent issues like leaks or no-heat get escalated immediately and routed to on-call vendors.
Multi-property portfolios
Each property gets its own vendor list and routing rules from a single agent identity.
Tenant communication
Agent keeps the tenant updated in-thread on vendor status, ETA, and completion.
Invoice handling
Vendor invoices get matched to the originating ticket and routed to AP for payment.
Why dispatch belongs to an agent.
Property management software handles the ticket database. It doesn't handle the email conversations between tenants, vendors, and managers — which is where the actual work happens. An agent that lives in the email layer dispatches faster and keeps every party informed.
Loomal gives property management an identity that owns the inbox, the vendor list, and the calendar coordination — with full audit per ticket.
Vendor data scoped
Vendor lists and rates live in vault entries scoped per property identity.
Per-ticket audit
Every dispatch decision and access window is logged with timestamp and identity.
Identity per property
Different properties can run on isolated identities with separate vendor relationships.
Route maintenance like a 24/7 dispatcher.
Triage, dispatch, and access — fully autonomous.