HR Service Desk SLAs and Escalation

An HR service desk only helps if requests actually get answered. A queue with no deadlines becomes another inbox, and a queue with deadlines nobody acts on is worse, because everyone can see the problem.

This guide covers how to set targets for employee requests, what should happen when one is at risk or overdue, and how to run it with HRSpace’s Service Me module, which includes SLA targets, routing rules and approval chains.

Two terms, two decisions

• An SLA (service level agreement) is a target for how fast a request will be answered or completed.
• Escalation is what happens when the target is at risk or missed.

A deadline tells you there’s a problem. An escalation gives someone responsibility for fixing it.

Step 1: Set the targets

Set two clocks for each request type:

• Response: how quickly someone acknowledges and starts. Acknowledging isn’t the same as solving.
• Resolution: how quickly the request is completed.

Here are examples for HR, not benchmarks. Base yours on your team’s capacity.

Request type	Response (example)	Resolution (example)
Policy question	1 working day	2 working days
Document request	1 working day	3 working days
Access or equipment for a new hire	Same day	Before the start date
Sensitive employee concern	Same day, to a named person	Agreed with the employee

Step 2: Define the clock before the rules

Settle these first, because getting them wrong makes correct rules fire at the wrong time:

• Working hours and time zone. Does the clock run around the clock or only in working hours? Handle weekends and holidays.
• Pause rules. Should the clock stop while you wait for the employee? Only if your policy says so, and write down which states count.
• Reopened requests. Does reopening start a new deadline?

Step 3: Escalate before the miss, and at the miss

The best escalation rules prevent breaches rather than record them. A common approach uses two points:

1. A warning at about 75 to 80 percent of the time elapsed. The current owner, and perhaps a backup, gets a nudge while there’s still time to act.
2. An escalation when the deadline passes. The request goes to a named person who can do something about it.

Choose the type of escalation by what’s needed:

• Functional: move the request to someone with the right skills or access, such as sending a payroll question to finance.
• Hierarchical: involve a manager who can decide, reassign or remove a blocker.

Whichever you choose, decide what the recipient must do. If the only action is “read the message”, the escalation isn’t finished.

Step 4: Name the owners

For each category, name an escalation owner and a backup. A manager who can see a delay isn’t always the person who’s authorised to resolve it, and that matters most for approvals: an escalated approval should go to someone who can approve, not around the approval.

Step 5: Give the recipient what they need

Include the request reference, the category, the target that was missed, the current owner and the next step. Keep personal details to those with a reason to see them, because many HR requests are sensitive. And keep the original deadline visible, so an escalation doesn’t hide the miss by moving the date.

Step 6: Avoid noise

• One escalation per breach. Make sure repeated checks don’t send the same alert again.
• Don’t re-escalate resolved requests. Check status at the time of action.
• Don’t treat every edit as a breach. Fixing a typo isn’t a new problem.
• Handle an unavailable owner. There should be a backup route, not silence.

How HRSpace makes this easier

HRSpace’s Service Me module ($0.50 per employee per month) gives employee requests a queue with:

• a request catalogue, so people choose what they need,
• routing rules, so each request goes to the right owner,
• SLA targets, so you can see which requests are late,
• approval chains, so decisions happen with the right people.

That already removes the biggest problem: requests disappearing into chat. And because it sits with onboarding, time off and employee records, a request about leave or a new starter’s laptop is in the same place as the rest of HR.

Check in your trial

Ask how overdue requests are handled in your setup:

• Can you be warned before a target is missed?
• Can a late request be reassigned or sent to a named person automatically?
• How does the clock treat working hours and waiting states?

If any of these aren’t automatic, use the fallback below.

A simple fallback

Have one person own a daily look at overdue and at-risk requests, and contact the owners. It’s manual, but it works until you automate, and it shows which categories keep slipping.

Measure what matters

Track response time and resolution time separately. A fast first reply doesn’t mean the request was solved. Then read the overdue and reopened ones. They usually point to the cause: unclear ownership, missing information, an unnecessary approval, or an SLA that was too tight to begin with. Fix that before adding more alerts.

What it costs

For a 50-person company:

• Base layer (records, documents, time off, timesheets): $50/month
• Service Me: $25/month
• Total: $75/month, billed monthly with no setup fee

A 14-day free trial needs no credit card.

Frequently asked questions

What is the difference between a response SLA and a resolution SLA?

A response SLA is the target for acknowledging a request. A resolution SLA is the target for completing it.

When should a request be escalated?

Ideally with a warning before the deadline, and again when it passes.

Should waiting tickets pause the SLA?

Only if your policy says so. Define which waiting states count.

What’s the difference between functional and hierarchical escalation?

Functional sends the request to someone with the right skills. Hierarchical brings in a manager with authority.

How do I stop duplicate escalations?

Record that a breach has been handled and check before repeating the action.

Can I try HRSpace before buying?

Yes, with a 14-day free trial and no credit card.

One last thing

Ask the person who receives an escalation what they’re meant to do when it arrives. If the answer is “read it”, fix the handoff before you automate more.

Where to go from here

To see Service Me working with your own request types, start a free 14-day HRSpace trial. You may also like our guides to onboarding tickets and HR service desks for multi-location retail.