A prospect asks about your refund window. Sayli answers from your refund policy, not from a guess. The Knowledge Base is how you teach Sayli what your team knows.
Teach Sayli what your team knows
Knowledge is org-scoped, so what you add gets reused everywhere. The live window, the brief, and Ask all draw from the same source.
There are two tiers. A Team library is shared across the org, so everyone benefits from the same facts. A My library stays private to you.
Three ways to add knowledge
Pick whatever fits the source you have.
Upload a PDF. Sayli reads it and adds it to the library you choose.
Context for one meeting
Sometimes a fact matters for a single call, not the whole org. You can attach context to one meeting and Sayli reads it before that call.
Attach a file, in .txt, .md, .pdf, or .docx, or point Sayli at an Obsidian note. It stays scoped to that meeting.
Where your knowledge shows up
When you add a document, Sayli splits it into passages and indexes them in a vector index. When you ask a question, Sayli pulls the most relevant passages and grounds the answer in them.
This is semantic retrieval. It matches on meaning, not keywords, so a question phrased one way still finds a passage phrased another.
Every answer in the live window, the brief, and Ask leans on the same library. Teach it once, and it shows up across all three.
Limits by plan
Knowledge Base storage scales with your plan. Viewers are read-only and cannot upload.