Search internal documents
The assistant works on your document collection – the knowledge your business already has.
Knowledge Assistant: Ask questions of internal documents and get answers with sources.
Target group: businesses whose knowledge sits in documents and folders. The knowledge is there – but it is buried in folders. Anyone who needs an answer should be able to ask, instead of having to know which folder and which version it is in. This matters most for new employees who do not yet know the filing logic.
Use cases
Tasks the Knowledge Assistant is built for.
Answers with source references
Every answer points to the relevant passage in the document. If the assistant finds no supporting passage, it says so instead of guessing.
Ask in plain language
No guessing search terms: you ask the way you would ask a colleague.
Onboarding
New employees find answers without knowing the filing logic.
Process knowledge
How do we handle a complaint? What applies to variation orders? – answered from your documents.
Website chat
The same principle answers questions on your website – like the chat assistant on this site.
Function modules
What the product includes.
- Connection to your document collection
- Questions in natural language
- RAG: answers from your own documents with source references
- Roles and access rights
- Website chat as a variant
Interface
The views your team works with.
Sample Knowledge Assistant interfaces without client data.
Integrations
What the Knowledge Assistant connects to.
| System | Purpose |
|---|---|
| DMS / network drive | Document collection |
| SharePoint / Microsoft 365 | Documents and permissions |
| Website | Chat assistant |
| DocMan Agent | Organised filing as a source |
Operation & security
Operating models, roles, data protection.
| Topic | Description |
|---|---|
| Operating models | On your own servers, in a Swiss private cloud or mixed. You decide where the documents are stored and which models can see them. |
| Security / roles | Answers respect your existing roles and permissions; access to answers follows the permissions on the source documents. |
| Privacy policy | Your data stays in the operating model you choose. We decide together which models can see which data classes. |
Industries
Where the Knowledge Assistant is used.
Case studies
AI in practice, used by Swiss companies.
Our case studies page shows which companies already use our solutions.
Related
Related use cases, building blocks and Labs topics.
Frequently asked questions
Frequently asked questions about the Knowledge Assistant
Why do source references matter?
The assistant is designed to name the documents it used. This makes expert review easier, but it does not rule out incorrect answers.
Is there a live example?
Yes – the chat assistant on this website works on the same principle: it answers questions based on the website content. Try it out at the bottom right.
How does the Knowledge Assistant differ from the DocMan Agent?
The DocMan Agent takes care of filing and organising – structure, naming, versions. The Knowledge Assistant answers questions from the content. The two complement each other.
How do I get started?
With a free analysis: together, we look at what document knowledge you have and which clearly defined pilot would bring the greatest benefit.
Next step
Demo, conversation or pilot – you choose how to start.
We show you the Knowledge Assistant in a demo, discuss how it would work in your business or start a pilot with you as a pioneer partner.