Memory for Logistics

Every distribution centre, every branch, the same procedure.

Receiving, dispatch, transport and delivery procedures become a reviewed knowledge base, with an owner and a review deadline. Checkers, drivers, service staff and AI agents query the same version.

Product screen, with sample data

The problem

Each distribution centre does it its own way.

And the customer notices at delivery.

One version in each site

The new procedure arrives by email or in the group chat, the old one is still printed at the dock, and each shift and each branch does it its own way.

The same questions all day

Delivery times, redelivery, damage and returns: the service team answers the same questions all day, and each agent answers differently.

AI without control

Each area tries a different AI tool, without knowing what leaves the organisation, what it costs or what information it answers from.

Before and after

What changes in the logistics operation.

From the published procedure to the dock, the route and customer service.

Without the company's memoryThe new procedure arrives in the group chat and each distribution centre keeps its own versionWith KlucoThe current procedure is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryThe old rule is still printed at the dockWith KlucoWhen the review deadline passes, the article is flagged as overdue
Without the company's memoryEach channel tells customers something different about the delivery policyWith KlucoAI agents and staff answer from the same knowledge base, and anything that depends on the order goes to a person
Without the company's memoryDamage, returns and redelivery are sorted out by message, with no recordWith KlucoA process with an agent step and human approval, with a deadline and a record
Without the company's memoryThe new driver calls the supervisor with every questionWith KlucoNew people ask the knowledge base in the team's channel and get the answer with its source document

What goes into memory

What a logistics operation 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.

  • Receiving and checking procedures
  • Storage, picking and dispatch procedures
  • Delivery policy, delivery times and redelivery
  • Handling of damage, lost goods and returns
  • Loading rules and cargo documentation
  • Safety rules in the warehouse and on the road
  • Onboarding scripts for drivers and operators
  • Internal system manuals

Use cases

Where logistics companies start.

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

  • 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
  • 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
  • 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 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
  • 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
  • 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 for every distribution centre.

The Brain turns warehouse, transport and delivery 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
  • 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 in customer service and in operational exceptions.

Service agents answer customers on WhatsApp and other channels about delivery times, the delivery policy and damage, with what is in the knowledge base, and hand over to a person what they do not know. Damage, returns and redelivery become processes, with an agent step and human approval within the deadline.

  • Human approval for sensitive actions
  • Approver notified on Slack, Google Chat, Telegram or WhatsApp
  • Request triage with an owner, a deadline and a priority
See the Agents
Product screen, with sample data

LLM Management and Chat

AI for head office and branches, with costs in Brazilian reais.

Operations, customer service and supervisors use the models their profile allows, in the Chat, which draws on the company's memory and can be installed as an app on computers and phones.

  • Access profiles per group of people
  • A budget per team, with its cost centre code
  • Use-case and adoption reports
See LLM Management
Product screen, with sample data

Control

What the operation 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
  • Human approvals, with a deadline, in process steps
  • The documents each agent may query
  • Personal data masking in logs and answers, when turned on
  • Audit log for configuration and chat

FAQ

What logistics companies ask.

Does Kluco track shipments or integrate with the TMS and WMS?

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. When a customer asks something that depends on the order's data, the agent hands the conversation over to a person.

How do I make sure every distribution centre and branch follows the same 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 customers?

Yes. Service agents answer on WhatsApp and other channels with what is in the knowledge base, hand over to a person what they do not know and ask for approval on sensitive actions.

Can drivers and operators ask the knowledge base away from a computer?

Yes. The assistant answers on WhatsApp, Telegram, Teams, Slack or Google Chat, and the Chat can be installed as an app on phones. New people ask the knowledge base instead of calling the supervisor.

Next step

See the same procedure reaching every distribution centre.

In the demo, we show the procedure knowledge base, a service agent answering from the knowledge base and a damage process with human approval.