The work the HR team answers for
Staff ask how much leave they have left, what a policy says about their situation and whether a benefit covers them. Leave and benefits requests follow. They arrive by email, in Teams or Slack, as files, or on a schedule.
The HR operations lead answers for what staff are told. That person is named as responsible for the agent, and the HR team works its review queue.
Example questions
For example only. The last one draws on a document most staff may not see.
What the assistant answers, and when it refuses
The assistant answers from your HR policies and handbooks in SharePoint, OneDrive or Google Drive, and cites every claim. It follows the permissions on each document, so an answer draws only on sources the person asking may see.
When it can’t confirm the asker may see a source, or can’t back an answer, it refuses and says why. When two versions of a policy disagree, it sends the question to a person to decide which one applies.
Answers →For example, “You have nine days of leave left this year.” The leave record and the leave policy are cited.
For example, “I can’t confirm you may see the salary bands, so I can’t answer from them.”
What the agent does
The agent handles the routine follow-up. It drafts the leave booking, sends the benefits form and replies to the person who asked. A request with several steps, such as a return from parental leave, is tracked as a case until it closes.
It holds a role in the HR team, with the HR operations lead named as responsible. It can carry its own Microsoft Entra identity. You set it up from a plain-language job description and plain-English rules.
What it can see and change
Your administrator grants each connection in your own systems. The agent reaches only what was granted, across about 200 business apps.
Integrations →How autonomy moves at your volume
Autonomy is set per task by your team’s run of approvals. Approvals with edits count as neutral and 5% of work is spot-checked. Two mistakes in its last 20 and a task steps back. The steps and timings below are the defaults. Your organisation can set its own steps when it sets Xalios up.
The timings are for one request type. Leave balance questions and benefits questions each move on their own count.
Autonomy →What never runs alone
People decide. The agent proposes until your team’s approvals say otherwise, and some work stays with a person whatever the count.
Conflicting policy versions
When two versions of a policy disagree, the question goes to a person to decide which one applies.
Actions you mark as serious
For example, leave outside policy or a change to someone’s benefits. You choose the list, and those actions wait for a person at every level.
For staff and works councils
Approvers can be pseudonymised in the record. We bring a works-council pack, and we make no promise of fewer colleagues.
On the record
An example record. One question from a member of staff, traced from what they asked to the person who decided.
Every step sits in one record with a tamper-evident history: what was asked, the sources, the check that let it run and who decided. The answer can be traced end to end months later.
The record →Bring the policy questions your team answered last month. We’ll start with the ones that come up most.