Skip to content

Knowledge base

Keep the wiki. Add the answer.

Your wiki and search stay. A question lands on the exact line, with why it matched.

01

Ten files is not an answer.

A wiki can store pages. It does not tell you which line you meant.

Rules without reasons

Pages fill with rules nobody can explain when you ask why they exist.

Search stops early

Search hands you ten files and leaves the reading to you.

Two pages, two truths

Refunds take 14 days on one page and 30 on three others, and nobody is shown both.

Before

You get a list of policy pages. You open each one. You guess which line still applies.

After

You get one answer, the exact lines, every source, and both sides of a conflict.

02

The loop for this team.

Keep the wiki. Bring pages in. Ask by intent. Show conflicts. Write missing answers back.

Wiki stays

Your wiki and search stay. Confluence imports as a copy with a link back.

Arrival is enough

When content arrives it is read, summarised, connected, and checked. Nobody tags or files anything.

One hop

The reading is done before anyone asks, so the question lands on the answer in one hop.

The loop
  1. Keep the wiki
  2. Import or clip
  3. Ask by intent
  4. See the line, and any conflict
  5. Write missing answers back

03

Answers by intent.

The question is matched to what you decided and meant, not only to the words on a page.

Exact line and why

Every result shows the exact line, its source, why it matched, and what it connects to.

Many sources, one answer

When several pages say the same thing, you get one answer with all of them cited.

The whole story

When the story is split, Cluesora follows connections it has already mapped.

04

Conflicts and dated history.

Disagreements stay visible. You can see what a page said on a date and who changed it.

Both sides shown

One page says 14 days, three others say 30. You see both, and where each came from.

Versions kept

New versions take over. Old ones are kept and dated, never deleted.

Sources stay original

Sources are never rewritten. Every answer traces to its origin.

Refund window · illustrative example

14 days

  • Refund policy (2023)

30 days

  • Support handbook
  • Billing FAQ
  • Customer terms

05

Holes get written back.

At a dead end, Teammate asks the person who knows and keeps the answer.

Notice the hole

Cluesora notices where the answer should have been.

Ask the owner

The question goes to the best-matched expert, then to the manager if needed.

Next search works

The kept answer is the source the next question lands on.

06

What this team uses.

Corpus is the map. The wiki stays the wiki.

Corpus

One map for uploads, clips, imports, agent writes, and Teammate answers.

Chrome clipper

Save only the page you choose. Saving again updates it.

Teammate

Ask in the app, Slack, or Teams, with sources on every answer.

AI agents

Agents search first, then save what they settle into the existing page.

07

What to measure.

Whether the knowledge base answers, and whether it stays honest.

One hop or ten files

Whether a question lands on the line, or still dumps a pile of pages.

Conflicts unhidden

Whether disagreements are shown instead of blended.

Holes closed once

Whether a missing answer is asked once and then kept.

History open

Whether you can open what a page said on a date, and who changed it.

Questions people ask.

Do we have to leave our wiki?

No. Your wiki and search stay. Confluence imports as a copy with a link back.

Do we have to tag pages?

No. When content arrives it is read, summarised, connected, and checked.

What if two pages disagree?

You see both sides and where each came from. Nothing is blended into one wrong answer.

Can we see an old version of a procedure?

Yes. New versions take over. Old ones are kept and dated, never deleted.

Agents that keep the page.

Engineering teams and their agents search first, then extend the doc that already exists.