← All guides

What is an AI maintenance coordinator?

An AI maintenance coordinator takes the repair requests that arrive after hours and between everything else, follows your response rules, contacts the right people, and records the next step. This guide explains what that means in practice, drawn from how Openhour's Maintenance Dispatcher is designed.

What an AI maintenance coordinator does

The agent takes requests from the channels you connect, gathers details, and follows your response protocol. It can contact your on-call team or vendors within approved limits, then record what happened. Your team spends less time passing messages between residents, vendors, and each other.

It starts with a text at 2am, an email or portal request, a voicemail, or a scheduled check. Then it checks your response protocol, collects the relevant details, contacts the right on-call person, and sends approved next steps.

  • Resident response recorded
  • On-call technician paged
  • Vendor response recorded
  • Work order logged

What it needs access to

To do the work, the agent reads on-call schedule and backup contacts, vendor list by trade, owner approval thresholds, and current local weather. The only things it can change are your business phone line, and property, unit and work orders.

Coverage depends on the connected channels, vendor availability, and your approved response protocol. Live call answering requires a separately scoped phone setup; voicemail processing is not the same service.

What it handles on its own, and when it asks

Within the rules you set, the agent handles answering the resident, your approved troubleshooting messages, dispatch within your cost threshold, and scheduling a vendor.

It stops and asks a person about anything over your spending limit, any decision to charge a resident, a resident who sounds frightened or angry, and the third occurrence in the same unit. Some of those never move to the agent, no matter how long it has been running.

What it should never do

Replace your emergency response service or decide who owes repair costs. Your existing emergency coverage stays active during testing. Before launch, we agree who receives urgent alerts, who backs them up, and which actions are authorized. Unclear or unanswered requests go to a person.

Where the time comes back

It saves the time your team spends collecting request details, contacting vendors, and updating work orders. Your team stays responsible for emergencies and exceptions.

What it is not

It is not an emergency service. Your existing emergency coverage stays responsible for urgent situations during testing and after launch. Before an agent goes live, we agree who receives urgent alerts, who backs them up, and which actions it is allowed to take.

Answering live phone calls is a separate project from processing texts, emails, portal requests, and voicemails. Ask any vendor which of those it actually covers.

Questions to ask any vendor

Whether you are looking at Openhour, a feature built into your property management software, or a standalone product, the same questions tell you whether the agent will actually work for your company.

  • What does it connect to in my software today, and what would my team still do by hand?
  • What does it do on its own, and what does it ask a person about first?
  • Can I see it run on my process, with my rules, before it touches real records?
  • What happens when it cannot finish? Who is told, and how?
  • Who hosts it, who fixes it when my software changes, and what is the bill?

How we would help

Our property management page describes the maintenance problem and how we would build a system for it.

Common questions

What does the Maintenance Dispatcher Agent do?

The agent takes requests from the channels you connect, gathers details, and follows your response protocol. It can contact your on-call team or vendors within approved limits, then record what happened.

What does the Maintenance Dispatcher Agent need access to?

Coverage depends on the connected channels, vendor availability, and your approved response protocol. Live call answering requires a separately scoped phone setup; voicemail processing is not the same service.

What will the Maintenance Dispatcher Agent never do?

Replace your emergency response service or decide who owes repair costs. Your existing emergency coverage stays active during testing. Before launch, we agree who receives urgent alerts, who backs them up, and which actions are authorized. Unclear or unanswered requests go to a person.

More guides

Tell us what’s taking up your team’s time.

Bring the work that keeps getting stuck. We’ll talk through your priorities and what it would take to move them forward.

What’s taking up your team’s time?

First, share your details. Next, choose a time on our calendar. We’ll bring business and technical experience to a conversation about the work slowing your team down.

On our first call

  • Talk through the operational work slowing your team down.
  • Explore the workflow, technical requirements, and a useful starting point.
  • Talk through the right service and next steps.

We’ll explain what fits the monthly implementation service and what would need a separately scoped custom build.