All solutions
Support function · People and HR

Consistent answers from current policy, with sensitive cases going to a person.

Staff ask HR the same policy questions all week, and answers differ by who replies.

For HR teams, the head of People who approves their releases, and the IT team that governs them.

How the example fits together: tools and an agent built on Unflood, with a person approving before anything is written.

Made from a conversation in Claude, released to the AI platforms your team already uses, running in your own environment.

Claude
Turn this conversation into an agent that answers staff questions from the current HR policy pages.
Unflood created the agent from this conversation, ran its multi-turn tests and asked the head of People to approve the release.
  • Unflood: HR policy agent created from this conversation 3m ago
  • Unflood: Multi-turn tests run, including a sensitive case to hand over 2m ago
  • Unflood: Released after the head of People approved 1m ago
  • Unflood: Shared with the People team Just now

See it happen in a chat

A person on the team asks for an agent. Unflood does the building in the background and comes back for the decisions that are yours.

  • Unflood tests them.
  • A person approves each release.
  • They are shared with the right people.
  • They are kept up to date, so you step in only when a decision is yours.

Examples for People and HR, to learn from

Example 1

Answer leave, expenses and notice questions from current policy

On Unflood: Knowledge: the current HR policies.

Example 2

Hand sensitive cases to an HR partner

Example 3

Answer new joiners' first-week questions

How a policy answer fits together

Knowledge
Current HR policiesThe policies an HR partner already maintains.
Agent
Policy answererAnswers from current policy, so replies agree.
Test suite
Past questionsCases from questions staff really asked.
Person
An HR partner takes sensitive casesSensitive cases go to a person.

Six moments that make the difference

Each one is shown on sample data, with this team's own example where there is one.

Build it from a conversation

Describe the agent in a Claude chat. Unflood records it, its tools and its tests.

In People and HR: Answer leave, expenses and notice questions from current policy

  • KnowledgeThe HR policy pages, bound by reference.
  • Builds itAn HR partner, from the policies they maintain.
Recorded from the conversation Policy answerer
HR policiesPast questionsHR partner
Drawn on sample data.

Test it

Suites and a judge run it; each failed case becomes an item to fix.

In People and HR: Multi-turn questions, including a sensitive one it must hand over.

  • TestsMulti-turn questions, including a sensitive one it must hand over.
Test lab
  • A case failsJudged against the version tested.
  • It becomes an item to fixNothing is lost between runs.
  • Retest, then release
Drawn on sample data.

Release it with approval

Package a version. Nothing reaches people without a person's approval; the builder cannot approve their own.

In People and HR: The head of People.

  • Release with approvalThe head of People approves each version.
  • Approves itThe head of People.
Release waiting for approval
  • Packaged byAn HR partner, from the policies they maintain.
  • Needs approval fromThe head of People.
The builder cannot approve their own release.
Drawn on sample data.

Share it

Choose who can use it, person by person or team by team, where the team already works.

In People and HR: All staff.

  • Uses itAll staff.
Who can use it
  • The People and HR teamAll staff.
  • A named personChoose person by person or team by team.
Drawn on sample data.

Keep it up to date

Change it, retest it, release the next version. Every version can be rolled back.

Versions
  • Current versionLive.
  • Next versionChanged, retested, waiting for approval.
  • Roll backEvery version can be rolled back.
Drawn on sample data.

The organisation stays in control

Members, roles and a record of every change belong to the organisation.

  • A workspace for the organisation, on its proven domains
  • Members and roles: who uses an agent and who changes it
  • Release approval by a second person
Record of every change
  • The builderCreated the agent.
  • UnfloodRan the tests.
  • The approverApproved the release.
Drawn on sample data.

How the team gets there faster

Your people describe the work and approve it. Unflood does the building, testing and publishing.

Today

Staff ask HR the same policy questions all week, and answers differ by who replies.

With Unflood

Consistent answers from current policy, with sensitive cases going to a person.

Your people do
  • Builds itAn HR partner, from the policies they maintain.
  • Approves itThe head of People.
  • Uses itAll staff.
Unflood does
  • Connects your tools and data
  • Writes and runs the tests
  • Packages each version
  • Publishes it where your team works
  • Retests every change before the next release
  • Keeps the record of who changed what

Talk to us about your team

Tell us the work your team wants an agent for. We set up a workspace with you and build the first one with the people who know the work.

Get in touch