Leave, handled from a single sentence
An enterprise now completes around 80% of leave requests without manual handling on x101, confirmed in minutes rather than days, with manager approval turnaround around 55% faster. Entitlement varied by country, contract, tenure and leave type, balances lived in one system while coverage lived in another, and the approval chain ran on reminders. x101 takes the request in one sentence, explains the entitlement against the rule behind it, checks coverage, routes the approval and updates every system that needs to know.
HR & Workforce
Last updated: 23 September 2026
The challenge
Leave looks like a solved problem until you look at the rules. Entitlement depended on geography, contract, tenure and leave type, so employees asked a person rather than trust the portal, coverage was compared by eye against a team calendar, and year-end accrual arrived as a surprise.
The rules were hard to self-serve
Entitlement varied by geography, contract, tenure and type, so employees asked a person.
Balances and coverage lived apart
The balance sat in the HR system and who else was away in a team calendar, compared by eye.
Approvals ran on chasing
Requests waited on a manager who had not seen the notification, and the follow-up was manual.
Downstream systems updated by hand
An approved request still had to reach scheduling and payroll, which happened late or not at all.
Non-desk staff underserved
Shift, field and plant workers had no practical way to request or check leave during a shift.
Year-end brought surprises
Accrual and carry-over liability became visible late, when the options for managing it had narrowed.
What x101 does
x101 takes the request in plain words and carries it to done. It works out the leave type, dates and applicable rules, returns the balance with the rule that produced it, checks coverage against the team calendar before the approval goes out, routes it to the right approver with context, and updates HR, scheduling and payroll once approved.
Asked in one sentence
An employee says what they want in plain words, by chat or on a call, and x101 works out the leave type, the dates and the rules that apply.
Entitlement explained, not just stated
The balance comes back with the policy rule behind it, so an unexpected number carries its own explanation.
Coverage checked first
The request is compared against team calendars and shift coverage, and any clash is raised before the approval goes out rather than after.
Routed and completed
The request reaches the right approver with context attached, and once approved, HR records, calendars, scheduling and payroll are all updated.
Works without a screen
Shift, field and plant staff make the same request by voice, with the same checks and the same confirmation.
Liability visible early
Accrual, carry-over and absence patterns are readable through the year, so the year-end position is managed rather than discovered.
Approval rules are enforced by the platform, not remembered by people. Entitlement is checked against the employee's own record, coverage rules apply before anything is approved, and every request, approval and downstream update is recorded.
The impact
Leave stopped being administration. Requests resolve in minutes with the reasoning attached, managers approve with coverage already checked, and the downstream systems are updated as part of the same flow rather than as follow-up work.
- ~80%
Fully automated
Requests completed without manual handling.
- Minutes
To confirmed outcome
Where requests used to take days of back-and-forth.
- ~55%
Faster approvals
Managers approving with coverage already checked.
- 100%
Balances explained
Every balance figure tied to the rule behind it.
| Dimension | Before | After · with x101 |
|---|---|---|
| Requesting | Portal forms people did not trust, or a message to HR | One sentence, typed or spoken, with the rules applied automatically |
| Entitlement | A number with no explanation | The balance returned with the rule that produced it |
| Coverage | Compared by eye against a team calendar | Checked automatically before the approval goes out |
| Approvals | Chased by reminder | Routed with context, turnaround around 55% faster |
| Downstream updates | Manual, late, or missed | HR, scheduling and payroll updated in the same flow |
| Accrual liability | Discovered at year end | Visible through the year, with patterns readable |
Leave was never one process, it was four: check the rule, check the balance, check who else is away, then tell four systems. Doing all four from one sentence is the whole change.
Solution summary · x101 leave management 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.
From Answer to Action
The request is checked, routed, approved and written to every system in one flow.
Explore From Answer to ActionCompany Knowledge
Leave policies and local entitlement rules explain every balance shown.
Explore Company KnowledgeVoice
The same capability over a phone call, for staff who work away from a screen.
Explore VoiceGoverned by Design
Approval rules enforced by the platform, with every step recorded.
Explore Governed by DesignInstant Analytics
Absence patterns and accrual liability answered from live data.
Explore Instant AnalyticsAI Explainability
Every balance and decision carries the rule that produced it.
Explore AI Explainability
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 entitlement complexity, country coverage and workforce profile.
Take leave off everyone's desk.
Balance, entitlement, coverage, approval and every downstream update handled in one conversation, by chat or over a call.