What is a helpdesk?
A helpdesk is the company's single entry point to IT support: the place employees call, write to or open a ticket with when something is not working. Behind the entry point sits a ticketing system, fixed priorities and a process that ensures cases get resolved, not just answered. Without a helpdesk, IT help ends up as emails to "the guy who can usually fix it", and nobody knows what has been resolved and what is still waiting.
Helpdesk vs. service desk: is there a difference?
In everyday speech: no. In ITIL terminology: yes. The helpdesk is historically the reactive function: the user has a problem, the helpdesk solves it. The service desk is the broader concept: it also handles service requests (new user, new PC, access to a system), changes and communication around planned maintenance, and it is the link between the users and the entire IT delivery. In practice, any serious support function today delivers both, and the name matters less than the substance: is there a single point of contact, a ticketing system and measurable response times? Then the foundation is in place, whether it is called a helpdesk or a service desk.
What is a ticketing system?
A ticketing system registers every enquiry as a case with a number, priority, owner and history. It sounds bureaucratic, but it is the opposite:
- Nothing disappears: the case exists until it is closed, even when it changes hands.
- Prioritisation: an outage in production comes before a question about an email signature.
- History: what was done the last time the user had the same problem? It is in the case.
- Patterns: ten cases about the same program in one week are not ten coincidences, but an operational problem that needs fixing at the root.
Ticket data is also the documentation of whether the provider is living up to its response times.
SLAs and response times in a helpdesk
A helpdesk without an SLA is a promise without measuring points. The SLA defines the priorities (typically P1 to P4), response time and resolution time per priority, opening hours and escalation paths. The two questions you should ask any provider: what counts as a response: an auto-reply email or a technician getting to work? And what happens if the times are not met? An SLA without consequences is a statement of intent. If you receive regular reporting on the cases, you can see for yourselves whether the promises hold.
How MI Support IT can help
MI Support IT runs a 24/7 service desk for Danish businesses: one point of contact, a ticketing system, fixed response times on all priorities and Danish-speaking support around the clock. Contact us if your employees need a number that always answers, or see our pricing.