Memory for the Public Sector

Many units, one version of every procedure.

Rules, procedures and service guidelines become a reviewed knowledge base, with an owner and a review deadline. Departments, service units and AI agents answer citizens from the same version.

Product screen, with sample data

The problem

The procedure changes. The guidance at the counter does not always follow.

And every staff change starts the learning over.

A different version in each unit

The new guideline arrives by official letter, the old one is still printed at the counter, and citizens hear different answers each time.

Knowledge that leaves with people

When a public servant moves to another department or retires, the way of doing things goes too, and newcomers learn by asking colleagues.

AI without a record

Public servants try AI tools on their own, without knowing what leaves the organisation, what it costs or what information it answers from.

Before and after

What changes in the public body.

From the published procedure to the answer a citizen gets.

Without the company's memoryThe new guideline arrives by official letter and each unit keeps its own copyWith KlucoThe current procedure is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryThe old version is still used in serviceWith KlucoWhen the review deadline passes, the article is flagged as overdue
Without the company's memoryNew public servants learn by asking colleaguesWith KlucoNewcomers ask the knowledge base and get the answer with its source document
Without the company's memoryEach channel answers citizens differentlyWith KlucoAI agents and staff answer from the same knowledge base, and the agent hands over to a person what it does not know
Without the company's memoryThere is no record of who changed whatWith KlucoAudit log for configuration and chat, with CSV export

What goes into memory

What a public body keeps in memory.

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

  • Rules, ordinances and internal instructions
  • Procedures for each citizen service
  • Service guidelines and scripts
  • Documents required for each service
  • Filing and case processing flows
  • Internal system manuals
  • Onboarding material for new public servants
  • Frequently asked questions from the public

Use cases

Where the public sector starts.

The most common use cases in government bodies, agencies and state-owned companies, with the part of the platform that does each one.

  • Procedures and rules in memory

    Internal rules and procedures live in one knowledge base, with an owner, a review deadline and a version history.

    Brain
  • One rule, every unit

    Branches, units and teams query the same version of each rule. When it changes, everyone answers from the new one.

    Brain
  • A service agent that answers from the knowledge base

    The 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.

    Agents
  • Audit trail

    Configuration changes and Chat use are recorded, with CSV export, and every agent run keeps its step by step.

    LLM Management and Chat
  • Personal data masked

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

    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

Brain · the memory

One procedure base for every unit.

The Brain turns rules, procedures and service guidelines into articles with an owner, a review deadline and a version history. When a procedure changes, AI proposes the update and the responsible department approves it.

  • Human approval before publishing what AI writes
  • Contradictions between documents become review suggestions
  • A record of who verified each article and when
See the Brain
Product screen, with sample data

Agents · AI agents

Agents that serve citizens from the current version.

Service agents answer on WhatsApp and the other channels with what is in the knowledge base, and hand over to a person what they do not know. Internal agents answer public servants' questions in Teams, Slack or Google Chat.

  • Human approval for sensitive actions
  • Masking of CPF, CNPJ, email and phone, when turned on
  • The history of every run, with step by step
See the Agents
Product screen, with sample data

LLM Management and Chat

AI for public servants, with a record and costs in Brazilian reais.

Public servants use the models their profile allows in the Chat, with the public body's memory. Every change to access, limits and keys goes into the audit log.

  • Access profiles per group of public servants
  • A budget per team, with the month's forecast in Brazilian reais
  • Audit log for configuration and chat, with CSV export
See LLM Management
Product screen, with sample data

Control

What the public body controls.

The public body sets up each control below in the console.

See security and LGPD
  • An owner and a review deadline on every procedure, with a record of who verified it and when
  • A person's approval before publishing what AI writes
  • The audience of each article: every agent or only internal assistants
  • Personal data masking, such as CPF, in logs and answers, when turned on
  • Audit log for configuration and chat, with CSV export, and the history of every agent run

FAQ

What the public sector asks.

How do I make sure every unit uses the same version of a procedure?

The current procedure sits in one knowledge base, with an owner and a review deadline. When it changes, everyone queries the new version, and every answer shows the document and its verification date.

Can agents serve citizens?

Yes. Service agents answer on WhatsApp and other channels with what is in the knowledge base, and hand over to a person what they do not know. Agents that talk to the public do not read articles marked as internal.

What happens to knowledge when the team changes?

It stays in the knowledge base, with an owner and a version history. Newcomers ask the knowledge base instead of interrupting colleagues, and learn how the public body works through skills.

How does Kluco handle personal data?

With access profiles, data isolated per customer, an audit log and the option to mask personal data, such as CPF, in the logs and answers of each agent. The product was designed around the principles of the LGPD, and the Security page covers each control.

Next step

See the public body's procedures reaching every unit.

In the demo, we show the procedure base, approval of what AI writes and a citizen service agent.