A meeting room books for eleven o’clock. The presenter arrives at 10:55. The room is hot, the projector will not connect to the laptop, and the coffee jug at the door is empty. Three problems, three queues: HVAC is a facility ticket, the projector is somewhere between IT and AV, and the coffee jug is housekeeping. By 11:10 the presenter has emailed three teams and given up.
This is what a facility help desk is supposed to fix. And in 2026, it is also where the most interesting changes are happening in service management, because the line between facility and IT has become administrative rather than real.
What a facility help desk actually is
A facility management help desk is the place employees report and request anything to do with the building and the workplace: maintenance, cleaning, HVAC, room bookings, visitor logistics, catering, security exceptions, contractor coordination. The platform behind it intakes the request, classifies it, dispatches the right person or contractor, tracks resolution, and closes the work. Same shape as an IT help desk; different subject matter.
In a smaller organisation the facility help desk is an email inbox and a whiteboard. In a 200-person organisation it is a SharePoint list. Past 500 people it becomes a real platform, usually because three things hit at once: the volume of requests outgrows tribal knowledge, the COO asks for a workplace performance report nobody can produce, and the facility team starts losing requests to “I emailed you last week, did you see?”
The good news is that the platform technology to run this well exists and has for a while. The interesting question in 2026 is not whether to have a facility help desk. It is whether it should be a separate platform from the IT help desk.
The artificial wall between IT and facility
For most of the last twenty years, IT and facility were managed in different platforms by different teams reporting to different leaders. The reasons were historical, not architectural. ITSM platforms (ServiceNow, BMC Helix, TopDesk, Jira Service Management) grew up serving IT. IWMS platforms (Planon, Spacewell, IBM TRIRIGA) grew up serving facility and real estate. The two product categories evolved separately. So did the buyers.
The wall is starting to look expensive.
Three reasons. First, the employee does not care which team owns the request. “I cannot get online in meeting room 4” is half an IT problem (the access point in that room is offline) and half a facility problem (the room itself has booking metadata that needs updating). When the help desks run on separate platforms, the employee submits the ticket twice, in two systems, with different reference numbers.
Second, the data is more shared than the platforms admit. The CMDB knows the AP in meeting room 4 exists. The facility platform knows meeting room 4 exists. Neither knows the other knows, so neither can correlate the access-point incident with the room-booking pattern that follows it.
Third, the buyer who pays for both is increasingly the same person. The COO, the head of business services, the operations director, somebody whose remit covers the whole employee surface. That buyer wants one dashboard, one cost report, one platform conversation with the vendor, and one implementation programme instead of two.
The wall persists because changing it requires both teams to agree on a platform, which means it usually does not happen until a contract renewal forces the conversation. The teams that did make the move are not going back.
What changes when both run on one engine
The visible change is the dashboard. Instead of two views that disagree on what “open tickets” means, the COO sees one timeline of every request flowing through the building, IT and facility together, with the slow ones at the top.
The less visible change is what the AI can do across both. Three examples worth being concrete about.
Onboarding as one event. A new hire, Daan, starts next Monday. The HR system fires the event. The platform creates an IT laptop request, a facility desk allocation, a visitor pass for the office manager for the first day, and an Outlook welcome session. One trigger, three teams, no email chain. The trace of every action is on the same timeline. When the laptop is late, the office manager knows without having to ask IT.
Cross-domain incident correlation. The Wi-Fi in the south wing is patchy on Wednesday. The IT side sees a cluster of “cannot connect” tickets. The facility side sees an HVAC contractor scheduled the same morning in the south wing’s ceiling space. The platform correlates them and surfaces the candidate root cause to the on-call engineer: the contractor likely brushed against the access-point cable. Two systems would have produced two unsolved investigations.
Workplace performance, honestly measured. The COO asks “how is the workplace performing this month.” The answer is not three slides from three teams; it is one dashboard with the real numbers: average time to resolve a facility request, IT incident MTTR, room utilisation, visitor flow, asset cost per employee. Numbers that disagree get reconciled inside the platform, not inside the meeting.
Where IoT actually helps (and where it is a distraction)
Smart-building IoT is real, and most of what gets sold under “IoT” is a distraction.
The places it earns its keep:
Occupancy sensors turn the meeting-room booking conversation from anecdote to data. The room that gets booked for eight people and never holds more than three is now visible. The team that books two rooms back-to-back because they keep over-running can be talked to with evidence rather than memory.
HVAC and air-quality sensors enable predictive maintenance for the systems where reactive maintenance is most painful. A boiler that is starting to drift can be serviced on a Thursday morning instead of failing on a Friday night.
Infrastructure self-reporting for printers, coffee machines and meeting-room AV closes the loop on consumables and minor maintenance without an employee having to file a ticket.
The places it is a distraction:
Sensors on every desk generate a lot of data and very few decisions. If your facility team is not already producing decisions from the room-level data, desk-level data will not help.
Real-time everything dashboards are usually a sign that nobody knows which signal matters. The right shape is the platform doing the filtering and surfacing the small number of signals that warrant action.
The honest framing: IoT helps when it removes work or enables a decision you could not have made otherwise. The rest is a slide deck.
Asset management is the shared substrate
The conceptual breakthrough that makes the cross-domain platform work is treating IT configuration items and facility assets as the same kind of object. A laptop and an HVAC unit have the same lifecycle: acquire, deploy, maintain, depreciate, retire, replace. The contract has the same shape, the maintenance window has the same shape, the cost-per-employee report rolls up the same way.
Once both inventories live on one engine, three things stop being a problem. The asset cost report stops being two spreadsheets that disagree on which department owns what. The contract renewals stop being a surprise because the same calendar surfaces them. The compliance audit (especially in regulated industries) stops being two evidence packages that have to be assembled separately.
The teams that fought hardest about this in the past were finance teams, who insisted IT capex and facility capex were different categories. They were not wrong about the accounting; they were wrong about the data model. The data model is the same. The accounting tags itself.
When you should still keep them separate
We are not pretending there are no scenarios where two platforms is the right answer. There are.
If your facility scope is dominated by capital projects and real-estate portfolio management (lease accounting under IFRS 16 or ASC 842, capex tracking, space planning at portfolio scale), a dedicated IWMS like Planon or IBM TRIRIGA is the right facility platform. The Gfacility surface for facility is workplace operations, not corporate real estate.
If your IT scope is dominated by very deep ITSM with hundreds of process variants and a dedicated platform team, ServiceNow or BMC Helix are usually the right ITSM platform. Pairing them with a separate facility platform is the right shape if both estates are at that depth.
The cross-domain unified platform shines in the middle: organisations large enough to need real platforms but not so large that each estate justifies its own enterprise programme. Mid-market and lower-enterprise, in market terms. That is roughly the range Gfacility is built for.
What we built
Gfacility is one engine for IT, Facility and Workplace, with the same data model across all three domains. The facility help desk runs in the same platform as the IT help desk and the workplace booking system. The asset inventory is one inventory. The CMDB and the facility asset register are not two databases; they are two queries.
The AI assistants take requests in Teams, Outlook, Slack and chat in plain language: “book the green room with catering for Tuesday at 14:00 for six people,” “the printer on floor 3 is offline,” “register a visitor for Friday.” The digital workers (autonomous agents) close the routine work without a human in the loop where it is safe. Every action is logged and reversible.
We host in the EU with ISO 27001 and GDPR baked in. The implementation is a week with a single solution architect, with importers for Axxerion, MCS, TopDesk and Planon on the facility side and ServiceNow, Jira Service Management, BMC Helix, Freshservice on the IT side. The side-by-side comparisons cover the detail.
The short version
The facility help desk in 2026 is not really a question about a help desk. It is a question about whether the wall between IT and facility is worth what it costs. For most growing organisations, the answer has flipped from “yes, it is how we have always done it” to “no, and the renewal is the moment to fix it.”
If you run IT, Facility or Workplace and the COO has been asking for one dashboard, book a 30-minute call and bring an export of your last quarter’s tickets from both teams. We will run them through the importer and show you, on your data, what one timeline looks like.
Frequently asked questions
What is the difference between an IT help desk and a facility help desk? +
The IT help desk handles incidents and requests about technology: laptops, accounts, software, network, identity. The facility help desk handles incidents and requests about the building: cleaning, maintenance, HVAC, room bookings, visitor logistics, catering. The work is shaped the same way (intake, classify, dispatch, resolve, close). The data is just about different things.
Why is splitting them a problem? +
Because the employee submitting the request does not care which team owns it. 'I cannot get online in meeting room 4' is half an IT ticket (the access point) and half a facility ticket (the room booking). When the two help desks run on separate platforms, the employee gets routed three times and the COO has no single view of how the workplace is performing.
Where does IoT actually help? +
Three places. Occupancy sensors flag rooms with broken booking patterns. HVAC and air-quality sensors enable predictive maintenance instead of reactive tickets. Print and coffee infrastructure can self-report when consumables are low. Everywhere else, IoT is a distraction that puts more data into your queue without removing work.
Can one platform really run both IT and facility? +
Yes, if the data model was designed for it. Bolting facility onto an ITSM tool through custom request types works for a while and then breaks when the facility team wants their own backlog and reports. The cleaner answer is one engine where an incident, a request, a room booking, a visitor and an asset share the same model and timeline.
How is asset management different in facility vs IT? +
Less than you would think. IT tracks laptops, monitors, accounts and software entitlements. Facility tracks chairs, plants, HVAC units, coffee machines and meeting-room AV. The lifecycle is the same: acquire, deploy, maintain, retire, replace. When both inventories live on one engine, the asset cost report stops being two spreadsheets that disagree.
What does AI close on the facility side? +
Room-booking exceptions ('the room I booked is too small, can you swap me'), recurring maintenance tickets that match a pattern ('the lift on floor 3 keeps reporting the same error code'), catering changes ('add three more lunches to Tuesday'), and the visitor-management edge cases that used to require an office manager to email three people.