Glossary / Service Desk

Service Desk

The IT team's single point of contact for support requests, incidents, and service requests — broader in scope than a traditional helpdesk, which is usually reactive, ticket-only support.

"Helpdesk" and "service desk" get used interchangeably, but the distinction ITIL draws is useful: a helpdesk is reactive and narrow — log the issue, route it, resolve it, close it. A service desk is broader and more proactive — it's also the intake point for service requests (provision a new laptop, add a user, grant an access change), and it's expected to own communication during a wider incident, not just individual ticket resolution.

In practice, most small and mid-sized IT teams and MSPs run one unified queue that does both jobs under whichever name they prefer — the functional distinction matters more in how an organization scales its process (does an incident automatically trigger status communication and a post-incident review, or does it just get closed when it's fixed) than in the label on the tool.

A service desk's effectiveness is usually measured by the same core metrics regardless of what it's called: SLA adherence, MTTR, ticket volume trend, and first-contact resolution rate — how often an issue gets solved without being escalated or bounced between technicians.

How Nexus handles this

Nexus runs one ticketing queue for both incidents and service requests against the same client and device record — SLA timers, escalation, and history in one place instead of a helpdesk tool and a separate request-management tool that don't share data.

Ready to see it in the platform?

Join the design-partner cohort and we'll show you exactly where this lives.