What file types can we upload?

PDF, Word documents, Markdown, plain text, CSV and JSON. Each file is extracted, split into passages and indexed for retrieval.

Do we need a knowledge base before starting?

No. Existing conversations in the connected mailbox already provide useful context, and most teams start with a handful of documents and grow from there.

How do we know which source an answer used?

Each draft lists the sources behind it, so a reviewer can check the claim directly instead of re-researching the case.

Is our knowledge used to answer for other customers?

No. Knowledge belongs to the workspace that uploaded it, enforced at the database level, and is never used to answer for another company.

Knowledge base AI

Turn the documents you already have into answers your team can cite.

A knowledge base nobody searches is an archive. QlintAI reads your documentation and brings the relevant passage to the case, at the moment someone needs it.

Get started Book a demo

Most companies do not have a knowledge problem in the sense of missing knowledge. They have documentation, policies, product sheets, procedures and years of resolved conversations. What they lack is a way to reach the right paragraph while a customer is waiting.

QlintAI indexes the documents you upload — PDF, Word, Markdown, plain text, CSV and JSON — and splits them into passages that can be retrieved and cited. When a case arrives, the passages that bear on it appear next to the draft, with the document they came from.

You do not need to reorganise your knowledge base first. Start with the handful of documents your team links to most often, and add more as gaps show up in real cases.

Firmware update fails on gateway v3

Needs reply · today

Maria Lindqvist · Nordbygg Service · 09:14

“We updated three gateways yesterday and two of them stopped reporting. Do we need to roll back, and is the new firmware compatible with the older sensors we bought in 2023?”

Prepared reply · review before sending

Hi Maria, no rollback needed. Gateways stop reporting when the update completes before the sensor pairing refresh — a power cycle on each unit restores reporting within two minutes. Firmware 4.2 is compatible with the 2023 sensor range; only the discontinued S1 module needs the legacy channel.

Approve & sendEditNothing sends by itself.

Questions detected

Is a rollback required?
Is firmware 4.2 compatible with 2023 sensors?

Sources used

Firmware 4.2 release notes
Compatibility matrix (internal)
Case #4471 — same symptom, resolved

Confidence

High on the rollback answer. The S1 module exception is flagged for a human to confirm.

Illustration of the QlintAI case view. Example content, not a real customer.

Upload what exists today

No migration project and no rewriting. Upload the documents your team already relies on and QlintAI does the indexing.

Retrieval at the point of need

Knowledge is surfaced inside the case, attached to the answer that uses it, rather than waiting behind a search box.

Gaps become visible

When a question cannot be answered from your material, QlintAI says so. Over time that is a precise list of what your documentation is missing.

Boundaries you can rely on

Indexed knowledge belongs to your workspace and is used only to answer for your company.

Checklist

Starting a knowledge base from scratch.

Begin with the five documents your team links to most often
Add the answers you retype every week, written once, properly
Include policies with their exceptions — exceptions are where drafts go wrong
Keep version information in the document, so answers can cite it
Let real cases tell you what is missing, rather than planning it all up front
Review flagged gaps monthly and close the important ones

Questions

Answers before you ask us.

Upload five documents and see what changes.

The first prepared answers will tell you more about the state of your knowledge base than any audit.