Settings & Customization
Every setting for knowledge base answers: Answer questions in tickets, About your server, Where else Atlas may look, and what Atlas does alone
These settings decide what the bot knows about your community, when it answers in a ticket, how long its answers are, and when it leaves a ticket to staff. They live on two tabs of the AI assistant page: the Answer questions in tickets card on What Atlas does, and the About your server and Where else Atlas may look cards on Help content.
This page lists every setting with its choices and default, and explains what Atlas does by itself, so you can set it up without guessing.
The knowledge base needs a Pro or Enterprise plan on the bot owner's account. Both the Atlas switch at the top of the page and the switch on AI assistant → Atlas → Answer questions in tickets must be on before the bot answers.
Change the settings, then click Save changes in the bar at the bottom of the page to apply them; unsaved changes are lost when you leave the page. You can keep editing while a save is in progress: changes made after you click Save changes stay in the bar until you save again.
About your server
This card, on the Help content tab, tells the bot who it works for. Atlas uses it in every answer. Fill it in first; it has the biggest effect on answer quality.
Go to AI assistant → Atlas → About your server| Setting | Limit | What it does |
|---|---|---|
| Name | 100 characters | Atlas introduces itself as the helper for this name |
| What your team helps with | 500 characters | What your team supports, for example We support our game launcher, accounts, and billing. Atlas uses it to tell which questions it should answer |
| Instructions for Atlas | 2,000 characters | Plain-language rules the bot follows, for example For billing questions, always mention our 30-day refund policy: its tone, what to mention or ask for first, and how to handle a kind of question. See the details below the table |
How Instructions for Atlas work:
- Facts and links you write here, such as a server address or a page link, can go to customers as written.
- A reply language or length you set here wins over the defaults.
- When none of your sources match a question, the bot still answers it from these instructions and Links Atlas can share if they cover it.
- Instructions cannot approve a request or give someone access.
- A counter under the box shows how much you have used.
Under Topics, links and product names on the same card:
| Setting | Limit | What it does |
|---|---|---|
| Topics to leave to staff | Up to 20 topics | Topics the bot must not answer. Instead of answering, even when part of the message is documented, it offers the Talk to Staff button and leaves the question to staff. Type a topic and press Enter, or paste several separated by commas |
| Product names | Up to 50 names, 100 characters each | Product names the bot should recognise and spell the way you do. Type a name and press Enter, or paste several separated by commas |
| Links Atlas can share | Up to 25 HTTPS links | Important pages the bot links customers to when one is what they need, without reading them as a source. Sources already include their own addresses |
To add to Links Atlas can share, paste the full https:// address and press Enter, or paste several separated by commas. To give a link a short name, type it in front, like Pricing https://example.com/pricing; the link then shows as that name, and hovering shows the address.
Answer questions in tickets
This card, on the What Atlas does tab under Answer members, turns knowledge base answers in tickets on and decides how they behave.
| Setting | Choices | Default | What it does |
|---|---|---|---|
| Answer questions in tickets (the card's switch) | On, Off | Off | Atlas replies to questions in tickets from your help content |
| When staff are around | Right away, Staff first, Outside hours | Right away | When Atlas answers. See When Atlas answers |
| Stay quiet once staff reply | On, Off | Off | Once a staff member replies in the ticket, Atlas stops answering there |
| How quickly Atlas answers | Fast, Normal, Patient | Normal | How long Atlas waits after the member's last message before it answers: 5, 10 or 20 seconds. See How quickly Atlas answers |
| Reply length | Short, Balanced, Detailed | Balanced | Short is a few sentences, Balanced a paragraph or two, Detailed step by step with more detail |
| Show sources | On, Off | On | Adds a Source: line under each answer with links to the pages it used. It applies everywhere Atlas answers members: tickets, help channels and ModMail. See Source line |
| Close the ticket when the member says it's solved | On, Off | Off | Closes the ticket when the member clearly asks. See Closing on request |
| When Atlas can't help | Stay out for the rest of the ticket, Stay out 1 day, 3 days, 7 days, 14 days, 30 days | Stay out 7 days | How long Atlas stays out of a ticket after handing it to staff. See Feedback & Learning |
| Ping staff roles on hand-over | On, Off | Off | Mentions your staff roles on the hand-over card |
| Let Atlas see member roles | On, Off | Off | Atlas sees the names of the member's server roles when it answers, so it can tailor answers, for example to members with a Premium role. Role names are only context: they never give anyone access |
Close the ticket when the member says it's solved is greyed out with Off while Only staff can close is on. while Only staff can close is on under Closing tickets → Closing rules.
When Atlas answers
When staff are around has three choices:
- Right away: Atlas answers as soon as the member asks.
- Staff first: Atlas waits 45 seconds so staff can answer first. If any staff message arrives during the wait, Atlas drops its answer.
- Outside hours: Atlas answers only while your server is closed, based on your business hours. This choice only shows on Enterprise while business hours are on under General → Business hours.
Whatever you choose, Atlas never talks over staff: it stays quiet while a staff member has replied in the ticket within the last 5 minutes or is typing. With Stay quiet once staff reply on, it stops answering in that ticket for good after the first staff reply.
How quickly Atlas answers
Atlas waits a moment after the member's last message, so a question typed across several messages gets one answer. How quickly Atlas answers sets how long that wait is:
- Fast: 5 seconds. Members get their answer sooner, but Atlas may answer before they have finished typing.
- Normal: 10 seconds. The default.
- Patient: 20 seconds. Slower, but best when your members write many short messages.
The wait applies wherever Atlas answers a ticket: Discord tickets, ModMail, website widget conversations and email tickets. Help channels are not affected. With Staff first, Atlas waits the 45 seconds for staff first and then this wait.
How Atlas builds an answer
Apart from the wait above, there is nothing to tune here: every server gets the most careful setup.
- Atlas waits a few seconds after the member's last message (see How quickly Atlas answers), so a question typed across several messages gets one answer.
- When a member opens a ticket with a form, Atlas answers what they wrote in the form like a first message, with the same wait and the same rules about staff.
- Very short messages such as
hinever trigger an answer. - It rewords an unclear question to search better, picks the strongest matching content, and keeps long sources focused on the parts that matter.
- Before handing a question to staff, it checks whether one of your Q&A entries answers it in other words.
- Answers using your support content are checked against that content before posting. These checks reduce unsupported product claims, but AI can still make mistakes. General technical answers, when enabled, follow the separate rules below.
- Answers using knowledge-base material show a
Source:line while Show sources is on. No match score is shown to members.
Source line
With Show sources on (the default), an answer built from your sources ends with a Source: line that links the pages it used. Answers from general knowledge alone and answers about an active incident have no source line either way. Turn Show sources off to post answers without it; the AI notice and the vote buttons stay.
Where else Atlas may look
This card, on the Help content tab, lets Atlas look beyond your sources.
Go to AI assistant → Atlas → Where else Atlas may look| Setting | Choices | Default | What it does |
|---|---|---|---|
| Answer general tech questions | On, Off | On | Lets the bot add general tech knowledge (browser, networking, operating system basics) where your content leaves a gap, and answer generic technical questions your content does not cover. Turn it off to answer only from your content |
| Search past Discord conversations | On, Off | Off | Lets the bot use answers staff and members already gave in your server's public channels |
| How far back to search | Last 30 days, Last 90 days, Last 6 months, Last year, All time | Last year | Shown while Search past Discord conversations is on. Older messages are skipped |
| Include ModMail conversations | On, Off | Off | Shown while Search past Discord conversations is on, on servers that use ModMail (or while it is on). Lets the bot use past ModMail conversations too, and search for ModMail tickets |
With Answer general tech questions on:
- The bot can fill gaps such as the exact Windows steps for a setting your docs name.
- Anything about your product still comes only from your content, and is still checked against it.
- Billing, account, security, and legal topics still go to staff.
- These answers follow the tone, greeting, sign-off, and reply language set in Instructions for Atlas.
- A reply from general knowledge alone carries the note
General AI knowledge, not from this server's knowledge basenext to the usualGenerated by AInotice.
With Search past Discord conversations on, the bot searches your server's message history for messages that share the key words of the member's question, and uses what it finds next to your knowledge base when it writes an answer or an AI Help draft. When your knowledge base has nothing relevant, a ticket can be answered from community messages alone. When your knowledge base already has a strong match, the bot answers from it without searching.
- Only public channels are searched: channels where everyone can see the channel and read its history. Staff-only channels, ticket channels, private threads, and the ticket being answered are never used. ModMail conversations are left out unless Include ModMail conversations is on (see below).
- Only messages written by people are used, never messages from bots or webhooks, and never the member's own earlier messages. Up to 5 messages are used per answer. A question needs at least two key words to be searched.
- Messages from the time in How far back to search are searched (the last year by default). The bot sees when each message was posted, and when an older message disagrees with your knowledge base or a newer message, it trusts the knowledge base and the newer message.
- Community messages are supporting context, not official content. Links and email addresses that appear only in community messages are never repeated in an answer.
- ModMail can contain private customer conversations, so Include ModMail conversations is off by default. When you turn it on, messages from your past ModMail tickets can be used as supporting context, and ModMail tickets use the search too: for AI Help drafts, and for answers in the member's DMs only when your knowledge base also has a match. Turn it on only if you want Atlas to use those conversations.
- Discord builds a search index for each server. On a large server, or one the bot joined recently, results can be missing until Discord finishes, and the bot simply answers from your knowledge base in the meantime.
Closing on request
With Close the ticket when the member says it's solved on, Atlas reads each short message from the person who opened the ticket and decides whether they are asking for it to be closed. It understands any language, and a reply like nope, that's all to a staff member who asked whether the ticket can be closed.
It keeps doing this after staff reply, so Stay quiet once staff reply and Atlas stepping back for staff do not turn it off.
- When the request is clear, Atlas closes the ticket and posts the Closed by AI message.
- When it is less sure, it posts a Close Ticket button instead, at most once per ticket. Pressing it is the same as the ticket's own Close button.
- It does not close a ticket for messages about closing something else, such as an app, a menu or another ticket, or for a plain
no, that's allto "anything else?". - It does nothing in tickets opened from a panel button with Mute AI replies on, and it does not close tickets when Only staff can close is on.
- In ModMail it never closes on its own. While Only staff can close is off, it sends the member the Close Ticket button in their DM, at most once per ticket; otherwise it does nothing.
- Each message it reads uses about 600 AI tokens. Members on Keep Atlas away from are not read by Atlas. A plain English request such as
you can close this ticketcan still show them the Close Ticket button.
Keep Atlas away from
This list is on AI assistant → Atlas → Keep Atlas away from, under Limits and who Atlas skips. Manage opens a list of members (up to 500, added by name or Discord user ID). Atlas does nothing in tickets these members open: no answers, no AI Help drafts, no translation, priority, tone alerts, sorting, summaries, or learning. Use it for people who misuse the bot or would rather talk to a person. Staff still see and answer their tickets normally.
The card also says how many panel buttons have Mute AI replies on. Tickets from those buttons are treated the same way.
Status Page Integration
Connect Better Stack or Atlassian Statuspage so the bot can mention a known outage when a member asks whether something is down.
Atlas keeps separate incidents when several updates arrive together. Resolving one incident removes only that incident from its context.
The integration is the Status page card under your sources on AI assistant → Atlas → Sources (Pro and higher). Atlas uses it when it answers from the knowledge base.
- Under Status page service, pick Better Stack or Atlassian Statuspage.
- Turn on the switch in the card's header.
- Copy the Webhook URL the card shows (and the one-time secret) into your status page's webhook settings; the card lists the steps for your service. On Better Stack, send the secret in a header named
x-ticketcord-webhook-secret.
Get a new URL replaces the URL if it leaks. Only the bot owner can turn it on, switch services, or get a new URL. Incident-based answers do not show a Source: line.
What happens
- A member sends a question in a ticket, or opens a ticket with a form.
- The bot waits for follow-up messages: 10 seconds, or 5 or 20 if you changed How quickly Atlas answers. With Staff first it first waits 45 seconds and drops the answer if staff reply, then waits that same time. With Outside hours it only goes on while your server is closed.
- If a staff member replied in the last 5 minutes or is typing, or Stay quiet once staff reply finds any staff reply, nothing is posted.
- The bot searches your sources and Q&A entries (and past Discord conversations when that is on), writes an answer in your Reply length, and checks it against your sources.
- The answer is posted with the source line (when Show sources is on), the AI notice, and vote buttons when Let members rate answers is on (on the AI assistant → Atlas → Learning card).
- When it has nothing to answer from, it offers the member a Talk to Staff button instead of guessing.
Recommended configurations
Three starting points. Each table lists suggestions for that setup, not a list of the defaults (some values match a default, others do not): the defaults are in the Answer questions in tickets table above.
Quick answers, staff first
| Setting | Suggested value for this setup |
|---|---|
| Reply length | Short |
| When staff are around | Staff first |
| Stay quiet once staff reply | On |
Full self-service
| Setting | Suggested value for this setup |
|---|---|
| Reply length | Detailed |
| When staff are around | Right away |
| Stay quiet once staff reply | Off |
| Close the ticket when the member says it's solved | On |
After-hours cover (Enterprise)
| Setting | Suggested value for this setup |
|---|---|
| When staff are around | Outside hours |
| Reply length | Balanced |
| When Atlas can't help | Stay out for the rest of the ticket |
Limits and gotchas
Atlas only answers from what it can read. Most wrong or missing answers come from an empty About your server card or a source that does not cover the question, not from a setting.
- Outside hours only shows on Enterprise once business hours are on.
- Detailed replies use more tokens per answer.
- Answers and AI Help drafts only link pages that appear in your sources, Instructions for Atlas, Links Atlas can share, or an active incident from your connected status page. Any other link is removed before the message is sent.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The bot answers questions it should leave to staff | Topics to leave to staff or What your team helps with are empty | Fill in About your server and list the topics that must go to staff |
| The bot uses the wrong product name | Product names is empty | Add every product name customers use under Topics, links and product names |
| Answers are too long or too short | Reply length does not suit your members | Choose Short or Detailed |
| The bot ignores a one-word message | Very short messages never trigger an answer | Expected: the member's next message with the actual question is answered |
| The bot does not answer while a moderator is in the ticket | Atlas always steps back while staff replied in the last 5 minutes or are typing | Expected. It answers again once staff have been quiet for 5 minutes, unless Stay quiet once staff reply is on |
| Close the ticket when the member says it's solved is greyed out | Only staff can close is on | Turn it off under Closing tickets → Closing rules |
| Outside hours is missing | The plan is below Enterprise, or business hours are off | Turn on business hours under General → Business hours |
| Changes do not take effect | You left the page without clicking Save changes | Make the change again and save |
Common questions
Which single setting matters most? About your server. Tell the bot your community name, what you support, your product names, and the topics to leave to staff before anything else.
How do I make the bot wait for a human first? Set When staff are around to Staff first on AI assistant → Atlas → Answer questions in tickets. Atlas then waits 45 seconds and drops its answer if a staff member replies.
Can I change how sure the bot must be before it answers? No. Every server uses the same carefully tested settings, and every answer is checked against your sources. To get better answers, fill in About your server and add sources that cover the questions members ask.
Does the bot show a match score?
No. Answers show a Source: line (unless Show sources is off) and the AI notice only.
Can I hide the source line under answers? Yes. Turn off Show sources on AI assistant → Atlas → Answer questions in tickets. It applies to every Atlas answer, including help channels and ModMail.
Can Atlas give different answers to members with a certain role?
Yes. Turn on Let Atlas see member roles on AI assistant → Atlas → Answer questions in tickets, and tell Atlas what each role gets in Instructions for Atlas, for example Members with the Premium role get priority shipping.
Can I limit past Discord conversations to recent messages? Yes. With Search past Discord conversations on, pick How far back to search on AI assistant → Atlas → Where else Atlas may look: the last 30 days, 90 days, 6 months, the last year (the default), or all time.
Can the bot translate for customers who write in another language? Not from this card. Translation is a separate feature; see Translation.
Why can't I see the knowledge base settings? If the bot owner's plan is below Pro, the AI assistant page shows a locked card with a Pro+ badge instead. On Pro and higher the cards are always visible, even while Atlas is off; the bot answers only once the Atlas switch and Answer questions in tickets are both on and saved.
Source citations for AI answers, the short version
Join our Discord server for support
Was this page helpful?
Last updated on