A help desk is the place employees go when they need IT help: a team, a process and a ticketing tool that record every issue or request, decide how urgent it is, and work it until it’s resolved. It can be run in-house, outsourced to a provider, or split between the two, and it is usually reached by phone, email, chat or a self-service portal.
At a glance
- The help desk is the first point of contact for IT issues and requests, from password resets to broken laptops.
- Every contact becomes a ticket with a category, priority, owner and history.
- Work is usually tiered: simple issues are fixed on first contact, harder ones are escalated to specialists.
- Coverage hours, channels and supported applications vary widely between in-house teams and providers.
- The ticket data shows where recurring problems are and whether support is keeping up.
What problem it solves
Without a help desk, IT support runs on hallway conversations, direct messages to whoever seems technical, and email threads that get lost. Urgent issues wait behind easy ones, the same problem is solved from scratch every time, and nobody can say how many issues there are or how long they take.
A help desk puts structure around that. Employees have one place to ask, issues are recorded and prioritized, routine fixes are documented so anyone can apply them, and managers get data on volume and response time. For small and mid-sized organizations it also solves a staffing problem: a provider can cover nights, weekends and peaks without hiring a full team.
How it works
Intake. Users reach the help desk by phone, email, chat or a portal. Some requests are handled through self-service, such as password reset tools or knowledge articles.
Ticketing and triage. Each issue is logged as a ticket in an IT service management (ITSM) or help desk tool, categorized and prioritized by urgency and business impact. Incidents (something is broken) are often handled separately from requests (someone needs something, such as a new account or software).
Tiers and escalation. Tier 1 resolves common issues using scripts and knowledge articles. Tickets that need deeper skills move to tier 2, and then to specialists, vendors or internal engineering. Hardware that needs hands-on work may be passed to field support. Network or service outages may be routed to a network operations center.
Targets and reporting. Response and resolution targets are usually set by priority in a service level agreement (SLA) or an internal standard. Reports track volume, response time, resolution time, first-contact resolution and satisfaction.
Outsourced models. A provider may run the whole help desk, handle tier 1 only, or cover after-hours. Some work in your ticketing system; others use their own and integrate with yours. See our help desk solution page for the common setups.
When it matters for buyers
- When the company grows past what one or two IT people can handle. Interruptions start crowding out projects.
- When you need after-hours or multilingual support. Staffing that yourself is expensive; providers spread it across clients.
- When audit, insurance or customers ask about access controls. Ticket records show who approved and changed access, and when.
- When you’re consolidating IT providers. The help desk is the part users notice, so changing it needs planning.
- When ticket volume is high but the causes repeat. The data can justify fixing root causes rather than adding staff.
Questions to ask vendors
- Which hours, channels and languages are covered, and how is after-hours support staffed?
- What are your response and resolution targets by priority, and what happens if you miss them?
- Which applications and devices do you support, and what is out of scope?
- Do you work in our ticketing system or yours, and who owns the ticket data if we leave?
- How do you learn our environment, and how is your knowledge base kept current?
- How do escalations to our internal team, other vendors and on-site technicians work?
- How is pricing calculated, and what triggers extra charges?
- What security controls apply when your agents reset passwords or change access?
How it differs from a service desk
The terms are often used interchangeably, but frameworks such as ITIL draw a line. A service desk is the single point of contact between IT and its users for all service matters: incidents, requests, changes and information. A help desk, in that view, is narrower and focused on fixing problems and restoring service. Many products and providers label themselves “service desk” when they include request fulfilment, asset records and change processes. When you compare offers, look at the scope listed in the contract rather than the name.
Problems this helps with
- Employees don't know who to call when something breaks
- IT staff buried in password resets
- No after-hours support
- No record of what was fixed or how long it took
