KnowledgeAssist — internal knowledge search with citations
An assistant trained on your own handbook that answers in plain language — and cites the section it came from.
Your documents 5 sources
- All staffEmployee handbook
- MixedSOPs folder
- All staffInternal wiki
- Sales onlyPrice list
Step 1 · Ingest
- Handbookv4.2 ✓
- SOPs84 files ✓
- Wiki210 pages ✓
- Version trackedEvery source
Your documents, and only your documents. Each one keeps its version date so an answer can be traced to what was current.
Step 2 · Index
- All staffHandbook §4 — Leave
- HR onlyPayroll SOP
- ProcurementSupplier terms
Read permissions come across with the content, so a question only ever gets answers the person asking is already allowed to see.
Step 3 · Retrieve
- Handbook §4.2 — Sick leave0.91
- Handbook §4.5 — Proration0.78
- SOP-Onboarding-030.44 — not used
- Threshold0.60
It reads before it answers, and it will show you exactly what it read. Weak matches are discarded rather than padded into the answer.
Step 4 · Answer
How many paid sick days do new starters get in year one?
2:07 PMTen, prorated from the start date. Source: Employee Handbook §4.2.
2:07 PMके प्रयोग नगरेको बिदा अर्को वर्ष सर्छ?
2:08 PMतपाईंको ह्यान्डबुकमा यो कुरा लेखिएको छैन। मैले HR लाई पठाएँ — सुनिताले जवाफ दिनुहुनेछ। नीतिबारे म अनुमान गर्दिनँ.
2:08 PMThe second answer is the important one. Where your documents are silent, it says so and refers it on — rather than inventing a policy.
Step 5 · Improve
- HR14 questions with no source document
- Review3 answers marked unhelpful ✓
- SourcesHandbook v4.3 → live same day ✓
- OwnersEach gap assigned to a person
The questions it cannot answer are worth as much as the ones it can — they are a to-do list for your documentation.
KnowledgeAssist
An assistant trained on your own SOPs, policies and internal documents, answering in plain language — in English or your team's own language — instead of somebody hunting through folders or interrupting the one person who knows.
You have probably been the bottleneck: the same five policy questions reach the same person every week, and the answer has been written down for years in a document nobody can find. Answering is quicker than explaining where to look, so the loop never breaks. What changes: the questions get answered from the document itself, with the section cited — and the ones your documents do not cover finally become visible.
- Ingest
- Index
- Retrieve
- Answer
- Improve
-
Ingest
Your handbook, your SOP folder, the internal wiki, three thousand resolved tickets, the price list somebody updates every week. Each keeps its version date, so an answer can always be traced to the document that was current at the time.
-
Index
The step most demos skip. Every passage inherits the read permissions it already had, so payroll guidance stays with HR and supplier terms stay with procurement. An assistant that answers everything to everyone is not a feature, it is a data breach.
-
Retrieve
When a question arrives, the relevant passages are pulled and scored. Anything below the threshold is left out rather than padded in — a weak match is how a confident-sounding wrong answer gets built.
-
Answer
A plain answer with the section cited, in whichever language the question was asked. And when your documents genuinely do not cover it, it says so and passes the question to whoever owns that policy. Refusing to guess is the whole point.
-
Improve
Every question with no source document is logged. Over a month that becomes a ranked list of the gaps in your own documentation, assigned to owners — which is often worth more than the answering itself.
- Knowledge-source audit
- Assistant trained only on your own documents
- Permission-aware answers and multi-language support
- Confidence flagging plus a monthly content-gap report