AddThisFeature

Knowledge Base Chat

Answer questions from the app's approved help articles and policies, with sources shown.

involved AI Analysis & Search

What it adds

A retrieval-backed answering surface over the app's published knowledge sources, restricted to what the asker is allowed to read.

What your agent is told to do

5
  1. 1

    Define which collections count as knowledge sources and mark each with an audience — public, customer, or internal. Filter the retrievable set by the asker's audience before retrieval, not after the answer is written.

  2. 2

    Restrict retrieval to currently published versions. Drafts, archived articles, and superseded revisions must be excluded from the corpus, not merely ranked lower.

  3. 3

    Cite every source used, and when two retrieved sources contradict each other, present both with their dates rather than picking one and hiding the conflict.

  4. 4

    Keep the answer inside the retrieved evidence. If retrieval returns nothing relevant, say the knowledge base does not cover it and offer the search results or a route to support.

  5. 5

    Re-index a source when it is published, edited, unpublished, or has its audience changed, using the app's existing background-job system, and drop any cached answer that cited it.

Edge cases it handles

8
  • An internal policy retrieved for a customer question is a disclosure incident. Audience filtering must run inside the retrieval query so no restricted passage ever reaches the model.
  • A draft rewrite of an article must never outrank the published version. If a source has no published revision, it is not in the corpus at all.
  • Contradictory sources are common when an old article was never retired. Show both with publication dates and say which is more recent rather than silently averaging them.
  • Answering beyond the retrieved evidence produces plausible policy that does not exist. Anything the retrieved passages do not support must be omitted, not softened with a hedge.
  • Edits must invalidate cached answers immediately. Serving yesterday's answer with today's citation is worse than having no cache, because the citation looks like verification.
  • Show the answer as assistance, not authority, and keep the underlying articles one click away so a user can check it.
  • When the model is unavailable, fall back to the existing keyword search over the same articles rather than showing an empty page.
  • Document Question Answering covers a single file uploaded by one user; this feature covers the app's shared published sources. Keep the two corpora and their permission models separate.

Definition of done

8
  • Retrieval is filtered by the asker's audience before any passage reaches the model.
  • Only currently published revisions are retrievable; drafts and archived material are excluded.
  • Every answer lists its sources, and conflicting sources are shown together with dates.
  • Questions unsupported by retrieved evidence return an explicit no-answer response.
  • Publishing, editing, or unpublishing a source re-indexes it and invalidates answers that cited it.
  • Keyword search over the same articles remains available when the model is unavailable.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.