When HR Becomes a Help Desk: What We Learned From Fixing It
Every HR team has a version of this problem: the information exists, the documents are written, the policies are clear, and yet employees keep asking the same questions. Where's the vacation policy? What do I do on my first day? Who approves this? Maya Cohen, Head of HR at a fast-growing tech company, spent months watching her team become a help desk. This is the story of how they diagnosed the real issue (it wasn't missing information, it was inaccessible information), what they tried before finding a solution that worked, and what they'd do differently if they were starting over. Including the parts that didn't go as planned.
Introduction
The day Maya Cohen realized something had to change wasn't dramatic. There was no system failure, no angry executive, no compliance incident.
It was a Tuesday afternoon. She had just answered the same question about the remote work policy for the fourth time that week - to four different employees, in four separate Slack messages. Each answer took maybe five minutes. Each answer already existed in a document the company had spent hours writing.
"That's when I thought: we don't have an information problem," she says. "We have an access problem."
Maya is Head of HR at a mid-sized tech company that has roughly doubled its headcount over the past two years. Like many HR leaders at fast-growing companies, she found that scaling the team was easier than scaling the systems around it. Documents multiplied. Folders nested inside folders. And when employees couldn't find what they needed, they did the natural thing: they asked HR.
This is a story about what happened when her team decided to fix that - and what they'd do differently if they were starting over.
The Real Cost of Repeated Questions
You've described your biggest HR challenge as "100 small problems a day." What does that actually mean in practice?
It means that individually, none of the interruptions feel significant. Someone asks where to find the vacation policy. A manager needs to know how to initiate an offboarding. A new hire can't figure out who approves expense reports. Each one takes five minutes.
But when you add it up across a team of two or three HR people - multiply it across fifty or sixty employees asking two or three questions a month each - you're looking at hours of lost time every week. Time that isn't going to recruiting, or retention, or the things that actually move the business forward.
The frustrating part is that we had the answers. We had Google Docs, Notion pages, onboarding PDFs, policy handbooks. The information existed. It just wasn't usable in the moment someone needed it.
Did you try to fix it internally before looking for a tool?
We did. We reorganized the folder structure twice. We sent reminder emails telling people where to find things. We created an FAQ document.
The FAQ document immediately became outdated. The reorganized folders helped for about three weeks. The reminder emails - people read them and then forgot.
The problem isn't that employees are careless. It's that when you need to know something in the middle of doing your job, you don't want to navigate a folder hierarchy. You want an answer. And the path of least resistance is asking a person.
Why Onboarding Was the Hardest Part
You mentioned onboarding specifically as a major pain point. What made it different from other HR challenges?
The stakes are higher. If someone can't find the sick leave policy in month six, it's annoying but recoverable. If a new hire gets confused in their first week - misses a compliance training, doesn't understand their benefits enrollment deadline, has the wrong expectations about their role - that affects their whole experience with the company.
And onboarding is inherently repetitive. Every person who joins goes through the same information, but they all go through it at different times, with different questions, at different levels of attention. We were essentially doing bespoke onboarding for every hire, which doesn't scale.
We also had a geographic problem. Some people join in-person and get a lot of informal context - they can ask their manager, they overhear conversations. Remote hires don't have that. They're often reading documents alone and hoping they didn't miss anything important.
What was the actual HR time investment per new hire?
Honestly, we never measured it carefully, which was part of the problem. But if I had to estimate - between the initial documentation send, the follow-ups, the "did you complete your training" check-ins, the questions during the first two weeks - it was probably four to six hours of HR time per hire. For a company that was bringing on eight to ten people a month, that adds up quickly.
What Changed When They Implemented Driftext
Walk me through what the decision to use Driftext actually looked like.
We weren't looking for another place to store documents. We were specific about that. We needed our existing content to work harder.
What drew us to Driftext was that it treats documents as a knowledge base rather than a filing cabinet. You upload your content, and employees can ask questions and get answers sourced directly from your materials - not generic answers, not hallucinated information, but responses grounded in what your company has actually written down.
We started with three things: the onboarding guide, the remote work policy, and the expense process. Those were our highest-traffic questions. We wanted to see if the concept worked before committing to a full rollout.
And did it?
Within the first month, the questions about those three topics dropped significantly. I won't give you a specific number because I don't want to overstate it - we weren't running a controlled experiment. But the pattern was clear. When employees knew they could get an answer instantly without waiting for someone from HR to be available, they used that option.
What surprised me was the after-hours piece. A lot of our employees work across time zones. HR obviously isn't available at 11 PM when someone in a different region is trying to figure out their benefits. Driftext was. That's a small thing, but it mattered to people.
What Didn't Go Perfectly
Most case studies skip the hard parts. What didn't work as expected?
A few things.
The quality of the tool is only as good as the quality of your underlying content. We had some documents that were genuinely confusing - written by committee, full of hedging language, missing context. When employees asked questions about those documents, the answers they got were also confusing. That was a mirror held up to our own inconsistencies.
So in parallel with rolling out Driftext, we had to do a content audit we'd been avoiding. That was uncomfortable but ultimately valuable.
The other thing is change management. Some employees adopted it immediately. Others kept asking HR directly out of habit - which is fine, but it meant the full value took longer to realize than we expected. You can't just deploy a tool and assume people will change behavior. You have to explain why it exists and make it easier than the alternative.
Is there anything you'd do differently?
I'd start the content audit first, before implementation. Clean up the documents, resolve contradictions, archive anything outdated. Give the tool the best possible foundation.
I'd also involve managers earlier. Managers are a huge source of HR questions, and they're also the people who influence how their teams behave. If a manager tells their team "just ask HR," that's what they'll do. If a manager says "check Driftext first," that becomes the norm.
The Broader Lesson
What's the bigger takeaway for HR leaders facing similar challenges?
I think the instinct in HR is often to solve information problems with more communication - another email, another meeting, another handbook. But communication that isn't findable isn't really communication.
The shift we made was treating our HR knowledge as a product. A product that has users, that needs to be usable, that should be measured on whether people can actually access it when they need it.
That reframe changed how we thought about a lot of things - not just the tool we chose, but how we write policies, how we structure onboarding, how we decide what to document in the first place.
Driftext was part of the solution, but the solution was really about taking information access seriously as an HR function - not just an administrative afterthought.
What This Looks Like in Practice
For teams considering a similar approach, Maya's recommendation is straightforward: don't start with everything.
Identify the five to eight questions HR answers most often. Look at what documents already exist to answer those questions. Clean up that content first. Then make it interactive.
The goal isn't to replace HR with a chatbot. The goal is to make HR's knowledge available whenever employees need it - so that when they do talk to HR, it's about something that actually requires a human.
That distinction, she says, is what changes the role.
"When HR stops being a help desk, it gets to be what it's supposed to be: a strategic function. That's better for the company and, honestly, it's better for the people doing the work."
Driftext is an AI-powered platform that turns company documents into interactive learning, knowledge Q&A, and employee self-service tools. Learn more at driftext.com.
Sources consulted: