A help desk ticketing system collects every customer request, from email, chat, web forms and social messages, into one queue where each request gets an owner, a status and a history. To pick one, list the parts your team needs, then check which tool covers them on the plan you would actually use. Small teams can start on a Free plan from Help Scout, Tidio or Zoho Desk. Growing email teams fit Zendesk or Freshdesk, chat-first teams LiveChat or Tidio, and online stores Gorgias.
What a help desk ticketing system has to cover
No single feature fixes scattered requests. A working setup has five parts, and a tool earns its place by how many of them it covers. The method behind each part is in our guide to how a ticketing system organizes requests. Here they are as a shopping list, in the order a request meets them.
- Intake. Every channel you answer lands in one queue: the support address, the website, social messages.
- The record. Each request becomes a ticket or thread with a status and a requester linked to earlier requests.
- Ownership. One assignee per request, plus a warning when two agents open the same one.
- Rules. Assignment, tags and status changes happen without anyone remembering to do them.
- Visibility. Views or folders show what is waiting, on whom, and since when.
Two neighbors matter too: a help center that lets customers answer themselves, and timers that hold the team to a response promise. They come later. A queue that loses requests cannot be rescued by a good help center. One scope note: if your requests come from employees about laptops and passwords, IT teams use their own class of service management tools. This guide is for customer support.
Use the trial with your actual support address, not a test inbox. A week of real traffic shows gaps in channels, statuses and rules faster than any feature list.
Starting with a free ticketing system
Three help desks in our catalog have a Free plan: Help Scout, Tidio and Zoho Desk. Zendesk, Freshdesk, Gorgias and LiveChat offer trials only. A free help desk ticketing system is a real option for a founder or a small team. Know the ceiling before customers depend on it, because each free plan stops at a different point.
Zoho Desk: a ticket queue for up to three people
Zoho Desk Free gives up to 3 users email ticketing on 1 support address. You forward your existing mailbox from Gmail, Google Workspace or Office 365, and each email becomes a ticket with the state Open, On Hold or Closed. Express raises the ceiling to 5 users and adds social channels and ticket merging. A sixth agent needs Standard. Our walkthrough of Zoho Desk ticket statuses and merges covers the queue itself.
Forwards your Gmail, Google Workspace or Office 365 support mailbox into one queue where every email, form, social message, chat or call becomes a ticket with an Open, On Hold or Closed state.
Help Scout: shared email that stays email
Help Scout works differently. Its shared Inbox holds conversations rather than tickets, so customers see an ordinary email reply. The Free plan covers email with collision detection, notes and assignment. It stops short of workflows, SLAs, routing and AI, and it allows 10 saved replies. Live chat and social messages join the same Inbox from Standard. That suits a team that wants order without making customers feel processed.
Collects support email in a shared Inbox of conversations with collision detection, notes and assignment, so each customer gets one reply from one owner.
Tidio: website chat and email together
Tidio puts live chat, email, Messenger, Instagram and WhatsApp into one shared inbox, and email ticketing is on Free. It is the free starting point for a team whose customers mostly begin on the website. Macros and automatic assignment arrive on Growth. On Free, watch the monthly conversation cap: once it is reached, agents cannot see new conversations until the reset or an upgrade.
Brings live chat, email, Messenger, Instagram and WhatsApp into one shared inbox, with email ticketing included on the Free plan.
Self-hosted versus a cloud-based ticketing system
Free can also mean open source. osTicket describes itself as an open source support ticketing system that is completely free [1]. The catch is the server. Its installation guide asks for a web server, PHP and a MySQL database with full privileges, plus general knowledge of all three [2]. A cloud-based ticketing system removes that job. NIST defines cloud computing as resources provisioned and released with minimal management effort [3]. Every help desk in this guide offers a trial or a Free plan, so you can test it on real traffic before you commit.
A two-step path: free inbox now, help desk later
The most common combination costs nothing at the start. Run a shared address in Gmail or Outlook while one or two people answer, as our guide to a free shared inbox in Outlook or Gmail shows. Move when two people answer the same email, or when a message sits with no owner. Keep the same support address and forward it in. Help Scout confirms forwarding with a verification code.
With Help Scout fed by forwarding, a reply typed in Gmail instead of the Inbox breaks the link to the conversation. Tell the team to answer only inside the help desk.
Ticket management for growing email teams
Past a handful of agents, the ticket record starts to carry the work. Everyone needs to read statuses the same way. Each person needs a queue. Rules need to hand out new work. Zendesk and Freshdesk are built around that record. Neither has a free plan; both offer a trial, which is enough to forward a real address and watch a week of traffic land.
Zendesk: views as working queues
In Zendesk, every incoming email, chat, call or social message becomes a ticket, and views act as the working queues. Tickets move from New through Open, Pending, On-hold and Solved to Closed. Agents cannot close tickets themselves; an automation does it after Solved, and a reply to a closed ticket starts a follow-up. Side conversations bring in colleagues without leaving the ticket. Our guide to Zendesk views, triggers and macros walks through the setup. The plan matters here: Support Team is email ticketing only, while chat, WhatsApp and social messaging arrive with Suite Team.
Turns every email, chat, call or social message into a ticket, uses views as working queues, and moves tickets from New to Closed with side conversations for colleagues.
Freshdesk: one shared inbox with routing rules
Freshdesk turns email, its customer portal, web forms, Facebook and phone apps into tickets in one shared inbox. Collision detection shows when a colleague is already viewing or replying. On Growth you route tickets by hand or by rule. Automatic assignment, round-robin or by load, needs Pro. Two limits shape daily work. Merges cannot be undone. Standalone Freshdesk also has no live chat or messaging channels, which sit in Freshdesk Omni.
Gathers email, portal, web forms, Facebook and phone apps into one shared inbox of tickets, warns when a colleague is already replying, and routes tickets by rule.
One queue for chat, social and email
Some teams hear from customers mostly in real time. For them, a ticket system that treats chat as an extra misses the main channel. The queue has to hold live conversations and slower email side by side.
LiveChat (now sold as Text) keeps chats and tickets in one inbox, alongside WhatsApp, Messenger and Instagram. Email reaches it by forwarding from Gmail, Microsoft 365, Yahoo or Outlook, and each message becomes a ticket. Statuses run Open, Pending, On hold, Solved and Closed, with priorities from Low to Urgent, on Essential. A chat that needs follow-up can turn into a ticket from the archive. Essential keeps 60 days of conversation history; Growth keeps it all. Our LiveChat messaging channels guide covers each connection.
Keeps chats and tickets in one inbox with WhatsApp, Messenger and Instagram, turns forwarded email into tickets, and gives each ticket a status and priority.
Tidio, covered in the free section, belongs in this group too. Its inbox already mixes chat, email and social messages on the Free plan.
Write down what Open, Pending and Closed mean for your team before the first ticket arrives. Every report you run later depends on those definitions.
When the requests come from an online store
Store support asks one extra question of every ticket. Which order is this? Gorgias answers it with a unified inbox built for online stores. Recent Shopify orders sit beside each conversation, and agents can edit, cancel or refund an order from the ticket. Statuses stay short: Open, Closed and Snoozed. It is a store help desk, not a general one. Starter includes 3 user seats, so a growing store team plans for Basic.
Puts store email, chat and social messages in one inbox and shows the customer's recent Shopify orders beside each conversation, so agents can edit, cancel or refund from the ticket.
Choosing a ticket system by channel and team size
Start from the channel most of your customers use and the size of the team that answers. Then test the ceiling of the plan you would buy, not the top plan.
| Your situation | Start with | Check before you commit |
|---|---|---|
| Founder or up to 3 people, mostly email | Zoho Desk Free or Help Scout Free | User ceiling; no workflows or routing on Help Scout Free |
| Website chat and social first | Tidio or LiveChat | Tidio's monthly conversation cap; history length on Essential |
| Growing email team that needs rules and views | Zendesk or Freshdesk | Support Team is email only; automatic assignment needs Freshdesk Pro |
| Shopify store | Gorgias | User seats on Starter |
Run one test on any shortlist. Forward your real support address during the trial, have two people open the same message, and check three things: does each request get one owner, does the second agent see a warning, and can you find last month's thread for that customer? A tool that passes all three on your plan keeps every request in one queue with one owner.
Frequently asked questions
What is the difference between a help desk and a ticketing system?+
A ticketing system is the queue: each request gets a record, an owner and a status. A help desk wraps that queue with channels, saved replies, a help center and reports.
Can I keep my support email address when I switch to a help desk?+
Yes. You forward the existing address into the help desk. Zoho Desk accepts forwarding from Gmail, Google Workspace and Office 365, LiveChat from Gmail, Microsoft 365, Yahoo or Outlook, and Tidio from any provider.
Do customers see a ticket number?+
It depends on the tool. Help Scout shows no ticket numbers by default, so replies read like normal email. Zoho Desk can thread replies by ticket ID from Standard, and Zendesk and Freshdesk give each request its own ticket record.
Should an IT team use a customer service ticketing system?+
Usually not. IT teams that track devices, access and outages use service management tools; LiveChat's maker itself points strict ITIL teams to ServiceNow or Jira Service Management.
The bottom line
A help desk ticketing system works when every request lands in one queue with one owner and a visible status. Pick by channel and team size, not by feature count. Small email teams can start free on Zoho Desk or Help Scout, and chat-first teams on Tidio. Growing email teams move to Zendesk or Freshdesk, chat-heavy teams to LiveChat, and Shopify stores to Gorgias. Whatever you choose, forward your real address during the trial and test ownership before you migrate.
- [1] osTicket (Nov 2026) https://osticket.com/
- [2] osTicket documentation (Nov 2026) https://docs.osticket.com/en/latest/Getting%20Started/Installation.html
- [3] NIST Computer Security Resource Center (Nov 2026) https://csrc.nist.gov/pubs/sp/800/145/final