Taking the service desk to HR, facilities and finance (ESM)

Enterprise service management (ESM) means using service desk tools outside IT. For a mid-market company it usually starts informally: HR sees IT's portal and asks for the same thing for leave questions, facilities wants a place for desk moves, finance wants purchase requests tracked. Done well, employees get one place to ask for help.

When is the right time to extend?

Extend after IT's own desk is stable: requesters use the intake path, categories are settled and reporting works. Bringing another department onto a desk that is still changing every week spreads the disruption. A sensible order is one department at a time, starting with the team that has the most repetitive requests.

What does each department need?

Each team needs its own catalog items, its own queue and its own owners, and some need privacy that IT does not:

• HR: benefits, payroll and employee lifecycle questions, with strict visibility so only HR sees personal cases.
• Facilities: desk moves, repairs and access cards, often with location fields and contractor tasks.
• Finance and procurement: purchase requests and invoices, with approval chains by amount.
• Legal: contract reviews and questions, with intake that captures the documents.

How do vendors package cross-department use?

Most platforms in this guide now describe some route for other departments, but they package it differently. On the pages we read:

• monday service names AI agents for HR (benefits, employee lifecycle, payroll and compensation), procurement, customer support, facilities, finance, marketing, legal, and learning and development. The plan for those agents is not stated.
• Halo (formerly HaloITSM) includes enterprise service management as standard: HR service delivery, finance and legal, facilities, an employee portal, approval workflows and multi-department routing.
• Freshservice sells Freshservice for Business Teams for HR, finance, facilities and legal, with requests, approvals, tasks, SLAs and routing; its pricing is not shown on that page.
• ServiceDesk Plus lets you set up separate service desk instances for HR, facilities, finance and legal, which ManageEngine says takes under 60 seconds each.
• SysAid gives each team its own secure service space, with segregated data and permissions, for IT, HR, finance, facilities and legal.
• Jira Service Management sits inside Atlassian's Service Collection, which Atlassian says extends service management to HR, facilities, finance and legal.
• Ivanti describes HR service management and facilities service management on the same configuration database.
• Zendesk runs customer service and employee service on one platform, with a self-service employee portal from Suite Growth.
• ServiceNow ITSM describes EmployeeWorks self-service; its departmental products were not in our sources.

The differences are in what comes built in (named agents, templates, separate spaces) and what each extra team costs.

What about licences?

Check who counts as a paid user. If each HR or facilities person who works requests needs an agent or seat licence, the cost of extending grows with every team. Requesters are usually free, but portal user caps can apply, as with monday service's 10 portal users on Standard and 100 on Pro.

Who owns the platform once several teams use it?

Agree a simple model before the second department joins: IT owns the platform settings and integrations, each department owns its catalog items, queues and knowledge. Hold a short monthly review where teams raise changes. This keeps one platform without making IT the bottleneck for every HR form.