The HR inbox, where the same policy is explained daily
An HR inbox contains two kinds of message that look identical from outside. One is somebody asking how much leave they have left. The other is somebody beginning to describe a problem with their manager, and it often starts with a question about policy.
4 min read
An agent can take the first pile entirely. Getting the second pile wrong is the kind of failure that ends up in a tribunal bundle.
What is safely answerable
Leave. Balances from your HR system, how to request, carry-over rules, public holiday handling, and what happens to leave when someone changes hours.
Payroll logistics. When payday is, how to read a payslip, how to update bank details through the proper channel, what a deduction means in general terms.
Policy explanation. Notice periods, expenses rules, remote work arrangements, sickness reporting procedure. Explaining what the policy says, quoted rather than applied.
Process navigation. Where a form lives, who approves what, how long a process takes, what happens next.
That last one is quietly the most valuable. Most HR frustration is not disagreement with a policy, it is not knowing where a request has got to and who is sitting on it.
What must never be automated
| Message | Why |
|---|---|
| Grievances and complaints about anyone | Formal process, and a written record |
| Anything about a manager or colleague's conduct | Even acknowledgement wording matters |
| Health, disability, or accommodation requests | Sensitive data and legal duties |
| Pay disputes, or an individual's pay decisions | Judgement and confidentiality |
| Redundancy, performance, or disciplinary matters | Legally consequential |
| Anything hinting at distress or safety | Immediately, to a named person |
| Whistleblowing of any kind | A defined route, untouched by automation |
The rule: the agent explains policy, it never applies policy to a person's situation. "The sickness policy requires notification before 09:00" is safe. "You should be covered for that" is an application, and it will be quoted back in a meeting.
Confidentiality changes the design
HR mail is the most sensitive internal correspondence in a company, which has three architectural consequences.
Scope the agent narrowly. It needs the policy documents and a leave balance lookup. It does not need access to personnel files, performance records, or other people's threads, per deciding what each agent is allowed to see.
Never let it add recipients. An agent copying a manager into a thread where an employee was asking about their options is a serious breach, and it is prevented structurally rather than by prompting, per when an agent and a person are on the same thread.
Decide what reaches the model. Employee messages contain health information, family circumstances, and financial detail without being asked to. Send the minimum, know which provider processes it, and keep bodies out of logs, per sending the model less than you think it needs.
The escalation has to feel private
Two details that matter more here than anywhere else.
The escalation message should not summarise what the employee said back to them, because a summary of a sensitive disclosure returned by an assistant reads badly. A short acknowledgement naming who is picking it up and when is enough.
And escalations should route to a person rather than a shared queue where possible. An employee writing about a manager needs to know a specific human has it, and the difference between "someone in HR" and "Maria in HR will reply today" is the difference between trust and a second, angrier message.
Where it pays
The volume is genuinely large in any company past a hundred people, and it is concentrated: the same twenty questions, spiking around payroll dates, leave-year ends, and any policy change.
The second effect is that people ask more, which is a good thing. Employees who know a question will be answered in minutes ask about their entitlements rather than guessing, and guessing is what produces the disputes that HR actually spends its time on.
Start with leave and payroll logistics, which are high volume, factual, and easy to source from systems you already run, per the first week with an email agent.
Questions
- Can an AI agent answer HR questions?
- Yes, for leave balances, payroll logistics, policy explanation, and process navigation. Never for grievances, conduct, health, pay decisions, or anything disciplinary.
- What is the line exactly?
- The agent explains what policy says. It never applies policy to an individual's situation, because that becomes a written commitment quoted in a later conversation.
- Why is scope stricter here?
- HR mail is the most sensitive internal correspondence you have. The agent needs policy documents and a balance lookup, not personnel files or other people's threads.
- What about someone describing a problem with their manager?
- Immediate escalation to a named person, with a short acknowledgement that does not summarise what they said back to them.
- Should escalations go to a shared queue?
- Prefer a named person. An employee raising something sensitive needs to know a specific human has it, not that it entered a queue.
- What is the unexpected benefit?
- People ask more. Employees who expect a fast answer check their entitlements instead of guessing, and guessing is what creates the disputes HR spends its time on.
Give your agent an address it can answer from.
Create an inbox