What is a help desk?
A help desk is the single, organised place where customers and staff ask for help and a support team answers. It receives requests through one front door, logs each one as a tracked ticket with a clear owner, keeps a full history of the conversation, and measures how quickly and well requests are handled. The word describes both the team that does this work and the software that supports it.
The short answer
A help desk in one paragraph
A help desk is a system, made up of people and software, for handling support requests in a consistent way. Instead of help arriving as a tangle of emails, calls and messages that anyone might pick up or quietly drop, every request enters one place, becomes a ticket, gets an owner, and is tracked until it is resolved.
The term is used in two slightly different ways, and both are correct. It can mean the support function itself, as in "raise it with the help desk", referring to the team and process that answer requests. It can also mean the software those people use, often written as helpdesk software, the application that captures requests, organises them into tickets, and keeps the record. In everyday speech the two meanings blur together, which is usually fine.
The idea grew up in IT support, where staff needed somewhere to report a broken laptop or a forgotten password and to be told when it would be fixed. It has since spread far beyond technology. Today a help desk can sit behind customer service, ecommerce, finance queries, trade-counter support or any function where people send requests and expect a dependable answer.
Why it exists
The purpose of a help desk
The purpose is simple to state and surprisingly hard to achieve without the right structure: make sure every request gets a good answer, on time, every time.
Left to a shared mailbox alone, support tends to fail in predictable ways. Two people reply to the same message and contradict each other. A request sits unread because everyone assumed a colleague had it. A customer is asked the same questions twice because nobody could see the earlier conversation. None of this is anyone being careless; it is the natural result of having no shared system. A help desk exists to remove those failure modes.
It does this by giving the work shape. Each request gets a state, so the team can see at a glance what is new, what is being worked on and what is waiting on the customer. Each request gets an owner, so there is always exactly one person responsible. Each request keeps its full history, so the next person to touch it has context. And the whole flow is measured, so the team can answer honest questions about how it is performing.
What a help desk is trying to deliver
| Nothing dropped | Every incoming request is captured as a ticket, so a message cannot quietly disappear in a busy inbox. |
|---|---|
| Clear ownership | One person is responsible for each ticket, which removes the "I thought you had it" gap. |
| Fast, fair response | Requests are triaged by priority and tracked against a target response time, so urgent issues do not wait behind routine ones. |
| Consistent answers | Shared history and saved replies mean customers get the same correct answer regardless of who replies. |
| Visible performance | Reporting shows volumes, response times and what is breaching, so problems surface before customers complain. |
How it works
How a help desk handles a request
Whatever the channel, a help desk follows the same basic lifecycle from the moment a request arrives to the moment it is closed.
Most help desks work through email and a shared support address, although some also take requests through a web form, a phone line or a chat widget. Whatever the entry point, the shape of the work is similar, and understanding that lifecycle is the easiest way to understand what a help desk actually does day to day.
- Capture. A request comes in and the help desk turns it into a ticket, recording who sent it, when, and what they asked.
- Triage. The request is read, sorted by priority, given relevant tags or categories, and routed towards the right person or team.
- Assign. The ticket is given a single owner who is now responsible for seeing it through.
- Respond. The owner replies to the customer, asks for any missing detail, and works towards an answer or a fix.
- Escalate when needed. Anything the front line cannot resolve is passed to a specialist or a manager, with the history attached.
- Resolve and close. Once the customer has what they need, the ticket is marked resolved, and the full record is kept for next time.
Behind that lifecycle sits a set of supporting tools that make the work repeatable: private notes for colleagues to discuss a ticket without the customer seeing, saved replies for common questions, filters and saved views so each person sees their own slice of the queue, and timers that track each request against an agreed response target. None of these are exotic; together they are what separates a help desk from a mailbox that several people happen to share.
A common confusion
Help desk vs service desk
The two terms are often used interchangeably, but in IT they mean different things, and knowing the difference helps you pick the right tool and the right language.
A help desk is request-led. Its job is to answer the question or fix the fault in front of it, quickly and well. It is tactical, reactive in the best sense, and judged largely on speed and quality of resolution. For most small and medium businesses, a help desk is exactly what is needed, and the simpler word is the honest one.
A service desk is broader and more formal. It still answers requests, but it also manages services end to end, often under a framework such as ITIL. Alongside day-to-day questions it handles incident management, problem management (finding and removing the root cause of repeat issues) and change management. A service desk is a single point of contact for an entire IT service, not just a queue of questions.
Side by side
| Main focus | Help desk: answer and resolve individual requests. Service desk: manage the wider service those requests belong to. |
|---|---|
| Typical scope | Help desk: support questions and faults. Service desk: incidents, problems, changes and service requests. |
| Framework | Help desk: light or none. Service desk: often aligned to ITIL or a similar standard. |
| Best fit | Help desk: most SMEs and customer support teams. Service desk: larger IT organisations with formal processes. |
The practical takeaway is to use the word that matches the job. If your team answers customer and staff requests and wants to do it reliably, you want a help desk. You do not need the heavier service-desk machinery, and calling a customer support tool a service desk usually just adds confusion.
The people
The role and job of a help desk
A help desk is a function as well as a tool. The role is to be the dependable front line between people who need help and the wider business that provides it.
The job of a help desk, described plainly, is to receive a request, understand it, answer or resolve it, and keep the person informed until it is closed. That sounds modest, but doing it consistently, at volume, under time pressure, is real skill. A good help desk turns a frustrated, half-explained problem into a calm, clear resolution, and leaves the customer feeling looked after rather than processed.
What help desk staff actually do
- Read and understand incoming requests, including the ones that are vague or written in frustration.
- Triage by urgency and impact, so the right things are dealt with first.
- Answer common questions accurately and quickly, often using saved replies for consistency.
- Investigate and resolve faults, or gather the detail a specialist will need.
- Escalate anything beyond their remit, with the full history attached so nothing has to be repeated.
- Keep clear records, so the team builds a memory rather than re-solving the same issue forever.
- Spot patterns and flag recurring problems, so the business can fix causes, not just symptoms.
Roles are often described in tiers. First-line (or tier one) staff handle the bulk of everyday requests and resolve most of them on first contact. Second-line specialists take the harder, technical cases. A help desk manager owns the queue overall, watches response times and workload, and is accountable for the service the team provides. In a small business, one or two people may wear all of these hats at once, which is exactly why a clear, shared system matters so much.
The engine room
Ticketing: the heart of a help desk
Almost every help desk runs on tickets. Each one carries the structure that turns a loose message into trackable, accountable work.
A ticket per request
Each incoming request becomes one ticket with a reference, a subject and the full thread, so it can be found, tracked and reported on later.
States and ownership
A ticket moves through states such as open, pending and resolved, and always has one owner who is responsible for it.
Priority and tags
Priority marks how urgent a request is, and tags group similar tickets so patterns and trends are easy to see.
History and notes
Every reply and private note is kept against the ticket, so anyone who picks it up has the complete context.
Targets and timers
A ticket can be tracked against a response target, so the team can see what is on time and what is at risk of breaching.
An audit trail
Who did what and when is recorded, which protects the customer, the agent and the business if a conversation is ever questioned.
Made concrete
Examples of a help desk in action
The clearest way to understand a help desk is to watch a request pass through one. Here are three short, ordinary examples.
IT support
A member of staff cannot log in on Monday morning. They email the IT help desk; the message becomes a ticket, tagged "access" and marked high priority. A first-line agent picks it up, resets the password, replies with clear instructions, and closes the ticket. Because it is logged, the team later notices a cluster of login problems after a system update and fixes the cause. That last step is the difference between answering requests and improving the service.
Customer support for a shop
A customer emails support@ to ask where their order is. The help desk creates a ticket, the agent checks the order, replies with a tracking link and a realistic delivery date, and tags it "delivery". The full thread is kept against the customer, so if they write again the next agent sees the whole story without asking them to repeat themselves. The customer feels remembered, which is most of what good support is.
Accounts and billing
A query lands at accounts@ about a duplicate invoice. It becomes a ticket, is assigned to someone in finance, and a private note is added so a colleague can confirm the figures before anyone replies to the customer. The customer only ever sees the polished public reply, never the internal back-and-forth. The separation between private notes and public replies is one of the quiet things a proper help desk gets right and a shared inbox does not.
Where Solves fits
How Solves relates to all this
Solves is a help desk in the customer support sense: an email-first, UK-first, multi-brand support tool built for small and medium teams.
Everything described above is what Solves is for. It turns shared inboxes such as support@, info@ and accounts@ into owned tickets, with states, a single assignee, priority, tags and saved replies. It keeps a hard line between public replies that reach the customer and private notes that never do, and it stores the full contact history so nobody has to ask twice.
On timing, Solves runs first-response and resolution SLA timers with per-brand or organisation targets, and a breaching view surfaces overdue tickets so the work due soonest is easy to find. Reporting shows volumes, response times and what is breaching. If you run more than one brand, Solves keeps each brand on its own support address and identity inside one shared queue, so a small team can cover several brands without juggling separate logins.
Solves is deliberately email-first. It does not run phone lines, live chat or social inboxes, and it is not a full IT service desk with formal change management. That focus is the point: it does the core help desk job, support email turned into owned, timed, accountable work, and it does that part well rather than spreading itself thin.
Help desk, not contact centre
When people say help desk they sometimes mean a full contact centre with phone, chat and social. Solves is the email-first kind: tickets, ownership, notes, SLAs and multi-brand support, built so a small team can run dependable support without staffing a switchboard.
Keep going
Related terms
A few neighbouring terms come up whenever help desks are discussed, and they are worth knowing.
| Support ticket | The single record a help desk creates for one request, carrying its state, owner, history and priority. |
|---|---|
| Shared inbox | A mailbox several people read, such as support@. It is where many teams start, before requests outgrow it and need tickets. |
| SLA | A service level agreement: the response or resolution time a team commits to, which a help desk tracks with timers. |
| Triage | Sorting incoming requests by urgency and routing them to the right owner, the first real step in handling a request. |
| Escalation | Passing a request the front line cannot resolve to a specialist or manager, with its history attached. |
FAQ
Common questions about help desks
What is the purpose of a help desk?
The purpose of a help desk is to give customers and staff a single, dependable place to ask for help and to give the support team a structured way to answer. It turns scattered requests into tracked tickets so nothing is missed, gives each request a clear owner, records the history of every conversation, and produces the data a team needs to see how it is doing and where it is struggling.
What is the job of a help desk?
The job of a help desk is to receive a request, understand it, answer or resolve it, and keep the customer informed until it is closed. In practice that means triaging incoming messages, assigning owners, replying clearly, escalating anything the front line cannot solve, and recording what happened so the next person has the full picture. The underlying goal is a fast, accurate, consistent answer every time.
What is a help desk in computer terms?
In IT, a help desk is the team and software that handle technical support requests: password resets, access problems, broken hardware, software faults and how-to questions. The software logs each request as a ticket, routes it to the right person, tracks it against a target response time, and keeps an audit trail. The word also describes the application itself, as in helpdesk software.
What is the difference between a help desk and a service desk?
A help desk is focused on answering and fixing individual requests quickly. A service desk is broader: it manages services end to end and usually adds formal processes such as incident, problem and change management under a framework like ITIL. Put simply, a help desk solves the request in front of it, while a service desk also looks after the wider service the request belongs to.
Is a help desk only for IT?
No. The term started in IT support but now covers any structured support function. Customer service teams, ecommerce returns desks, account teams and trade-counter support all run on the same idea: a single front door for requests, a ticket for each one, a clear owner, and a record of what was done. Solves is a customer support help desk built around shared inboxes such as support@ and accounts@.
See what an email-first help desk feels like
Solves turns your support, info and accounts inboxes into owned, timed tickets across every brand, in one place.