What Is a Service Desk in Facility Management?

Every facility issue starts the same way: someone notices something wrong and has to tell somebody who can fix it. What happens between that moment and the repair being logged, assigned, and closed out is the entire job of a facility management service desk — and whether that process takes five minutes or five phone calls is usually the difference between a well-run building and a chaotic one. The term gets used loosely, covering everything from a shared inbox to a fully staffed 24/7 operation with its own software, which makes it hard to know what a facility service desk should actually include. Get it right, and requests move through a predictable pipeline with a clear owner at every stage; get it wrong, and issues get reported twice, forgotten once, and resolved by whoever happened to answer the phone. In this article, we cover what a facility management service desk is, what it actually does, and how to tell a working one from a ticket graveyard.

A facility management service desk is the single point of contact for reporting, triaging, and tracking facility-related issues and requests — from a broken light fitting to a full HVAC breakdown — across one building or an entire portfolio. It sits between the people who notice a problem (staff, tenants, customers) and the people who fix it (in-house teams or contractors), turning an informal report into a logged, assigned, and trackable task. A service desk can be a person answering a phone line, a shared inbox with a triage process, or dedicated software with its own workflow — the format varies, but the function is the same: nothing gets lost between "someone noticed" and "someone fixed it."

Behind the single point of contact sits a specific, repeatable sequence of work. A functioning facility service desk typically covers:

• Request intake: capturing a reported issue through phone, email, app, or web form, with enough detail — location, asset, urgency — to act on it.
• Triage and prioritisation: sorting requests by urgency and type, so a burst water pipe is not queued behind a flickering light.
• Assignment and dispatch: routing the task to the right in-house team member or contractor based on trade, availability, and site.
• Status tracking: keeping the requester and the facilities team updated on whether a task is open, in progress, or resolved.
• Escalation: flagging tasks that are overdue or breaching a response-time SLA, before they become a bigger problem.
• Closure and documentation: confirming the work is done, recording it against the asset’s history, and closing the loop with whoever reported it.

A service desk is not a standalone tool — it is the front door to the entire facility management operation, and its output is only as good as what happens after a ticket is logged. A request comes in, gets triaged and assigned, and then depends on the same maintenance plan, contractor network, and documentation standards that govern the rest of the operation to actually get resolved. Where the service desk adds distinct value is in visibility: it turns a scattered set of phone calls and hallway conversations into a single, searchable record of what went wrong, where, and how often — data that a facilities team can use to spot recurring problems long before they become a full asset failure.

A single site can get away with an informal reporting process — everyone knows who to call, and the building is small enough that nothing stays broken for long. That informality breaks down completely once a portfolio grows past a handful of locations: without a central intake point, requests arrive through a dozen different channels, get triaged inconsistently by whoever happens to answer, and leave head office with no reliable way to see which sites generate the most issues or which contractors respond fastest. A service desk that spans every location turns that scattered picture into one queue, one set of response-time standards, and one place where a regional or head-office team can see exactly what is happening across the portfolio without calling each site individually.

The table below sets out the main trade-offs between running a service desk internally and having one managed externally.

Whether it is run in-house or outsourced, a facility service desk worth relying on needs a few things in place:

• Multiple intake channels: phone, email, app, and web form, so a request can be logged however the reporter finds easiest.
• Clear response-time standards: defined SLAs by urgency level, with visibility into whether they are being met, not just a promise in a contract.
• Asset and location context: every ticket linked to a specific site and piece of equipment, not a vague text description.
• Escalation built in: automatic flags when a ticket is ageing or a deadline is at risk, rather than relying on someone to notice.
• Reporting across sites: a single view of ticket volume, response times, and recurring issues across the whole portfolio, not one spreadsheet per location.

Most facility service desks that stop being useful fail in a few predictable ways:

• Too many uncoordinated intake channels: phone, email, and three different inboxes with nobody responsible for consolidating them into one queue.
• No defined ownership per ticket: a request that is "assigned to the team" rather than to a named person or contractor tends to sit until someone happens to notice it.
• Treating closure as optional: tickets that get fixed but never formally closed leave a service desk’s data unreliable and its reporting meaningless.
• No feedback loop to the requester: staff and tenants who report an issue and hear nothing back stop reporting issues at all, which hides problems rather than solving them.
• Measuring activity instead of outcomes: tracking how many tickets were logged says little; tracking how many were resolved within the target time says everything.

Wowworks gives facility teams a single intake point for requests across every site, with tickets triaged, assigned to a vetted contractor, and tracked through to a documented close-out. Instead of a service desk that depends on someone remembering to update a spreadsheet, requests, response times, and completion records live in one system that head office, contractors, and site teams all see the same version of. For organisations running a service desk across multiple locations, that structure is what keeps response times measurable and recurring issues visible — instead of buried in a hundred separate phone calls.