Knowledge assistant with LangChain & Milvus The answer is in the manual. Page 214. Somewhere.

Support, sales and engineering search PDFs, wikis and data sheets every day. We build knowledge assistants that answer only from approved documents, show the source and say when something is not in there.

Discuss a use case
Example

Is the VX-200 valve approved for chlorine at 60 °C?

Yes, up to 70 °C, but only with an EPDM seal.Source: VX-200 data sheet, rev. 3, table 2

And for ozone?

The approved documents say nothing about that. Shall I pass the question to engineering?

The problem

An answer should not take half an hour.

Today

  • Jumping between PDFs, wiki and data sheets.
  • Ctrl+F in the wrong document. Again.
  • Waiting until the one person who knows has time.
  • Piecing fragments together and hoping they are current.

With a knowledge assistant

  • Ask in plain language.
  • Get a short answer with a source.
  • Open the source directly and check it yourself.
  • Know clearly when the answer is not in the documents.

Your company knowledge is under lock and key? We find the key.

Manuals, data sheets and policies become searchable, and every answer shows where it was found.

Discuss a use case
Small locked treasure chest

How it works

Three steps to answers with sources.

  1. Connect sources

    PDF, Word, Excel, Confluence, SharePoint or Drive. Links to the original passage are kept, and so are access rights.

  2. Make it searchable

    Semantic search for meaning, keyword search for part numbers and exact clauses. Milvus holds the vectors, LangChain runs the flow.

  3. Ask and check

    Read the answer, open the source. If nothing is found, the assistant says so instead of guessing.

Where it helps

Wherever the answer is buried in documents.

  • Customer support

    Product, warranty and policy questions without switching between colleagues and folders. For example: “Does the warranty cover outdoor use?”

  • Engineering

    Specifications, procedures and compatibility. For example: “Which seal kit fits the X700 pump series, rev. B?”

  • Compliance

    Clauses, certificates and retention periods, with the source. For example: “How long do we keep customer data according to policy?”

  • Sales

    Terms, pricing rules and features for quotes. For example: “Which volume discounts apply to framework contracts?”

Common questions

What teams want to know beforehand.

Which documents work?
PDF, Word, Excel, PowerPoint, HTML, Markdown and text. Plus connections to Confluence, SharePoint and Google Drive.
How do you prevent wrong answers?
Answers come only from passages that were found and name the source. If the information is missing, the system says so. Before launch we test with real questions from your team.
What happens when documents change?
New and changed documents are read in again regularly. How often is set per source.
Where does our data live?
With you, in a private cloud or operated by us, depending on your requirements. Your documents serve only as a source for answers, not for training models.
Does it work across languages?
Yes. A question in German can be answered from an English data sheet, with a reference to the original passage.

Bring ten real questions. And the documents that go with them.

Discuss a use case