A support ticket system records every fault report and request about a piece of software, who is dealing with it and how long it has taken. The best software support ticket system for a given company depends mainly on two things: who raises the tickets, and where the developers who fix the problems do their work. On that basis our shortlist for a company of 10 to 500 people is Jira Service Management, Zendesk, Freshservice and Zammad. Each suits a different situation, and they are not listed in order of merit.
What makes supporting software different
A general help desk mostly answers questions. Supporting software also means passing some tickets to developers, because the answer is a change to the code. That adds requirements a shared mailbox cannot meet:
- A link to the developers’ work. The ticket stays with the person who reported it, and a linked item in the developers’ own tracker (Jira, Azure DevOps or GitHub Issues) carries the fix. Each side can see the other’s progress.
- Severity and response targets. A fault that stops the business is treated differently from a spelling mistake, and the system times each ticket against the target agreed for its severity.
- A history. Every ticket is kept, so recurring faults can be spotted and a dispute about what was reported, and when, can be settled by looking it up.
- A way in for users. Email at least, and usually a web form or portal where the reporter can see the status without asking.
How we chose these four
We did not test every product on the market, and we have not ranked these. We looked for products that:
- take requests by email and through a web portal;
- can time tickets against response targets;
- can link a ticket to an item in a developer tracker;
- publish how they charge, and can be tried before buying;
- were being sold and actively developed when we checked in October 2026;
- make sense for an organisation of 10 to 500 people.
The earlier version of this article included ServiceNow. It is still a major product, but it is built for large organisations with a dedicated service management team, so we have left it out on the sixth test.
The four systems compared
| Product | Suits | Hosting | How it is charged |
|---|---|---|---|
| Jira Service Management | Teams whose developers already work in Jira | Vendor’s cloud | Free plan for up to three agents, then per agent |
| Zendesk | Support for customers outside the company | Vendor’s cloud | Per agent, free trial |
| Freshservice | An internal IT desk that also supports business systems | Vendor’s cloud | Per agent, free trial |
| Zammad | Organisations that want open source or their own server | Self-hosted or vendor’s cloud | Free to self-host, hosted per agent |
An agent is a person who works on tickets. These products charge for agents, and the people who raise tickets do not normally need a paid seat.
Jira Service Management
Jira Service Management is Atlassian’s service desk, now sold as part of what Atlassian calls its Service Collection. Its advantage is that it sits on the same platform as Jira, the tracker many development teams use, so a support ticket and the developers’ work on it are linked without any extra integration.
One change matters if you host your own software. Atlassian stopped selling the self-hosted Data Center edition to new customers on 30 March 2026, and that edition reaches the end of its life on 28 March 2029. For a new buyer, Jira Service Management is a cloud product.
It is the natural choice where Jira is already in use. Where it is not, it means adopting Atlassian’s way of working for the sake of a service desk.
Zendesk
Zendesk is a customer service product first. It handles email, web chat, messaging and telephone in one place, with a help centre where customers can find answers for themselves. That makes it a good fit for a company supporting its own software product for outside customers.
Zendesk publishes a free integration that links its tickets to Jira issues. Check which plan you need before comparing costs: response and resolution targets, for example, are not included in the entry-level plans.
Freshservice
Freshservice is the IT service management product from Freshworks. Besides tickets it covers the wider duties of an internal IT team, such as recording changes and keeping a register of equipment and software. Connectors are available for both Jira and Azure DevOps, which is relevant if your developers work on the Microsoft stack.
It suits an organisation whose IT team supports staff and business systems from one desk. Freshworks sells a different product, Freshdesk, for customer-facing support, and the two are easy to confuse.
Zammad
Zammad is an open source ticket system, released under the AGPL licence. You can install it on your own server without a licence fee, or pay the company behind it to host it. It takes tickets by email, telephone and chat, supports response targets, and can link tickets to issues in GitHub and GitLab.
It is worth a look where tickets will contain data you need to keep on your own servers, or where per-agent charges would mount up. The trade-off is that a self-hosted system is one more piece of software for you to update, back up and secure.
If a supplier supports your software
Many companies never choose a ticket system at all, because the supplier that maintains their bespoke system provides one. In that case the questions are different:
- Can you see all your tickets and their current status, not just the ones you raised yourself?
- Is the severity of each ticket recorded, and can you see whether the agreed response target was met?
- Can you export the full history? It is your record of how the system has behaved, and a new supplier will want it.
- Is there a telephone number for urgent faults, so that a serious problem does not wait in a queue?
The response targets themselves belong in the contract. We cover those in why a service level agreement is a good idea and in what a software support contract should include.
Checks to make before you commit
Run a trial with real tickets. Take the last twenty problems your users reported and put them through the system as if they had just arrived. This shows more than any feature list.
Test the link to the developers’ tracker. Raise a ticket, pass it to a developer and follow it back. If the link is clumsy, people will stop using it and go back to forwarding emails.
Count the seats. Per-agent pricing depends on who counts as an agent. Find out whether a developer who only comments on a ticket now and then needs a paid seat.
Find out where the data is held. Tickets contain names, email addresses and often screenshots showing customer records. Check where the vendor stores them and what its contract says about personal data, and take advice if you are unsure of your obligations.
Check you can leave. Confirm that the full ticket history can be exported in a form another system could import.
A shared mailbox is a reasonable start for a small team. The time to move on is when two people answer the same email, or a report goes unanswered because each assumed the other had it.