Service Catalogue vs. Help Desk vs. Service Desk: What's Actually the Difference?
These three terms get used interchangeably all the time, and that’s created a lot of unnecessary confusion for business owners trying to figure out what they actually need. Here’s the plain-language version.
Help desk is the oldest and simplest concept: a place to report that something is broken. Your laptop won’t turn on, the printer is jammed, the internet is down. A help desk is reactive by nature — it exists to fix problems after they happen.
Service desk is a broader evolution of the help desk. It still handles things that are broken, but it also acts as the single point of contact for anything IT-related — questions, requests, and incidents all funnel through one place. Think of it as the help desk’s older, more organized sibling.
Service catalogue is different from both because it isn’t about reporting problems at all — it’s about requesting things you already know you need. A new employee needs a laptop and system access. Someone needs a software license renewed. A department needs a shared drive set up. None of these are “broken.” They’re planned, expected requests, and a service catalogue turns them into a simple, structured menu instead of a one-off conversation every time.
Why the distinction actually matters
If your business only has a help desk or a service desk, every request — broken or not — goes through the same reactive, first-come-first-served queue. A new hire’s laptop request sits in the same pile as a genuine emergency. There’s no way to say “this needs my manager’s approval first” or “this should automatically trigger five specific setup tasks.”
A service catalogue sits alongside your help desk, not instead of it. Broken things still get reported and fixed quickly. But planned, requestable things — the stuff you can see coming — get their own clear, approved, trackable path.
Our MyIT Portal brings both together: a service desk for when something’s wrong, and a Service Catalogue for everything your team already knows it needs. Worth asking: does your current setup actually separate the two, or is everything just landing in one inbox?