Memory for Operations

The written procedure, running as a process.

Kluco keeps operating procedures in a reviewed knowledge base, with an owner and a review deadline. From them, AI proposes processes with agent steps, rules and approvals by people, and every case leaves a record.

Product screen, with sample data

The problem

The procedure exists, but everyone does it their own way.

And requests travel by email until someone notices they have stopped.

A procedure in several versions

The official document says one thing, the team's spreadsheet says another, and whoever joined yesterday follows the one they found first.

Forgotten approvals

The request waits in someone's inbox, the deadline passes and nobody notices until the requesting area chases it.

Automation starts from scratch

Even with the procedure written down, automating it means describing every step again, and nobody knows where the process gets stuck.

Before and after

What changes in Operations.

From the written procedure to the completed case.

Without the company's memoryThe procedure exists in three versionsWith KlucoThe current procedure is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryDesigning the process starts from scratchWith KlucoYou paste the procedure and AI proposes the flow, saying what an agent can do and what stays with a person
Without the company's memoryThe approval is forgotten in someone's inboxWith KlucoThe approval has a deadline, and approved, rejected and deadline passed each have their own path
Without the company's memoryNobody knows where the request stoppedWith KlucoEvery case has a timeline, and the indicators mark the step that is the bottleneck
Without the company's memoryRequests arrive with no owner or priorityWith KlucoAn agent organises new requests with an owner, a deadline and a priority, and a person approves before saving

What goes into memory

How operations work, in one place.

Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and every article keeps its version history. A procedure stored in the knowledge base can be pasted straight into process mapping.

  • Operating procedures and work instructions
  • Rules for receiving goods and returning them to suppliers
  • Approval limits
  • Opening and closing checklists
  • Turnaround agreements between areas
  • Quality and safety rules
  • Onboarding guides for new people
  • Minutes of operations meetings

Use cases

Where Operations starts.

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

  • A procedure that becomes a process

    Paste the procedure the company already follows and AI proposes the flow, with agent steps and human approvals with a deadline.

    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
  • Request triage with approval

    An agent sorts new requests with an owner, a deadline and a priority, and a person approves before anything is saved.

    Agents
  • 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
  • AI proposes, a person approves

    When AI writes or updates an article, the change can wait for the approval of whoever owns the topic.

    Brain
  • 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

Agents · AI agents

The procedure the company already follows becomes a process.

Paste the procedure and AI proposes the flow, saying what an agent can do and what should stay with a person. The canvas takes agent, rule, AI text, notify and wait steps, and every case keeps its own timeline.

  • Approval with a deadline: approved, rejected and deadline passed
  • Cycle time and time per step, with the bottleneck marked
  • Start from another system (ERP, form, n8n) with a key
See the Agents
Product screen, with sample data

Brain · the memory

Procedures with an owner and a review deadline.

The Brain turns operating procedures into articles with an owner, a review deadline and a version history. New people ask the knowledge base instead of interrupting the team.

  • Article flagged when its review is overdue
  • Skills with the step by step of each task
  • AI proposes updates, with human approval if you want it
See the Brain
Product screen, with sample data

LLM Management and Chat

AI for the operations team, with limits and visible costs.

The team uses the models the company allows in the Chat, which draws on the procedures in memory. In LLM Management, you track limits and cost.

  • Company skills in the Chat's "/" menu
  • A limit per person and a budget per team
  • Cost in Brazilian reais, with the month's forecast
See LLM Management
Product screen, with sample data

Control

What Operations controls.

The company sets up each control below in the console.

See security and LGPD
  • Who can approve each step, and the deadline in days
  • A process that stays switched off until you choose the agents and the approvers
  • Per-tool rules and a monthly budget for each agent in the steps
  • A key for another system to open cases, with no duplicates
  • An owner and a review deadline on every procedure

FAQ

What Operations teams ask.

Do I have to design the process from scratch?

No. Paste the procedure the company already follows and AI proposes the steps, saying what an agent can do and what stays with a person, with the source passage of each one. You review, adjust on the canvas and only then switch the process on.

What happens if nobody approves in time?

Deadline passed has its own path on the canvas, just like approved and rejected. If it is not connected, rejecting and missing the deadline close the case. The decision shows up in the Approvals inbox and as a task for the approver.

Can our ERP open cases?

Yes. You generate a key, and the ERP, a form or n8n opens a case by calling the process address. Send the order number from the other system along with it: the same call repeated does not open two cases.

How do I know where the process gets stuck?

The indicators show the last 90 days of each process: cases, cycle time, how many went through a person and how approvals ended. The per-step table shows the average time of each step and marks the bottleneck.

Next step

See one of your procedures become a process.

In the demo, we show AI mapping, approval with a deadline and the timeline of a case.