How to buy help desk software

A help desk is chosen on features and paid for by headcount, and those two decisions are made against different documents. What separates the shortlist from the invoice is who a vendor counts as a user, what they meter besides users, and which of the things you came for sit one tier above the one you were quoted.

This guide is built from prices read off the vendors’ own pricing pages, with the page, the moment it was read and the vendor’s exact wording recorded against every figure. The pricing statements below can be checked rather than trusted — and where we have not read a vendor’s page, the page says so rather than filling the gap with an estimate.

Advice last reviewed 2026-08-03.

What the prices actually say

Measured from the prices we hold, at the moment this page loaded.

  • 13 of the 18 Help Desk Software products we track hold no price we have read from the vendor’s own pricing page. That is a gap in our reading rather than a proven silence from those vendors — some of them hold a price we took from elsewhere and have not yet checked against the source, and we do not record which pages we tried. For 4 of them we hold no price we would print at all, from any source. Everything measured below therefore describes the 5 products whose pricing pages we have read, and does not claim to describe the rest.
  • Every one of the 14 pricing plans we read for Help Desk Software off the vendors’ own pricing pages is priced per seat. Not one of them is a flat fee for the account, so among the plans we read there is none that stops charging you as the team grows. Budget this category by headcount first: whatever rate you settle on, you pay it once for every person you put on it, so the seat count multiplies every other decision you make.
  • Across the per-seat plans we read, the published list price runs from $84 to $1,668 per seat per year. That is the span of what a published seat costs, not the span of what a help desk costs: it is a rate per person, and it does not move with how much anybody uses the product. A seat costs the same whether the person holding it works the queue all day or answers the occasional escalation.
  • Those figures were read from 7 vendor pricing pages between 3 August 2026 and 16 August 2026. Each price we hold records the page it came from, the moment it was read and the vendor’s own wording for what the amount covers. Vendors move prices without announcing it, so open the current page before you sign anything.

Settle what counts as a seat before anyone quotes you

In a category billed per seat, the definition of a seat is the negotiation. We hold no measurement of how any vendor defines one, so do not assume two quotes are counting the same people until you have read both definitions.

The people at the edges of that definition are where the quotes diverge. The engineer who gets pulled into one escalation a month, the account manager who needs to read the history before a call, the finance lead who only wants the reports. Ask about them by name, at each vendor, before you compare two numbers — the answer is not something you can infer from a headline rate.

  • What exactly makes someone billable — a login, a reply, or an assignment?
  • Is there a light, collaborator or read-only seat, and what can it actually do?
  • Can a person be added to a ticket without becoming a paid seat?
  • What is the minimum seat count on the tier you want?
  • Do bots, shared mailboxes or automation rules consume a seat?

Commit for a year, staff for a quarter

A support team is not the same size all year. Headcount can rise for a launch, a migration, a holiday season or an incident, and fall again afterwards. An annual commitment sized to your busiest month means paying for that month in every other one; an annual commitment sized to your quietest means renegotiating under pressure at exactly the wrong moment.

So ask about direction, not just price. Adding seats mid-term and removing them mid-term are two separate permissions, and a contract may grant one without the other. Which of them you have is worth more to your budget than the headline rate, and it is a question you have to put to each vendor rather than one you can read off a pricing page.

Then do the multiplication yourself rather than trusting the saving on the page. Take the month-to-month rate, multiply by twelve, and compare it to the annual price. Sometimes the gap is real and worth the commitment. Sometimes the two numbers are the same, and you would be locking yourself in for nothing.

  • What is the month-to-month rate, and the twelve-month total, as two separate numbers?
  • Can you reduce seats mid-term, or only at renewal?
  • Can you add seats temporarily for a peak and drop them after?
  • Is the annual amount billed up front or spread across the year?
  • What is the renewal price, and is any increase capped in the contract?

Find the meters that are not seats

A seat price is the headline and it is not the whole bill. The list below is the set of things worth asking about separately, because a per-seat rate does not tell you how any of them are counted.

For each one, the useful question is not what the limit is but what happens when you cross it. A cap that stops your team replying to customers on a busy Monday is a different product from one that quietly adds a line to next month’s invoice, and a headline rate distinguishes neither.

  • Tickets, conversations or contacts per month, and the price of the next block.
  • Which channels are included — email, chat, voice, social, messaging — and which are priced apart.
  • Whether a knowledge base or customer portal is included or a separate purchase.
  • Email sending volume, and whether it runs through your domain or theirs.
  • API calls and webhooks, and whether your own integrations count against them.
  • File storage for attachments, screenshots and call recordings, and how long they are kept.
  • Automation rules, workflows or credits, and how they are consumed.

Check which tier holds the one thing you came for

Arrive with your specific requirements written down: service level targets, business hours and holiday calendars, round-robin assignment, a customer satisfaction survey, an audit trail, single sign-on. Find out which tier holds yours at each vendor before you compare entry rates, because a rate you cannot buy is not a price.

That is where the expensive mistake happens, and the tier ladder is what makes it expensive: the step up is charged per seat, so it is paid for every seat including the ones that will never touch the capability you moved for. Before you accept that, ask whether the capability can be bought as an add-on, whether it can be enabled for some seats only, and whether the tier below genuinely cannot be made to do the job.

