What is an IT ticketing system, and when do you need one?
An IT ticketing system turns a request for help into a record with a number, a status, an assignee and a history. Instead of searching inboxes and relying on corridor conversations, the IT team can see what needs doing and employees can see where their request stands. This guide explains how it works and when it pays off.
At a glance
A ticketing system turns emails, phone calls and corridor requests into numbered tickets with a status and an assignee. It pays off as soon as more than one person handles IT or requests get lost. Good systems make reporting easier than calling, otherwise nobody uses them.
What an IT ticket contains
A ticket is a request with a memory. “The printer on the second floor prints only blank pages” becomes ticket #1278, with the person who reported it, the device, a category, a priority, an assignee in IT and a history of replies and notes. The ticket stays open until it is resolved, and can still be read afterwards. Anyone covering for a colleague can pick up the history.
The difference from email is organisational, not technical. An email sits in one mailbox and is either read or unread. A ticket has a status that looks the same to everyone: new, in progress, waiting for reply, resolved. Reading a message no longer makes it disappear from everyone else’s to-do list.
The five stages of a ticket
- Report it. Someone sends an email to the IT address, fills in a form in the portal or scans a QR label on the device. That creates a ticket with a number.
- Sort it. IT or a rule sets the category and priority and assigns the ticket to someone.
- Work on it. Follow-up questions, internal notes, attachments, perhaps an appointment at the person’s desk. It all ends up in the history.
- Resolve it. IT sets the ticket to resolved. The requester is notified and can object.
- Close it. After a while without a reply, the ticket is closed. It is kept for reports and later questions.
The main parts of a ticketing system
- Intake. A mailbox, a portal, sometimes phone or chat. Every channel ends up in the same ticket.
- Status. Shows where a ticket stands. Good systems have a “Waiting for reply” status, so that deadlines do not run unfairly.
- Assignment. One person is responsible. Not “IT”, but Deniz.
- Deadlines. How quickly to respond and resolve, often called SLAs.
- Knowledge. Guides, so that the same question is not answered from scratch every time.
- Reports. How many tickets, how fast and on which topics.
You do not need every feature on day one. A reliable queue is more valuable than an elaborate workflow nobody understands.
Signs that a shared inbox is no longer enough
There is no fixed number. These signs point towards a ticketing system:
- More than one person handles IT requests.
- Requests get lost because they arrive in the corridor, in Teams and by email.
- People ask whether their request arrived.
- On holiday, nobody knows what is open.
- Management asks how much IT has to do, and there is no answer.
If one person does IT on the side and an email arrives every couple of days, a ticketing system is overhead. A shared inbox is enough then, and that is no failing.
Three common concerns
“A ticket will make everything slower”
Only if reporting is more awkward than a phone call. A form with twelve mandatory fields gets bypassed. A form that already knows the device and the room gets used.
“A ticketing system monitors the people in IT”
It can produce reports per person. Whether and how you use them is a decision to make deliberately: agree what will be measured, who can see it and why, and involve the works council early where there is one. See ticketing and the works council.
“We need to introduce ITIL first”
No. Most internal IT teams with fewer than five people need tickets, statuses, deadlines and knowledge. Change and problem management based on ITIL comes when it is needed, and often never.
How employees experience a ticketing system
For people in the company, a ticketing system is at best invisible. They write an email as before or fill in a short form, get a number and later an answer. What they notice is the difference afterwards: they no longer have to ask whether their request arrived, because they can see the status themselves.
At worst it is an obstacle. Anyone who has to create an account, pick one category out of twenty and look up an asset tag just to report a broken printer would rather phone. That is why the success of a ticketing system depends less on the IT console than on the report form that everyone else uses.
Three kinds of system: internal IT, customer service, ITSM
Very different tools go by the name “ticketing system”. Customer service tools are built for requests from outside, with chat, phone and social media. ITSM platforms model the processes of ITIL, with change management, problem management and a CMDB (configuration management database). Internal help desks focus on requests from your own people to your own IT, with a portal, devices and knowledge.
For a company of 20 to 500 people with a small IT team, the third kind is usually the right one. The first two can do more, but they need more setup and more explanation.
A small example
Monday, 09:10 (Europe/Berlin). At the fictional company Brenntal Armaturen, the projector in the meeting room shows no picture. Jana scans the QR label on the device, and the form already knows the room and the device, so she writes one sentence. Before she sends it, the system suggests a guide. It does not help, so Jana sends the request: ticket #1287. Deniz sees it in his list at 09:20, with a deadline of 14:00. At 09:41 the cable has been replaced and the ticket is resolved, and Jana taps thank you. Everything is in the history, in case the projector acts up again next week.
What happens without a ticketing system
Without a system, you end up with systems of your own: a notebook next to the keyboard, a spreadsheet, flags in Outlook, notes stuck to the monitor. Each of them works as long as one person maintains it and is never ill. A spreadsheet can list open work, but the replies still sit in mailboxes, and notes depend on someone remembering to update a row.
The problem only shows with holiday, illness or resignation, and then all at once, because the context goes with the person. A ticketing system keeps the conversation and the work in the same place.
What to look for when choosing
- Can someone report a problem without instructions? Try it with a person from accounting.
- Does it support your sign-in method, such as Microsoft 365?
- Do deadlines run on your business hours and public holidays?
- Are prices based on support staff or all accounts, and which features cost extra?
- Where is the data hosted, and is a data processing agreement available?
- Can you export your data when you leave?
Next, use the rollout plan, compare cost models or look up terms in the glossary.
Frequently asked questions
Is a help desk the same as a ticketing system?
Almost. A help desk is the support service that takes in requests, and a ticketing system is the tool for it. In everyday speech, both words are often used for the software.
Does a company with 30 employees need one?
Not necessarily. If IT runs on the side and little comes up, a shared inbox is often enough. As soon as requests get lost or someone needs cover during holidays, a ticketing system helps. The number of channels, lost requests and people involved matters more than headcount alone.
How does ticketing differ from ITSM?
ITSM stands for IT service management and covers more than tickets, for example change and problem management based on ITIL. Ticketing is the core of it, but not all of it. A small internal IT team can start with ticketing without adopting a complete ITSM framework.
What does a ticketing system cost?
From free, for open-source software you run yourself, to a few hundred euros a month. Hosting, maintenance and setup still take time. How to compare fairly is covered in the cost guide.
Further reading
- Roll out an IT ticketing system in four weeksHow to roll out an IT ticketing system in a small company without a big project: a four-week plan, an announcement email template, common mistakes and starter categories.
- Shared mailbox or ticketing systemFive signs your shared Outlook inbox needs a ticket queue. Compare ownership, deadlines, reporting and costs, while keeping your existing IT email address.
- GlossaryPlain-English definitions of help desk terms: SLAs, response time, escalation, knowledge base, Entra ID, MCP and DPA, with links to practical guides.