Memory for HR

The right policy, in the channel where people already ask.

Leave, benefits, expenses and internal rules become a reviewed knowledge base. An assistant answers in Slack, Teams or Google Chat with the source policy, and HR looks after what needs a person.

Product screen, with sample data

The problem

HR answers the same questions every month.

And each manager explains the policy their own way.

Repeated questions

Leave, meal vouchers, health plan and expenses take up the team's day, even though it is all written down somewhere.

Onboarding that depends on people

New joiners learn by asking the colleague next to them, and each colleague teaches differently.

Personal data in any AI

Without a company AI, people paste colleagues' data into personal tools, with no control and no record.

Before and after

What changes in HR.

From an employee's question to the reviewed policy.

Without the company's memoryThe policy is in a PDF nobody can findWith KlucoThe current policy is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryThe question reaches HR by messageWith KlucoThe assistant answers in the team's channel, with the source policy
Without the company's memoryEach manager explains the rule their own wayWith KlucoEveryone gets the same answer, from the same source
Without the company's memoryNew joiners depend on the colleague next to themWith KlucoNew joiners ask the knowledge base and learn the company's way through skills
Without the company's memoryNobody knows which AI the team usesWith KlucoOne company chat, with access profiles and an audit log

What goes into memory

What HR answers, in one place.

Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and become articles that AI keeps up to date.

  • Leave and absence policy
  • Benefits and how to use them
  • Expense reimbursement
  • Code of conduct
  • Onboarding handbook
  • Career and review framework
  • Remote and hybrid work rules
  • Holiday and break calendar

Use cases

Where HR starts.

The most common use cases in HR, with the part of the platform that does each one.

  • Questions on leave, benefits and policies

    The questions HR gets every month are answered in the team's channel, with the source policy and the date of its last review.

    Agents
  • Onboarding for new joiners

    People who just joined ask the knowledge base instead of interrupting the team, and learn the company's way of working through skills.

    Brain
  • A policy assistant in the team's channel

    People ask in Slack, Teams or Google Chat and get the answer with the source article.

    Agents
  • Personal data masked

    When the company turns it on, the agent masks personal data in its logs and answers.

    Agents
  • An unanswered question becomes an article

    What the knowledge base could not answer goes into a queue. Someone answers it once, and the answer becomes an article for everyone.

    Brain
  • One company chat instead of personal accounts

    GPT, Claude, Gemini and other models, all in the Chat, with the access the company sets and an audit log.

    LLM Management and Chat

Agents · AI agents

An HR assistant in the team's channel.

The assistant answers in Slack, Microsoft Teams or Google Chat with what is in the knowledge base, and you set who can use it and what it can do.

  • Slack, Microsoft Teams, Google Chat and Telegram
  • Knowledge limited to chosen documents
  • Personal data masking, when turned on
See the Agents
Product screen, with sample data

Brain · the memory

Policies with an owner and a review deadline.

The Brain turns HR's documents into articles with an owner and a review deadline. When a rule changes, AI proposes the update and HR approves it.

  • A queue of unanswered questions
  • Skills that hold the company's way of working
  • Audience per article: all agents or internal assistants only
See the Brain
Product screen, with sample data

LLM Management and Chat

AI for the whole company, with on-the-job training.

Each person uses the models their profile allows, in the Chat, which draws on the company's memory. The team learns by doing, with the house way of working built in.

  • Access profiles per group of people
  • A limit per person and a budget per team
  • Adoption report
See LLM Management
Product screen, with sample data

Control

What HR controls.

The company sets up each control below in the console.

See security and LGPD
  • An owner and a review deadline on every policy, with a record of who verified it and when
  • The audience of each article: all agents or internal assistants only
  • Who can use each assistant, through the access profile
  • Personal data masking in logs and answers, when turned on
  • Audit log for configuration and chat

FAQ

What HR teams ask.

Does the assistant work in Teams?

Yes. Agents work in Microsoft Teams, Slack, Google Chat, Telegram and WhatsApp. You choose the channels and who can use each agent.

Does the assistant see salary and review data?

Only if you put those documents in the knowledge base and allow it. Each agent queries only the documents you choose, and the company can turn on personal data masking.

How does the policy stay up to date?

Every article can have an owner and a review deadline. When the deadline passes, the article is flagged. When the source document changes, AI proposes the update, which can wait for HR's approval.

Does it help with onboarding?

Yes. New joiners ask the knowledge base instead of interrupting the team, and skills hold the company's way of doing each task.

Next step

See the HR assistant answering in your team's channel.

In the demo, we show the policy knowledge base, the assistant in chat and the access controls.