Several versions of the same conditions
Products are revised every year, and old conditions still apply to old policies. Finding the right version takes time.
Memory for Insurers
General conditions, coverage and claims procedures become a reviewed knowledge base, with an owner and a review deadline. Customer service, broker support and AI agents answer from the same version.
The problem
And a wrong answer becomes a complaint.
Products are revised every year, and old conditions still apply to old policies. Finding the right version takes time.
Deadlines, documents and approval limits for each type of claim live in different manuals, emails and spreadsheets.
An AI without the insurer's knowledge base answers with what sounds right, without citing the clause.
Before and after
From the published conditions to the answer the policyholder gets.
| Without the company's memory | With Kluco |
|---|---|
| Without the company's memoryThe right conditions are in one PDF among many | With KlucoThe current conditions are in the knowledge base, with an owner and the date of their last verification |
| Without the company's memoryThe old version is still in use | With KlucoWhen the review deadline passes, the article is flagged as overdue |
| Without the company's memoryThe answer does not say where it came from | With KlucoEvery answer shows the passages consulted and their verification date |
| Without the company's memoryA new question gets lost in customer service | With KlucoAn unanswered question goes into a queue and becomes an article |
| Without the company's memoryAI publishes what it wrote | With KlucoWhat AI writes can wait for the approval of whoever owns the product |
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 at insurers, with the part of the platform that does each one.
Internal rules and procedures live in one knowledge base, with an owner, a review deadline and a version history.
BrainThe agent serves customers on WhatsApp and the other channels with what is in the reviewed knowledge base, and hands over to a person what it does not know.
AgentsWhat the knowledge base could not answer goes into a queue. Someone answers it once, and the answer becomes an article for everyone.
BrainWhen AI writes or updates an article, the change can wait for the approval of whoever owns the topic.
BrainEach agent queries only the documents you choose, and the access profile sets who can use each agent.
AgentsWhen the company turns it on, the agent masks personal data in its logs and answers.
AgentsBrain · the memory
The Brain turns conditions and procedures into articles with an owner, a review deadline and a version history. Every answer shows the passage and its verification date.
Agents · AI agents
Create one agent for home insurance and another for motor, each limited to the documents you choose and with clear approval rules.
LLM Management and Chat
Customer service, claims and underwriting use the models their profile allows, in the Chat, which draws on the insurer's memory.
Control
The company sets up each control below in the console.
FAQ
The knowledge base keeps each document with an owner, a review deadline and a version history, and every answer shows the passage and its verification date. Versions that apply to older policies can stay in the knowledge base as separate articles, each with its own title.
Yes. Each agent queries only the documents you choose, and the access profile sets who can use each agent.
That is not its role. Agents answer and organise based on the documents, and sensitive actions can require a person's approval. The decision stays with the insurer's team.
With access profiles, data isolated per company, an audit log and the option to mask personal data in the logs and answers of each agent. The Security page covers each control.
Next step
In the demo, we show the conditions knowledge base, an agent per product and approval of what AI writes.