Memory for Energy and Utilities

Every region, every field crew, the same procedure.

Operating, maintenance and safety procedures and customer service policies become a reviewed knowledge base, with an owner and a review deadline. Technicians, service agents and AI agents query the same version.

Product screen, with sample data

The problem

Each region learned the procedure its own way.

And a change does not reach every field crew at the same time.

One version in each region

The revised procedure sits in a folder, the field crew follows the version it got in training, and each region does it its own way.

New people depend on those who already know

The new technician learns from the most experienced colleague, and the supervisor stops what they are doing to answer questions that are already covered by some procedure.

A different answer on each channel

The policy for a duplicate bill or a new connection changes, the phone team already knows, and WhatsApp still answers by the old rule.

Before and after

What changes in operations and customer service.

From the published procedure to the field crew and the customer.

Without the company's memoryThe revised procedure sits in a folder and each region 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 keeps circulating among field crewsWith KlucoWhen the review deadline passes, the article is flagged as overdue
Without the company's memoryThe new technician calls the supervisor with questionsWith KlucoNew people ask the knowledge base and get the answer with its source document
Without the company's memoryEach service channel answers customers its own wayWith KlucoAgents and service staff answer from the same knowledge base, and the agent hands over to a person whatever it does not know
Without the company's memoryThere is no record of who changed whatWith KlucoAudit log for configuration and the Chat, with CSV export

What goes into memory

What an energy or utilities company 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.

  • Operating procedures per site and region
  • Preventive and corrective maintenance routines
  • Safety rules and the internal NR-10 procedures
  • Equipment lockout, isolation and release procedures
  • Customer service policies: duplicate bills, new connections and reconnection
  • Scripts for scheduled and unscheduled interruptions
  • Onboarding material for field crews
  • Equipment and internal system manuals

Use cases

Where energy and utilities companies start.

The most common use cases at power distributors and generators, water and sanitation companies and gas distributors, 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
  • 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
  • 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
  • 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

Brain · the memory

One procedure for every region and field crew.

The Brain turns operating, maintenance and safety procedures into articles with an owner, a review deadline and a version history. When something changes, AI proposes the update and the responsible department approves it.

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

Agents · AI agents

Agents that serve customers from the current version.

Customer service agents answer on WhatsApp and other channels about duplicate bills, interruptions and connection requests with what is in the knowledge base, and hand over to a person anything that depends on account data. In processes, agents do steps and people approve within the deadline.

  • Human approval for sensitive actions
  • Approver alerts in Slack, Google Chat, Telegram or WhatsApp
  • The history of every run, step by step
See the Agents
Product screen, with sample data

LLM Management and Chat

AI for engineering, operations and the office, with a record and costs in Brazilian reais.

Engineers, analysts and supervisors use the models their profile allows in the Chat, with the company's memory. Every change to access, limits and keys goes into the audit log.

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

Control

What the company controls.

The company 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 internal assistants only
  • Human approvals, with a deadline, in process steps
  • Audit log for configuration and the Chat, with CSV export, and the history of every agent run

FAQ

What energy and utilities companies ask.

Does Kluco read meters, the operations system or billing?

No. It organises procedures, policies and rules and delivers that information to people and agents. Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook.

Does the customer service agent answer about a customer's account?

It answers with the policies and procedures in the knowledge base, such as the rules for a duplicate bill or the documents needed to request a new connection. Anything that depends on account data, it hands over to a person.

Can safety procedures, such as NR-10 ones, go into the knowledge base?

Yes. The company's safety procedures, including its NR-10 procedures, sit in the knowledge base with an owner and a review deadline. Kluco organises and delivers those procedures, and complying with the rules remains the company's responsibility.

Can field crews ask the knowledge base from their phones?

Yes. The assistant answers in Teams, Slack, Google Chat, Telegram or WhatsApp, and the Chat can be installed as an app on the phone.

Next step

See the same procedure reaching every region.

In the demo, we show the procedure knowledge base, a customer service agent that answers from the current version and the audit log.