Skip to content
Let’s Talk
HR AGENTS / GUIDE

How to Run Acceptance Tests on an HR Chatbot Before Launch

Four test accounts, three checks and a recorded decision for each scenario.

The builder’s own test shows the chatbot works with the builder’s access. Test it again as an employee would use it, in the same channel and with the same access, and write down what counts as a pass before you start.

IT has already demonstrated it. Isn’t that the test?

A demonstration with an administrator’s account shows it can work. Employees have different access and use a different route, so their experience needs its own test.

1. Test with four accounts.

The intended employee
Gets the guidance that applies to them, with a source they can open.
An employee from a different group
Gets the guidance for their own group, and sees nothing meant for others.
Someone without access
Gets a useful message about where to go, with no misleading answer.
The HR reviewer
Sees the follow-up information they need and no more.

Use test accounts in the channel employees will use, with made-up personal details.

2. Run three checks HR can judge.

Finding the policy. Ask where to submit leave. The answer gives the right steps for that employee and a reference they can open.

Changing a record. If updates are part of the pilot, change the test account’s own phone number. Confirm the saved value in the HR system, and confirm that another person’s record can’t be opened.

Asking for help. Submit a made-up request. The receiving team finds one case with the agreed details.

3. Test a failed submission.

Make a request fail on purpose and read what the employee sees. A request passes through four states: submitted, received, reviewed and resolved. The employee is told only the one that has happened.

Practical check: After a failure, does the employee know the request did not arrive?

4. Record a decision for each scenario.

Pass. Write down the scenario, the test account, the expected result and the observed result.

Fix and retest. Record the problem and who owns it, and run the same test after the fix.

Outside this pilot. Mark what isn’t being used, and have the builder confirm that those actions are switched off.

A fictional record for one scenario.

Scenario
A part-time employee asks where to submit leave.
Account
A test account in the part-time group.
Expected
The part-time leave steps, with a link that opens.
Observed
The right steps, but the link asked for a sign-in the account didn’t have.
Decision
Fix and retest. The owner of the policy folder corrects the access.

Read more: Can an HR Agent Work Without an HRIS? · How to Test an AI Agent With Questions It Hasn’t Seen · Letting AI Update HR or Payroll Records: Approve Every Change First

The record is fictional. Use test accounts and made-up personal details. This is general guidance, not advice for your situation.