IBM Software / SaaS global

IBM HR

Customer Service Automation

IBM HR needed to replace fragmented, multi-channel support and repetitive manual work with a single service experience that could answer policy questions, execute transactions, and route complex cases consistently across a global workforce.

40% reduction in the HR team’s operational costs over the past four years
55.1 K pieces of user feedback collected in 2024
7,000 policy pages are accessible
75% reduction in support tickets raised since 2016

Reported impact

Business outcome

AskHR reduced HR operating cost, cut support tickets sharply, achieved high containment and manager adoption, and shifted the HR operating model toward hybrid automation without removing human support for complex needs.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

IBM evolved AskHR from a virtual assistant into an agentic HR support layer powered by IBM watsonx Orchestrate and deep enterprise-system integration. The service exposes more than 7,000 policy pages and automates more than 80 HR tasks through a conversational interface that classifies employee prompts with compliant large language models, routes them to the right HR domain, and either triggers a backend task or returns an AI-generated answer in the user’s preferred language. Behind the scenes, AskHR connects to systems such as Workday, SAP, Concur, and SAP SuccessFactors so employees can retrieve payslips, submit vacation requests, obtain verification letters, or receive personalized payroll and policy guidance, while managers can initiate transfers or organizational updates. The two-tier operating model keeps routine work with AI and escalates only complex needs to human advisors, giving IBM a hybrid digital-labor pattern for HR service at global scale.

Data flow

An employee or manager submits an HR question in natural language, watsonx Orchestrate classifies it and routes it to the relevant HR domain, AskHR generates a compliant response or triggers a workflow in Workday, SAP, Concur, or SuccessFactors, and only the more complex requests move to human advisors.

Solution architecture

6 components · 3 layers
  1. Storage
    • Workday Supplies enterprise HR data and workflows that AskHR uses for employee support.
    • SAP Supports backend HR and payroll process integrations used by AskHR.
    • Concur Provides travel-related workflow context and transactions for AskHR automations.
    • SAP SuccessFactors Enables manager workflows such as employee transfers and organizational updates inside AskHR.
  2. Serving
    • AskHR agents Provide the employee-facing conversational experience and execute automated HR tasks across domains.
  3. Orchestration
    • IBM watsonx Orchestrate Adds generative AI and agentic automation so AskHR can classify prompts, route work, and trigger HR workflows.

Architecture clues

  • AskHR runs as a two-tier support model with AI for routine work and human advisors for complex cases.
  • Large language models classify prompts into domains such as Benefits, Payroll, and Career and Skills.
  • The service has been refined continuously for more than six years before the 2025 watsonx Orchestrate upgrade.

Evidence from the source

“Behind the scenes, complex HR processes are streamlined through deep integration with enterprise systems such as Workday, SAP and Concur.”
“Over the past six years, IBM has continuously refined their internal virtual agent, AskHR, to automate more than 80 HR tasks and handle over 2.1 million employee conversations annually.”
“The AI agent helped contribute to a 40% reduction in the HR team’s operational costs over the past four years.”
“The adoption of AskHR has reached 99% among managers.”
“the team integrated IBM watsonx Orchestrate to enhance AskHR’s gen AI and agentic automation capabilities.”
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    IBM HR customer story

    First-party
    https://www.ibm.com/case-studies/ibm-askhr
    Source type
    Vendor-published customer story
    Published
    Aug 21, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.