Why internal IT and HR support costs more than anyone measures

In most companies, the team that answers the most repeated questions per day isn't the one handling customers. It's the one handling their own employees — and it's also the only one nobody asks for a report. When someone in customer support repeats an answer twenty times, there's a dashboard showing it. When the same thing happens to IT or HR, no record is left anywhere: the question arrives through a WhatsApp group, a direct message, a stray email, it gets answered, and it disappears.

Where internal support actually lives in a company today

In no system built for it. Customer-facing support almost always has a platform with SLAs, categories and reports; IT or HR support, on the other hand, runs on channels nobody designed to carry it — the team chat, the inbox of the person who "knows about that", a voice note. There's no ticket to open and no closure to count, so there's also no way to see, at the end of the month, how much real time went into resolving questions that had already been resolved before.

How much time is lost because the answer exists but nobody knows where to look

Quite a bit more than common sense suggests. A Gartner survey of nearly 4,900 office employees, at companies of 100 people or more, found that 47% of digital workers struggle to find the information or data they need to do their job. It's almost never a problem of the answer not existing — it exists, in the head of someone in IT or HR, or in an internal document nobody can find; the problem is that reaching it depends on knowing who to ask, and that dependency stops holding up as soon as the team grows a little.

Why this hurts more than the number of questions suggests

Because the cost isn't spread evenly. HappySignals' Global IT Experience Benchmark, which processes millions of employee responses about their experience with IT, has been recording year after year that 13% of incidents account for 80% of perceived productivity loss. In practice, that core is usually a small and always identical set of questions — access, time off, reimbursements, setup — that nobody ever fixes at the root because, one by one, each request looks too small to justify sitting down and solving it.

What happens when two or three people become the only channel for internal questions

They turn into a bottleneck without anyone deciding it. Every new question competes for their attention with the work they should in theory be doing — recruiting, negotiating with a supplier, resolving an actual infrastructure incident — and the same two people end up answering the same thing over and over to each new person who joins. The most expensive outcome isn't the time lost as such: it's that an urgent request can end up buried behind ten simple questions that arrived first through the same informal channel.

Is adding more people to the IT or HR team enough?

No, because the problem isn't how many people there are, it's where the knowledge lives. Adding people spreads the load, but each new person still depends on the same two or three who "know" — the bottleneck moves, it doesn't disappear. What does change the pattern is making the answer available without depending on one specific person: an agent trained on the team's real policies and processes, with the same narrow permissions and human oversight any AI agent in production needs, resolving repeated questions through the channel each employee already uses and handing off to a person only when the case really calls for it. It's the same mechanism that already works in customer support — at Takenos, an agent with conversation memory resolves 70% of enquiries autonomously, in roughly a minute per case — applied inside the company instead of outside it.

---

Before adding one more person to the IT or HR team, it's worth measuring something much simpler: how many times a week the same internal question comes up, and how much real time it takes from whoever answers it today. That figure almost never exists in any report yet — and it's usually the first clue to where the real cost is.

To see how this is built for processes that aren't customer-facing: Other StudioChat solutions.

Sources:

• Gartner — Digital Worker Experience survey (conducted 2022, released May 2023): "47% of digital workers struggle to find information or data needed".
• HappySignals — Global IT Experience Benchmark: "80% of lost time with IT incidents comes from only 13% of tickets."