GLOSSARY

What is a help desk? What a helpdesk does

A help desk is the software a team answers customers from, with a shared inbox, tickets, help articles, chat and reports. What each part does and costs.

A help desk is where a company answers its customers. At a software company it’s usually one piece of software, such as Zendesk, Freshdesk or Help Scout. Every email, chat and form message lands in one queue, each one becomes a ticket with an owner and a status, and a set of help articles answers the common questions before anyone writes in. Helpdesk, written as one word, means the same thing.

The name is also used for an IT help desk, the team a company’s own staff contact when a laptop won’t start or a password needs resetting. Many IT teams call theirs a service desk. This page is about the customer kind, the one the people who pay you write to.

If you answer support yourself, you may not need a help desk yet. Deacon is an AI customer support agent that answers your customers on your site in seconds, from your own docs, and hands you the questions that need you. It also sorts what customers ask into topics, so you can see which are feature asks and which are bug reports. It has a free plan.

The help desk plans and prices below were read on each vendor’s pricing page on 21 October 2026, and each price links there.

What a help desk does

A help desk does three jobs for a team that answers customers.

  • It catches every question. Email, chat on your site and a contact form arrive in one queue, so nothing sits in one person’s inbox while they’re away.
  • It gives each question one owner. Every request shows who has it and where it’s got to, so two people don’t reply to the same customer and nobody assumes someone else has.
  • It tells you what customers keep asking about. Reports count requests by tag and by channel and time the replies, and the help centre takes the common questions off the queue.

Bigger teams also split the work into support tiers, where generalists answer first and pass the harder questions to specialists and then to the engineers.

The parts of a help desk

Most help desks are built from the same seven parts. The names change from one vendor to the next, but the jobs stay the same.

Shared inbox

What it does
One queue for every message, which the whole team works from
Also called
Inbox, queue, views

Tickets

What it does
Each request kept as one record, with a number, an owner, a status and the whole thread
Also called
Conversations, cases

Knowledge base

What it does
Help articles customers search for themselves
Also called
Help centre, docs

Live chat

What it does
A chat window on your site or in your app, answered by a person or an AI agent
Also called
Messaging, widget

Saved replies

What it does
Stored answers a person drops into a reply
Also called
Canned responses, macros

Automation

What it does
Rules that tag, assign, remind and close tickets
Also called
Triggers, workflows

Reports

What it does
Counts of requests, reply times and what people asked about
Also called
Analytics, dashboards

Each part has more to it than a row can hold. Ticketing system covers what a ticket holds and how it moves from New to Closed. Knowledge base covers what goes in the help articles, and canned responses has eight saved replies a software company can start from. Helpdesk automation sets out which plan unlocks each kind of rule, and first response time and ticket volume are two figures worth reading in the reports.

One question through a help desk

To see the parts work together, follow one question at a small software company with two people on support.

  1. At 21:40, a customer of an invoicing app opens the chat on the pricing page and asks whether the Team plan can bill in a second currency. Nobody is online, so the chat takes their email, and the question becomes a ticket in the shared inbox.
  2. A rule tags it “pricing” because it names a plan. Another assigns it to whichever of the two has fewer open tickets.
  3. At 08:15 the next morning, the owner opens it, drops in the saved reply on currencies, adds a line about the Team plan and sends it. The ticket now waits on the customer.
  4. The customer writes back to say thanks, and the ticket is marked solved.
  5. At the end of the month, the report shows 31 tickets tagged “pricing”, 12 of them about currencies. The team writes a help article on currencies and links it from the pricing page.

Step 5 is where a help desk pays for itself, and it only works if the tags are right. A rule that misses half the currency questions makes the problem look half its size.

Help desk vs ticketing system, service desk and shared inbox

These terms get swapped for each other all the time. This is how they differ.

Is a help desk the same as a ticketing system?

Nearly. A ticketing system is the part that files each request as a ticket with an owner and a status. A help desk is a ticketing system with the rest built around it, such as the help centre, chat, saved replies and reports. Most people use the two names for the same product.

Help desk vs service desk

A service desk is the IT version, and usually the bigger one. It takes staff’s requests for new things, such as accounts for a new starter or a replacement laptop, as well as their reports that something broke. Ticketing system explains how IT teams sort those two kinds of ticket.

Help desk vs shared inbox

A shared inbox is the lighter tool. It’s one support address, such as support@, that a few of you read together, and it shows who’s answering each email so nobody replies twice. It feels like ordinary email. You outgrow it when you want chat on your site, a help centre or reports on what people ask.

Help desk vs customer service software

Customer service software is the wider name for anything you answer customers with, whether that’s a help desk, a live chat tool or an AI agent on your site. Our guide to help desk software for a small business ranks eleven of them, with what three people pay on each.

Try Deacon for free

Install Deacon

What a help desk costs

Zendesk, Freshdesk and Help Scout all charge for each person who answers, every month. These are their first paid plans, billed yearly.

Zendesk

Free to start
A 14-day trial
First paid plan, billed yearly
Support Team, $19 an agent a month
Three people a month
$57

