When customer or staff support runs through a shared inbox, requests get missed, two people answer the same email, and nobody can say how long customers wait. A ticketing system fixes that by turning every request into a tracked item with an owner, a status and a history. An open source helpdesk gives you that structure without per-agent licence fees, and lets you host it where you choose.
What a helpdesk system does
Whatever product you choose, look for these core capabilities:
- Multi-channel intake: email at minimum, plus web forms, and possibly chat, phone notes or social channels.
- Ticket lifecycle: statuses (new, open, pending, resolved, closed), priorities and categories.
- Assignment and routing: automatically send tickets to the right team or person based on rules.
- SLA tracking: service level targets for first response and resolution, with alerts before they are breached.
- Canned responses and macros: reusable replies and actions for common requests.
- Knowledge base: self-service articles that reduce repeat questions.
- Customer portal: customers can see and update their own tickets.
- Reporting: volumes, response times, backlog and agent workload.
- Integrations and API: links to CRM, user directories, monitoring and chat tools.
Well-known open source helpdesk options
The projects below are established and actively used. Features, editions and licences change over time, so check each official site for current information.
Zammad
Zammad is a modern web-based helpdesk with a fast interface, multi-channel support (email, chat, phone, and integrations with messaging and social platforms), a knowledge base, SLAs and solid reporting. It suits teams that want a contemporary agent experience. It runs on Linux with PostgreSQL and is typically paired with a separate search engine (Elasticsearch or a compatible alternative) for fast search, so hosting needs are moderate rather than minimal.
osTicket
osTicket is a long-established PHP and MySQL ticketing system. It covers the essentials well: email and web form intake, help topics, routing, SLAs, canned responses and a customer portal. Its interface is more traditional, but it is lightweight and simple to host, which suits small teams and internal IT support.
GLPI
GLPI combines a helpdesk with IT asset management, tracking computers, software licences and equipment alongside tickets. It is a strong fit for internal IT departments that want incidents linked to the assets involved.
Others
Other projects, including some with ITIL-oriented features for IT service management, are worth evaluating if your processes are more formal. Apply the same criteria below.
Comparing options
| Question | Why it matters |
|---|---|
| Who are the users: customers, employees or both? | Customer support needs portals and multiple channels; internal IT may need asset links |
| Which channels do you need now and in a year? | Adding channels later may require a different product |
| How complex is routing? | Multiple teams, languages or products need flexible rules |
| Do you need formal SLAs? | Contracts with response commitments need reliable tracking and reporting |
| What must it integrate with? | CRM, single sign-on, monitoring or chat tools |
| Who will host and maintain it? | Some options are lighter to run than others |
| Is a hosted or supported edition available? | Useful if you prefer not to manage servers |
Setting up an open source helpdesk
1. Design your workflow first
Before installing anything, agree on categories, priorities, teams and statuses. Keep it simple: a handful of categories that match how work is actually divided is better than a long list nobody uses consistently.
2. Define service levels
Set realistic targets for first response and resolution by priority, and decide business hours and holidays. Configure these in the system so it can warn agents before targets are missed.
3. Configure email properly
Connect your support mailbox and make sure outgoing mail is authenticated with SPF, DKIM and DMARC records for your domain, so replies reach customers instead of their spam folder. Test threading so customer replies attach to the correct ticket.
4. Build the knowledge base gradually
Start with answers to the ten most common questions. Add articles whenever agents notice they are writing the same reply repeatedly.
5. Integrate where it saves time
Single sign-on for agents, customer data from your CRM and alerts from monitoring tools can all reduce manual work. Add integrations once the basics are working.
6. Secure and maintain it
Run it over HTTPS, enforce strong authentication for agents, keep the application and server updated, and back up the database and attachments off the server. Support tickets often contain personal data, so restrict access appropriately and set retention rules.
Making it stick
- Route everything through the system. Requests handled outside it, by direct email or chat, undermine reporting and accountability.
- Review reports regularly to spot recurring problems that could be fixed at the source.
- Refine categories and rules after the first month based on real data.
- Ask for feedback from customers, for example a short satisfaction rating when tickets close.
Open source helpdesk or SaaS?
SaaS helpdesks are quick to start and need no server administration, but per-agent pricing grows with your team and advanced features often sit in higher plans. An open source helpdesk makes most sense when you have several agents, want control over data, or need integrations that subscription tiers restrict. Our open source solutions cover helpdesk selection, installation and integration, and server management keeps the platform updated and backed up.
Key takeaways
- A ticketing system brings ownership, tracking and reporting to support requests.
- Zammad, osTicket and GLPI suit different needs, from modern multi-channel support to internal IT with asset tracking.
- Design categories, priorities and SLAs before configuring the software.
- Authenticate outgoing email, secure the system, and route every request through it.