Launch checklist
Use this before you tell your community that Thoth support is live.
Tick each box in order. If you used Path 1 or Path 2 from the setup guide, most of the Discord items are already done.
1. Bot is in your server
- [ ] Thoth shows as online in the member list
- [ ] You (or an admin) have Manage Server permission
2. Discord setup is complete
Run /thoth-config view in Discord. It should show that support is linked and ready.
- [ ] A start channel exists (for example
#start-support) with a ticket panel (buttons from Thoth) - [ ] At least one ticket type is enabled
- [ ] Staff channels exist or are linked:
#ticket-transcripts,#staff-review,#learned-tips - [ ] Each enabled ticket type has a category for new ticket channels
How you got here (check one):
- [ ]
/thoth-config setup— new server setup - [ ]
/thoth-config link— connected existing channels - [ ] Dashboard save +
/thoth autoconfig— website configuration
If anything is missing: see Setup guide or Troubleshooting.
3. Staff are configured
- [ ] At least one staff role is set (in the setup form or dashboard Settings)
- [ ] Real support staff have that role on Discord
- [ ] Staff know tickets are private channels and replies happen there
4. Knowledge is in place
- [ ] You added FAQs, policies, or guides in dashboard Knowledge (or used
/ingestfor quick notes) - [ ] You tested several real questions in Playground and the answers look good
- [ ] You know how to add or update content later (upload, paste, or URL)
5. Test as a regular user
Use an account without a staff role (a second account or a friend):
- [ ] Open a ticket from the panel in the start channel
- [ ] A private ticket channel opens
- [ ] Ask something covered by your docs — Thoth replies with a relevant answer
- [ ] Click Request human and confirm escalation works as you expect
6. Test as staff
- [ ] Join an escalated or open ticket
- [ ] Reply in the channel — Thoth should pause while staff are active (cooldown)
- [ ] Run
/closein the ticket channel - [ ] A transcript appears in
#ticket-transcripts - [ ] The user receives a rating DM (👍 / 👎 / Skip)
7. Team and community readiness
- [ ] Staff know to run
/closewhen a ticket is resolved - [ ] Staff know where escalations appear (
#staff-review) and where tips are suggested (#learned-tips) - [ ] You told users where to open tickets (for example: “Go to #start-support and click a button”)
Optional (recommended)
- [ ] Auto-learn is on (or you plan to maintain knowledge manually)
- [ ] Business hours are set if you want different behavior outside support hours (Settings)
- [ ] Transcript retention matches your policy
- [ ] You reviewed Insights after a few real tickets
When every box in sections 1–7 is checked, you are ready to announce support.
Need help? Troubleshooting · FAQ