Repeated questions
Leave, meal vouchers, health plan and expenses take up the team's day, even though it is all written down somewhere.
Memory for HR
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.
The problem
And each manager explains the policy their own way.
Leave, meal vouchers, health plan and expenses take up the team's day, even though it is all written down somewhere.
New joiners learn by asking the colleague next to them, and each colleague teaches differently.
Without a company AI, people paste colleagues' data into personal tools, with no control and no record.
Before and after
From an employee's question to the reviewed policy.
| Without the company's memory | With Kluco |
|---|---|
| Without the company's memoryThe policy is in a PDF nobody can find | With 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 message | With KlucoThe assistant answers in the team's channel, with the source policy |
| Without the company's memoryEach manager explains the rule their own way | With KlucoEveryone gets the same answer, from the same source |
| Without the company's memoryNew joiners depend on the colleague next to them | With KlucoNew joiners ask the knowledge base and learn the company's way through skills |
| Without the company's memoryNobody knows which AI the team uses | With KlucoOne company chat, with access profiles and an audit log |
What goes into memory
Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and become articles that AI keeps up to date.
Use cases
The most common use cases in HR, with the part of the platform that does each one.
The questions HR gets every month are answered in the team's channel, with the source policy and the date of its last review.
AgentsPeople who just joined ask the knowledge base instead of interrupting the team, and learn the company's way of working through skills.
BrainPeople ask in Slack, Teams or Google Chat and get the answer with the source article.
AgentsWhen the company turns it on, the agent masks personal data in its logs and answers.
AgentsWhat the knowledge base could not answer goes into a queue. Someone answers it once, and the answer becomes an article for everyone.
BrainGPT, Claude, Gemini and other models, all in the Chat, with the access the company sets and an audit log.
LLM Management and ChatAgents · AI agents
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.
Brain · the memory
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.
LLM Management and Chat
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.
Control
The company sets up each control below in the console.
FAQ
Yes. Agents work in Microsoft Teams, Slack, Google Chat, Telegram and WhatsApp. You choose the channels and who can use each agent.
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.
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.
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
In the demo, we show the policy knowledge base, the assistant in chat and the access controls.