IT Support & Consulting
Internal Helpdesk: Ticket Channels, Priorities, and Response Times
A working internal helpdesk needs three decisions: one official ticketed channel, priority rules you can explain, and time targets that separate first response from resolution. This guide covers all three.
SEO and Content Specialist
7 min read
Short answer: a working internal helpdesk needs three things. One official channel that turns every request into a numbered ticket, priority rules derived from impact and urgency rather than from who asks loudest, and time targets that separate first response from resolution, counted within agreed service hours. The target numbers are set from your team’s capacity and your business needs.
In many offices, IT requests arrive through group chats, private messages, phone calls, and people stopping by the IT staff’s desk. It is fast at first, but nobody knows how many requests are open, which are most urgent, or why the same problem keeps coming back. An internal company helpdesk fixes this in a simple way: one entry point, clear queue rules, and a record that can be read again. This guide explains how to set it up, whether handled by internal staff or a provider, as compared in Subscription IT Support, In-House IT Staff, or Call When Broken.
An internal company helpdesk: one channel for all requests
There can be many channels, but there must be one record. Employees can send a form, email a dedicated address, or call. Whatever the route, the agent creates a ticket and all handling is recorded in that ticket. This rule prevents the three most common problems:
- Lost requests because they lived only in one private conversation.
- No trail when the same problem returns or staff change.
- No measurement, so you cannot answer how many requests came in this month and how many were resolved.
A minimal ticket helps: who is asking, what happened, since when, who or how many people are affected, and the type. The more complete the first entry, the fewer back-and-forth questions. In Legia’s subscription IT support service, all requests come in through one official channel with a ticket number and a handling trail that can be traced.
Separate incidents from service requests
These two ticket types need different treatment, so categorize them separately from the start:
| Type | Meaning | Example |
|---|---|---|
| Incident | Something that used to work is now broken or slow | Wi-Fi down on one floor, internal application won’t open |
| Service request | Something asked for with a known procedure | New employee account, application installation, access to a shared folder |
Incidents are chased as fast as possible because work has stopped. Service requests are better scheduled, and some can be standardized into fixed steps, such as the new-employee account flow in IT Onboarding for New Employees.
Priority: impact and urgency
Priority set by feeling has two effects: everything is treated as urgent, or whoever is loudest always goes first. A common approach in helpdesk tools is a matrix that maps impact (how many people or processes are affected) and urgency (how fast it must be handled) to a single priority level. Atlassian gives a 4 x 4 example matrix in its documentation:
| Impact \ Urgency | Critical | High | Medium | Low |
|---|---|---|---|---|
| Widespread | Highest | Highest | High | Medium |
| Large | Highest | High | Medium | Low |
| Limited | High | Medium | Low | Lowest |
| Minor | Medium | Low | Lowest | Lowest |
Atlassian stresses that the matrix is only an example, and that the meaning of priority and urgency differs from one team to another, depending on resources and other factors. For an office with dozens to hundreds of users, a 4 x 4 table is often too detailed. The simplification below is enough and easy for users to remember. It is the author’s suggestion, not a fixed standard, and the examples are illustrations:
| Priority | Traits | Illustrative example |
|---|---|---|
| High | Many people or core processes stopped, with no workaround | File server or email unreachable for the whole office |
| Medium | One person or one team stopped, or a workaround exists | One employee’s computer won’t start |
| Low | Annoying but work continues, or a scheduled request | Application installation request, peripheral replacement |
Write the table on one page that every employee can read, so setting priority does not feel arbitrary. Also provide a way to raise priority with a written reason, for example “there is an audit deadline tomorrow”.
Response time and resolution time are two different numbers
These two measures are often mixed up, though they mean different things. First response time is the time from the ticket arriving until an agent starts handling or replies. Resolution time is the time until the problem is solved. A provider can meet the first by merely replying while the fix takes days, so the two need to be written separately. Helpdesk tools separate them too: Jira Service Management’s documentation says a new service project immediately has “Time to first response” and “Time to resolution” SLAs.
Atlassian’s documentation describes an SLA timer as a stopwatch with three conditions: start, pause, and stop. From that there are three decisions for you to make:
- When the clock starts. Usually when the ticket is created.
- When the clock pauses. The example in that documentation is a “waiting for customer” status: while the agent waits for the user’s answer, the clock should not run.
- Which calendar applies. Targets are counted within agreed working hours, so time outside the calendar, including breaks, holidays, and weekends, is not counted. The documentation also suggests defining which tickets each target covers through fairly constant criteria, such as priority.
As for the numbers, do not copy another company’s. Set them from three things: the service hours your team can actually cover, the impact of each priority on operations, and your own ticket history. Start with realistic targets, measure for a few months, then tighten them if they are consistently met. How to read these numbers in a contract is covered in What Is an SLA in an IT Service Contract.
One ticket’s path from entry to closure
- Received and recorded with the minimum fields.
- Classified: type (incident or request), category, and priority.
- Assigned to one person responsible, not “the team”.
- Handled and logged: the steps tried and their results are in the ticket, not in chat.
- Escalated if it passes the target or exceeds the owner’s ability, to a pre-defined escalation contact.
- Confirmed by the user that the problem is solved, then closed with its cause.
Step 6 is the one most often skipped. A ticket closed without a cause makes recurring problems invisible.
Measures worth reporting each month
A useful report does not have to be long. These four measures are enough to judge whether the helpdesk is helping:
- Tickets per category, to see where the load is heaviest.
- Most frequently recurring problems, as material for permanent fixes.
- Percentage of tickets meeting targets for response and resolution.
- Age of tickets still open, so none are left behind.
In Legia’s service, the monthly report contains the number of requests, the types of problems that come up most often, and recommendations so they do not recur.
Common mistakes
- Allowing side channels. Requests that go through private chat are not recorded, so the monthly report is incomplete.
- Every ticket is high priority. If so, priority no longer distinguishes anything. Review the rules.
- No escalation owner. Tickets stall because it is unclear who has authority to decide.
- Targets without a calendar. The clock runs at night and on weekends, so targets look like they always fail.
- No asset list. Agents guess which devices and licenses are affected. How to build one is in Inventory of Assets and Software Licenses.
How Legia does it
In the IT Support & Infrastructure Management service, work begins with an initial inventory of 1 to 2 weeks: servers, devices, accounts, licenses, and the state of the network. Legia then opens one official channel, sets up monitoring and backups, and explains them to employees, within 3 to 5 working days. All requests are numbered tickets and tracked. Response time follows the service hours and severity levels written in your contract, with disruptions that stop work handled first. Most requests are resolved remotely. The other services in this pillar are on the IT Support & Consulting page.
Frequently asked questions
Does a small company need a ticket system?
Yes, as long as there are more than a handful of IT requests per week. A ticket system does not have to be expensive or complicated. What matters is one place to record and one priority rule. Without it, workload and recurring problems stay invisible.
Who sets priority, the user or the agent?
Users report the impact they feel, and agents set the priority based on the agreed table. Give users a way to raise priority with a written reason, so both sides have room.
Is response time counted around the clock?
Not necessarily. It is usually counted within agreed service hours. Atlassian’s documentation describes a working calendar that stops the clock outside working hours, breaks, holidays, and weekends. Out-of-hours service can be agreed separately for certain priorities.
What happens when a ticket passes its target?
Escalate to the pre-defined owner, record the cause of the delay in the ticket, and review it in the monthly report. If delays repeat in the same category, check capacity or the category itself, not just the person.


