home / use cases / knowledge and answers / company-knowledge-assistant

A colleague who has read every document

An Aivell indexes your manuals, contracts, price lists and memos into a knowledge base that lives on the box. Anyone on the team asks in the chat widget and gets an answer with the source document named. Indexing, search and answering all run onboard — your documents never leave the building.

Watch the demo

starts when: Someone on your team asks a question in the chat widget

The problem

Every company runs on one person who knows where everything is. Which price list is current, what the warranty actually says, where the certificate from 2019 went. When she is in a meeting, the question waits. When she leaves the company, the answers leave with her.

The documents exist — that’s the irony. Manuals, contracts, memos, spec sheets, all sitting on the share in folders nobody can navigate. McKinsey reckons around 45% of professional-services work is automatable with current technology, and a fat slice of it is exactly this: finding and repeating something that is already written down. Cloud tools that “chat with your documents” exist, but they start by asking you to upload the documents. For contracts and internal memos, that conversation ends quickly.

How your Aivell does it

  1. Your documents get indexed, onboard. Point the Aivell at the folders that matter. It reads every file — office documents, PDFs, scans, even photographed pages — and builds a knowledge base that lives on the box, behind your firewall.
  2. Anyone asks, in plain language. The chat widget sits on your intranet or your team’s start page. “What’s our warranty on refurbished units?” works better than any folder tree ever did.
  3. Answers come with receipts. Every answer names the document and section it came from, so a skeptical colleague can check in one click. A guardrail keeps the assistant inside your approved folder — it cannot answer from anywhere else.
  4. Conflicts get surfaced, not smoothed over. Two documents disagreeing is information. The chore says show both and tell Elena, so your documentation converges instead of drifting.
  5. The gaps become a list. Questions with no written answer are logged, and a Friday digest hands them to whoever owns the docs. The knowledge base gets better precisely where people actually look.

The chore is a page of plain language — what to answer, what to refuse, who to flag. Change the rules the way you’d re-brief a colleague, and the guardrails make sure the assistant physically cannot wander outside them.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · answer team questions ● active

answer questions from the chat widget, any hour, any day

search the knowledge base first — never answer from memory

always name the document and section the answer came from

if two documents disagree, show both and flag it to Elena

pricing questions use the current price list; older versions don't count

questions about clients or salaries are off-limits — point to Elena

no source found? say so plainly and log the question

every friday send Elena the week's unanswered questions

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Chat widget takes questions from the team
Knowledge Base finds and cites the right passage
Documents & Vision reads new files into the index
Email sends the weekly gaps digest

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Knowledge Base Answers may draw only on the approved company folder; documents outside it are invisible to the assistant.
Chat widget Serves your own network only — the widget is never exposed to the public internet.
Email The digest goes to one internal address; no other outbound mail from this chore.

Questions, answered.

What happens when two documents contradict each other? +

The chore covers it — show both passages, name both files, and flag the conflict to the person who owns the documentation. Contradictions get found and fixed instead of silently propagated.

Is this one of those tools that uploads our files somewhere? +

No. The documents are indexed on the box, the search runs on the box, the answer is written on the box. An Aivell can run air-gapped; a contract you index is exactly as private as a contract in your filing cabinet.

How do answers stay current when documents change? +

New and updated files are re-read and re-indexed as they arrive — drop them on the share or mail them in. The assistant always cites the version it used, so a stale answer names its stale source.

What does it do when the answer simply isn't written down? +

It says so — no improvising, that's a guardrail, not a hope. The question lands in a log, and the Friday digest turns your team's unanswered questions into a documentation to-do list.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee