AI in Facility Management

Agents for People Who Do Not Have Time for Software

Oct 26, 2026 11 min read

AI agents suit facilities teams that have no time for software because the agent does the logging, assigning, chasing and checking inside your system, while your people keep working the way they already do: by phone call, message or voice note.

At five sites, one coordinator can still re-key every request and chase every vendor. At 300 sites, the same steps pile up faster than any team can clear them, and the first things to slip are the close-out notes, the vendor follow-ups and the invoice checks. This article explains why software adoption has been hard in facilities management, what changes when agents take over those steps, and how to check that your team is getting hours back.

Key takeaways

Software adoption stalls in facilities because the second step, entering the work into a screen, is the first thing a busy team skips.
An agent completes that second step as part of doing the work, so the record fills in without your team opening a screen.
Your team keeps using the phone, WhatsApp, email and voice notes it already uses, which means there is nothing new to learn.
The agent decides routine steps inside rules you set, and a person decides exceptions, approvals and anything outside those rules.
You can check the result with a baseline taken before go-live and three numbers reviewed each week: accuracy, exception rate and hours returned.

Why has software adoption been hard for facilities teams?

Software adoption has been hard in facilities because most systems ask the people closest to the work to do data entry after the work is finished. A technician closes a repair and then has to write the completion note. A coordinator takes a tenant call and then has to create the work order, pick the category and set the priority. A manager approves a vendor visit and then has to attach the quote. Each step is small, but each one happens after a full day on site, on calls and with vendors.

The result is a system of record that is only partly filled in. Work orders close days after the job, completion notes are one line long, preventive maintenance tasks are ticked in bulk, and vendor insurance certificates sit in an email folder instead of on the vendor record. Teams do not skip these steps because they dislike the software. They skip them because the hours in a day belong to the building, the tenant and the vendor.

The pattern gets worse as the portfolio grows. Every new site adds more requests, more vendors, more invoices and more statutory certificates, but it does not add more hours to a coordinator's day.

The pressure on teams is also rising. In Johnson Controls' 2026 AI and Digitalization in Facilities Management report, based on a December survey of 260 US facility managers, 72% said labor shortages have a moderate to severe impact on operations. The people who would otherwise do the extra data entry are the same people who are already stretched.

This is a different problem from the one covered in our article on why AI projects in facility management fail, which looks at data quality, scope and change management. This article looks at time: Asking busy people to learn and maintain one more screen has never worked for long.

What changes when agents do the entry and follow-up?

An AI agent is software that takes on one defined job, such as logging a request, assigning a technician, chasing a vendor, checking an invoice or tracking a certificate, and completes it inside your existing system. Because the agent records the work as it does it, your team no longer has to open a screen afterwards to make the work count.

Facilities teams are already moving in this direction. In the same Johnson Controls survey, 67% of facility managers said their organization is already using AI. The 2026 McKinsey State of AI survey of 1,719 respondents also found that nearly three-quarters of high performers fundamentally redesigned their workflows, which means they changed who does each step instead of adding AI to the old steps.

The table shows four common moments in a facilities day, first when your team does the step in the software and then when an agent does it.

Moment in the day	When your team does it in the software	When an agent does it
A tenant reports a fault after hours	Someone writes up the request the next morning and chooses the category, location and priority.	The service intake agent takes the report, structures it and creates the work order at the time of the call.
A job needs a technician	A coordinator checks skills, location and SLA by hand and assigns the job.	The service dispatch agent assigns the job using those same details and confirms the technician is attending.
A vendor owes a quote or a service report	Someone sends reminders and updates the record when the document arrives.	The vendor coordination agent follows up and attaches the document to the job.
An invoice arrives	Finance compares it with the work order, the purchase order and the contract rate card.	The invoice processing agent checks it first and sends only the exceptions to a person, with the reason attached.

The same idea applies to vendor certificates, where the building compliance agent reads each insurance certificate and permit, checks the expiry date and asks the vendor to renew before it lapses. Our guide on how to track vendor and contractor compliance with AI walks through that job in detail, and our guide on how to dispatch work orders with AI does the same for dispatch.

How do teams work with agents without training?

