Blog

ServiceNow Workplace Service Delivery vs elia: An Honest Comparison

Content Marketing Specialist
­­­­­–

Last updated on Aug 20, 2026

You already use ServiceNow for IT, so it’s pretty natural to ask: why not use it for the workplace side too? Facilities requests, desk and room booking, space management, who sits where, all of it.

You can! ServiceNow has a workplace product for it, called Workplace Service Delivery (WSD for short). But it's not the only way to go, and plenty of teams keep ServiceNow for IT and use a workplace platform like elia for everything on the workplace side. The two can connect, so you don’t have to choose one or the other.

So let's go through it:

  • what ServiceNow WSD and elia each are
  • a side-by-side feature comparison
  • who looks after your workplace, and why that's the real decision
  • the all-in cost
  • how to run them together instead of choosing

This post is about the choice between them. If you just want the full rundown on WSD itself, what it is, all the modules, where it falls short, we have a separate ServiceNow WSD overview for that.

TL;DR: The short answer

PICK SERVICENOW WSD IF: You're already all-in on ServiceNow across IT and HR, have a platform team that knows it well, and want to keep everything in one place and on one contract. Just keep in mind that IT will probably look after the workplace too (because on ServiceNow, they do).

PICK ELIA IF: Your office is more than desks and rooms, and you want your workplace team to own the tool instead of IT. You get booking, visitors, service requests, smart lockers, occupancy sensors, and health and safety in one system, and your team can make changes themselves, no waiting on a ticket.

OR DO BOTH: Keep ServiceNow for IT, put the workplace on elia, and connect them so IT requests still go where they need to. You get a tool built for the workplace management team and you keep ServiceNow doing what it's best at. And since people are already in elia day to day, more workplace requests get captured, and the IT ones can flow over to ServiceNow on their own.

ServiceNow WSD vs elia: What each one is

ServiceNow WSD

ServiceNow WSD
Source: ServiceNow

WSD is ServiceNow's workplace suite, built on the Now Platform, the same foundation as its IT and HR products, so everything sits in one system. That’s quite handy: a new hire gets added in HR, for example, and that can kick off the IT work for their laptop and the workplace setup at the same time.

Its limit: it's a workplace layer on an IT platform, so it gets set up and looked after like one.

What you get:

  • desk, room, and parking booking from the Employee Center, your phone, or Outlook
  • workplace visitor management (the lobby kiosk is a separate piece)
  • service requests worked as cases (on paid fulfiller licenses)
  • floor plans, space planning, and move management
  • indoor mapping and third-party sensor data through Workplace Connectors
  • preventive and corrective maintenance, for spaces and equipment
  • lease administration to track property contracts and renewal dates
  • close to 20 apps altogether, including a Concierge AI agent, though most teams will only use a few of them

elia

elia
Source: elia

elia is a standalone workplace operations platform, so you’re getting it for the workplace rather than as part of a bigger enterprise suite. It works with Microsoft 365, Google Workspace, and Slack. It’s also ISO 27001 certified and built and run in Canada. Around 150,000 people use it, including teams at Québecor and Cascades.

On the software side, you get:

  • desk booking on an interactive floor plan, with filters, neighbourhoods, and your own booking rules
  • room booking that syncs with Outlook and Google Calendar
  • visitor management with a check-in kiosk and automatic host notifications
  • service requests for catering, IT, and maintenance, right from the floor plan
  • health and safety module for incident reporting and first-responder tracking
  • occupancy analytics from native sensors
  • an automation engine for booking rules, reminders, tasks, and full workplace workflows
  • an open API and webhooks to connect elia to the rest of your stack
  • a mobile app for booking on the go

There’s hardware too: desk and room occupancy sensors, meeting-room display screens, a touchscreen kiosk, an IoT gateway, and a smart lock that turns existing lockers into bookable ones.

You don’t have to buy all of that upfront, either. You can start with the software and add hardware later.

Side-by-side feature comparison

Dimension ServiceNow WSD elia
What it is Workplace suite on the ServiceNow platform Standalone workplace platform (software + hardware)
Who looks after it IT or the ServiceNow platform team Workplace team
Setup & admin Configured on the platform, often with a partner Self-service, no scripting
Changes go live Usually on IT's schedule Right away
Desk & room booking Yes Yes
Visitor management Yes, kiosk is separate Yes, with kiosk and host alerts
Service requests Yes, as cases using fulfiller licenses Yes, built in
Space management Yes Yes, with analytics
Move management Yes, dedicated module Not a separate module
Maintenance & leases Yes, dedicated modules Via service requests; no separate lease contracts module
Health & safety A separate ServiceNow product, not in WSD Yes
Occupancy sensors Third-party, via Workplace Connectors elia's own sensors
Connects with Other tools through ServiceNow's own integrations Microsoft, Teams, Google, Slack, and an open API
Pricing Custom quote, no public price Free plan; $500–$1,000/mo by places, unlimited users; Enterprise custom
Setup time 6–12 weeks a module, 6–12 months a full rollout Days, often no training
Compliance Inherits your ServiceNow platform's ISO 27001, built and hosted in Canada

