HR Service Desk: Handling Employee Requests Without the Inbox

An HR service desk gives employees one place to ask HR for things — pay questions, leave, contracts, letters, benefits, workplace concerns — and gives HR a queue where every request has an owner, a status and a deadline. What sets it apart from an IT desk is privacy: HR requests often contain salary, health or personal details, so the queue must be visible only to HR, enforced by permissions. Add self-service for policy questions and payroll-aware deadlines.

Why HR outgrows email

HR teams typically receive requests by email, chat and hallway. The problems mirror IT's — lost requests, "any update?" chasers, no numbers — with two additions:

• Sensitivity. A salary question forwarded to "whoever handles this", or visible in a shared inbox, is a confidentiality breach.
• Deadlines that matter legally or financially. A pay error found after the payroll cut-off waits a month; a visa letter needed by Friday is useless on Monday.

Categories that fit HR

Use categories in employees' words, each with an owner and a target. An example:

Category	Examples	Typical target	Notes
Pay and payslips	Missing overtime, tax code, payslip access	2 business days; faster near payroll	Escalate before cut-off
Leave and absence	Balance corrections, unusual leave	2 business days	Routine requests go through the leave workflow
Letters and documents	Employment verification, visa letter	3 business days	Ask for the deadline on the form
Contracts and changes	Hours, role, address, bank details	5 business days	Some need manager approval
Benefits	Insurance, pension, enrolment	3 business days	Often involves a provider
Policy questions	"Can I work abroad for two weeks?"	2 business days	Prime self-service candidates
Workplace concern	Grievances, wellbeing	Same day acknowledgement	Most restricted queue

Targets are illustrative; set yours from your own history. How categories and targets work in general is covered in help desk ticket categories.

Privacy: enforced, not promised

An HR desk must guarantee who can see what:

• Only HR sees HR requests. Not IT, not managers, not other employees — enforced in the system's permissions, so a misconfigured screen or direct API call can't expose them. LetRelay enforces access with database row-level security; see role-based access for internal tools.
• Tighter scopes for the most sensitive categories. Workplace concerns may be visible only to named HR leads.
• Requesters see their own requests and nothing else.
• Managers see what they need to approve, not the full request history.
• Minimize what you collect. Don't ask for a medical reason when a date range is enough.

European data-protection law is a useful reference even outside Europe: GDPR's principles include data minimization and purpose limitation, and it treats health data as a special category needing extra protection. Sick-leave reasons and wellbeing concerns fall squarely there.

Leave: a workflow, not a ticket

Routine leave requests shouldn't be free-text tickets at all. A structured leave flow — type, dates, half-day, reason — routed to the right approver, with nobody able to approve their own leave, handles them faster and more accurately. The HR desk then handles the exceptions: balance disputes, unusual leave, policy questions. See attendance and leave management for small teams.

Deadlines that know about payroll

Generic targets miss HR's calendar. Two practical adjustments:

• Ask for the requester's deadline on categories where one exists (letters, visa documents) and use it to set the request's due date.
• Escalate pay requests before the payroll cut-off, not after their generic target. A pay correction filed two days before cut-off should jump the queue.

Self-service for policy questions

A large share of HR questions are about policy: holiday carry-over, expenses limits, parental leave, working abroad. Each answered once in a clear article saves every repeat:

• Title articles as employees ask ("Can I carry over unused holiday?").
• Put the short answer first, then details and exceptions.
• Show matching articles while people type a new HR request.
• Keep an owner and review date — policies change.

The method is in how to write knowledge base articles. An AI assistant can answer from those articles if it's grounded strictly in them and says "ask HR" when they don't cover the question — HR is a bad place for a model to improvise. See RAG for internal documentation.

HR and IT: sharing a desk without sharing data

Many companies run IT and HR from the same request desk: one front door for employees, separate private queues behind it. That works well if:

• The team picker routes clearly ("Pay, leave, contracts or benefits → HR").
• Each team's queue is private to that team.
• Cross-team requests — onboarding and offboarding — are split into linked parts, so IT sees "create accounts for Priya, starting 3 November" without seeing her salary. See the IT onboarding checklist and the offboarding checklist.

A worked example: a visa letter

Monday 10:00 — Arjun files a request under Letters and documents: "Employment verification letter for my visa appointment." The form asks for the deadline; he enters Thursday, because his appointment is Friday morning.

• The request's due date becomes Thursday 12:00 — not the category's generic three business days, which would have been Thursday end of day and too late to print and collect.
• It lands in HR's queue, visible only to HR. Arjun's manager isn't involved; nothing about his visa is visible elsewhere.
• Tuesday 14:00 — Meera in HR drafts the letter from a template, confirms his job title and start date from the HR system, and attaches it to the request.
• Arjun gets a notification, downloads it, and confirms it has everything the embassy needs. The request is resolved in a day and a half, well before his deadline.

Without a desk, this is an email to a shared HR address that someone reads Wednesday, a reply asking for his start date, and a letter on Thursday evening — technically on time, practically too late.

Metrics HR can use

• Volume by category — where HR's time goes, and what self-service could absorb.
• First response and resolution per category (median and 90th percentile).
• Requests resolved before the requester's deadline for letters and documents.
• Pay requests resolved before cut-off.
• Repeat policy questions — each is an article waiting to be written.

These are the same principles as help desk metrics that matter, with HR's deadlines added.

FAQ

What is an HR service desk?

A single place for employees to submit HR requests — pay, leave, documents, contracts, benefits, concerns — where each becomes a tracked item with an owner, status and deadline, visible only to the right people.

How do you keep HR requests confidential?

Make HR queues visible only to HR through enforced permissions, restrict the most sensitive categories further, collect only necessary information, and never route HR requests through shared inboxes.

Should HR and IT use the same help desk?

They can share one front door if each team's queue is private and cross-team requests like onboarding are split so each team sees only what it needs.

What HR requests can be self-service?

Policy questions — holiday carry-over, expenses, parental leave, remote-work rules — and routine leave requests through a structured workflow.

Sources

• GDPR Article 5 — Principles relating to processing
• GDPR Article 9 — Special categories of personal data
• Wikipedia — Shared services
• Atlassian — Knowledge management