Setup checklist

A panel works with its defaults. Before you announce it, go through this list once. It takes about ten minutes and saves most support questions later.

#Server

• Prefix and language. Set both in Server configs. The language decides the bot's own replies and the defaults of new panels.
• Dashboard roles. Give your admins a dashboard role, so they can change settings without the Discord Administrator permission.
• Blacklist roles. Add roles such as Muted. Members with them cannot use commands or buttons. Never blacklist @everyone.
• Bot permissions. Run $debug once in the panel channel and once in a ticket. It lists anything that is missing.

#Panel

• Support roles under General. Do not pick @everyone here, otherwise every member sees every ticket.
• Categories under Category. Add an overflow category if you expect more than 50 open tickets: Discord allows 50 channels per category.
• Permissions under Permissions. The defaults hide tickets from @everyone and let the owner write while the ticket is open.
• Ticket message under Ticket. Tell members what you need from them. Mention the support role with {@Support} if you want a ping.
• Limits under Limits and schedule. One open ticket per member is the default.
• Transcript channel under Transcripts, so closed tickets leave a record.
• Log channel under Logging, so the team sees who did what.

#Try it

1. Send the panel with $panel 1 or from the dashboard.
2. Open a ticket with a second account.
3. Check that the member sees the ticket and other members do not.
4. Close the ticket, reopen it, save a transcript and delete it.

If anything fails, $debug in the ticket shows the bot's permissions in that channel, the plan of the server and the ticket details.

#Before you grow

• Free servers have up to 10 panels and 25 custom commands. Premium raises both.
• Discord allows 500 channels per server. Delete closed tickets you no longer need, or let an automation do it.