IT support requests: how to get employee requests in order without a separate helpdesk system
Management9 min read
How to organize IT support requests: intake channels, priorities, response times, assigning to specialists, reporting and how not to lose requests from chats.

IT support requests are employees' appeals for technical help: the printer doesn't work, access to a system is needed, a laptop broke, a new messenger has to be connected. While there are few employees, requests get solved "on the fly". When there are dozens a week, they get lost without a single system, and the IT specialist works in constant firefighting mode.
IT requests in a minute
| Element | How to organize it |
|---|---|
| Entry point | One form or a shared channel instead of private messages |
| Request card | What happened, to whom, how urgent, a screenshot |
| Category | Access, equipment, software, communications, new workstation |
| Priority | Critical, high, normal, low |
| Assignee | Assigned manually or automatically by workload |
| Deadline | Response and resolution time by priority |
| Report | How many requests, which categories, how many overdue |
Why requests get lost
- Too many channels. Some write in Telegram, some call, some catch IT in the corridor.
- No priority. Everything is urgent, so the truly urgent waits in the common queue.
- No status. The employee doesn't know whether their request was picked up and writes again.
- No history. The same problem is solved from scratch every time.
- Workload isn't visible. The manager doesn't understand why IT "can't get anything done".
How to organize request intake: 6 steps
1. One entry point
Choose one main channel: a form on the internal portal, a shared "IT help" chat or a dedicated bot. Politely redirect all requests from other channels there.
2. Required fields
At minimum: what happened, where (workstation, branch), how much it interferes with work, a screenshot or photo. The more precise the description, the fewer follow-up questions.
3. Categories
| Category | Examples |
|---|---|
| Access | New employee, password reset, system permissions |
| Equipment | Laptop, printer, phone, peripherals |
| Software | Installation, updates, errors |
| Communications | Internet, messengers, telephony |
| Workstation | Setting up a place for a new hire, relocation |
4. Priorities and deadlines
| Priority | When | Response | Resolution |
|---|---|---|---|
| Critical | A department is down or clients are affected | 15 minutes | Within the working day |
| High | One employee can't work | 1 hour | 1 day |
| Normal | Work is possible but inconvenient | 4 hours | 3 days |
| Low | A wish, an improvement | 1 day | By agreement |
The deadlines are indicative — set your own based on your team size.
5. Assignment
If IT has several people, requests are assigned by specialization (equipment, software, access) or by workload. It matters that every request immediately gets an assignee rather than hanging "in the common queue".
6. Feedback
After resolving it, send the employee a short message and close the request. If a problem repeats, that is a reason not just to fix it but to look for the cause.
Example of a request card
| Field | Value |
|---|---|
| Subject | Telegram messages aren't arriving in the work account |
| Requested by | Olga, sales department, Tverskaya branch |
| Category | Communications / messengers |
| Priority | Critical — clients aren't getting replies |
| Assignee | Igor (IT) |
| Response time | 15 minutes |
| Status | In progress |
| Comment | Account reconnected, recheck in 30 minutes |
IT support metrics
| Metric | What it shows |
|---|---|
| Requests per week | The overall workload |
| Distribution by category | Where the systemic problems are |
| Response time | How quickly a request is picked up |
| Resolution time | How long it takes to get a result |
| Share of overdue requests | Whether resources are sufficient |
| Repeat requests | Whether problems are truly solved |
If requests of one category repeat every week — for example, "the printer at the branch doesn't work" — replacing the printer is cheaper than continuing to repair it.
Do you need a separate helpdesk system
For large IT departments with dozens of specialists, yes: they need SLAs, a knowledge base and asset tracking. For a company where IT is one to three people, a separate system is often excessive. It is enough for requests to:
- arrive through a single form;
- turn into tasks with an assignee, priority and deadline;
- be visible on a kanban board or in a list by status;
- have history and comments.
This can be done in the same system where the company manages clients and tasks — without another subscription. More in the article on overdue tasks.
Typical processes worth describing in advance
Some requests repeat month after month. For them, it pays to describe the process with steps once instead of building it from scratch every time.
A new employee's start
| Step | Who does it | Deadline |
|---|---|---|
| Get the start date and job title from HR | Department head | 5 days ahead |
| Prepare a laptop and workstation | IT | 2 days ahead |
| Create accounts and email | IT | 1 day ahead |
| Grant permissions in work systems by role | IT + manager | On the start date |
| Connect the work messenger | IT | On the start date |
| Give a short briefing | IT | First day |
It is convenient to tie this process to onboarding through a shared template: more in the article on employee onboarding.
An employee's departure
This process matters more than it seems. Forgotten access of a former employee is one of the most common risks of a client database leak.
- Get the date of the last working day.
- Hand over clients and open tasks to a colleague.
- Disable access to all systems on the last day.
- Keep work conversations and files within the company.
- Collect and check the equipment.
Connecting a new communication channel
The company starts receiving client requests in a new messenger or on a new platform. You need to connect the account, assign people responsible for chats, check notifications and warn the team.
How to build the relationship between IT and the rest of the team
The conflict of "IT does nothing" versus "employees know nothing" exists in almost every company. Simple agreements defuse it:
- Public response times. An employee knows an ordinary request will be picked up within four hours and doesn't write again after ten minutes.
- Visible status. An employee sees the request is "in progress" rather than guessing.
- Short instructions. For frequent questions — a password reset, connecting a printer — a ready step-by-step guide in the shared file storage.
- A monthly report. Leadership sees how many requests were resolved and where problems repeat. This is an argument for a budget for new equipment or a second specialist.
How to work out whether you need a second IT specialist
A simple estimate: take the number of requests per month and the average time per request.
| Indicator | Example |
|---|---|
| Requests per month | 180 |
| Average time per request | 40 minutes |
| Time on requests | 120 hours |
| Planned work (updates, purchasing) | 50 hours |
| Total workload | 170 hours |
| Working hours for one specialist | ~165 |
If the workload is consistently above working time and the share of overdue requests is growing, it is time to think about a second person, or about which recurring problems can be eliminated for good.
Common mistakes
- Taking requests in private messages. They get lost and don't make it into the report.
- Everything is urgent. Without priorities, truly urgent requests wait alongside wishes.
- Not closing requests. The employee doesn't know the problem is solved and writes again.
- Not analyzing repeats. The same problems are solved for months.
- Not showing the workload. Leadership doesn't understand whether a second specialist is needed.

