Reported operating use · Enterprise HR
AI HR service desk: IBM example
IBM reports that AskHR, built on IBM watsonx Orchestrate, connects to enterprise HR systems and carries out tasks such as letters, leave requests and organizational changes. The 2025 agentic upgrade sits within a service transformation that began in 2016, so historical cost reductions cannot be credited to it alone.
Employee transfers, letters, leave and HR escalation
IBM
Internal production; multi-agent orchestration added in 2025 to a much older service programme.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
The workflow at a glance
IBM reported work
Illustrative summary of the published account
Reported work components. Their arrangement does not imply a fixed execution order or simultaneous work.
- Internal service
AskHR system connections
Connects enterprise HR systems to employee assistance.
- HR tasks
Letters, leave and organizational changes
Task execution spans several employee-service needs.
- Service context
Human support improvements
The agentic upgrade belongs to a longer programme with reported early dissatisfaction.
What the source reports
AskHR connects to enterprise HR systems and executes tasks including letters, leave requests and organizational changes. Its 2025 agentic upgrade sits within a transformation beginning in 2016. IBM also reports early employee dissatisfaction and later improvements to human support. Historical cost reductions cannot be credited solely to the agentic upgrade.
Reported technology: IBM watsonx Orchestrate. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
Proposed practice environment
Prepare an HR request and advisor handoff
Illustrative project design to scope with your enterprise.
- 1 · Set up the environment
Fictional HR tenant
Synthetic org chart, leave balances, manager authority and location policies.
- 2 · Preparation and agent contributions
Prepare HR task and handoff
Draft a letter or test request and preserve sensitive-case context for an advisor.
- 3 · Independent checks
Check records and privacy
Independent HR references verify eligibility, letter contents and permitted backend changes.
- 4 · People decide acceptance
HR owner accepts journey
Review actual resolution and accessible human support for complex cases.
A reviewable evidence package
A verified practice HR artifact and advisor handoff record.
If a check fails → withhold acceptance.
A sensitive case is contained without a useful path to a human. Withhold acceptance, repair, independently recheck and return to owner review.
Failure or owner rejection returns to review
- Hold
- → 2 · Revise work
- → 3 · Rerun independent checks
- → 4 · Owner review
Operating boundary. No live employee records, HR communications or consequential employment decisions.
- Systems and tools
- Inferred test scope: HR test tenants and document-generation APIs.
- Data and state
- Inferred test scope: Employment status, manager authority, location policy and transfer state.
- People and handoffs
- Inferred test scope: Employee/manager request; HR advisor owns complex cases.
- Rules and authority
- Inferred test scope: Country and role-specific access; consequential decisions need authorized approval.
- Normal and exception cases
- Proposed test cases: Eligible transfer, wrong manager, conflicting policy, sensitive personal circumstances.
- Reset and replay
- Not reported. Proposed: Restore synthetic org chart and leave balances; prevent real HR communications.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Handle a leave, letter or transfer request with location-specific policy; route a sensitive or ambiguous case to an advisor.
Review gate: Check eligibility, manager authority, record changes, privacy and accessible human support; evaluate the employee experience alongside task completion.
Challenge the result: Use a sensitive case that cannot be resolved by the agent. Human access and handoff quality must count toward the outcome.
What needs checking
- Proposed: compare backend changes and letter contents with approved requests.
- Proposed: measure whether the employee reached useful resolution, including human availability.
- Proposed: HR specialists review location-specific policy and difficult employee journeys.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Questions about this example
- What does IBM use AI for in HR support?
- AskHR connects to enterprise HR systems and executes tasks including letters, leave requests and organizational changes. Multi-agent orchestration was added in 2025 to a much older service program, and the workflow also covers employee transfers and HR escalation.
- Where do people stay involved in IBM's AskHR?
- The workflow includes HR escalation, and IBM reports later improvements to human support after early employee dissatisfaction. The source does not detail review steps. A proposed check, not IBM's, has HR specialists review location-specific policy and difficult employee journeys.
- How strong is the evidence for IBM's AskHR account?
- It is reported internal production use, but the 2025 agentic upgrade sits inside a program that began in 2016. Its incremental causal contribution and failure distribution are not isolated, and IBM also reports early employee dissatisfaction.
- What would an enterprise need to build something like AskHR?
- This is Nuvepro's proposed design, not IBM's: HR test tenants, document-generation APIs and a restorable synthetic org chart with leave balances, with real HR communications blocked. Checks compare record changes and letters with approved requests and measure whether employees reached useful resolution.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- The incremental causal contribution and detailed failure distribution of the 2025 agentic upgrade are not isolated from the older service programme.
More hr and recruiting examples
- AI candidate sourcing: Anthropic exampleAnthropic
- AI talent market research: Oracle exampleOracle
- AI candidate sourcing: Blue Castle Agency exampleBlue Castle Agency
- AI hiring outreach: Alex Lieberman exampleHiring-outreach workshop example (Alex Lieberman)