What problem does it solve?
HR shared services answer the same questions every day: how many days of leave do I have left, where is my payslip, does the policy cover this expense, what happens to my benefits if I move country. The answers exist, but they are spread across policy PDFs, intranet pages and HR systems, differ by country, entity and grade, and change every year. Employees raise tickets or email a business partner, and HR spends skilled time on lookups.
A generic chatbot makes this worse if it gives one answer to everyone. The value comes from answers grounded in the current policy that applies to this person, plus the ability to complete the simple transaction behind the question. The risk is the opposite failure: HR data is among the most sensitive an organization holds, and some conversations (grievances, misconduct, wellbeing) must reach a person, not a bot.
How does it work?
- Know who is asking. The assistant runs inside the employee's signed in session and reads only that person's attributes that matter for policy: country, entity, grade, contract type.
- Retrieve the applicable policy. Retrieval is filtered to the documents that apply to that population, and the answer cites the policy and section it came from.
- Read personal data only through the HR system. Leave balances or payslip locations come from HR system APIs scoped to the requester, never from documents about other people.
- Start simple transactions. Leave requests, employment verification letters or address changes go through the HR system's normal workflow and approvals.
- Route sensitive topics to people. Grievances, disciplinary matters, harassment, health and wellbeing are detected and handed to HR or employee assistance, with the employee's consent.
- Audience
- Employee facing
- Autonomy
- Supervised agent
- Adoption
- Early adopters
- Channels
- Microsoft Teams, Internal tools, Web chat
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
| KPI | Median | Reported range | Data points | Claimed by |
|---|---|---|---|---|
| Employee adoption | Too few to pool | 90% to 99% | 2 | 2 organization |
| Containment rate | Too few to pool | 94% | 1 | 1 organization |
| Cost reduction | Too few to pool | 40% | 1 | 1 organization |
| Cycle time reduction | Too few to pool | 33% | 1 | 1 vendor |
| Interactions handled | Not pooled | at least 11.5 million | 1 | 1 organization |
Value drivers: Lower cost to serve, Employee productivity, Speed and cycle time.
Indicative value
An organization with 20,000 employees
USD 160,000 to USD 1.1 million
HR handling cost avoided per year
How this is calculated
Formula: employees * queriesPerEmployee * containment * costPerQuery. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Employees employees, employees | 20,000 | 20,000 | The reference organization. |
| HR questions and requests per employee per year that reach HR today queriesPerEmployee, queries per employee per year | 2 | 4 | Editorial assumption, replace with your HR case volume. |
| Share resolved by the assistant without HR staff containment, fraction of queries | 0.4 | 0.7 | Conservative against the benchmark on this page (IBM reports a 94% containment rate of common questions for AskHR after years of refinement). |
| Cost of an HR handled query costPerQuery, USD per query | 10 | 20 | Editorial assumption for a shared services centre. Replace with your own cost. |
What it leaves out: Gross handling cost only. It leaves out the platform and integration cost, employee time saved by faster answers, and the effect of fewer errors from outdated policy copies. Savings usually show as capacity redeployed within HR, not as headcount.
Who already uses it?
4 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Bank of America
United States · Banking · 2020
Bank of America launched Erica for Employees in 2020, building on its customer facing assistant, to give staff technology support such as mobile device password resets and device activation. In 2023 it was extended to HR topics such as where to review health benefits and how to find payroll and tax forms. The bank reports that most employees use it and that it has more than halved calls into the IT service desk.
- Employee adoption: at least 90%, as of April 2025
"Today, over 90% of employees use Erica for Employees, with the virtual assistant having reduced calls into the IT service desk by more than 50%."
Claimed by: organization - Contact deflection: at least 50%, calls into the IT service desk, as of April 2025
"Today, over 90% of employees use Erica for Employees, with the virtual assistant having reduced calls into the IT service desk by more than 50%."
Claimed by: organization
IBM
United States · Technology and software · 2016
IBM's internal virtual agent AskHR automates more than 80 HR tasks, from payslip and sickness policy questions to job verification letters and vacation requests, and lets managers start transfers and organization changes in SAP SuccessFactors. AskHR has been refined since 2016; IBM added watsonx Orchestrate for generative and agentic automation in 2025. IBM reports high containment, fewer tickets and lower HR operating cost from the assistant over that longer period.
- Containment rate: 94%, common questions
"AskHR also achieved a 94% containment rate of common questions, has led to a 75% reduction in support tickets raised since 2016, and created more than 11.5 million employee interactions in 2024 alone."
Claimed by: organization - Interactions handled: at least 11.5 million, calendar year 2024
"AskHR also achieved a 94% containment rate of common questions, has led to a 75% reduction in support tickets raised since 2016, and created more than 11.5 million employee interactions in 2024 alone."
Claimed by: organization - Contact deflection: 75%, HR support tickets raised, since 2016
"AskHR also achieved a 94% containment rate of common questions, has led to a 75% reduction in support tickets raised since 2016, and created more than 11.5 million employee interactions in 2024 alone."
Claimed by: organization - Cost reduction: 40%, over four years
"The AI agent helped contribute to a 40% reduction in the HR team’s operational costs over the past four years."
Claimed by: organization - Employee adoption: 99%, managers
"The adoption of AskHR has reached 99% among managers."
Claimed by: organization
Turing
United States · Technology and software · 2025
Turing (listed by Google Cloud as Turing Enterprises), an AI company headquartered in San Francisco, built a custom AI model trained on its internal knowledge that drafts replies to HR support tickets. Google Cloud reports a one third cut in ticket processing time after two days of development. A plan to automate 60% of its 52,000 annual HR tickets with Gemini Gems is a target, not a result.
- Cycle time reduction: 33%
"Turing also built a custom AI model trained on internal knowledge to draft replies to HR support tickets, reducing ticket processing time by 33% after two days of development."
Claimed by: vendor
Vituity
United States · Healthcare · 2020
Vituity, a healthcare organization owned and led by a partnership of nearly 5,000 physicians, deployed a Moveworks AI assistant called Otto in Microsoft Teams in April 2020, connected to ServiceNow, Okta and internal knowledge. It started with IT workflows such as password resets, account provisioning and software access, then expanded into HR questions and other operational domains. The vendor reports that the average time to close issues fell by one full business day and that first line help desk capacity was freed.
- Productivity gain: 40%, level 1 help desk capacity
"It now absorbs a significant share of routine IT and HR requests — including password resets, software access, HR questions, and account provisioning— freeing up 40% of level 1 help-desk capacity."
Claimed by: vendor
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Current HR policies per country and entity, each with an owner and effective date
- Employee attributes that decide which policy applies (country, entity, grade, contract)
- The list of topics that must always go to a person
Systems to integrate
- HR information system (for example Workday or SAP SuccessFactors) for balances and transactions
- Payroll and benefits portals for links and documents
- Identity provider for single sign on
- HR case management for handover
Complexity: Medium
A policy question answerer is quick to build. Personalization by country and grade, access scoping to the individual, and transactions in the HR system are where the effort goes, along with keeping policy documents current.
- 1
Map the question volume
Pull a year of HR tickets and emails and group them. Most volume sits in a few topics: leave, pay, benefits, letters and expenses. Start there.
- 2
Fix the source documents first
Remove duplicates and old versions, tag each policy with the population it applies to and an effective date. The assistant can only be as current as this library.
- 3
Scope retrieval and data to the person
Filter retrieval by the employee's attributes and read personal data only through HR system APIs scoped to the requester. Test that no answer can reveal another employee's data.
- 4
Define the human topics
Agree with HR, legal and employee representatives which topics always go to a person and how the handover works, including confidential routes.
- 5
Add transactions one at a time
Start with letters and leave requests that already have approval workflows, and let the HR system enforce the rules rather than the assistant.
- 6
Consult before launch
Where works councils or unions have a say in employee monitoring tools, involve them early and document what is and is not logged.
Guardrails
- Answers cite the policy and section, and the assistant refuses when no applicable policy is found
- Personal data only through APIs scoped to the signed in employee
- Automatic handover for grievances, misconduct, harassment, health and wellbeing
- No decisions on pay, performance, promotion or discipline; the assistant informs, HR decides
- Conversation logs with restricted access and a defined retention period
KPIs to instrument
- Containment per topic, counting a follow up ticket within seven days as not contained
- Answer accuracy on a monthly sample checked by HR per country
- Employee adoption and satisfaction
- Share of sensitive conversations correctly handed over
- Time to complete letters and leave requests
Human in the loop
HR owns the policy content, every sensitive topic and every decision about an individual. HR business partners review a weekly sample of answers per country, and policy owners approve changes before they reach the knowledge base.
Common failure modes
- The wrong country's policy
- A correct answer for Germany given to an employee in Singapore. Filter retrieval by the employee's attributes and test each country separately.
- Leaking another employee's data
- Documents or logs that contain personal data are retrieved for the wrong person. Keep personal data out of the document index and scope every lookup.
- Automating what needs empathy
- A distressed employee gets a policy extract. Detect sensitive topics and route to a person.
- Drift into decisions
- The assistant starts screening internal applications or ranking requests. That changes its risk class and needs its own assessment.
What are the risks and rules?
EU AI Act
Depends on design
Answering policy questions and starting routine requests is limited risk, with the Article 50 duty to disclose AI. It becomes high risk under Annex III point 4 if it is used to make or support decisions on recruitment, promotion, termination, allocating tasks based on individual behaviour or personal traits, or the monitoring and evaluation of workers; an employer deploying it then must also inform workers' representatives and the affected workers before use (Article 26(7)). Sensitive topic detection should work on what the employee writes: inferring emotions of people in the workplace from biometric data such as voice or facial expressions is prohibited under Article 5(1)(f), except for medical or safety reasons.
Guidance
- Annex III, high risk AI systems referred to in Article 6(2) (European Union, Europe). Point 4 lists employment and worker management uses that would make an HR assistant high risk.
- Article 50, transparency obligations for providers and deployers of certain AI systems (European Union, Europe). Employees must know they are interacting with AI unless this is obvious from the context.
- Employment practices and data protection: monitoring workers (UK Information Commissioner's Office, Europe). Relevant to how conversation logs about employees are kept, used and disclosed under UK GDPR. The ICO says the guidance is under review after the Data (Use and Access) Act.
Controls to put in place
- Data protection impact assessment covering logs, retention and access to conversations
- Inventory entry with an owner in HR and a documented list of topics routed to people
- Access to conversation logs restricted and audited
- Consultation with employee representatives where required
- Periodic accuracy review per country and policy area
Frequently asked questions
- How much of HR's question volume can an assistant take?
- A mature deployment takes most routine questions. IBM reports a 94% containment rate of common questions for AskHR, which recorded more than 11.5 million employee interactions in 2024, and says it helped contribute to a 40% reduction in HR operating costs over four years. That took several years of refinement; plan for lower rates at launch.
- Is an HR chatbot high risk under the EU AI Act?
- Not when it answers policy questions and starts routine requests. It becomes high risk under Annex III point 4 if it is used for recruitment, promotion, termination, allocating tasks based on behaviour or personal traits, or evaluating employees, which needs a separate assessment.
- Should IT and HR share one assistant?
- Often yes: employees do not care which department owns the answer. Bank of America's Erica for Employees started with IT support and added HR topics such as benefits and payroll forms, and Vituity's assistant covers both IT and HR requests. Keep separate content owners and data scopes behind the single front door.
How to cite this page
Blits.ai AI Use Case Library, "AI assistant for HR and policy questions", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/hr-and-policy-assistant. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published