Every organisation has the same quiet problem. The answers exist, somewhere, in a procedures manual, a circular from two years ago, a product sheet or a senior colleague’s head. New staff ask the same questions again and again, and experienced staff lose part of every day answering them. A knowledge assistant is an agent that reads your own documents and answers staff questions from them, with a reference to where the answer came from. Done well, it is one of the most useful internal tools you can build. Done badly, it becomes a confident source of wrong answers.
How it works, in plain terms
The assistant does not “learn” your manuals in the sense of memorising them. When a staff member asks a question, the system first searches your documents for the passages most likely to contain the answer. It then hands those passages to the model with an instruction: answer using only this text, and say which document and section you used. This approach is usually called retrieval.
Two things follow from this. First, the assistant can only be as good as the documents it searches. Second, you can check every answer, because every answer points back to a source. That second point is what makes it safe to use at work.
Getting the documents ready
This is most of the work, and most organisations underestimate it.
- Collect everything in one place. Operations manuals, HR policies, product guides, standard operating procedures, frequently asked questions from customer service, and official circulars.
- Remove the dead versions. If there are three versions of the leave policy, the assistant may quote the oldest one. Keep only the current version of each document, and give each a clear date.
- Break up the monsters. A single 300-page manual with no headings is hard to search. Clear section headings make a large difference to answer quality.
- Write down the unwritten. Some of the most asked questions have no document at all. Spend an afternoon with the people who answer questions most often and write their answers down. This is useful even if you never build the assistant.
- Decide who sees what. Salary scales and disciplinary procedures should not be searchable by every staff member. Set access by role before you load anything.
Rules that keep answers trustworthy
Write these into the assistant’s instructions and test them.
- Always cite the source. Every answer ends with the document name and section. Staff learn quickly to click through when it matters.
- Say “I could not find this” plainly. If the documents do not cover the question, the right answer is to say so and name who to ask. An assistant that fills gaps with general knowledge will tell a branch officer the wrong process with total confidence.
- Do not decide, only inform. “What is the approval limit for a branch manager?” is a fair question. “Can I approve this?” is a decision for the manager, and the assistant should say so.
- Answer in the language asked, where you can. Staff in Sri Lanka often think in Sinhala or Tamil even when the manuals are in English. Models can answer in those languages, but quality varies. Test it with real staff before you promise it.
Measuring whether it helps
Add a simple thumbs up or thumbs down to every answer, and log every question. After a few weeks you will learn three useful things.
- Which questions are asked most. These point to training gaps or confusing processes.
- Which questions got “I could not find this”. These are gaps in your documents, and each one is a small writing task.
- Which answers got a thumbs down. Usually the cause is an outdated or contradictory document, not the model.
For a rough sense of value, say a head office team of four people each spend an hour a day answering routine questions from branches. If the assistant handles half of those, that is around two hours a day returned to work that needs them. The real test is whether the senior people notice fewer interruptions after a month.
Where it falls short
A knowledge assistant is weak in a few predictable places. It struggles when the answer needs information from several documents that disagree with each other. It cannot answer questions about things that are not written down, and a surprising amount of how a business really runs is not. Tables and scanned pages are read less reliably than clean text. And it cannot tell you that a policy is out of date; it will quote whatever you gave it.
It is also not a replacement for training. New staff still need to understand why processes exist, not only what the steps are. Treat the assistant as a well-organised colleague who has read every manual, not as the person who designed them.
If you are considering one, start small: pick one department, gather its documents, clean them, and test the assistant with the twenty questions that department is asked most. If it answers those correctly and cites them properly, you have something worth widening. If it does not, the problem is almost always in the documents, and fixing them is worth doing anyway.