HR case management: the practical guide

HR case management is how an HR function tracks, manages and resolves the questions, issues and requests that employees bring to it. A case is the record of one employee's conversation with HR. It collects the notes, emails, phone calls, chats, attachments and tasks belonging to that conversation into a single view, so the next person to pick it up sees the whole history rather than a fragment of it.

The software category is also called HR service management or HR service delivery. Different analysts and vendors use different labels for substantially the same thing: a platform for running HR shared services operations, with a knowledge base, case routing, service level monitoring and an employee facing portal.

The practical test of whether you need it is simple. If your HR team cannot answer how many questions it received last month, how long they took to resolve, or which questions came up most often, then the work is being tracked in inboxes and spreadsheets and the answers do not exist. See what that looks like as a product on the HR case management page.

Almost every HR function that runs case management at scale organizes it into tiers. The pattern is consistent enough to plan against, and the four models below are published by the customers themselves rather than drawn from a template.

Tier 0 is self service. The employee finds the answer without a person. At Old National a 450 article knowledge base handles 47% of all inquiries here. At Tower Health, a portal with over 325 articles took calls into HR from 40,606 a year to 18,736, a 54% reduction. At Lenovo, a knowledge base and an AI chatbot deflect 87% of cases before a person is involved.

Tier 1 is the service center. Generalists who resolve most of what arrives. Lenovo runs 60 staff across four geographic centers handling 13,000 cases a month against a 92% first contact fix target, currently achieving 96%. Tower Health's tier 1 answered 34,768 of 52,313 cases in a year, 66% of the total. Old National runs five HR generalists at this tier.

Tier 2 is subject matter expertise. Benefits, compensation, payroll, HRIS. At Lenovo this is roughly 50 people handling the 4% that tier 1 could not close, about 520 cases a month. At Tower Health it is 17,545 cases a year, 34%. At Northside Hospital it is specialists in benefits, compensation and payroll.

Tier 3 is leadership and employee relations. Deliberately rare. Lenovo's centers of excellence and HR business partners see fewer than 10 cases a month. Old National routes ER casework to three advisers with investigation expertise. Northside escalates to senior and benefits leaders, typically where several employees hit the same issue and someone has to establish whether there is a vendor or file problem behind it.

The shape to aim for is a wide base and a narrow top. If tier 2 is absorbing a third of your volume, the problem is usually tier 0 content, not tier 1 capability. See how this maps onto a service model on the HR shared services page.

Plenty of organizations already own ServiceNow, Zendesk or Freshservice and reasonably ask why HR cannot use it. Sometimes HR can. The structural differences that decide it are these.

Confidentiality works differently. IT tickets are generally visible to the IT team. HR cases frequently must not be. Case level restriction, rather than team level permission, is the requirement, and it is the one most often discovered late.

Retention works differently. HR records carry statutory retention periods and subject access obligations that IT tickets do not.

Who configures it works differently. An HR service model changes when the HR operating model changes, which is more often than an IT platform release cycle allows for. The question to ask is who adds a case type, and how long that takes.

A fuller comparison is on the HR service delivery versus ITSM page.

A case management system is only as good as the channels feeding it, and the mix is rarely what HR expects before they measure it.

Email is almost always the largest and the least visible. Tower Health received 122,000 employee inquiries by email. Email that does not become a case is work nobody can see, count or improve, which is why email to case with automatic threading matters more than it sounds.

The portal is where you want volume to go. Not because it is cheaper to serve, though it is, but because a portal question that gets answered by an article is a question that never becomes a case at all.

Chat and AI sit between the two. They catch the employee who could not find the article but is not ready to write an email. Lenovo runs a chatbot at tier 0 alongside its knowledge base. See HR Copilot for how the AI layer works.

Phone and walk ups do not disappear. Old National creates a case immediately for anything arriving by phone, email or chat, which is the discipline that keeps the reporting honest.

Inside the HCM. Some teams want the request raised where the employee already is. See HCM integrations for how Dovetail connects to your system of record.

Three components, in the order finance will ask for them.

Capacity released. Deflection at tier 0 and first contact fix at tier 1 both convert directly into hours. Old National's automation absorbed the equivalent workload of two full time HR employees and lifted shared services productivity by 20%.

Risk reduced. Harder to quantify and usually more persuasive to a general counsel than to a CFO. Documented casework with a complete audit trail is the difference between defending a claim and reconstructing a file.

Payback. G2 measured Dovetail at an 8 month payback period against a 14 month industry average, reported in April 2025.

If you want the first of those three modelled against your own headcount rather than someone else's, the HR and ER maturity assessment does it in about five minutes and returns a report you can circulate.