Write the requirement down before the demos start. A feature list assembled during a demo is a list of the things the vendor chose to show you.

  • Name the capabilities you will not launch without, before the first demo.
  • For each one, which tier is it on, and is it available as an add-on instead?
  • Can a capability be enabled for a subset of seats, or is it account-wide?
  • Which of them are in the trial, and which are switched off until you buy?
  • Are there limits inside the feature — how many rules, how many surveys, how many calendars?

Handle a vendor who will not publish a price

If you meet a vendor who will not put a number in front of you, resist reading a motive into it. We cannot tell you which vendors those are: the pricing section above states how much of this category we have read off vendor pages, and it says nothing about why the rest is missing, because our data cannot tell us. What is true either way is that a missing price is a cost of a different kind — it has to be asked for rather than read, which takes time you have to plan for, and the number that comes back is shaped by what the vendor has learned about you before quoting it.

That is not a scandal — negotiated pricing is a normal way to sell software. It does mean you should not start there. Price the published tiers across your whole shortlist first. That gives you a floor, a ceiling and a sense of what published tiers cost before anyone asks about your budget, and it turns the quote-only conversation into a comparison instead of an opening bid.

  • Ask for the price of the tier below the one they are steering you toward.
  • Ask what specifically triggers the jump to the quote-only tier.
  • Ask for the quote in writing, with the seat count and term it assumes.
  • Ask what the same quote would be at half and at double that seat count.
  • Ask what the price becomes at renewal, not just in year one.

Price the exit while you are still choosing

A help desk accumulates the record of every problem your customers have had and every answer your team gave. Two years in, that archive is the reason changing tools feels impossible — and what it costs to move is decided in this evaluation, not the one you will run later.

Ask what an export actually produces, and ask before you sign rather than after. "You can export your data" covers everything from a complete ticket history with attachments, private notes, timestamps and the agents who wrote them, to a spreadsheet of subject lines.

If you are publishing a knowledge base or a customer portal on the vendor’s platform, ask the same question about the articles and their addresses. A help centre that has been collecting search traffic for two years is an asset, and whether that value survives a migration is a question to settle before you sign.

  • What does a full export contain — conversation threads, private notes, attachments, custom fields, timestamps, agent identities?
  • What format is it in, and can you run it yourself without opening a support ticket?
  • Can you export knowledge base articles, and can you keep their addresses if you move?
  • How long is your data kept after cancellation, and how long can you still reach it?
  • What is the notice period, and does the contract renew automatically?

Run the trial on real tickets, in a real week

A demo tenant is built to make the product look inevitable: a handful of tidy tickets, no backlog, no duplicates, no angry thread that has been reopened four times. Your queue is not shaped like that.

Import a real slice of it, connect the mailbox your customers actually write to, and have the people who will live in the tool work an ordinary week inside it. The question a trial answers is not whether the product can do the thing. It is how many clicks it costs an agent to close a routine ticket, and whether anyone can find last year’s answer to the question being asked again today.

  • Import real tickets, including the messy threads and the duplicates.
  • Connect the real inbound channel on the plan you would actually buy.
  • Have a real agent work an ordinary week, and count the clicks on a routine ticket.
  • Search for something only an experienced agent would know, and see what comes back.
  • Confirm the features you liked are on your tier, not the one above it.

Help desk products we have published

There is nothing to compare here yet. A product appears in this table only once its page is published, so this guide never links you to something you cannot open. The advice above stands on its own and does not depend on the list.

Questions people ask

Is help desk software priced per agent?
That depends on the plan, and this page does not guess: the pricing section above states what we measured across the plans we read from vendors’ own pricing pages, and it changes when that measurement changes. Where a plan is priced per seat, the bill scales with the number of people who work in the tool rather than with the size of your company or your ticket volume.
What is a light agent or collaborator seat?
It is a name given to a cheaper or free seat for someone who needs to see tickets and comment internally but does not reply to customers — an engineer, a product manager or an account owner, for instance. It is not a standard term and we hold no measurement of who offers one or what it includes, so treat it as a question to ask rather than a feature to assume: find out whether such a seat exists on the plan you are pricing, and exactly what it can do, before assuming your occasional contributors are free.
What should I do when a help desk price is not on the vendor’s page?
Ask for it in writing, with the seat count, tier and term it assumes, and price the published tiers on your shortlist first so the answer arrives into a comparison rather than into a vacuum. We will not tell you why a price is missing: we record which products in this category hold a price we read from the vendor’s own pricing page and which do not, we do not record which pages we tried, and guessing at a reason on a vendor’s behalf would be inventing the one thing this page exists not to invent.
Does this guide rank help desk products?
No. A ranking would need review evidence we do not have, and a ranking assembled without it is an opinion wearing a number. This guide explains how the category is priced and what to ask. The comparison below lists the products we have published, with the starting price we hold for each.
How current are the prices behind this page?
Every price we hold records the page it was read from and the moment it was read, and the pricing section above states that date rather than implying the figures are current today. Where we could not establish what a figure meant — a monthly rate or an annual total, a per-seat charge or a whole-account fee — we withhold it and say so instead of printing a number we cannot stand behind.