Docs/Knowledge sources

AI assistant

Knowledge sources

Websites, Discord channels, files and notes the assistant can read.

What knowledge sources are#

The assistant only answers from what it can read: your knowledge sources and the solutions your staff approved. If the answer isn’t there, it hands the ticket to staff. Adding your rules, FAQ and guides is the quickest way to make it useful.

Manage sources in Discord with /sources manage (or the Knowledge sources step of /setup and /config). You need the Management tier.

Adding a source#

TypeWhat you give itNotes
WebsiteA link to a page, a docs site or a sitemap.xmlChoose “Just this page” or “Several pages of the site” (up to 50). For several pages, pick which ones with patterns: /wiki/** reads a whole section, /wiki/* one level, anything else one exact page, and a skip list leaves pages out. “Check which pages are read” previews the result. Read in the background; takes about a minute.
Discord channelA channel like #rules or #faqEach message becomes a document. Edits and deletions are picked up automatically. Setup suggests channels with names like rules, faq, info or store.
FilePDF, Markdown or textUp to 5 MB.
Written entryA title and some textFor facts that aren’t written down anywhere else. Markdown works; use ## headings for sections.

A page you added as its own source is never read again by a site source. So if your rules page is a Rules source, a Guide source for the rest of the wiki skips it, and nothing is indexed twice or under the wrong kind.

Long documents are split into sections by their headings, so the assistant can point at the exact part it used.

What the AI learned#

Under Knowledge in the dashboard, What the AI learned lists the answers it took from solved tickets (with what staff did, and a link to the ticket) and the staff notes and rewrites it reads before answering. Forget removes one: a forgotten answer is no longer searched and is not learned again from the same ticket.

Kinds of content#

Every source has a kind. It changes how much weight it gets and how carefully it is used:

KindHow it is used
Docs / guidesNormal knowledge, slightly preferred over old ticket answers.
FAQSame as docs.
RulesAuthoritative. Quoted word for word, ranked highest, and any answer that uses it goes to staff review.
Terms & policiesAuthoritative, same as rules.
Store & payment termsAuthoritative, same as rules.

Good to know

Learned solutions from closed or imported tickets are their own kind. They rank just below the sources above, so your official docs win when both match.

Limiting to categories#

Open a source to choose the categories it is used for, e.g. store terms only for Store & payments tickets. With no categories picked, the source is used everywhere.

Keeping it up to date#

  • Websites and Discord channels are re-read automatically once a day.
  • /sources resync re-reads every website and channel source right away.
  • When a rules, terms or payment page changes, the staff channel gets a short “what changed” summary, and the AI uses the new version from then on.
  • Files and written entries don’t change on their own; replace them to update.
  • /ai and /status list how many sources you have and which ones are failing.

Testing what the AI finds#

/sources test question: shows the top five pieces of knowledge the assistant would find for a question, with their source, kind and how well they match. Add category: (a category key) to search as if the ticket were in that category.

Nothing relevant? Add a source that answers it, or approve solutions from past tickets. Curious how matching works? See How the AI works.