Docs menu
Writing good knowledge documents
Which files you can add, the size limits, and how to write and structure documents and FAQ entries so the assistant finds the right answer and cites it. Test with the playground.
The assistant answers only from your knowledge. When it writes a draft, it searches your documents for the passages that fit the customer’s questions, writes the reply from those passages and cites them. If nothing fits, the draft says what is missing instead of making something up. Good documents therefore matter more than anything else for good drafts.
What you can add
Open Knowledge in the menu. There are three ways to add knowledge:
- Files: drop them on Drop files here or click to choose files. Supported: PDF, DOCX, TXT, Markdown, HTML, CSV and EML (a saved email).
- Paste text: a Title and the Text, for example a policy copied from your website.
- Add FAQ: one Question and its Answer, stored as a small document.
Each item gets a Status: Queued, Processing, then Ready. Only ready documents are used. Re-index processes a document again; Delete removes it and its passages.
Limits
| What | Limit |
|---|---|
| One file | 20 MB |
| A PDF | 2,000 pages |
| Reading one file | 60 seconds, then it fails with “Reading the file took too long.” |
| Documents per workspace | 200 |
| Knowledge storage per workspace | 500 MB |
| Pasted text or an FAQ answer | 1,000,000 characters |
| A title | 300 characters |
| An FAQ question | 2,000 characters |
Replies the assistant learned from your sent mail (Learned from replies) do not count toward the document and storage limits.
The same content can only be added once: a second copy gives “Already in your knowledge base.” with a link to the existing document.
Scanned PDFs (pictures of pages without a text layer) cannot be read: they fail with “No text found. Scanned images are not supported.” Run them through text recognition (OCR) first, or paste the text.
How documents are split
Every document is cut into passages of roughly 2,000 characters (about 500 tokens), with a small overlap between neighbours. A heading starts a new passage, and passages never end in the middle of a sentence. When a draft is written, at most two passages per document and at most eight in total are given to the AI.
That has a few consequences for how you write.
Tips for documents that work
One topic per section, with a clear heading. “Returns”, “Delivery times”, “Warranty”. A heading starts a new passage, so the passage about returns does not get mixed with the one about payment.
Write the answer in full sentences, with the facts in the sentence. “You can return an item within 30 days of delivery.” is found and quoted well. A table cell with only “30” is not.
Repeat the subject. A passage is read on its own, without the rest of the page. “The warranty on e-bikes is two years” works; “It is two years” does not.
Use the words your customers use. If customers say “send back”, mention “send back” next to “return”. Search looks at both meaning and exact words.
Keep it current and in one place. Two documents with different opening hours give contradicting drafts. Delete or update the old one, and re-index after a change to a file.
Leave out what should not be in a reply. Internal notes, margins and staff names in a document can end up in a draft.
Any language is fine. Search works across languages, but it works best when the documents are in the language your customers write in.
Prefer text files for text. A clean DOCX, Markdown or HTML page gives cleaner passages than a PDF with columns, headers and footers.
FAQ entries
FAQ entries are the most precise knowledge you can add: one question, one answer.
- Write the question the way a customer would ask it: “Can I pick up my order in the shop?”
- Make the answer complete on its own, including conditions and exceptions: “Yes. Orders placed before 14:00 are ready for pickup the next working day at our shop. Bring your order number.”
- One question per entry. For a second question, add a second entry.
- When a draft shows Missing info, that is often a good new FAQ entry.
Test with the playground
Open Playground, type a question a customer might ask and click Ask.
- The Answer shows Sources: chips with the document title. Click one to see the Quoted passage and open the document.
- “Not found in your knowledge base” means no passage matched well enough. The answer lists the Missing information. Add a document or FAQ entry and ask again.
- “Nothing relevant was found, so no AI call was made (no cost).” means the search found nothing at all, so no tokens were used.
Try a handful of real questions from your inbox, including ones you know are not covered: the right answer to those is “not found”. Then check a document’s passages under its Chunks (click its title) if an answer quotes the wrong part.
Learning from your replies
Under Settings → AI behaviour, Learn from sent replies saves replies you sent with few changes (or rated 👍) as a Past reply. Email addresses, phone numbers, IBANs and postcodes are replaced before saving. They appear under Knowledge → Learned from replies, where you can view and delete them. Past replies rank below your official documents: when they disagree, the document wins.
Something unclear or missing in the docs?Tell us.