How it works in Mestra
In Mestra, IT requests are ordinary tasks, just with their own process:
- A request form. The form builder creates a form for employees; each submitted request automatically becomes a task.
- Priority, tags and assignee. A task has a priority, category tags, a deadline and an assignee or group.
- List and kanban. Requests are visible by status: pending, in progress, solved, unsolved.
- A process template. For typical requests — for example, "prepare a workstation for a new hire" — a process with steps and a checklist is launched from a template.
- Workload-based distribution. AI gives a new request to the specialist with fewer open tasks.
- Files and comments. Screenshots, conversation and the solution are inside the task, and the history is saved.
- Internal team chat. Urgent questions can be discussed in the internal chat without going to private messengers.
Frequently asked questions
How should I receive requests to the IT department?
Through a single channel — a form or a shared chat — where each request becomes a task with a category, priority, assignee and deadline.
Which priorities should I use for IT requests?
Usually four: critical (a department is down or clients are affected), high (one employee can't work), normal (inconvenient but work is possible) and low (a wish).
How do I assess the workload on the IT department?
By the number of requests per week, response and resolution times, the share of overdue requests and the distribution by category.
Do I need a helpdesk system if the IT department has one to three people?
Not necessarily. If IT is one to three people, it is enough for requests to turn into tasks with a priority and deadline in a shared work system.
How can I reduce the number of requests?
Analyze recurring problems and eliminate their cause, prepare instructions for frequent questions and prepare new hires' workstations in advance.
Summary
IT requests stop getting lost when they have one entry point, a clear priority, an assignee and a deadline. A report by category and repeats helps not only to put out fires but to eliminate their causes.
In Mestra, requests from the form automatically become tasks with a priority and assignee, are visible on a kanban board, and AI distributes them based on workload. Try Mestra free for 15 days at mestra.chat.


