3 min read
By Mike
Support Server Template for a Discord Bot or Product
A support server template is built around one rule: answer common questions without a human, and move real problems into private tickets. This layout puts FAQ and announcements up front, tickets one click away and staff tools out of sight, with a Noxyr setup to copy.
Who needs a support server
This is for people who support something: a Discord bot, a game mod, a SaaS tool, a course or a store. Users show up with the same ten questions and a few hard ones. The layout below keeps the ten easy ones in public and the hard ones private.
Roles and permissions
Support teams need a clear ladder, because who can see a ticket matters as much as who can answer it.
| Role | What it can do |
|---|---|
| Owner | Full control, billing and bot management. |
| Support Lead | Close or reopen any ticket, claim tickets, edit panels. Can time out members. |
| Support | Reply in and claim tickets. No access to server settings. |
| Helper | Volunteer role. Can answer in #community-help but cannot see tickets. |
| Member | Can read FAQ and post in help channels. |
| Muted/Unverified | Sees only the verify channel until they press the button. |
Suggested channels
| Category | Channel | What it is for |
|---|---|---|
| Info | #start-here | What the server is and how to get help |
#rules | Short rules | |
#status | Outages and known issues | |
#faq | Pinned answers, kept short | |
| Help | #open-a-ticket | Ticket panel with a button or dropdown |
#community-help | Public questions that other members can answer | |
#suggestions | Feature requests with voting | |
| Staff (private) | #ticket-logs | Transcripts and closed tickets |
#support-team | Handover and escalation | |
#bot-logs | Server logs |
Keep #open-a-ticket read-only for everyone. The panel button creates the private channel.
Noxyr setup, in order
- Run
/quickcreatefor a starter ticket panel and FAQ, or/quicksetup ticketto answer the setup questions. - Create a panel for each kind of request with
/ticketsetup panel_create, each with its own staff role and form questions. Post it with/ticketsetup panel. If you have several departments, post one dropdown with/ticketsetup panel-v2. - Turn on auto-close for idle tickets and transcripts. See auto-close and transcripts.
- Add a feedback channel with
/suggestions setupand/suggestions post. - Switch on server logs with
/serverlogs setfor deleted messages and joins. - Enable the AI chat helper for the FAQ, and turn on the verify button with
/verify setupif bots are a problem.
What to check after launch
- Read three real tickets before you edit the form questions. Ask only what you always need.
- Use claiming (
/ticket claim) so two staff do not answer the same ticket. - Ask for ratings at close. The ratings guide explains the flow.
- Check your numbers in the ticket analytics page after a week, then trim panels nobody uses.
Handling the public side
Most of your load can stay out of tickets. Pin three or four short answers in #faq and link them whenever someone asks again. Where the bot allows it, the AI chat feature can answer from your own FAQ so staff only see what it cannot solve.
Use #status for outages. A single post saying "we know, we are fixing it" prevents fifty identical tickets. Keep #community-help open so experienced users can answer each other, and reward the useful ones with the Helper role.
Common mistakes
- One giant panel with ten buttons. Group requests into three or four clear choices.
- Staff who can see everything. Give each department its own staff role per panel.
- No closing habit. Close tickets with a note on what fixed the problem, so the transcript helps next time.
Where to go from here
The ticket bot page shows every ticket feature, and the ticket system setup guide goes deeper. Compare AI and human handling in the AI chatbot page. Need a different channel plan? Use the structure generator.
Common questions
How do I set up a support server on Discord?
Create public info channels, one ticket channel with a panel, and private staff channels. Then add roles for support staff and use a ticket bot such as Noxyr to open private tickets.
How do I stop two staff replying to the same ticket?
Use ticket claiming so one staff member owns each ticket.
Should support tickets be public?
No. Tickets can hold account details, so use private channels visible only to the member and the staff roles.
Is a ticket bot free on Noxyr?
Yes. Tickets, panels, forms, transcripts and ratings are all free.