Teams work with agents through the channels they already use. A technician on a plant room visit can send a voice note or a WhatsApp message about what was found. A tenant can call the helpdesk number or send an email about a fault. A site manager can ask in plain words which jobs are overdue at a building and receive the answer in the same conversation. The agent reads what arrives, understands it against the asset, the contract and the SLA, and turns it into a structured record.

Because nothing new is introduced to the people who report, respond or approve, there are no menus to learn, no mandatory fields to remember and no extra login for site staff, contractors or tenants. This matters most for those groups, since they were never going to spend time in a system but their work still needs to reach the record.

Here is a check you can run this week. Pull the list of work orders closed in the last month and count how many have a completion note that says what was found and what was done. If most of them have a one-line note or none, the gap is not carelessness. It is the second step being skipped, and it is the clearest sign of where an agent would return time to your team.

What does the agent decide, and what does your team still decide?

The agent decides routine steps inside rules you agree before go-live, and your team decides everything that carries judgment, risk or cost. Agreeing this line first is what lets a busy team trust the agent without watching it.

Area	The agent decides	Your team decides
Intake	The agent logs the request, sets the category and priority from your SLA matrix, and creates the work order.	Your team decides what counts as an emergency and how the after-hours rules are written.
Dispatch	The agent assigns a technician using skills, location and SLA, and confirms attendance.	Your team decides the exceptions, such as a restricted area or a vendor that needs approval first.
Vendors	The agent chases quotes and service reports and records what arrives.	Your team decides whether to accept a quote, change a vendor or end a relationship.
Invoices	The agent checks each invoice against the work order, purchase order and rate card.	Your team decides how to handle a flagged invoice and approves anything above the limit you set.
Compliance	The agent tracks expiry dates and asks vendors to renew before certificates lapse.	Your team decides whether a vendor with a lapsed certificate may work on site.

Three safeguards sit around these decisions. Agents can first run in shadow mode, where they propose what they would do and a person confirms each one, so you can compare their choices with your team's before anything is automatic. Approval gates and spend limits are agreed before go-live, so anything above them goes to a person. Every action is traced and can be replayed, and the agent acts with the permissions of the person it works for, never above them.

How do you check the agents are giving time back?

You check by taking a baseline before go-live and reviewing three numbers every week afterwards. A baseline is a snapshot of how the work runs today: how many requests arrive each month, how many minutes your desk spends on each one, and how often the first attempt contains an error. Two to four weeks of CMMS history, plus a few days of timing with your team, is usually enough.

The three weekly numbers are accuracy, exception rate and hours returned. Accuracy is how often the agent's choice matches what an experienced person would have chosen, based on a weekly sample. Exception rate is the share of items the agent passes to a person. Hours returned is the desk time saved compared with the baseline, counted after the time your team spends reviewing exceptions.

Measuring matters because projects without it tend to stall. Gartner predicts that over 40% of agentic AI projects will be canceled by the end of 2027, and it names escalating costs, unclear business value and inadequate risk controls as the reasons. A baseline and three weekly numbers answer the second reason directly, because they show the value in hours.

The example below is illustrative and uses round numbers so the maths is easy to follow. These are not Facilio customer results, so replace them with your own baseline.

Step	Calculation	Result
Baseline desk time	500 requests a month, at 20 minutes each for logging, triage, assignment and chasing	10,000 minutes, or 166.7 hours
Requests the agent completes	80% of 500 requests, with 3 minutes of review each	400 requests, or 1,200 minutes
Exceptions handled by a person	20% of 500 requests, at the full 20 minutes each	100 requests, or 2,000 minutes
Desk time with the agent	1,200 minutes plus 2,000 minutes	3,200 minutes, or 53.3 hours
Hours returned before adjustment	10,000 minutes minus 3,200 minutes	6,800 minutes, or 113.3 hours
Hours returned, counted conservatively	75% of 6,800 minutes, to allow for interruptions and variation	5,100 minutes, or 85 hours a month

Counting 75% of the saving is a deliberate choice, because some freed minutes are lost to switching between tasks and not every month looks the same. Our article on how to measure whether an AI agent is working covers the full method, including how to score accuracy.

What can go wrong, and how do you fix it?

When an agent is not returning the time you expected, the cause is usually one of a small number of things, and each has a direct fix.

