HR policy assistants that employees trust

Why trust decides adoption

A manufacturing company with a plant near Sanand and an office in Ahmedabad launches an HR assistant on Microsoft Teams. In the first week, a plant supervisor asks how many earned leaves he can carry forward. The assistant answers from the office policy, which allows more than the plant's. He plans his leave on that answer, HR turns it down, and the story goes round the canteen by lunch.

After that, nobody at the plant uses the assistant. The fault lay in the design: the assistant had no way to tell plant staff from office staff.

An HR assistant is only useful if employees trust it enough to act on its answers. That trust comes from a few design choices.

Answer from the policy that applies to this person

Most companies have more than one version of the truth: different leave rules for plant and office, for staff and workers, for probation and confirmed employees, sometimes by state because of local laws. The assistant must know who is asking and use the right policy.

In practice:

• Connect the assistant to your HR system (Keka, greytHR, Zoho People, Darwinbox or similar) so it knows the person's location, grade and status.
• Tag each policy document with who it applies to.
• When the assistant cannot tell which policy applies, it asks or hands over to a person.

Show the source

Every answer should name the document and section it came from: "Section 3.2 of the Sanand plant leave policy, revised April 2026." This lets the employee check, and it lets HR see quickly when the assistant used the wrong document.

When the answer is not in any policy, the assistant should say so plainly and pass the question to HR. "I could not find this in the policies I have. I have sent your question to the HR team" earns more trust than a confident guess.

Keep personal data private

An HR assistant sits close to sensitive data: salaries, deductions, medical leave, disciplinary matters. Design for that from the start:

• Each employee sees only their own data. Leave balance, payslip date, their own requests.
• No discussion of individual pay. The assistant can explain how the salary structure works in general, and route questions about a specific person's pay to payroll.
• Sensitive topics go to a person. Harassment complaints, medical matters and grievances should reach a named HR person directly, with a clear, kind message to the employee.
• Logs are protected and time limited. Conversation logs contain personal data, so they need the same care as HR records, and a retention period.

Under the DPDP Act your company is responsible for employee personal data processed by the assistant. Agents and the DPDP Act sets out the duties in more detail.

Let it do small things, with approval

Answers are useful. Taking the next step is more useful. A good HR assistant can:

• raise a leave request with the right dates and type, for the manager to approve,
• draft an address proof or experience letter, for HR to check and issue,
• book a slot with HR for a conversation.

Each of these keeps a person as the decision maker. The assistant saves the typing and the back and forth.

Speak the way employees speak

Plant staff may write in Gujarati or Hindi, or in a mix with English, often on a phone. Test the assistant on how your people actually write, including short messages like "PL kitna bacha". If a large part of your workforce does not use Teams or email, consider WhatsApp, with careful thought about privacy on shared phones.

Keep the policies current

The assistant is only as good as the documents behind it. Agree who owns each policy, how updates reach the assistant, and remove old versions on the day a new one takes effect. Review the questions the assistant could not answer every month; they often show gaps in the policies themselves.

A simple launch plan

1. Start with leave and holidays, the most frequent and least sensitive questions.
2. Test on fifty real questions from the HR inbox, across locations and grades.
3. Launch to one location first, with HR reviewing a sample of answers each day.
4. Add payroll questions, letters and onboarding once trust is established.

The HR copilot, the leave policy guide template and the HR team page show how this fits together on AksharAI.