They cover a lot of the same basics. The real difference comes down to how much of the workplace each one covers, and who's in charge of it.

Let’s start there.

Big question: who looks after your workplace?

ServiceNow didn't make WSD a separate product. They built it on their main platform, the same one that runs IT tickets. So every desk, room, request, and visitor is a record on that platform, treated like an IT ticket would be.

Config, roles, booking rules, module installs, and integrations sit with the ServiceNow team. Facilities works with what they’ve built, so moving a few desks or changing a booking rule typically means filing a ticket and waiting for IT to get to it.

And an office never sits still:

  • teams grow
  • a floor gets renovated
  • a service process changes
  • a new site opens

On ServiceNow, every one of those is a platform job.

The maps take some work too: ServiceNow's own setup docs have you export floor plans from AutoCAD as a special file and match every room and desk to a record, then redo it whenever something moves. The booking screen employees see is simple, but getting everything behind it set up properly is another story.

elia puts more of that in the hands of the workplace team. You can change rules, open up a floor, or adjust how requests work yourself, without scripting or waiting for IT.

Scope: How much of the workplace do they cover?

This is usually the real deciding factor, and it's often not about desks at all. Some of the teams we talk to don't even want booking! They need a better way to deal with facilities requests, see occupancy, or keep HR, facilities, and IT working from the same information.

Both tools do the basics just fine: floor plans, booking, and seeing who’s in. elia’s case is everything around that:

  • a facilities request and what happens after someone submits it
  • visitors checking in at reception
  • booking a locker for the day
  • logging a safety incident
  • seeing which rooms sit empty all afternoon
  • using occupancy data to make better calls about your space

You can get most of that with WSD too, but it can mean adding more modules and setting up the pieces they depend on (neighbourhoods need Space Management switched on, live Outlook availability needs the Exchange Online connector, the lobby kiosk is its own component). With elia, many of those things are already part of the platform.

Integrations: one platform vs across your stack

WSD makes the most sense when you’re already using ServiceNow across the company. If IT and HR are there, adding the workplace side means you’re building on something you have. If you’re not using ServiceNow much outside of IT, that benefit is smaller. You’re taking on the whole platform for the workplace rather than adding to something that’s already in place.

elia is a bit more flexible here. It works with Microsoft, Google, and Slack, supports both Outlook and Google Calendar, and connects out through its API to the systems you use, like your HR platform (Workday, Greenhouse, and the like) and ServiceNow. It doesn't assume you've picked one stack.

Hardware: none vs native sensors and screens

Hardware: none vs native sensors and screens

ServiceNow doesn’t make the hardware. WSD can pull in data from third-party sensors, but you have to buy and connect them yourself through Workplace Connectors. Until you have those sensors in place, your usage data is really just booking data, which can make the office look a lot busier than it actually is.

elia makes its own sensors and screens, so the hardware is already part of the platform. If someone books a room and never shows up, you can see that. You’re not dealing with a separate hardware setup or another vendor to get that data.

You don't have to choose: elia and ServiceNow together

It gets a bit more interesting here.

Most ServiceNow clients we talk to don't want to get rid of ServiceNow, and they shouldn't. It's doing its job for IT. Nobody's trying to replace it. The point is just to stop making the workplace live inside an IT platform.

ServiceNow is built to connect one system to another, and elia can be the workplace piece it connects to. It holds the workplace side, desks, rooms, visitors, requests, sensors, and passes anything that's an IT job over to ServiceNow, where IT already works.

This integration has a quieter upside, too. A lot of workplace requests never make it into ServiceNow because people aren't in it. They don't know the interface, or they never open it. When the request starts in the tool people are in every day, it gets captured.

And ServiceNow isn't the only thing elia connects to. The same automation engine links to the systems you might use, your HR platform included, so information moves on its own instead of getting entered twice.

A couple of examples of what that looks like:

  • With ServiceNow: someone files a request in elia that turns out to be an IT issue, so it becomes a ServiceNow ticket where IT works it. And it goes both ways: when IT updates the ticket, that status flows back into elia, so whoever reported it sees the progress without leaving elia.
elia automation module
Source: elia
  • From your HR system: someone joins the company and gets added in Workday or Greenhouse, and elia picks that up to set their space or desk assignment on its own. No one enters the same details twice.
elia automation module
Source: elia

For the employee, none of that needs to be complicated. They report a broken light or a jammed door in elia. If IT needs to deal with it, the request gets sent to ServiceNow in the background.

Pricing: the real all-in cost

