What you can give it
The knowledge base is what the agent knows about your business: your policies, your FAQs, your manuals. It’s fed from several sources, and each one comes in its own way.
- DocumentsPDF, text, Markdown and HTML, up to 10 MB. If a file can’t be read or has no text, it tells you why instead of adding it empty.
- Your websiteA single page or the whole site. It crawls pages on the same domain, uses the sitemap when there is one, and you can limit it with a URL pattern to keep, for example, only the help section.
- NotionImport a page from your workspace through your own Notion connection. Empty pages aren’t saved.
- TextFor what isn’t written down anywhere: a new policy, an exception, an answer you want it to always give the same way.
How it gets prepared
When it comes in, each document is split into paragraph-sized chunks. Each chunk is stored twice: by meaning, to find “it arrived broken” when the document says “defective product,” and by its exact words, to find a reference number or a proper name.
If something fails while preparing a chunk, it isn’t lost: it’s stored anyway and can still be found by its words.
Each agent, with its own
Documents are assigned agent by agent. One brand’s support agent doesn’t answer with another brand’s manual, and an agent with no assigned documents doesn’t search any of them: it would rather say it doesn’t know.
When a document changes
When you import a source again, Qopper compares it section by section: what’s new, what was removed and what changed. And it flags changes that touch numbers as important: a deadline, a percentage, a price. Those are exactly the changes that, if they slip by, make the agent promise something that’s no longer true.
