Key takeaways
- A facility complaint that exists only in a call log or WhatsApp group has no owner, no SLA clock, and no history.
- Complaint management software for FM companies must be shaped around clients and sites — not a single building helpdesk.
- The record should include assignment, status timeline, attachments, and a path into a service report or quotation.
- If you cannot filter “open, high priority, this site, this week,” you do not have a complaint system. You have a list.
Complaint management software for facility management is not a nicer inbox. It is the difference between “someone was told” and “this ticket is assigned, timestamped, and still open at this site.”
FM companies lose complaints in predictable ways. The client calls the account manager. The account manager messages a supervisor. The supervisor forwards a voice note. By the time a technician arrives, the original severity, the client ticket ID, and the promised window have already drifted.
This article is the practical version of that problem: how complaints actually disappear, what a usable register looks like, and how to run it across several clients without drowning in filters.
Where facility complaints actually get lost
In FM work the complaint is rarely raised by an employee sitting on your LAN. It comes from a client facility manager, a site POC, a security desk, or your own helpdesk taking a phone call. The channels are messy on purpose. Your record cannot be.
- No site on the ticket. “AC not cooling” is not a job. “AC not cooling, Tower B, 4th floor AHU, Client X” is a job.
- No assignee, only a group. Groups create bystanders. An assignee creates a name you can call.
- Status that gets overwritten. If “open” becomes “closed” in the same cell, you cannot show the client when it moved, or who moved it.
- No link to the work artefact. The complaint is closed in a sheet. The report is a separate Word file. The quotation is a third email. Nobody can reconstruct the job later.
If you cannot answer “who owns this, at which site, since when?” in 20 seconds, the complaint is already operationally lost — even if someone still remembers it.
What a complaint record must contain for FM companies
A generic ticketing tool will let you type a subject line. An FM complaint needs fields that match how you bill and how you staff:
- Client company
- Site
- Service (electrical, HVAC, plumbing, housekeeping, and so on)
- Priority
- Description and reported-by details
- Assignee — technician or account manager
- Client’s own ticket ID, when they have a helpdesk
- Attachments: photos, WSR, extra documents
- A status that can move through quotation stages, not just open/closed
DWD FMS complaint management is built on that shape. You raise a complaint with company, site, service, priority, and description. You assign it. Configurable statuses — including quotation stages — keep colour-coded lists honest. Status changes are stored as history, not overwritten.
Assignment is the feature everyone skips and then regrets
WhatsApp feels faster than “creating a ticket.” It is faster for the first 30 seconds. It is slower for the next three days, because there is no owner.
A working assignment model for FM looks like this:
- The person who logged the call can assign a technician in the same action
- Account managers can own the client relationship without owning the spanner
- Helpdesk users can log volume without seeing every other client’s data
- Company admins and site POCs, if you give them a login, see only their organisation
DWD FMS supports technician assignment, account-manager auto-assignment on professional plans, and role-aware views so a client POC is not browsing your other contracts.
Finding a complaint should take seconds, not a scroll
Once you pass a few hundred open items, a flat list is theatre. You need:
- Filters by company, site, status, priority, date, and assignee scope
- Status summary cards you can click to slice the list instantly
- Export to Excel when a client still wants a spreadsheet for their weekly review
That last point matters. Replacing Excel as the system of record does not mean you never email an .xlsx again. It means the export is a snapshot of the truth, not the place the truth lives.
One complaint, one place: comments, files, quotes, reports
The detail page is where FM software earns its keep. For each complaint you should see:
- Profile: dates, assigned user, service, client ticket ID
- Comments and a status timeline
- Pre/post images and work summary files
- Linked quotations
- A service report tab, so nobody asks “where do I start the report?”
From that same record a technician can initiate a service report, and an account manager can raise a quotation from the rate card when the visit is chargeable. Standalone quotations still exist for work that never began as a complaint.
Start free
Log the complaint that is currently living in a chat
Create your DWD FMS portal, add a company and a site, and raise the first ticket. No credit card. Live in under a minute.
How this differs from a generic helpdesk or enterprise CAFM
| Generic helpdesk | Enterprise CAFM / IWMS | FM-shaped complaint system (DWD FMS) | |
|---|---|---|---|
| Organising idea | Requester and agent | Building, space, and asset hierarchy | Client company → site → service → technician |
| Time to first ticket | Hours | Weeks to months | Minutes after signup |
| Field completion | Often desktop-only | Varies; often a separate mobile module | Technician app for status, photos, signature, report |
| Commercial follow-through | Rarely | Work orders; quoting may be a different product | Quotations from per-client rate cards, linked to the complaint |
If you operate one campus for yourself, a full IWMS may be the right buy. If you are an FM contractor juggling ten clients, buying a campus stack is how projects stall. You needed a complaint register that your technicians will actually finish.
A one-week way to stop the leaking bucket
- List every open complaint from WhatsApp and the spreadsheet. Do not tidy history. Capture what is still live.
- Create companies and sites first. A ticket without a site is how the mess restarts.
- Agree five statuses, not twenty. Example: Open → Assigned → In progress → Quotation → Closed.
- Give technicians the mobile app on day one. If closure still requires a laptop, they will keep using WhatsApp.
- Send the client the first PDF report from a real closed job. That is the moment the new process becomes real for them.
Frequently asked questions
Can clients raise complaints themselves?
Yes, on plans that include client portal access. Company Admin and Site POC logins are scoped to their own company or site, so they are not browsing your other contracts.
Can we attach photos to a complaint before the report exists?
Yes. Complaints in DWD FMS support attachments, including pre/post images and work summary reports, plus comments and the status timeline.
Can we still export to Excel for a client MIS?
Yes. Export is a reporting convenience. The live register stays in the portal so two people are not editing two different files.
What if the same issue comes back next month?
Because complaints sit on the same company/site structure as assets, you can see that the unit has a history instead of treating every call as brand new.
About this guide. Written by the Digital Work Desk facility team from the complaint workflows we ship: raise/assign, colour-coded statuses with full history, filters and summary cards, attachments, and a service-report tab on the same ticket. If you want the product view, see complaint management in DWD FMS.
The next client call is the test. Put it in a system with an owner, not a group.