WhatsApp chatbots for facility service requests

What it actually does

Someone in a building notices a problem. A tap is leaking, the air conditioning in a meeting room is not working, a light is out.

Today they usually have to call a number, send an email, or log into a portal they have never used. Many will not bother, which means the problem goes unreported until it gets worse.

With a WhatsApp channel, they message a number the same way they message anyone else. A bot asks a short series of questions: what is the problem, where is it, a photo if useful. That becomes a work order in your facility management system, assigned by the usual rules. When the job is done, the user gets a message telling them so.

The point is not the technology. It is that you remove the step where someone has to learn your system before they can tell you something is broken.

Why WhatsApp rather than an app or portal

Occupants, tenants, visitors and subcontractors are not going to install your app. They will not remember a portal password they use twice a year.

WhatsApp is already on their phone and they already know how it works. There is nothing to install, nothing to learn, and no password to reset. In the Gulf and across much of Asia and Latin America, it is the default way people message businesses, so it also feels normal rather than unusual.

A second advantage is that the conversation has a history. The user can scroll back and see what they reported and what happened, which cuts down chasing calls.

How the flow usually works

A typical setup has four parts.

The user messages your WhatsApp business number. A bot handles the conversation, asking what the problem is and where. It may offer buttons or a short list rather than free text, which keeps the data clean.

The bot passes the details to your CAFM or CMMS system, which creates a work order, applies your priority rules and assigns it to a team or contractor.

The technician receives the job in the normal way, through the mobile app or their usual queue. Nothing changes in how the work itself is managed.

Status updates flow back to the user’s chat when the job is accepted, scheduled and completed.

Some setups also let the bot answer simple questions without creating a job, such as the status of a request the user made earlier.

What it is good for

• High volume, low complexity requests such as lighting, cleaning, temperature complaints and minor repairs
• Buildings with many occasional users, such as residential communities, retail, schools and shared offices
• Reducing calls to a helpdesk that spends its day logging routine jobs
• Capturing problems that would otherwise go unreported
• Getting a photo at the point of reporting, which helps the technician arrive prepared

What it is not good for

Be honest about the limits, because this is where these projects disappoint.

It is not an emergency channel. A gas smell, a fire alarm, someone trapped in a lift, or a major water leak needs a phone call to a human. Say this clearly in the bot’s welcome message and repeat it if the user’s words suggest urgency.

It is not a replacement for a helpdesk. Complicated requests, anything needing negotiation, and anything the bot cannot understand still needs a person. Always build a clear route to a human, and make sure someone is actually at the other end.

It is also not a good fit where the reporter needs to be verified before a job can be raised, unless you handle identity separately. Anyone with the number can message it.

What you need to set one up

Five things, roughly in this order.

A WhatsApp Business Platform account. This is Meta’s business messaging product, not the consumer WhatsApp app or the small business app. It requires business verification, which takes time, so start it early.

A phone number dedicated to the service. It cannot be a number already registered to a personal or business WhatsApp account.

A provider or platform to run the conversation. Either your CAFM vendor offers this built in, or you use a separate messaging platform that connects to your system.

An integration into your facility management system, so messages become work orders rather than sitting in an inbox somebody has to read.

A conversation design. This is the part people underestimate, and it is covered next.

Costs vary by provider and by Meta’s own messaging charges, and those charges have changed more than once. Get current pricing in writing before you commit, and ask specifically how messages are counted.

Rules you need to know

WhatsApp is a permissioned channel. Businesses cannot message people freely.

Users generally have to opt in before you can message them, and there are restrictions on sending messages outside an active conversation. Messages you send to reopen a conversation usually have to use pre-approved templates rather than free text.

These rules are set by Meta and they do change. Treat anything you read about them, including this page, as needing confirmation against Meta’s current documentation before you design your flows around it. Your provider should be able to tell you the current position.

The practical effect for facilities work is small, because the user starts the conversation by reporting a problem. Just be aware if you plan to send proactive notices, such as planned water shutdowns, as that is a different kind of message with different rules.

Designing the conversation

The quality of the conversation design decides whether people use it twice.

Keep it short. Three or four questions is usually enough: what, where, how urgent, and a photo.

Use buttons and lists rather than open text wherever you can. Free text means your data arrives as “aircon broken upstairs”, which nobody can route automatically.

Pull locations from your own asset and location data rather than asking people to type them. If your register is clean, the bot can offer the right building and floor. If it is not, this is another reason to fix it first.

Confirm what was logged and give a reference number. People want to know the message reached something real.

Tell them what happens next and roughly when. Silence after a report is the main reason people go back to phoning.

Support the languages your building actually uses. In the UAE that usually means at least English and Arabic, and often more depending on the site.

Security and data

Two things to settle with your legal or compliance team before launch.

You will hold phone numbers and message content, sometimes including photos of the inside of a building. Decide how long you keep them and who can see them.

Check where your provider stores and processes the data, especially if you have data residency obligations. This is the same question you would ask of any cloud service.

Also plan for what happens when someone sends something that does not belong in a maintenance system, because eventually they will.

How to tell whether it is working

Measure it, or you will only have opinions.

Useful things to look at: how many requests come through WhatsApp compared with phone and email, how many conversations are abandoned partway, how often people escalate to a human, how long jobs raised this way take to close compared with other channels, and whether total reported jobs went up after launch.

That last one is the interesting number. A rise in reported problems is usually a good sign. It means you are hearing about things you previously did not.

Frequently asked questions

Do users need to install anything?

No. That is the main advantage. They message a number from the WhatsApp they already have.

Can a WhatsApp bot handle emergencies?

It should not. Route urgent situations to a phone number and say so clearly in the bot’s first message and in any reply where the wording sounds urgent.

Does it work with any CAFM system?

Only if the system can accept requests from an outside channel, through an integration or an API. Ask your vendor directly whether they support it, and whether it is built in or needs a third-party platform.

Can it send updates as well as receive requests?

Yes, though messaging rules affect what you can send and when, particularly for messages outside an active conversation. Confirm the current rules with your provider.

What languages can it support?

Whatever you build. Match the languages your occupants actually speak rather than defaulting to English alone.

Is WhatsApp secure enough for this?

Message content is encrypted in transit, but the more important questions are who can see the data once it reaches your provider and your CAFM system, and where it is stored. Ask those.

For other facility management terms explained in plain English, see our FM glossary.