Teach Dri: the company knowledge base
For the administrator: upload documents so Dri can answer about delivery times, freight, payment and products, choosing the right type and source.
For: Administrator · SupplierUpdated on 2026-10-09
Where to find it
In your account menu, under Dri's knowledge, Documents tab.
The same entry opens the four tabs on the subject (Documents, Open questions, Conflicts and Quality) and stays highlighted while you are on any of them. Only organization administrators see this entry.
What the company knowledge base is
It is where Dri learns about your company. Everything she answers customers and sellers about delivery time, freight policy, payment conditions, branches or product specifications comes from here, and only from here. What is not in the base, she does not know, and her right answer in that case is to say she does not know.
The base belongs to the organization: a document applies to all its stores.
The base has no say on price, discount and stock: they come from the catalog, the price tables and the ERP. See How Dri answers with the company knowledge base: and what she does not do.
What is worth teaching first
The questions Dri gets most and cannot answer, without the base, are about the company, not about the product:
- delivery time: "what is the delivery time?", by region if it varies;
- default payment terms: "what are your payment terms?";
- service: hours, showroom address, how to reach someone;
- product care and specifications that are not in the registration: "is the decorative paper washable?", "can it go in the microwave?".
A short document with these answers already removes most of the "I don't know". The questions left unanswered appear in Dri's knowledge, on the Open questions tab, and are the best list of what to write next. See Dri's questions: what she could not answer.
How to upload a document for Dri
- Click Upload document, or drag the file onto the Documents list. A .md file with a header already brings title, type, origin and who can read it, and the window shows what it decided.
- In File, click Choose file. It accepts PDF, Word (.docx), spreadsheet (.xlsx), text (.csv, .txt, .md), HTML and image, up to 20 MB.
- In Title (optional), give a clear name; if empty, the first
#heading of a .md or .txt file is used and, without one, the file name. Dri uses the title to cite the source ("according to our delivery policy…"). - Choose the Type: Organizational, Sales policy, Technical sheet, Frequently asked questions or Other.
- Choose the Source: Collected (the default) or Curated.
- Click Upload. The screen says "Document received. It is in the queue — the list follows it."
What to send, how to write it and how to choose type and origin: see Which documents to send to Dri and how to write them.
Why the document Type matters
The type changes how the text is read and where Dri looks:
| Type | what the reading produces |
|---|---|
| Organizational | facts about the company: branches, departments, people in charge, deadlines |
| Sales policy | each rule becomes a fact with the condition and the exception made explicit |
| Technical sheet | "product X has attribute: value" |
| FAQ | the question helps find it, the answer becomes the fact |
| Other | generic reading |
Choosing wrong gives no error, and that is the problem: it produces facts with the wrong shape, which retrieve poorly. And an Other document stays out of searches for technical questions and commercial questions.
Collected or Curated
Collected is right for almost everything: a document that already existed, with useful information mixed with irrelevant. The reading is strict: when in doubt, the passage goes to Review.
Curated is a statement: "this was written for Dri". The reading is more permissive (when in doubt, it becomes a fact) and the document weighs more than a collected one when the two contradict each other: the curated one goes in, the other stays out, without anyone needing to decide.
Use it sparingly: if everything is curated, the weights become equal and no contradiction resolves by itself: they all go to Conflicts.
The document list
The table shows Document, Type, Source, State, Yield, Yield, Sent and Actions. On a phone, the same information comes in cards.
- State goes from In queue to In the knowledge base (or Review, or Failed). ⚠️ Review is not "ready": the document already answers with what passed, and there are passages parked awaiting a decision.
- Yield says how much of the document became knowledge and, by difference, how much was discarded.
- Yield shows how many facts and passages it generated.
States, errors and the details of each document: see After uploading: the processing and the details of a document.
Updating or removing a document from the base
- To update the content, upload the new version and delete the old one. Leaving both makes the base have two values for the same subject: a conflict.
- Reprocess (arrows icon in Actions) rereads the stored original file. It is for a document that failed, not for replacing the content.
- Delete (trash can icon) asks for confirmation and removes from the base right away the document, the facts and what is in the index. Dri stops answering with that immediately.
The full cycle of the knowledge base
The Documents tab is the first step of four:
- Documents: you teach.
- Open questions: what customers asked and she did not know. See Dri's questions: what she could not answer.
- Conflicts: two documents saying different things. See Knowledge base conflicts: when two documents disagree.
- Quality: whether it is paying off, and a place to test questions. See Knowledge base quality: test what Dri answers.
Uploading documents without ever opening the other three is feeding a base without knowing whether it is answering.