AI for HR and staff questions

Monday morning in HR. The inbox holds a question about how many holiday days can be carried over, one about parental leave and one about how the wellness allowance works. All three have answers in the staff handbook. Still, they take time, for the person asking and for the person answering, and next week the same questions will arrive from someone else.

It is one of the clearest examples of where AI helps right away.

Answers instantly, from your own guidelines

An assistant that reads your HR guidelines can answer at any time, in seconds, with a reference to the right document. The employee does not have to wait until after lunch. HR gets fewer routine questions and more time for the work that needs a person, such as conversations, recruitment and the working environment.

It helps managers too. A new manager preparing a first performance review, or wondering which steps apply to a new hire, can get support from your own process instead of searching the intranet. That makes the role more secure and means the same process is followed across the organisation.

And when answers come from the same material, everyone gets the same answer. Someone who started yesterday gets the same reply as someone with ten years in the job. That reduces misunderstandings and makes it easier to treat everyone equally.

Where the line is drawn

An assistant should answer general questions from general guidelines. It should not handle individual HR cases. What applies to parental leave is something the assistant can answer directly. If an employee writes that she and her manager disagree about her leave, the assistant should refer her to HR.

Write that boundary into the assistant’s instructions. Then employees know when the answer comes from the handbook and when a person in HR takes over.

There is another kind of boundary, the one around the data. HR handles some of the most sensitive information in the organisation. Pay, health, assessments and cases do not belong in an assistant that everyone can ask. The staff assistant should read the handbook, not payroll data or case files. With role-based access, HR can have its own assistant with broader material that only HR can reach, and sign-in uses the accounts people already have.

The questions are sensitive too

It is easy to forget. The question itself can reveal something. Someone asking about sick leave, notice periods or parental leave is telling you something about their situation, perhaps before they have spoken to anyone.

That is why it matters where questions are processed. If everything stays in your own environment, nobody has to worry about the question ending up elsewhere, and it is never used to train models. That makes it easier for people to ask what they actually want to know.

Get started by gathering the staff handbook and the most common guidelines, removing old versions and letting a few managers and employees try it first. Follow up on which questions got poor answers. Usually a document is missing, and then you know what needs writing.

How it works in iSearch

With iSearch you create an assistant for staff questions, with your own instructions and connected to your guidelines. Every answer shows which documents were read. Role-based access decides who reaches which material, and sign-in uses SSO and MFA.

The whole chain can run in your own environment, the language model included. Questions and documents stay with you and are never used to train models.

See how iSearch is used, read more about security or book a walkthrough.