A help desk handles the user’s individual request: it logs, prioritizes and resolves. A service desk manages the full catalog of IT services, with defined processes, service levels and owners. The difference is not team size, it is scope: one resolves requests, the other manages services.
Help desk: what it solves and where it stops
When an employee can’t print, isn’t receiving email or needs access to an application, the first point of contact is the help desk. In many IT teams across Latin America, this is the most common model: a ticket channel —email, form or chat— where the incident is received, an owner is assigned and the resolution is recorded.
A help desk works reactively. Its main job is to reduce user downtime and bring the service back to normal as quickly as possible. The metrics that matter in this model are first response time, resolution time and user satisfaction score (CSAT).
Where does it stop? At the closed ticket. There is no structured service catalog, no formal service level agreements by request type and, usually, no integrated change or asset management processes. That doesn’t make it an inferior model: for organizations with fewer than 50 users, or with IT centralized around a few critical applications, a well-run help desk does exactly what it should.
The key is knowing when volume, complexity or business demands start to outgrow what a reactive model can handle. That is the moment a service desk becomes necessary.
Service desk: what it adds
A service desk doesn’t replace the help desk: it includes it and expands it. In practical terms, it still handles incidents and requests, but within a broader framework: a service catalog with clear definitions, service level agreements (SLAs) by request type, approval workflows for changes and metrics that report to the business, not just to IT.
Under the ITIL 4 framework —the most widely adopted reference in the region for IT service management— the service desk is one of the core practices of service management. It includes incident management, request management, problem management (to eliminate root causes) and, when integrated, change management.
A concrete example: in a company with 200 users, the help desk resolves “email isn’t working.” The service desk, besides resolving that incident, has already recorded that corporate email is a critical service with a 2-hour SLA, that a technical owner is assigned and that recurring incidents on that service are being analyzed as a problem to fix at the root.
The daily difference is significant: a service desk reduces the number of repeat incidents because it has processes to eliminate their causes, while a help desk keeps resolving them one by one.
From a compliance standpoint, organizations that must comply with ISO/IEC 20000-1 —the international standard for IT service management— require a service desk by definition. The standard calls for a documented service catalog, formal SLAs and measurable processes.
Side-by-side comparison table
The table below summarizes the structural differences between the two models. It is the starting point for diagnosing which one your team is operating today:
| Dimension | Help desk | Service desk |
|---|---|---|
| Scope | Individual incidents and requests | Full catalog of IT services |
| Processes | Ticket logging, assignment and closure | Incidents, requests, problems, changes and assets |
| Key metrics | Response time and CSAT | SLA per service, availability, first-contact resolution rate |
| Who reports | End users | End users + business stakeholders |
| When to adopt | From the first IT team | When the service catalog outgrows reactive management |
| Sign that it falls short | Repeat tickets, informal SLAs, no asset traceability | Not applicable: it scales with the business |
How to tell which one you are running today
You don’t need a formal audit to run a first diagnosis. Answer these questions:
- Do you have a written catalog of the services IT delivers? If not, you are in help desk mode.
- Does each type of request have a defined SLA that has been communicated to users?
- Is there a documented process for managing changes (installations, updates, migrations)? If changes are coordinated over WhatsApp or email with no record, that is a clear sign.
- Do you track recurring problems and work to eliminate their root cause? If every incident is handled as if it were the first, the model is reactive.
- Does IT report service availability metrics to management? If it only reports closed tickets, the focus is operational, not strategic.
If you answered “no” to three or more of these questions, your operation is working as a help desk, regardless of what it is called internally. That isn’t necessarily a problem: it may be exactly what you need today. The problem appears when volume, service criticality or business demands exceed what that model can manage.
The path from help desk to service desk
The evolution doesn’t require an overnight transformation. The most common path in mid-sized organizations in Latin America follows these steps:
- Document the current service catalog, even in a spreadsheet. List which services IT delivers, who uses each one and what the impact is if it fails.
- Define basic SLAs: response time and resolution time by request type and criticality level. Communicate them to users.
- Separate incidents from service requests in the ticketing system. “The system isn’t working” is not the same as “I need access to this application.”
- Add a minimal problem management process: review recurring tickets monthly and assign an owner to eliminate the root cause.
- Evaluate a service desk platform that supports these processes in a structured way, not just as a ticket repository.
On that last point, OTRS is one of the most widely used platforms in the region for running a complete service desk, with support for ITIL, SLA management, service catalog and workflow automation. Aufiero Informática distributes OTRS in Latin America and can support you through evaluation and implementation.
Which tool for each model?
The tool doesn’t define the model, but it enables or limits it. For a basic help desk, any ticketing system does the job. For a service desk, the platform needs to support a service catalog, SLAs configurable by request type, approval workflows for changes and reporting oriented to service availability, not just ticket volume.
If you are evaluating how to choose the right tool for the size and maturity of your operation, the next step is to compare which features are essential for your case and which you can add in a second stage.
OTRS, available through Aufiero Informática across Latin America, covers these requirements natively. It is an ITIL 4-aligned platform that lets you scale from a basic help desk operation to a full service desk without changing tools. If your team already uses a ticketing system but is running into its limits —no SLAs, no catalog, no problem management—, an OTRS evaluation can show the jump in capability available without replacing the whole process from scratch.
Frequently asked questions
What is a help desk?
It is the point where users report IT incidents and requests, with a record, a priority and an assigned owner.
What is a service desk?
It is the management of the full catalog of IT services, with processes, service levels and metrics.
What is the difference between a help desk and a service desk?
The help desk resolves individual requests; the service desk manages services end to end. In Spanish, both are often called “mesa de ayuda” or “mesa de servicios”, and the terms are used loosely in practice.
Can you start with one and grow into the other?
Yes, and it is the most common path: first support, then the catalog.
How many people do you need for a service desk?
There is no minimum. The trigger is the number of distinct services IT delivers, not the size of the team.