ServiceNow doesn’t publish its pricing, so every deal is different. Most numbers you’ll find come from independent sources and people who’ve worked with the platform.

The licensing depends on what people need to do:

License type Who it's for What it means for cost
Fulfiller Facilities and workplace staff who work and close cases The expensive one. The bill goes up as more people need to work cases.
Requester Employees who book a space or send in a request Free in ServiceNow's standard model
Business stakeholder Approvers who sign off but don't resolve cases Somewhere in the middle. If they accidentally pick up a fulfiller role, it bumps you to the higher fee.

Then there’s the implementation. WSD isn’t something you just turn on and start using. Some estimates put implementation at 3-5 times the license cost, with a 50-fulfiller rollout estimated at $500,000 to $2 million in the first year. A single module can take 6-12 weeks, while a full rollout can take 6-12 months.

elia does pricing a little differently. You pay for the bookable seats you set up, then add the modules you need, like visitor management or health and safety. Hardware is separate if you want to use it, and larger companies can get a custom Enterprise plan. So there isn't one simple number I can give you for everyone, but you do start with published pricing.

elia pricing
Source: elia

Keep in mind this though: you can't really put these numbers side by side. The $500,000-$2 million ServiceNow figure is for one specific 50-fulfiller rollout and includes the setup and people around it. elia is a subscription based on bookable seats and the modules you choose, with custom pricing for larger setups.

Run your own figures, ours included.

ServiceNow WSD vs elia: Pros and cons

ServiceNow WSD
Pros
  • Everything lives in one system, with workflows that can connect IT, HR, and the workplace
  • Your IT team is already familiar with the platform and how it's secured
  • It's a good fit if your company already runs heavily on ServiceNow
  • It's built for enterprise scale, with the security and compliance big, regulated organizations need
  • The booking experience itself gets fairly good feedback
Cons
  • IT owns it, right down to who can see and do what, so changes and access setup run through their queue, not your workplace team
  • There's no public pricing, and licenses and implementation can make the final cost hard to predict
  • A months-long rollout, and it doesn't end there: you need a dedicated ServiceNow team to keep it running
  • No hardware of its own, so real occupancy data leans on third-party sensors
  • If you're not already using ServiceNow, it's a lot of platform to take on
elia
Pros
  • Workplace managers can do it themselves and make changes right away
  • Most people can pick it up without much training
  • One system for booking, visitors, requests, health and safety, sensors, and lockers
  • Its own sensors and hardware feed data straight into the platform
  • It connects with ServiceNow, so IT can keep working there
  • Pricing is published, it's ISO 27001 certified, and it's built and supported in Canada
Cons
  • It's another platform to buy, secure, and roll out
  • Sensors and screens cost extra
  • It's a smaller vendor than ServiceNow (the trade is faster support and quicker rollouts)
  • It doesn't replace ServiceNow for IT, so you're running two systems that need to talk

How to figure out which one

Write down what you need the workplace tool to do over the next couple of years, and who you want looking after it:

  • Already on ServiceNow and just need the basics? Then WSD is probably the way to go, especially if you're perfectly happy to hand over setup and changes to IT.
  • Looking at requests, occupancy, visitors, safety, multiple sites, or want your workplace team to manage things themselves? You'll be adding modules and cost to get there. A tool like elia is the simpler answer, and it still connects back so IT keeps its tickets.

At the end of the day: how much do you need your workplace tool to do, and who do you want in charge of it?

See the whole workplace in one place

If that sounds like your office, take a look at what elia does, and how it sits next to ServiceNow rather than against it.

Book a demo

Where I got the info

WSD details are from ServiceNow's own product and setup documentation. Cost and timeline figures are from independent pricing and implementation breakdowns (Quackback, Desk365, Virima) and ServiceNow's own reported customer numbers, since ServiceNow doesn't publish workplace pricing.

elia details and pricing are from elia.io and the elia pricing page.  Bear in mind that prices can vary depending on where you are and what kind of deal you can negotiate, so always check in with the vendor for the very latest pricing.

is a Content Marketing Specialist at elia. With 10+ years in content marketing, she writes about workplace trends and the tools that help teams work smarter. Part strategist, part storyteller, Tamara brings equal amounts of data, creativity, and a little Moon Prism Power to every piece she creates. 🌙✨
Contents
    Subscribe to our newsletter
    Subscribe to the elia newsletter for exclusive product updates and industry best practices. You can unsubscribe at any time.
    Thank you! You're subscribed.
    Oops! Something went wrong while submitting the form.

    Frequently Asked Questions

    Answers to Your Common Queries

    Can elia work with ServiceNow?
    Is elia a replacement for ServiceNow?
    What are the main ServiceNow WSD alternatives?
    Can the workplace team manage elia without the help of IT?
    What's included in the ServiceNow Workplace Service Delivery suite?