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.
Memory for Logistics
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.
The problem
And the customer notices at delivery.
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.
Delivery times, redelivery, damage and returns: the service team answers the same questions all day, and each agent answers differently.
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
From the published procedure to the dock, the route and customer service.
| Without the company's memory | With Kluco |
|---|---|
| Without the company's memoryThe new procedure arrives in the group chat and each distribution centre keeps its own version | With 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 dock | With KlucoWhen the review deadline passes, the article is flagged as overdue |
| Without the company's memoryEach channel tells customers something different about the delivery policy | With 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 record | With 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 question | With KlucoNew people ask the knowledge base in the team's channel and get the answer with its source document |
What goes into 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.
Use cases
The most common use cases in logistics, with the part of the platform that does each one.
Branches, units and teams query the same version of each rule. When it changes, everyone answers from the new one.
BrainInternal rules and procedures live in one knowledge base, with an owner, a review deadline and a version history.
BrainThe 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.
AgentsPaste the procedure the company already follows and AI proposes the flow, with agent steps and human approvals with a deadline.
AgentsAn agent sorts new requests with an owner, a deadline and a priority, and a person approves before anything is saved.
AgentsPeople who just joined ask the knowledge base instead of interrupting the team, and learn the company's way of working through skills.
BrainBrain · the memory
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.
Agents · AI agents
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.
LLM Management and Chat
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.
Control
The company sets up each control below in the console.
FAQ
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.
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.
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.
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
In the demo, we show the procedure knowledge base, a service agent answering from the knowledge base and a damage process with human approval.