Different rules in each store
The new policy arrives by email or in the group chat, the old one is still on the notice board, and customers hear different answers in each store.
Memory for Retail
Exchange policies, store procedures and campaign rules become a reviewed knowledge base, with an owner and a review deadline. Sales associates, managers, franchisees and AI agents answer from the same version.
The problem
And the customer notices at the exchange counter.
The new policy arrives by email or in the group chat, the old one is still on the notice board, and customers hear different answers in each store.
Campaign rules, deadlines and conditions change with every seasonal date, and seasonal staff start without knowing where to look.
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 policy to the answer at the counter.
| Without the company's memory | With Kluco |
|---|---|
| Without the company's memoryThe new policy arrives in the group chat and each store keeps its own version | With KlucoThe current policy is in the knowledge base, with an owner and the date of its last verification |
| Without the company's memoryLast campaign's rule is still in use | With KlucoWhen the review deadline passes, the article is flagged as overdue |
| Without the company's memoryThe store's question becomes a call to the regional office or head office | With KlucoThe sales associate asks in the team's channel and gets the answer with its source document |
| Without the company's memoryEach channel answers customers differently | With KlucoAI agents and staff answer from the same knowledge base |
| Without the company's memoryExchange exceptions are approved by message, with no record | With KlucoA process with an agent step and the manager's approval, with a deadline and a record |
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 retail, 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.
BrainPeople ask in Slack, Teams or Google Chat and get the answer with the source article.
AgentsThe 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.
AgentsPeople who just joined ask the knowledge base instead of interrupting the team, and learn the company's way of working through skills.
BrainWhat the knowledge base could not answer goes into a queue. Someone answers it once, and the answer becomes an article for everyone.
BrainPaste the procedure the company already follows and AI proposes the flow, with agent steps and human approvals with a deadline.
AgentsBrain · the memory
The Brain turns policies, procedures and campaign rules 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.
Agents · AI agents
An assistant answers stores on WhatsApp, Teams, Google Chat or Slack, with the source article. Service agents answer customers with what is in the knowledge base and hand over to a person what they do not know.
LLM Management and Chat
Marketing, operations and store managers 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
Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and resolved service conversations can come in too. The platform does not replace the store's systems: it organises what the company knows and delivers it to people and agents.
The current policy 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.
New people ask the knowledge base in the team's channel or in the Chat, instead of interrupting the manager, and get the answer with the source article. What the knowledge base cannot answer goes into a queue, and the answer becomes an article for everyone.
Next step
In the demo, we show the policy knowledge base, an assistant answering a store in the team's channel and a customer service agent.