An HR helpdesk that IT cannot read

HR requests are not IT requests with different words on them. They are more sensitive, more repetitive, and more damaging when they go to the wrong person. Here is how to run both desks in one system without HR ending up inside the IT queue.

Why HR gets put in the IT helpdesk, and why it usually goes wrong

It starts sensibly. IT already has a ticketing tool, HR is drowning in "what is my leave balance" emails, and somebody suggests a second queue. Two weeks later an HR coordinator raises a ticket about an employee's salary revision, and discovers that every IT engineer can read it, because most helpdesk tools treat permissions as a nice-to-have bolted onto a flat ticket table.

The damage is not usually a leak. It is that HR quietly stops using the system for anything that matters, goes back to email for the sensitive half of their work, and you are left with a queue that handles ID card replacements while the real workload is invisible again.

The fix is not a separate product with a separate bill. It is that queue membership, not job title, should decide what a person can see — and that the default for a new queue should be closed rather than open.

How the separation actually works here

None of that requires a second workspace, a second invoice or a second login for the people who work in both. One bill, one set of reports for whoever is allowed to see them, and one place employees go for help regardless of which team owns the answer.

• A queue has its own agent list. An IT engineer who is not on the HR queue cannot see HR tickets in search, in reports, in exports or by guessing a ticket URL.
• Administrators are not automatically readers. A platform admin can manage the queue without being able to open its tickets, which is the distinction most tools miss.
• Every view of a restricted ticket is written to the audit log, including by admins, so "who read this" is a question with an answer.
• Attachments inherit the ticket's permissions. A payslip attached to an HR ticket is not a public file with an unguessable URL.
• The knowledge base has the same split: an HR policy article can be visible to all employees, to one department, or to HR only.

The requests an HR desk actually gets

Across the HR desks we have seen set up, the volume is remarkably consistent. Roughly half is information that is written down somewhere nobody can find: leave policy, notice period, reimbursement limits, insurance cards, which form to use. A quarter is transactional — letters, certificates, address changes, bank detail updates. The rest is genuinely case-by-case, and that is the part worth the team's attention.

Which is why the first thing an HR desk should build is not a workflow but a knowledge base. Twelve well-written articles will absorb a third of the volume within a quarter, and unlike a workflow they help the person at eleven at night when nobody is on the desk.

• Leave policy and how to apply, with the actual balances explained.
• Reimbursement: what is claimable, the limits, and the deadline each month.
• Insurance: the card, the network hospitals, and how to claim.
• Employment and address-proof letters: what to ask for and the turnaround.
• Notice period, exit process and what happens to unused leave.
• New joiner: the first-week checklist, and who to ask for what.

Onboarding and offboarding, where the two desks meet

The one place HR and IT genuinely need to be in the same system is a joiner or a leaver. HR knows the start date; IT provisions the account and the laptop; finance needs the bank details; the manager needs to know none of the above went missing. Run that as one parent request with tasks assigned across teams, and every team sees only their own task while HR sees whether the whole thing is on track.

Offboarding is the same shape and higher stakes. An account that stays live after someone leaves is the most common audit finding in mid-size Indian companies, and it is almost always a communication failure rather than a technical one. A checklist that both teams can see fixes more of it than any tool feature. We publish a free offboarding checklist template, which is a reasonable place to start even if you never buy anything from us.

What this costs

HR agents are agents, and cost the same as IT agents. Employees raising HR requests are requesters, and are free and unlimited like every other requester. A three-person HR team answering requests for six hundred employees is three seats.

There is no separate HR module to license, and no per-employee fee that makes the system more expensive as you hire. If that seems like leaving money on the table, it is — we would rather you put HR on the desk than decide it is too expensive to bother.

Questions