Memory for Education

The same regulations on every campus and in every school in the network.

Academic regulations, the calendar, registrar procedures and financial rules become a reviewed knowledge base, with an owner and a review deadline. The registrar's office, the service centre, academic coordinators and AI agents answer from the same version.

Product screen, with sample data

The problem

Each campus applies the regulations its own way.

And families notice at re-enrolment time.

Different answers on each campus

One campus registrar's office accepts the request, another asks for an extra document. Students and families hear different answers for the same rule.

Deadlines that change every semester

The calendar, re-enrolment, scholarships and make-up exams change every semester, and last year's calendar is still going around the group chats.

Student data in any AI tool

Without an AI tool from the institution, people paste student data into personal tools, with no control and no record.

Before and after

What changes across the school network.

From the published regulation to the answer on WhatsApp.

Without the company's memoryThe new regulation arrives by email and each campus keeps its own versionWith KlucoThe current regulation is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryLast year's calendar is still in useWith KlucoWhen the review deadline passes, the article is flagged as overdue
Without the company's memoryThe registrar's office question becomes a call to the coordinator or head officeWith KlucoThe attendant asks in the team's channel and gets the answer with its source document
Without the company's memoryOn WhatsApp, each attendant answers families 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 memoryStudent data goes into personal AI toolsWith KlucoThe institution's own chat, with access profiles, an audit log and masking when turned on

What goes into memory

What an education institution keeps in memory.

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

  • Institutional bylaws and academic regulations
  • Academic calendar and semester deadlines
  • Registrar procedures: enrolment, documents and certificates
  • Re-enrolment, scholarship, discount and leave of absence policies
  • Rules for exams, make-up exams and grade reviews
  • Service scripts for students and families
  • Teacher and coordinator handbook
  • Internal system manuals

Use cases

Where education institutions start.

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

  • 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
  • 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
  • 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
  • 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
  • Personal data masked

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

    Agents
  • Model access by profile

    Each group of people uses the models, agents, skills and memory its profile allows.

    LLM Management and Chat

Brain · the memory

One set of regulations, every campus.

The Brain turns regulations, calendars and procedures into articles with an owner, a review deadline and a version history. When a rule changes, AI proposes the update and the responsible department approves it.

  • Human approval before publishing what AI writes
  • A queue of unanswered questions that become articles
  • Contradictions between documents become review suggestions
See the Brain
Product screen, with sample data

Agents · AI agents

Agents that answer students and families from the knowledge base.

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. An assistant answers the registrar's office and coordinators on Teams, Google Chat or Slack, with the source article.

  • Personal data masking, when turned on
  • Human approval for sensitive actions
  • Request triage with an owner, a deadline and a priority
See the Agents
Product screen, with sample data

LLM Management and Chat

AI for teachers and administrative teams, with control.

Teachers, coordinators, the registrar's office and finance use the models their profile allows, in the Chat, which draws on the institution's memory.

  • Access profiles per group of people
  • A limit per person and a budget per team
  • Use-case and adoption reports
See LLM Management
Product screen, with sample data

Control

What the institution controls.

The institution sets up each control below in the console.

See security and LGPD
  • An owner and a review deadline on every regulation, with a record of who verified it and when
  • A person's approval before publishing what AI writes
  • The documents each agent may query
  • Personal data masking in logs and answers, when turned on
  • Audit log for configuration and chat

FAQ

What education institutions ask.

Is Kluco a teaching tool for students?

No. It serves the institution's staff and its service channels: it organises regulations, procedures and policies and delivers that information to people and agents. Classes and assessment stay with the teachers.

Does Kluco integrate with the academic management system?

Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook. The platform does not replace the academic or finance systems: it organises what the institution knows and delivers it to people and agents.

Can agents serve students and families?

Yes, on what is in the knowledge base: deadlines, documents, the calendar, re-enrolment and scholarships. You set the rules for each agent, the actions that need approval and whether personal data is masked. What the agent does not know is handed over to a person.

How does Kluco handle student data, much of it about minors?

With access profiles, data isolated per company, an audit log and the option to mask personal data in each agent's logs and answers. The institution decides what each agent may query. The Security page details each control.

Next step

See the same regulations reaching every campus.

In the demo, we show the regulations knowledge base, an agent answering a family on WhatsApp and a registrar's office assistant in the team's channel.