Helpdesk software: how to choose one
Helpdesk tools are built for support teams whose whole job is support. If support is one of the things you do — between projects, alongside the invoicing — most of the category is priced and shaped for somebody else.
What to look for
Is support your product or part of your service?
A support team of twelve needs routing, SLAs and reporting. A team of four answering clients between other work needs a shared queue that nobody has to administer.
What does a ticket cost you?
Per-agent pricing is the norm and the entry prices in this category are high. Count everyone who occasionally replies to a client — that is your seat count, and it is usually larger than expected.
Can support work reach an invoice?
For billable support this is the whole question. If hours spent on a ticket cannot become an invoice line, somebody is retyping them or, more often, not billing them at all.
Does a ticket connect to the work it causes?
Most requests turn into a task for somebody. If the ticket and the task live in different systems, the client is told it is being handled and nobody can see by whom.
How does a client raise a ticket?
Email, a form, a portal, a chat widget. Clients who have emailed you for years will keep emailing; check the tool turns that into a ticket rather than demanding they learn a new way.
Do you actually need SLAs?
SLA timers, escalation rules and satisfaction surveys are what the higher tiers sell. If nobody has contractually promised a response time, you are paying for reporting you will not read.
What happens to the history?
The value of a helpdesk shows up two years in, when you can find what was agreed with a client in 2024. Ask about retention and export before that history exists.
Is the knowledge base worth having?
A public help centre pays for itself when the same question arrives weekly. If your requests are all bespoke, it is a section you will never fill in.
Kinds of tool on the market
Enterprise support platforms
The full apparatus: routing, SLAs, automation, reporting, a public help centre. Built for support as a department, and the price and setup effort assume one.
Shared inbox tools
Email, made collaborative — assignment, internal notes, no ticket numbers in the client's face. Lighter to adopt, and they stop at the inbox.
Chat-first tools
A widget on your site with a ticket system behind it. Excellent when requests arrive from strangers browsing, less relevant when your clients are named and under contract.
All-in-one platforms with a helpdesk module
Tickets on the same data as the projects and invoices, so a request can become a task and the hours can be billed. Fewer support-specific features, and no seat charged for the person who replies twice a month.
What the tools on the market cost
Entry prices for a single agent, from each vendor's own pricing page. This is the most expensive category a small service business is likely to shop in, which is why the seat count matters more here than anywhere else.
| Tool | Best for | Price |
|---|---|---|
| Zendesk | Support at scale, with a help centre and full reporting. | From 19 USD per agent a month, billed annually |
| Freshdesk | A cheaper route to the same shape of product. | From 19 USD per agent a month billed annually; automation sits in the 55 USD tier |
| Help Scout | Teams that want a shared inbox, not a ticket system. | 25 USD per user a month; annual billing is advertised as 16% less |
| Front | Client communication managed like an inbox, at scale. | From 65 USD per seat a month, billed annually |
| Oplero | Billable support that has to reach the invoice. | Free during the beta, then 1.99 USD per user a month |
Prices checked July 20, 2026
Common mistakes
Buying a support platform for occasional support
The features that justify the price — routing, SLAs, deflection — are the ones a four-person team never switches on. Match the tool to the volume you actually have.
Counting only the people who answer daily
Per-agent pricing catches everyone with an account. The colleague who replies twice a month costs the same as the one who lives in the queue.
Letting support work go unbilled
For contracted support this is the most expensive mistake in the category. If tickets and time live apart, the hours are real and the invoice does not show them.
Forcing clients into a new channel
A portal nobody uses is worse than an inbox everybody does. Whatever you choose has to accept the email a client sends out of habit.
Where Oplero fits
Oplero's helpdesk is a module in the workspace rather than a product of its own: a client's email becomes a ticket, the ticket becomes a task somebody owns, the time on it carries their rate, and the hours reach the invoice without being retyped. Clients follow their requests in the same branded portal that holds their quotes and invoices. It has no SLA engine, no CSAT surveys and no deflection reporting — if support is your business, a dedicated platform will serve you better. If support is part of the service you bill for, this is the connection the dedicated ones do not make.
Frequently asked questions
What is helpdesk software?
A system that turns incoming client requests into tickets with an owner, a status and a history, so nothing is lost in a shared inbox. The category ranges from full support platforms with routing and SLAs to shared inboxes that add assignment and internal notes to ordinary email.
How much does helpdesk software cost?
Entry tiers typically run from 19 to 65 USD per agent a month, and pricing is per agent almost everywhere. That makes the honest cost depend on how many people in your team ever reply to a client, not on how many tickets you handle.
Can a helpdesk bill for the time spent on a ticket?
Rarely on its own. Most helpdesk tools have no rates or invoicing, so billable support means integrating a timer and an invoicing service, or accepting that some of those hours go unbilled. Tools where tickets, time and invoices share one database — Oplero among them — do it without the integration.