rapidFOX Logo
rapidFOX
Smart Helpdesk

What is a help desk?

Guides · rapidFOX Lesezeit 9 min

A help desk gathers every customer request in one place and turns emails, calls and messages into cases you can follow. This guide explains how one works, what kinds there are, which features count, what it costs and when the move is worth making.

Help desk – the definition

A help desk is software that collects incoming requests from customers or colleagues and turns each one into a ticket: a case with a number, an owner, a status and a complete history.

The word describes the job rather than the technology. What makes it a help desk is not the database underneath but the three things a mailbox cannot give you: somebody owns this, it is due by then, and here is everything that was said.

How does a help desk work?

The path is always the same, whatever the product:

  1. Arrival. An email reaches your support address, a form is submitted, or somebody types in a phone call. Each becomes a ticket with a reference.
  2. Assignment. The ticket goes to a person or a team – by rule, or because somebody picks it up. From that moment it belongs to someone.
  3. Work. Replies, internal notes and attachments accumulate on the ticket. The status says where it stands: open, waiting, done.
  4. Closing. The case is resolved and stays readable. Nothing is deleted, and the next similar case starts with the answer to this one.

The reply goes back out as an ordinary email from your own address. Customers do not need an account, and most of them never notice a system is involved.

What kinds of help desk are there?

Three distinctions actually matter when you are choosing:

  • External or internal. A customer help desk answers the people who buy from you; an IT service desk answers your own colleagues. The mechanics are the same, the tone is not.
  • Cloud or self-hosted. Operated for you, or on your own server. Self-hosting keeps control and hands you the maintenance; both are defensible, and the wrong one is the one nobody maintains.
  • Lean or platform. A tool that does support well, or a platform where support is one module. The second only pays off if you use the other modules.

The features that matter

Feature lists are long and mostly beside the point. These six carry the day:

  • Email integration. Incoming mail becomes a ticket, replies go back as email. Without this, nothing else matters.
  • Ownership and status. One person owns it, and its state is visible without opening it.
  • Deadlines. A response and resolution time with a visible warning – see SLA explained.
  • Search. Across subjects, messages and attachments. A help desk you cannot search is an archive.
  • A knowledge base. So a good answer is written once – see building a knowledge base.
  • Reporting. How many arrived, how many were cleared, how long it took. Honestly counted.

Help desk, ticketing system or shared inbox?

Help desk and ticketing system mean the same thing in practice; the first emphasises the goal, the second the mechanism. The difference that matters is against a shared inbox: a mailbox several people can read has no owner, no status and no deadline, and it fails in a predictable way – see the problems with a shared inbox.

A fuller comparison is in help desk vs ticketing system.

What does a help desk actually give you?

  • Nothing is lost. Every request exists as a case, whether or not anybody remembered it.
  • No duplicate answers. One owner, visible to everyone.
  • Faster replies. Because the history, the templates and the knowledge base are where the reply is written.
  • Something to point at. What was promised, when, and whether it happened.
  • Handovers that work. Holiday, sickness, someone leaving – the case does not leave with them.

When is it worth moving off the mailbox?

There is a reliable signal, and it is not team size. It is the first time two people answer the same customer, or the first time something important is read and not answered. Both mean the mailbox has stopped being able to hold the work.

As a rule of thumb: from two people answering, or from about 20 requests a week, the mailbox costs more than the software. How to make the move is in introducing a help desk.

What does a help desk cost?

Almost all of them charge per seat per month. The published number is rarely what you pay: the tier that includes automation, reporting or AI is usually one or two levels above the one in the advertisement, and some functions are add-ons on top.

Before comparing prices, work out which tier actually covers what you need – then compare those. There are also genuinely free options with real trade-offs, described in free help desk software.

Try rapidFOX free for 7 days

Help desk software with a local AI – GDPR compliant, hosted in Germany. No card, ready in 2 minutes.

Start free now

Common questions

What is the difference between a help desk and a ticketing system?

In practice, none. "Ticketing system" emphasises the individual cases, "help desk" the purpose behind them. Vendors use both for the same product.

Do our customers need an account?

No. They write an email as they always did and get an email back. A help desk changes what happens on your side, not on theirs.

How long does it take to set one up?

Connecting a mailbox is minutes. Being genuinely comfortable takes a week or two, mostly spent deciding on statuses and who owns what.

Is a help desk worth it for a team of two?

Yes, and two is often exactly the point where it starts to be – one person cannot collide with themselves, two can.

Does it work without an internet connection?

Cloud products need one. Self-hosted products need your server to be reachable, which for internal support may be a local network.

Can we keep our existing support address?

Yes, and you should. The mailbox is connected over IMAP and SMTP; replies go out from the same address.

What happens to emails already in the mailbox?

They stay where they are. Most teams start fresh and keep the old mailbox readable for a few months.

Is a help desk GDPR compliant?

It depends entirely on the product and where it runs. What to look for is in <a href="/ratgeber/ticketsystem-dsgvo">GDPR and your help desk</a>.

Read on