What is HR service delivery / case management software, and how is it different from an HRIS?

HR service delivery software runs the flow of employee questions and requests into HR and back out as answers. Each request becomes a tracked case, and around that case sit a self-service portal, a searchable knowledge base, a ticket queue with assignment and routing, service level targets, and reporting on what employees are asking about.[1][4] The category travels under two other names, HR case management and the employee help desk, and all three describe the same job.[1]

TechTarget frames it as how an HR department offers services to and interacts with employees, usually through a knowledge base or chatbots on the company intranet, backed by a case and knowledge management module where HR staff resolve issues.[1] AIHR describes it more broadly as the people, technology, and processes that keep HR operations running consistently and in line with legal and internal standards.[3]

The case is the unit of work

A case is one employee's request that needs resolving, whether that is a question about a paycheck, a document upload for a leave claim, or a report of a workplace concern.[2] Treating the request as a case, rather than an email in someone's inbox, is what makes the rest possible, because the request gets an owner, a due date, a full record of every reply, and a status the employee can check.[2][6] Once the case is closed, its history stays attached to it, which matters most for the sensitive requests HR handles.[3][6]

Where it sits next to your HRIS

The software assumes an HRIS already exists and does not try to be one. It draws on the employee record to identify who is asking and to route the case correctly, then hands back to the system of record only the occasional completed transaction.[1][8] The reporting points the other way too, since a spike in questions about one policy or one form is a signal that the policy text, or the HRIS workflow behind it, is failing employees.[1]

A single request moves through six stages, and following one shows how the pieces fit. Take an employee who cannot find their updated benefits summary.

1. Self-service tries first

The employee opens the portal and searches, and the knowledge base offers the benefits article before any case exists.[4][6] Workday surfaces suggested articles as the employee types, and Freshservice publishes the same policies and how-to guides in a self-service portal, both aiming to answer the question without a ticket.[6][7] Most of the value of the whole system is decided here, since a portal that resolves 80 to 90 percent of routine questions is what keeps the upper tiers from being overwhelmed.[10]

2. A case opens on the channel the employee already uses

When the article does not answer it, the employee opens a case from the portal, from email, from chat, or from a message inside Microsoft Teams or Slack.[6] Workday delivers this support directly in Slack and Teams so the request does not require learning a new tool.[6] The case records who is asking and what they need, and it now has an owner and a history.[5]

3. Routing sends it to the right place

The case is assigned by topic to the team or specialist who handles it. ServiceNow documents case assignment and Advanced Work Assignment for exactly this, and Freshservice routes each request automatically to the appropriate person.[5][7] Routing is where tiering happens in practice, because a password reset, a benefits question, and an employee relations complaint each go to a different queue.[3]

4. A clock and an escalation path attach

Every case carries a due date and an escalation route, so a request that stalls is flagged rather than forgotten.[2][6] Workday manages the case lifecycle and its routing rules centrally, which is what makes the commitment enforceable across a large team.[6]

5. Sensitive cases get separate handling

Cases that touch leave, accommodation, pay disputes, or misconduct move through confidential handling, restricted to the people who need to see them.[6] ServiceNow keeps distinct case types for VIP and employee relations matters for the same reason, since those records carry legal weight and cannot sit in a shared mailbox.[5][3]

6. The closed case becomes data

After resolution the case joins the reporting: how many came in, on what topics, how long they took, and how satisfied the employee was.[1][4] A cluster of cases about one form is the clearest signal available that the form, the policy, or the HRIS step behind it needs fixing.[1]

The tiered model is the design the whole category is built around: employees start at self-service and move up to a human only when they need one.[4][10] It comes out of Ulrich's model of HR, and most vendors and analysts describe four levels.[2]

Tier 0, self-service

Tier 0 is the portal and knowledge base, where employees and managers answer their own questions and complete transactions without contacting anyone.[10][4] Strong implementations push 80 to 90 percent of routine traffic through this tier, and that percentage decides whether the tiers above it stay manageable.[10]

Tier 1, the HR help desk

Tier 1 is the shared-services team or help desk that picks up what self-service cannot, handling routine questions and aiming to resolve most of them on first contact.[10][3] This layer is the direct equivalent of an IT service desk, and it is where the ticket queue lives.[4]

Tier 2, specialists

Tier 2 is the specialists who take escalations that need deeper expertise, in areas such as compensation, benefits, or labor law.[3] Moving this work off the generalists' desks is a large part of the payoff, since analysts report centers of excellence cutting the administrative time they spend on inquiries by 70 to 80 percent once tiering is in place.[10]

Tier 3, centers of excellence and strategic HR

Tier 3 is the strategic and highly specialized layer, the centers of excellence and senior HR who handle sensitive or high-impact matters such as legal disputes and employee relations.[3] Not every organization runs a formal Tier 3, and the number of tiers varies, but the direction is consistent: keep each request at the lowest tier that can actually resolve it.[2][3]

Case volume, distribution, and compliance exposure decide whether this software earns its place, far more than headcount alone.[3][10] A 60-person company with one HR generalist and a shared inbox rarely needs it, while a 6,000-person company across a dozen locations almost always does.[3]

When it earns its place

Larger and more distributed organizations adopt HR service delivery once the volume and variety of requests stop fitting in an inbox.[3][10] Volume is usually the trigger, because a shared mailbox has no owner, no due date, and no view of what is backing up.[2] Distribution adds a second reason, since employees in different offices should get the same answer to the same policy question, and a shared knowledge base is how that consistency holds.[10] The heaviest reason is documentation, because leave, accommodation, pay disputes, and employee relations investigations create records that need confidential handling and an audit trail a mailbox cannot provide.[3][6]

When an HRIS inbox is enough

Smaller and single-site teams usually get everything they need from their HRIS self-service and a shared email address.[8] At low volume the overhead of building a knowledge base and configuring routing outweighs the saving, and the analytics have too few cases to say anything useful.[1] The signal to reconsider is not a headcount number but a pattern: the same questions asked over and over, requests slipping through email, or a sensitive case that ended up in the wrong person's mailbox.[2][3]

Three neighboring tools get mistaken for HR service delivery, and the boundaries matter during a buying process.[1][8][9]

It is not an HRIS

An HRIS is the system of record for employee data and core HR transactions, not a request-handling desk.[8] The distinction that holds up in a demo is ownership, since the HRIS owns the employee record while HR service delivery owns the case about it.[8][1] A published sibling on HRIS, HRMS, and HCM covers the record system in depth; the short version is that the two are complementary, and most large employers run both.[8]

It is not a general IT service desk

An IT service desk runs on ITSM, the practice of designing, delivering, and controlling IT services, with the desk as the single point of contact for incidents and requests.[9] HR service delivery uses the same ticketing and knowledge-base machinery, which is why ServiceNow sells both, yet it is tuned for HR cases, HR knowledge, and the confidentiality of personnel matters rather than for broken laptops.[4][5] Pointing an IT service desk at HR work usually misses the privacy controls that HR cases require.[6][3]

It is not an engagement or experience platform

Engagement and experience platforms measure how employees feel through surveys and sentiment, while HR service delivery resolves the concrete requests they raise.[1] The two get confused because both claim the phrase employee experience, though one produces scores and the other produces closed cases.[1] A pulse survey tells you satisfaction is down; a case queue tells you three hundred people cannot find the new benefits form.[1]