How to set up an AI ticket system in Discord
A classic Discord ticket system files questions. An AI ticket system answers them: the bot replies from your own docs and past resolutions the moment a ticket opens, resolves what it can, and hands your staff a written briefing for the rest. This walkthrough sets one up from zero with OnyxBot. Budget about five minutes, and nothing here needs a credit card; the free plan runs the whole flow.
What you are building
By the end you will have: a ticket panel members click to open tickets, an AI that answers those tickets from knowledge you connected, optional public-channel answering that deflects questions before a ticket exists, and an escalation path where staff get pinged with a briefing covering the issue, what the AI already tried, and a suggested next step.
Step 1: Invite the bot
Sign in at onyxbot.io with Discord, pick your server, and authorize the invite. The permissions it requests are the ones a ticket system needs: creating and managing the ticket threads, posting panels, and mentioning your staff roles on escalation. If the bot shows offline after the invite, this checklist covers the usual causes in a minute.
Step 2: Connect what the AI should know
Open AI, then Knowledge in the dashboard and add your first source. Two options:
- Add Website crawls your docs, FAQ, or store pages and indexes them for answering. Start with the site your members ask about most; a deep crawl picks up the pages behind it.
- Upload File ingests documents directly if your knowledge lives in files rather than on a site.
Free includes 100 knowledge sources, which is far more than a first setup needs. The connecting your first source guide covers formats and what indexes best. One honest note: the AI answers only from what you give it plus what it later learns, so thirty seconds spent connecting the right site beats any other configuration on this page.
Step 3: Choose where it answers in public (optional but recommended)
Under AI, then Configuration, add your support or general-help channels as watched channels. OnyxBot answers questions there before anyone opens a ticket, and stays silent everywhere else. Prefer it quieter? Enable mention-only mode so it waits to be @mentioned. This is public-channel deflection: every question resolved in-channel is a ticket that never consumed staff time.
Step 4: Publish your ticket panel
Open Tickets, then Panels and press New panel. Add your categories (support, billing, appeals, whatever your server routes), map the staff roles for each one, attach an intake form if you want structured questions up front, pick the channel, and publish. Free includes one panel and five categories. Full options live in panels and categories.
Tickets open as threads, not channels, so you will not creep toward Discord's 500-channel cap the way channel-per-ticket bots do. Why that matters is covered in channel limits and thread tickets.
Step 5: Test the loop
Open a ticket yourself and ask something your docs answer. You should see the AI reply with the fix and ask the member to confirm. Then ask something your docs do not cover: the AI escalates, your staff role gets pinged, and the ticket carries a briefing instead of a cold start. That escalation is the part to show your staff, because it is the difference between "a bot answered wrong and went quiet" and "a bot did the first pass and told me what it tried."
What happens after setup
The system improves on its own from here. When your staff resolve a ticket, OnyxBot extracts the question and answer as a knowledge candidate; you approve or edit it in the approval queue, and the next member with that problem gets the answer instantly. Watch the first week in Tickets, then Inbox, skim the approval queue every few days, and keep an eye on AI spend under Billing ($1 of monthly usage is included free; a typical answer costs a fraction of a cent, per what an answer costs).
Coming from another ticket bot rather than from zero? Run OnyxBot alongside it first; the migration guide sequences the cutover so no open ticket gets stranded.