Where to go next

Now that the basics work, here's what most teams configure next.

You have a working panel. Members can open tickets. Your team can see and close them. Here is what most teams configure next.

High impact, do these first

1. Add your full support team and configure their permissions

A single "support role" is a fine start, but most teams have layers, such as senior staff, junior mods, and trainees. Use Ticket King's dashboard permission areas to give each role exactly what it should have.

Dashboard permission areas

2. Set up logging

Without logs, you'll lose track of who closed what and why. Configure the log channels in Settings → Logging.

Log channels

3. Decide your claim policy

When a staff member starts working on a ticket, do they claim it so others know it is handled? Should the ticket become read-only to everyone else when claimed? By default, claiming is on and a claimed ticket becomes private to the opener, the claimer, and the bot. Pick the claim mode that fits your team.

Claiming a ticket

4. Customize the panel embed and custom ticket name

Match the panel and ticket channels to your server's style. A few minutes of customization makes the bot fit your server instead of looking generic.

Edit the embed

Title, description, color, image, footer.

Edit the embed

Custom ticket name

What new ticket channels are named. Covers variables and character limits.

Custom ticket name

Server embed color

Set the accent color once, applies everywhere.

The server embed color

Medium impact, do these in week one

Add option questions to your panels

Asking members 1 to 5 questions before the ticket opens reduces back-and-forth. Questions like "What is your in-game username?", "Which game mode?", and "Have you seen the FAQ?" are answered before staff even reads the ticket.

What option questions are