3 minutes can be enough to answer one benefits question, but HR teams at mid-size companies seldom record those minutes. Questions arrive through email, Slack, phone calls, and hallway conversations. Each exchange seems minor. Taken together, they represent a substantial amount of time that would stand out if someone measured it.
When benefits leads or HR generalists at mid-size companies begin tracking their hours, the same pattern appears: benefits questions, plan interpretation, and enrollment assistance take up a meaningful share of the HR team's work, both during open enrollment and across the rest of the year. Identifying where those hours go is necessary before deciding which work can be redirected.
Difficulties measuring benefits support time
The challenge is not the absence of benefits support work. The challenge is that it is spread across types of interaction that HR teams do not reliably record. An email defining "in-network" may take three minutes. A Slack exchange about FSA deadlines may take five minutes. A call explaining why a claim was denied may last fifteen minutes. None is necessarily entered into a ticketing system or assigned to a project code. Instead, each is folded into the day's ordinary work.
That pattern produces a consistent undercount. HR managers estimating their benefits-question workload usually report less time than measurement reveals because they remember clear transactions, such as the 30-minute meeting or complicated COBRA question, while overlooking the accumulated effect of short exchanges. A two-minute response sent at 8:47 AM about the FSA grace period hardly feels consequential. Ten such responses each week, across 50 work weeks, amount to roughly 17 hours per year for one question category.
Typical yearly distribution of time
Benefits support does not occupy the same amount of time throughout the calendar. It tends to cluster in three periods: open enrollment, usually 6 to 8 weeks in the fall; the weeks immediately after the plan year starts in January, when employees use benefits under new terms and encounter unexpected costs; and the periods surrounding dependent changes tied to qualifying life events.
At a 200-employee company, an HR generalist may spend 20 to 40 percent of working time on benefits questions, enrollment assistance, and carrier follow-up during open enrollment. For a 2-person HR team, that effectively leaves little availability for other HR responsibilities while enrollment is underway.
A second surge follows January 1. Employees who selected different plans now encounter deductible resets, updated in-network provider lists, or new FSA balances. Many also no longer recall what they elected in October. In numerous mid-size company HR departments, the number of questions during the first two weeks of January is similar to the volume in the week before open enrollment ends.
Question types and resolution patterns
From an HR time standpoint, benefits questions are not all alike. They generally fit into categories distinguished by resolution time and by the degree of HR judgment involved:
Plan explanation questions (what is my deductible, how does the FSA work, is this provider in-network) usually take under 5 minutes when HR can answer immediately, and as long as 15 minutes when research is needed. These questions call for no HR judgment. They have factual, plan-specific answers.
Enrollment action questions (how do I add a dependent, where do I submit my FSA claim, can I change my election) involve guiding an employee through a process, frequently in a third-party portal or carrier system. They average 10 to 20 minutes because the employee may not be at the system when asking for help.
Claims and dispute questions (why was my claim denied, why is my deductible higher than expected, can you look into this) consume the most time and are the questions for which HR is most often placed in the wrong role. The carrier must ultimately take action. HR can direct the employee and explain the next steps, but cannot directly resolve the claim itself. These interactions often cost more time than expected because the question returns to HR more than once before it reaches the carrier.
Complex benefits decisions (should I choose the HSA plan or the PPO, how much should I contribute to my FSA) combine plan details with the employee's personal financial and health circumstances. HR time is particularly difficult to replace here because these decisions require plan knowledge along with judgment informed by the individual's situation.
Open enrollment cost is just part of the picture
HR teams and their leaders often assess benefits support mainly through open enrollment. Preparation, materials review, and Q&A sessions are visible activities with scheduled time. The cost of the other ten months is harder to see, so it is often valued less than it should be.
For a 2-person HR team supporting a 200-employee company, a reasonable estimate for non-enrollment benefits support is 5 to 10 hours per week across the team during steady-state months. That figure rises to 15 to 25 hours per week during open enrollment and the two-week period following January 1. This is not an unusual estimate. It matches the recurring picture from the HR teams in our early pilot group.
The takeaway is that benefits support is not limited to enrollment season or resolved when November ends. It is an ongoing operational expense throughout the year, marked by two concentrated surges that often displace other HR priorities.
What question mix indicates about automation fit
The four categories above are not equally suited to automation. Plan explanation questions are the most direct fit for a conversational agent because they are factual, specific to the plan, and repetitive. Different employees will ask about in-network deductibles in similar terms, and the correct answer remains the same.
Enrollment action questions are well suited to automated guidance for the walkthrough portion, such as explaining how to reach a particular screen. The carrier system must still receive and process the action, however. In most cases, the constraint is not HR's explanation but the employee completing the transaction.
Claims questions present a more limited automation opportunity. Defining a field on an EOB can be automated. Working through a claim dispute with the carrier cannot. A tool that suggests it can resolve disputes when it cannot creates a poorer result than directing the employee to contact the carrier.
Complex benefits decisions combine plan information that can be automated with personal context that cannot. A tool can clearly show each plan's deductible, out-of-pocket maximum, and premium. Determining whether the HDHP fits a particular employee depends on details the tool cannot verify.
Using these figures to build the internal case
HR teams making a capacity case to leadership are stronger when they have real time estimates. In most cases, a simple two-week log is enough: one HR team member records time by category for benefits-related interactions. The resulting figure does not have to be exact. It must be defensible.
This does not mean benefits support is wasted time. Complex questions, judgment calls, and meaningful employee conversations are precisely the work HR teams are equipped to handle. The point is not to make HR unavailable. Rather, a considerable share of today's volume is factual, repeatable, and answerable without HR involvement. Redirecting that share gives HR more room for the difficult work that depends on professional judgment.