Helpdesk

In short: The central point of contact for users who have technical problems or questions about IT systems.

In more detail: Takes in requests (phone, email, ticketing system), solves simple problems directly, and forwards more complex cases to specialised teams (“2nd/3rd-level support”). A typical field for the system integration specialisation.

In Depth

Tiered support (levels 1-3)

Helpdesks usually work in tiers:

• 1st-level support: takes in requests and solves standard problems directly (resetting a password, known issues via a knowledge base/FAQ). Needs broad but not deep knowledge — the goal is to resolve as many requests as possible without escalation.
• 2nd-level support: handles more technically demanding cases that need deeper system knowledge (e.g. network configuration, software conflicts), but no development/source-code changes yet.
• 3rd-level support: usually the developers or administrators of the respective system themselves, brought in for rare, novel, or fundamental problems (e.g. a genuine software bug).

A ticket moves through the tiers until it’s resolved — ideally, most requests (often 70-80%) can already be resolved at 1st level, which saves cost, since higher support tiers tie up considerably more expensive specialists.

Ticketing systems as a central tool

The central tool is a ticketing system (e.g. Zendesk, Jira Service Management, OTRS, Freshdesk), which documents every request with a status (open, in progress, resolved), priority, history and responsible person in a traceable way — important both for tracking individual cases (who did what and when can always be traced) and for later analysis (which problems occur frequently, where a structural fix is worthwhile instead of repeated individual-case support, e.g. a better error message in the product itself that avoids triggering a request at all in the future).

Metrics (KPIs)

Common quality measures for a helpdesk: first response time (how quickly does someone respond at all for the first time), resolution time (how long until the problem is actually fixed), first-contact resolution rate (share of cases resolved on first contact, without follow-up questions/escalation), and customer satisfaction (often captured via a short survey after a ticket is closed). These metrics serve both internal quality control and often contractually agreed service level agreements (SLAs) with customers.

Self-service as a supplement

Many modern helpdesks increasingly rely on self-service: searchable knowledge bases, chatbots for simple standard questions, and community forums where users help each other — with the goal of reducing ticket volume for simple, recurring questions from the outset, before a human even needs to get involved.

Internal vs. external helpdesk

A rough distinction is made between internal IT support (for the company’s own employees — e.g. “my laptop won’t start”) and customer support/customer success (for a product’s paying end customers). Both use similar tools and processes, but differ in prioritisation and tone: internal support can usually maintain more direct, more technical contact, while customer support has to pay more attention to communication and customer experience, since revenue and customer retention are directly at stake here.

See also: System Integration