Johnson Controls' 2026 report found that data quality and integration issues were the biggest barriers to scaling AI for facility managers. That is why several fixes below begin with the records the agent reads.

What you see	Likely cause	The fix
Requests still reach the desk by hand.	A channel your people use, such as a shared mailbox or a site phone, is not connected to the agent.	Connect that channel so the request arrives where the agent can read it.
The exception rate is high on dispatch.	Skills, zones or vendor details are missing or out of date on the record.	Update the records the agent reads, then watch the exception rate over the next two weeks.
Invoices are flagged that should pass.	A rate card or contract term changed and the agent is still checking against the old one.	Load the current rate card and confirm the rule with finance.
The team keeps a side spreadsheet.	People do not yet trust the agent's choices.	Run the agent in shadow mode for longer and share the weekly accuracy number with the team.
Too many items wait for approval.	The approval limit is set lower than your team actually needs.	Review the limit with the budget owner and raise it where the risk is low.

There are also times when it is better to wait. If your requests do not yet have an agreed SLA matrix, or if vendor and asset records are mostly blank, an agent will have little to work from, and the first job is to fill those records. A short clean-up first usually pays back quickly, because every agent reads the same record.

How does Facilio take the change project off your team?

Facilio takes the change project off your team by having FM Ops Engineers do the setup, run the agents with you and keep tuning them. They are Facilio engineers who know facilities operations, and they work alongside your team rather than handing over a manual.

The work follows a clear order. The engineers first map how your operation runs today, then connect the systems you already use, such as your CMMS, ERP and finance system. They set up the agents for the work you choose, confirm the results with your team in shadow mode, and then go live with the approval gates you agreed. After go-live they review the weekly numbers with you and adjust the agents when a number slips.

Facilio has ready agents for service intake, service dispatch, vendor coordination, invoice processing and building compliance, and they run on the Facilio CMMS or on the system you already have. When your process is not covered by a ready agent, the FM Ops Engineers build a custom agent or app for you on the platform. Custom work is built for your operation in weeks, and it is not available off the shelf. Our article on how Facilio takes a custom app from idea to live workflow shows how that works.

Charter Hall, an Australian property funds manager, selected the Facilio CMMS through a competitive tender and now runs invoice processing and contract validation on the same operating layer. Facilio's FM Ops Engineers stayed with the team through the rollout, and you can read the details in the Charter Hall story.

Your part is to share how the work runs today, confirm the rules you want the agents to follow, and decide which exceptions should reach a person. Your team does not need to attend training sessions, because the way they work with an agent is the way they already communicate. If you would like to see how this could work for your operation, you can request an AI agent demo and start with one function.

The bottom line: are AI agents worth it for a team with no time for software?

AI agents are worth it when your team spends hours each week logging requests, chasing vendors and checking invoices by hand, because those are the steps an agent completes without asking your people to learn anything new. They are worth less if your requests have no agreed SLA matrix or your vendor and asset records are mostly empty, so the first step in that case is to fill those records.

Your first step this week is to count how many of last month's closed work orders have a completion note that says what was found and what was done. That count is your first baseline number, and it shows where an agent would return the most time.

Frequently asked questions about AI agents for busy facilities teams

Do facilities teams need training to use AI agents?

No. Your team keeps using the phone, WhatsApp, email and voice notes it already uses, and the agent turns what it receives into structured records. FM Ops Engineers set the agents up and explain the approval rules to the people who use them.

What tasks in facility management can AI agents take on?

Agents can take on request intake, technician dispatch, vendor follow-up, invoice checking and vendor compliance tracking. Each one works inside rules you set, and a person handles exceptions and approvals.

Will AI agents replace my CMMS?

No. The CMMS remains the system of record, and the agents work on it. Facilio's agents run on the Facilio CMMS or on the CMMS, ERP and finance systems you already use.

What happens when an AI agent gets something wrong?

Anything outside the rules you agreed goes to a person with the details attached, and every action is traced so it can be reviewed. You also compare the agent's accuracy with a person's choice each week, so errors show up in the numbers early.

Who looks after the agents after go-live?

Facilio's FM Ops Engineers run and tune the agents with your team. They review accuracy, exception rate and hours returned each week and adjust the agents when a number slips.

About the Author

Abirami N