Freshdesk

Free to start
A 14-day trial
First paid plan, billed yearly
Growth, $19 an agent a month
Three people a month
$57

Help Scout

Free to start
A free plan with 5 users, 1 inbox and 1 Docs site
First paid plan, billed yearly
Standard, $25 a user a month
Three people a month
$75

The last column is our arithmetic. Zendesk’s Support Team is $25 an agent on monthly billing. Zoho Desk has a Free edition for 3 users, which its pricing page calls Free Forever.

If you’d rather pay nothing at all, free ticketing systems compares the hosted free plans with open source help desks you run on your own server, and what each really costs to keep going. AI help desks sets out how eleven help desks bill the AI agent that answers your customers, by resolution, outcome, session or credit.

When a small team needs a help desk

The number of people answering decides it, more than the number of questions. A help desk is built to share support between people, so it starts to pay when the sharing gets hard.

  • A second person has started answering, and you’ve each replied to the same customer, or each left it for the other.
  • Questions come in by email, chat and social messages, and you’re copying them between tabs to keep track.
  • A customer’s contract promises a reply within so many hours, and you need a warning before you miss it.
  • Searching your inbox is the only way to find what a customer said last month.

Before that, a help desk mostly files your questions in a neater list. What takes a founder’s time is answering the same ones again and again, so the first fix is getting those answered without you. How to reduce support tickets shows how to find which questions those are.

Where Deacon fits beside a help desk

Deacon isn’t a help desk, and a team on a rota with a queue to share still needs one. For a founder who answers support alone, it does the parts of a help desk that matter before there’s a team, and it tells you more about what your customers want than a queue does.

Shared inbox

In Deacon
No. Chats from your site land in Deacon’s dashboard, where anyone on your team can reply, with no routing or assignment and no support inbox for email

Tickets

In Deacon
No ticket numbers, statuses or owners. People waiting for a reply are the first group in What needs you

Knowledge base

In Deacon
Deacon answers from the one you have, along with your site’s pages, files and text you paste in

Live chat

In Deacon
Yes. A chat widget on your site, where Deacon answers first and you reply in the same chat when someone needs you

Saved replies

In Deacon
Each answer you write goes into Deacon’s help document, and Deacon answers from it from then on

Reports

In Deacon
Topics, What needs you and the pages people asked on, below

It shows you which features and fixes customers are waiting on. Topics group similar questions, count the people who asked, and label a group as a feature ask, a bug report or a how-to when one kind leads it. Analytics › Widget lists what visitors asked you to build, in their own words. When one page’s questions go unanswered more often than the rest, and enough people have asked, it names that page as the one where people get stuck.

It shows you what visitors asked on each page. Analytics › Website lists your most visited pages, each with the questions people asked Deacon there and how many it couldn’t answer. It counts the visits from the same script as the chat, so there’s nothing else to add.

What it can’t answer lands on your to-do list. When your docs don’t cover a question, Deacon says it doesn’t know rather than guess, and asks for the visitor’s email. What needs you lists the questions still unanswered, each a click from writing the answer. Once you write it, Deacon uses your answer next time. It shows you the reply it now gives under “Deacon now says”, and the other open questions your answer also covers.

When someone needs a person, you hear about it. The owners on your team get an email about three minutes after a visitor leaves an address or asks for a person, unless one of you has already seen it in the dashboard. Your reply appears in the visitor’s chat under your first name, and one who has closed the chat sees a red count on the chat button. If people log in to your app, it can pass Deacon their name and email, so you see who’s asking and they don’t have to type their email to get a reply.

It’s built for sites made with AI app builders. Deacon goes on your site with one script tag, and Install opens on the steps for your site builder when your home page shows which one it is, Lovable, Bolt, Replit and Base44 included. Every plan has every feature, and the free one asks for no card and has no end date.

Questions about help desks

What does a help desk do?

It collects every customer question in one place, gives each one an owner, and keeps track of it until it’s answered. Most also hold the help articles customers read for themselves, and report on what people asked and how fast the team replied.

Is it help desk or helpdesk?

Both. Some write it as two words and some as one, and they mean the same thing. The Cambridge Dictionary lists it as helpdesk.

What does an IT help desk do?

It fixes problems for a company’s own staff, such as a laptop that won’t start, a password that needs resetting or an app someone can’t get into. An IT help desk job is a common entry-level role in IT, which is why career guides turn up among the results when you search for what a help desk is.

Do I need a help desk if I answer support alone?

Usually not yet. One person can’t trip over a teammate, so the ticket owners and routing do little for you. A help centre and an AI agent that answers on your site save more time, and a help desk earns its place once a second person starts answering.

Can Deacon work alongside a help desk?

Yes, as two separate tools. Deacon has no helpdesk integrations, so it answers visitors on your site and brings the ones that need you to its own dashboard and your email, while your help desk carries on with the rest.

Try it on your own documentation

Add your help pages, ask it the question you know your docs cannot answer, and watch it say so.

Start free

Free plan, no card.