Test Atlas

Test Atlas lets you try Atlas before it talks to your members. You type a question the way a member would, and Atlas runs it through the same answer steps as a real ticket, with your saved settings and help content. Instead of posting anything, it shows you what it would do: answer, ask a question first, offer Talk to staff, or stay quiet, with the reply, the sources it used, and why. You can also replay your latest closed tickets and compare what Atlas would answer with what your staff replied. It works while Atlas and Answer questions in tickets are still off, so you can check your help content first and turn answers on when you are happy with them.

Go to AI assistant → Atlas → Test Atlas

Run a testCopy Anchor Link

What the result showsCopy Anchor Link

The result appears under the question box, like a short chat: your question first, then what Atlas would do.

OutcomesCopy Anchor Link

When Why says Atlas sends the answer and then hands the ticket to your staff, the reply goes out and the ticket is handed over after it, because the reply itself says staff need to step in.

Replay recent ticketsCopy Anchor Link

The Replay recent tickets card on the same tab runs your latest closed tickets through Atlas, one after another, and shows for each ticket what the member asked, what Atlas would answer today, and the first reply your staff gave.

Which tickets are replayed:

• The server's latest closed channel and thread tickets, newest first, with at least two messages.
• Not ModMail tickets, and not tickets whose messages were removed by your retention settings.

What each ticket shows:

How Atlas answers a replayed ticket:

• It uses your help content and saved settings as they are now, and the ticket's category, like a new ticket in that category.
• It leaves out what it learned from that ticket: the learned answers that came from it (the ticket shows how many), and the ticket's own conversation when it searches past Discord conversations. It never repeats a saved answer.
• A learned answer from the ticket that was later merged into another answer, when Atlas tidies up learned answers, can still be used.

A ticket shows "The member did not write a question to replay" when the member never wrote anything, and "This ticket can no longer be replayed" when it was reopened, deleted, or its messages were removed in the meantime.

What a test does and does not doCopy Anchor Link

• Nothing is posted. A test posts nothing in Discord, creates no ticket, pings no one, and does not post the hand-over card.
• The same answer steps and settings. A test uses your saved help content, About your server (including Topics to leave to staff), Reply length, Where else Atlas may look, and the Outside hours choice of When staff are around, like a real ticket.
• It works before answers are on. A test runs while the Atlas switch or Answer questions in tickets is off. Members get answers only once both are on; the tab reminds you while they are off, with a link to the switch.
• Each test is a new ticket's first message. There is no earlier conversation and no staff in the ticket, so a test never waits for staff (Staff first) and Stay quiet once staff reply does not come into play.
• Member settings do not apply. Limit per member, Keep Atlas away from, and panel buttons that turn Atlas off are about real members and their tickets, so tests ignore them.
• It leaves no trace. Tests do not count in Stats, do not become learned answers in Staff Q&A, and are not remembered: asking a follow-up starts over.

TokensCopy Anchor Link

Each test uses the bot owner's AI tokens like a real answer, billed the same way. The result shows how many the test used, and the line next to Ask Atlas shows how many tokens are left this month, with a Buy more link. A repeated answer uses no tokens. On AI usage, tests count as knowledge base usage.

Limits and gotchasCopy Anchor Link

• You can run up to 10 tests a minute. A replay is counted separately: up to 20 replayed tickets a minute, and up to 10 tickets in one replay.
• Search past Discord conversations under Where else Atlas may look needs the bot to be online. While it is offline, a test answers without searching your Discord.
• ModMail servers answer in DMs in a different way, so Test Atlas is not available for servers in ModMail mode yet.
• Answers can vary a little between runs of the same question, as they do in tickets.

TroubleshootingCopy Anchor Link

Go to AI assistant → Atlas → Sources

Common questionsCopy Anchor Link

Can I test Atlas before turning it on? Yes. Test Atlas works while the Atlas switch and Answer questions in tickets are off. Members get nothing until you turn both on.

Does a test post anything in my Discord server? No. A test posts nothing, creates no ticket, and pings no one. It only shows the result in the dashboard.

Do tests cost tokens? Yes. Each test uses the bot owner's AI tokens like a real answer, and the result shows how many. A repeated answer uses no tokens.

Why does a test not show my latest change? Tests use your saved settings. Click Save changes, then ask again.

Who can run tests? Only the bot owner, on a Pro or Enterprise plan, because tests use the owner's AI tokens. Dashboard staff see the tab without the question box.

Do tests show up in Stats or teach Atlas anything? No. Tests do not count in Stats, do not create learned answers, and are not remembered between questions.

Can I see what Atlas would have answered in tickets we already handled? Yes. Replay recent tickets on the Test tab replays your last 5 or 10 closed tickets and shows Atlas's answer next to your staff's first reply. Atlas answers without what it learned from each ticket, so the comparison is fair.

How much does a replay cost? Each replayed ticket uses about as many tokens as one test. The card estimates the total from your last test, and shows the tokens used as it runs. Stopping still finishes the ticket in progress.

Can I test a ModMail server? Not yet. Test Atlas is not available for servers in ModMail mode.