Knowledge Base
Set up the knowledge base so your bot answers tickets from your own documentation and learns from your staff
The knowledge base connects your documentation, Discord channels, uploaded files (text, Markdown, or Word), and GitHub repositories to your bot. When a customer asks a question in a ticket, the bot answers from that content, shows where the answer came from, and hands the ticket to staff when it does not know. It also learns new answers from tickets your staff close. This page is for the admin setting it up for the first time.
The knowledge base is available on Pro (2 sources) and Enterprise (15 sources). GitHub repository sources are Enterprise only. Turning the AI answers on and off is a dashboard setting; there is no slash command for it. Upgrade your plan
How it works
- Add sources: web pages, Discord channels, uploaded files, or GitHub repositories.
- The bot reads them: each source is read when you add it and again on the schedule you choose.
- The bot answers: when a member asks a question in a ticket, the bot waits a few seconds for follow-ups, searches your sources, and posts an answer with a source line (unless Show sources is off).
- Staff stay in control: the bot never talks over staff, and when it has no answer it offers a Talk to Staff button that hands the ticket to your team.
- The bot learns: when a ticket closes, the staff answers in it become question-and-answer entries. Depending on your Learning choice they go live at once or wait in Staff Q&A for your approval.
Getting started
The settings are on the AI assistant page. Its What Atlas does tab turns answers on; its Help content tab holds your sources, About your server, and Learning; its Test tab shows what Atlas would answer before members see it; its Staff Q&A tab lists the entries to review; its Stats tab shows how answers do.
Turn on Atlas and answers
Go to AI assistant → Atlas → Answer questions in tickets. Switch on the Atlas card at the top of the page and the Answer questions in tickets card, then click Save changes in the bar at the bottom of the page.
Add your first source
Go to AI assistant → Atlas → Sources. In the Add a source card, choose Web page, Discord channel, File, or GitHub repository, fill in the fields, click Add source, and then Save changes (a file is saved as soon as you add it). The first read starts by itself. Wait until the source shows Ready under Your sources.
Describe your community
Fill in AI assistant → Atlas → About your server: your community name and what you support, and under Topics, links and product names your product names and any topics the bot must leave to staff. This is what stops the bot answering questions that are not yours to answer.
Test it
Go to AI assistant → Atlas → Test Atlas and ask a question that your documentation answers. You see what Atlas would reply, with its sources, and nothing is posted in Discord; this works before answers are on. See Test Atlas. Then open a test ticket and ask again: within about 10 seconds the bot posts an answer, with 👍 and 👎 buttons under it while Let members rate answers is on.
Manage sources, entries, and settings from an AI tool instead of the dashboard.
Where answers come from
The bot answers from two kinds of knowledge, and searches both for every question:
- Sources: content it reads directly. Add them on the Sources card:
- Web Page: a page, or a page plus the pages it links to.
- Discord Channel: messages from a channel the bot can see.
- GitHub Repository (Enterprise): Markdown files from a repository.
- File: a
.txt,.md, or.docxdocument you upload. Its text is searchable, and AI also turns it into Q&A entries.
- Q&A entries: single questions with their answers, listed under Staff Q&A:
- entries you write with Add an answer;
- entries AI made from your files;
- entries learned from closed tickets;
- entries learned from solved threads in public help channels;
- entries merged when Atlas tidies up learned answers.
With Search past Discord conversations on (on the Where else Atlas may look card), the bot can also use answers already given in your server's public channels. See Settings & Customization.
See Adding Sources and Q&A Entries for the details of each.
Source types
| Type | What it reads | Limits |
|---|---|---|
| Web page | One page, or a page plus the pages it links to (set How many pages to read) | Up to 100 pages per source on Pro, 500 on Enterprise. HTTPS only. |
| Discord channel | Messages from a text channel the bot can see | The newest 20 messages on Pro, 100 on Enterprise; new messages replace the oldest. Very short messages are skipped. Include bot messages is off by default. |
| File | A .txt, .md, or .docx file you upload. Only its text is sent, and AI turns it into Q&A entries | At most 50,000 characters (256 KB) of text; Word files up to 10 MB. Only the bot owner can add or remove files. Files cannot be edited after upload; remove and re-add to replace. |
| GitHub repository (Enterprise) | Markdown files from a connected repository, optionally limited to a branch and folder | Connect GitHub first from AI assistant → Atlas → Sources. Re-syncs automatically on each push to the chosen branch. |
Use specific pages such as pricing, guides, or an FAQ instead of a broad landing page. Focused pages give cleaner answers. A file needs no special format: AI reads it in any layout and adds the questions it answers to Staff Q&A.
Full details for each type, refresh schedules, and source statuses are on Adding Sources.
Worked example: a game server
A community running a survival game server wants the bot to answer the same questions it gets every day.
- AI assistant → Atlas → Sources: add the server's rules page as a Web page with How many pages to read set to Just this page, add the
#faqchannel as a Discord channel, and upload the server's FAQ document as a File, which becomes Q&A entries such as "How do I join?" and "How do refunds work?". - About your server: Name
Ember Survival, What your team helps withWe help with joining the server, ranks, store purchases, and in-game bugs, and under Topics, links and product names, Product namesEmber Survival,VIP rank,Legend rankand Topics to leave to staffban appeals,staff applications. - Instructions for Atlas:
Be friendly and brief. Always give the server IP as play.example.com. For purchase problems, ask for the order number before anything else. - Answer questions in tickets: leave When staff are around on Right away. The bot still steps back whenever a moderator is already replying.
- Learning: choose Ask me first (the default for a new knowledge base is Add automatically) for the first weeks, so a moderator approves each new answer in Staff Q&A. Once the answers look right, switch to Add automatically, and after a moderator has explained how rank transfers work in a ticket, the bot answers the next person itself.
After a week, open the Stats tab to see which sources get 👍 votes, and Staff Q&A to approve the entries waiting for review.
What the customer sees
An answer is a normal message from the bot in the ticket, replying to the customer's question:
- The answer text, at the Reply length you chose (Short, Balanced, or Detailed).
- A line
Source: <source title>. - A small grey footer:
Generated by AI. Staff can verify important details.This notice is always shown and cannot be turned off. - 👍 and 👎 buttons when Let members rate answers is on (on AI assistant → Atlas → Learning). 👎 asks for a reason and what could be improved; staff can also type the correct answer.
When the bot has nothing relevant, or the request is something only your team can do (an account change, a topic under Topics to leave to staff, or a member asking for a person), it says I don't have enough knowledge base information to answer that. Use the button below to request staff help. with a 🙋 Talk to Staff button, and keeps answering the customer's next questions. The same message and button appear when a temporary problem stops Atlas from finishing an answer. This hand-over is always on. A message that needs no answer, such as thanks or "any update?", gets no reply.
Members can attach screenshots, and the bot reads them with the message:
- A screenshot of an error, a log, or a settings screen is answered even when the member writes nothing with it.
- An image with nothing to help with gets no reply, like thanks: a meme, a photo, a payment receipt sent as proof with no question, or a screenshot showing that something works now.
- When an answer says what a screenshot shows (an error code, a message, a value, whether a setting is on), that is checked against the screenshot before the answer is sent. An answer that misreads it is rewritten, and if it still does not match, the member gets the Talk to Staff reply instead.
Pressing the button posts a Staff Assistance Requested card and confirms A staff member has been notified and will be with you shortly! Only the ticket creator or staff can press it, and after one is posted, unanswered questions in the next 5 minutes do not post another.
In ModMail the message and button arrive in the customer's DM, and staff see a 🙋 Talk to Staff Offered card in the ticket channel.
Follow-ups to an answer are understood in context: tldr, show that in markdown, or send me the link after an answer are matched to the question it answered, not searched on their own words.
When the bot's own answer says staff should take over, it posts a 🤖 AI Escalation card in the ticket with the customer's question under User Question. With Ping staff roles on hand-over on, the card mentions your staff roles (or the button's own ping role when one is configured).
After a hand-over (the button, a request for a person, or the bot handing over) the bot stays quiet in that ticket for the time set in When Atlas can't help (7 days by default; Stay out for the rest of the ticket keeps it out for good).
When Ask for details when a member only says hello is on, a greeting-only message that feature will reply to (the first message from the member who opened the ticket, once per ticket) is left to it, and the knowledge base does not answer it. If the member already wrote what they need and nobody has replied, a greeting counts as a nudge: the knowledge base answers the earlier message.
Learning from closed tickets
Learning runs with no command. Choose how it works on AI assistant → Atlas → Learning, under New answers from solved tickets:
| Choice | What happens |
|---|---|
| Off | Atlas does not learn from solved tickets |
| Ask me first | Each new answer waits in Staff Q&A until you approve it |
| Add automatically (default for a new knowledge base) | New answers Atlas is sure about are added right away and posted in the alerts channel; the rest wait for review |
- A ticket closes (by staff, by inactivity auto-close, or because the user left). Tickets with fewer than 3 messages are skipped, and so are tickets Atlas is kept away from.
- The bot extracts question-and-answer pairs where staff gave the answer, redacts personal data, and scores each pair.
- With Add automatically, pairs Atlas is sure about go live at once and are searchable in the next ticket. An Auto-Learned from Ticket #123 card lands in the AI alerts channel showing the confidence, category, question, and answer, with an Undo button that removes the entry (turn off Post each new answer in the alerts channel on the Learning card to skip these cards). At most 50 answers a day go live this way; the rest wait for review.
- Pairs that wait (every pair with Ask me first) show in Staff Q&A as Waiting. A Pending Review card for the ticket with Approve, Edit, and Reject buttons is posted to the AI alerts channel so staff can act from Discord.
- A new pair that overlaps an existing entry is treated as a duplicate, an enrichment (a new detail added to the existing answer), or a supersession (a newer fact replaces the old one) instead of becoming a near-duplicate. With Add automatically, enrichments and corrections are applied only to entries the system learned itself and nobody edited, and post a KB Entry Updated or KB Entry Superseded card with Undo. Everything else, and every update with Ask me first, waits in Staff Q&A marked Suggested update.
- While Tidy up answers regularly is on (the default), Atlas tidies up the answers it learned as often as How often says (monthly by default): it merges duplicate entries into one and archives stale unused ones, then posts a Knowledge Base Consolidated summary.
The AI alerts channel is set under General → Where the bot posts; without one, cards go to your logs channel.
Reviewing what was learned
Go to AI assistant → Atlas → Staff Q&A. The Staff Q&A tab shows the list, and a count on the tab says how many answers are waiting.
- Filter by All, Waiting, Approved, Approved by Atlas, or Ignored, search, and use Approve or Ignore on each waiting entry; Edit and approve, Edit, and Delete are in the entry's ⋯ menu.
- Add an answer adds a hand-written entry that is available immediately. Entries created from an uploaded file show the file's name.
- Delete all waiting answers, in the ⋯ menu next to Add an answer, deletes every waiting entry at once and cannot be undone.
- Deleting an approved entry also removes it from search.
Everything about entries is on Q&A Entries.
Limits by plan
| Pro | Enterprise | |
|---|---|---|
| Sources per server | 2 | 15 |
| Pages per web source | 100 | 500 |
| Discord messages per channel source | 20 newest | 100 newest |
| GitHub repository sources | No | Yes |
| AI tokens per month | 10M | 30M |
| Read a source again by hand | Once every 8 hours | Once every 8 hours |
Answers cost tokens from the bot owner's monthly allowance, billed at 1.15 tokens per token used (AI model and tokens). Detailed replies use more tokens per answer. See AI usage for real consumption.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The bot never answers | Answer questions in tickets or the Atlas switch is off, or no source is Ready | Turn both switches on, save, and wait for at least one source to finish reading |
| The bot answers some people but not the ticket creator | The creator is on Keep Atlas away from, the ticket came from a panel button with Mute AI replies on, or the creator reached their Limit per member | Check AI assistant → Atlas → Keep Atlas away from and the panel button, or reset their usage on AI assistant → Atlas → Limit per member |
| The bot stops answering once a staff member types | Atlas always steps back while staff replied in the last 5 minutes or are typing; with Stay quiet once staff reply on it stops for good | Expected. Turn off Stay quiet once staff reply if you want the bot to come back once staff go quiet |
| Answers say "I don't have enough knowledge base information" for questions your docs cover | The relevant page was not read (see How many pages to read), or the source is not Ready | Check the source's page or message count under Your sources, and add a page that covers the question |
| A learned entry is wrong | The staff answer in the closed ticket was wrong or incomplete | Press Undo on the card in the alerts channel, or Edit or Delete it in Staff Q&A. Choose Ask me first to approve every new answer |
| No Auto-Learned or Pending Review cards appear | Neither an AI alerts channel nor a logs channel is set, or the bot cannot post there | Choose a channel under General → Where the bot posts; entries still appear in Staff Q&A |
| Voting or feedback fails with TC018 | Voting is unavailable for that message (for example the feature was turned off after the answer was posted) | See TC018 |
Common questions
How long does the bot wait before answering? About 10 seconds after the member's last message, so that a question typed across several messages is answered once. You can change it to 5 or 20 seconds with How quickly Atlas answers. With When staff are around set to Staff first, it waits 45 seconds first so staff can answer.
Can I stop the bot answering during working hours? Yes, on Enterprise: set When staff are around to Outside hours on AI assistant → Atlas → Answer questions in tickets and turn on business hours under General → Business hours. On other plans use Staff first, which holds the answer for 45 seconds and drops it when a staff member replies.
Does the bot learn from every closed ticket? Only when Learning is not Off, the ticket has at least 3 messages, staff answered in it, and Atlas is not kept away from the ticket. Personal data is redacted. With Ask me first every new answer waits for your approval; with Add automatically confident answers go live, at most 50 a day.
How do I teach the bot something it got wrong? Open Staff Q&A, find the entry the answer came from and Edit it, or add the right answer with Add an answer. It is searchable immediately. If the answer came from a source, fix the page, channel, or file and read it again or re-add it.
Can the bot answer general questions that are not in my docs? Yes, unless you turn off Answer general tech questions on AI assistant → Atlas → Where else Atlas may look. It is on by default.
Atlas uses general tech knowledge such as browser, operating system, or networking basics: to fill gaps your docs leave (your docs say to turn on automatic time, and it gives the Windows steps), and to answer generic technical questions your docs do not cover.
A reply that comes only from general knowledge carries the note General AI knowledge, not from this server's knowledge base before the usual Generated by AI notice. Anything about your product, such as its features, prices, limits, or policies, still comes only from your docs, and billing, account, security, and legal topics still go to staff.
Why did the bot close a ticket by itself? Close the ticket when the member says it's solved was on and the customer clearly asked to close the ticket. Turn it off if you want staff to close every ticket.
Can I keep the AI away from one user? Yes. Add them to AI assistant → Atlas → Keep Atlas away from. Atlas then does nothing in their tickets, and staff see and answer them as normal.
Train Atlas on your knowledge base, the short version
Join our Discord server for support
Was this page helpful?
Last updated on