The HR service desk that answers itself
An enterprise HR function now resolves around 75% of routine employee requests without HR involvement on x101, moves new joiners from offer accepted to fully productive around 50% faster, and has returned around 65% of HR time to higher-value work. Most of what the team handled was never complex, it was repetitive: the same policy questions, the same record changes, the same onboarding checklist across the same systems. x101 answers from the governing policy, completes the update in the system of record, and carries a new joiner through onboarding across every team involved.
HR & Workforce
Last updated: 23 September 2026
The challenge
The volume was high, the judgement required was low, and it crowded out the parts of the job that needed a person. Policy answers depended on who you asked, onboarding meant coordinating five systems owned by five teams, and changing an address became a ticket.
The answer depended on who you asked
Policy questions were answered from memory or from a document that might not be current, so the same question got different answers.
Onboarding spanned five owners
Getting a joiner productive meant coordinating identity, payroll, equipment, access and training, each owned by a different team on a different tool.
Simple updates routed through HR
Changing an address, bank detail or emergency contact became a ticket, when the employee could do it under the right controls.
Non-desk staff hardest to reach
Field, plant and shift workers do not sit at a laptop, so their requests arrived by phone or not at all.
Repetitive load on a skilled team
The same questions consumed the capacity meant for cases that genuinely need judgement.
No view of where it stalls
Nobody could say which policies confused people or where onboarding consistently lost days.
What x101 does
x101 became the front door for employee services. A question is answered from the current governing policy with the clause shown. A record change is completed in the system of record rather than raised as a ticket. A new joiner is carried across every team that has to act. And anything needing judgement reaches a person with the context already gathered.
Policy answered from the source
A question in plain words returns the answer with the exact passage from the current policy, so what the employee is told is what the policy says.
Updates completed, not queued
Personal record changes are made in the system of record within the employee's own permissions, and confirmed back in the same conversation.
Onboarding carried end to end
A joiner's identity, payroll setup, equipment, access and training are coordinated across the teams that own them, each step confirmed as it lands.
Available on a phone call
Staff away from a screen ask the same questions and make the same updates by voice, with the same rules applied.
Escalated when judgement is needed
Anything sensitive, contested or outside policy routes to a person with the context already gathered, rather than starting over.
The pattern becomes visible
Which questions recur, where onboarding stalls and which policies confuse people are readable from the record, so the process itself can be fixed.
Entitlement is not negotiable. Each person sees and changes exactly what they are entitled to, every action is recorded against them, and sensitive categories route to a human by policy rather than by the model's judgement.
The impact
The repetitive load left the team. Employees get a consistent answer from the current policy at the moment they ask, joiners reach productivity faster, and HR spends its time on the cases that actually need it.
- ~75%
Self-served
Routine requests resolved without reaching the HR team.
- ~50%
Faster to productive
From offer accepted through to fully onboarded.
- ~65%
HR time returned
Capacity moved from repetition to judgement.
- 100%
Answers cited
Every policy answer tied to its document and version.
| Dimension | Before | After · with x101 |
|---|---|---|
| Policy answers | Depended on who was asked and which copy they held | Answered from the current governing document, with the clause cited |
| Record changes | Raised as a ticket, queued behind HR | Completed in the system of record within the employee's permissions |
| Onboarding | Five teams, five tools, coordinated by hand | Carried across every owner, each step confirmed as it completes |
| Non-desk staff | Phone calls into a queue, or nothing | The same service by voice, with the same rules applied |
| HR capacity | Consumed by repetition | Returned to cases that need judgement |
| Process insight | No view of where things stalled | Recurring questions and onboarding delays visible from the record |
The team was never short of expertise, it was short of time. Handing the repetitive nine-tenths to a system that answers from the actual policy, and completes the change rather than logging it, is what gave the expertise somewhere to go.
Solution summary · x101 employee services deployment
The parts of x101 this uses
Nothing here was built for one customer. Each capability below is standard platform behaviour, applied to this problem.
Company Knowledge
Policies, handbooks and local addenda answer questions with the governing clause shown.
Explore Company KnowledgeFrom Answer to Action
A record change is completed in the system of record, not raised as a ticket.
Explore From Answer to ActionVoice
The same capability over a phone call, for staff who work away from a screen.
Explore VoiceAI Explainability
Every answer names the policy and version it came from.
Explore AI ExplainabilityGoverned by Design
Each person sees and changes exactly what they are entitled to.
Explore Governed by DesignBuild Your Own Agent
HR shapes its own agent as policies change, without waiting on engineering.
Explore Build Your Own Agent
About this case study. The customer's identity is withheld at their request. Improvement figures reflect the target and expected outcomes of the deployment and are indicative; actual results vary with policy complexity, system coverage and workforce profile.
Give your people a straight answer.
Policy answered from the source, updates completed under governance, onboarding coordinated across every system, by chat or over a call.