Deflection Targets in an HR Service Center

Rank by volume, variability, and ownership.

1. Employment verification letters (15%). Highest certainty, lowest risk: a single template with defined data fields can be fully automated or generated on demand. This is the right first project because failure is cheap and the volume is predictable.
2. Password and access resets (18%). Deflectable, but this is an IT dependency, not an HR one. If HR simply routes the ticket to a service desk, HR volume falls and total company effort is unchanged. Negotiate single sign-on and IT self-service as the real fix and count honestly.
3. Benefits questions (22%). Concentrated in six weeks, so the business case is seasonal staff avoidance rather than headcount reduction. Deflect only the repeat questions (enrollment deadlines, plan comparison basics) through a knowledge base; plan-specific exceptions still need a human and errors are costly.

What must be true first:

• A knowledge base with named article owners and a review cadence, because unmaintained content generates wrong answers and rework.
• An agreed definition of deflection: resolved without a human touch and without reopening within seven days. Otherwise misrouted and abandoned tickets get counted as wins while work moves into shadow channels.
• Usability testing of the portal, since 30% adoption with an existing portal suggests a design or trust problem, not an awareness problem.

Deflection targets measured as an aggregate will be met by the employees who were already digital, while the plant population falls further behind. That produces a two-tier service experience and, in a benefits context, real financial harm.

• Instrument by segment. Report portal adoption, resolution time, first-contact resolution, and satisfaction split by site and by channel. Aggregate satisfaction of 61% can conceal a plant population at 40%.
• Keep human channels open and stop treating them as legacy. A phone or walk-up route is not a failure of the model; it is the correct channel for a population with one kiosk per 80 employees and limited computer comfort.
• Cheap capacity first: add kiosks, convert break-room space to a staffed help point during open enrollment, and train a small group of onsite digital ambassadors. This costs far less than the coordinator hours it recovers.
• Do not set separate lower service standards for plants. If plant employees wait longer because their channel is deprioritized, the deflection program has created an equity problem that will surface as grievances or a benefits enrollment failure.

Communicate the model as channel choice rather than channel replacement; the credibility of the whole program depends on employees not experiencing deflection as abandonment.

Diagnose the baseline first. 1,900 tickets ÷ 22 coordinators ≈ 86 tickets per coordinator per month, about four per workday. For a transactional center, that is low, which means one of three things: average handle time is very high, a large share of work is never logged as a ticket (calls, walk-ups, drop-ins), or coordinators carry non-ticket duties. Until channel capture and handle time are measured, any staffing plan is guesswork and any deflection the team achieves will show up as unmeasured shadow work.

Test the 40% target against composition. The three named categories total 55% of volume, so 40% is arithmetically reachable, but only if password resets move to IT and the benefits deflection is seasonal. A realistic phasing: verification letters in the first quarter, IT resets once the service desk capability exists, benefits knowledge base before the next open enrollment. State explicitly that the headline number will fluctuate with the enrollment calendar.

Staffing the tiers:

• Tier 1 handles high-volume, scripted contacts across phone, chat, and portal, with decision authority to resolve without escalation.
• Tier 2 handles leave, benefits exceptions, and employee relations intake, staffed from the coordinators with the strongest judgment, not simply the longest tenure.
• Define escalation criteria in writing and track escalation rate as a quality metric; a tier 1 that escalates everything has produced no gain.

Hold headcount decisions until after measurement. Cutting coordinators to fund the target before handle time and channel capture are known is the most common way these programs fail.