# Where to go 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.

{% content-ref url="/pages/RK4hI1VK3OmRDu2Okj2Y" %}
[Dashboard permission areas](/docs/permissions-and-your-support-team/permission-areas.md)
{% endcontent-ref %}

### 2. Set up logging

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

{% content-ref url="/pages/BdzAJh6nhAgNyRVnzgM9" %}
[Log channels](/docs/logging/three-log-channels.md)
{% endcontent-ref %}

### 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.

{% content-ref url="/pages/Blu3D3m8EWaNtKWG4Qa9" %}
[Claiming a ticket](/docs/tickets/claiming-a-ticket.md)
{% endcontent-ref %}

### 4. Customize the panel embed and ticket name format

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.

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-window-maximize">:window-maximize:</i> <strong>Edit the embed</strong></td><td>Title, description, color, image, footer.</td><td><a href="/pages/987R9qKqqc69cNg6Jakh">Edit the embed</a></td></tr><tr><td><i class="fa-tag">:tag:</i> <strong>Ticket name format</strong></td><td>What new ticket channels are named. Covers variables and character limits.</td><td><a href="/pages/EqvfVPSum3JqDjq3shlP">Custom ticket name format</a></td></tr><tr><td><i class="fa-palette">:palette:</i> <strong>Server embed color</strong></td><td>Set the accent color once, applies everywhere.</td><td><a href="/pages/gV3NEl5Zm3vFMXMjYyck">The server embed color</a></td></tr></tbody></table>

## 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.

{% content-ref url="/pages/QNRwt6LnGKeeAJyZJBDu" %}
[What option questions are](/docs/forms/what-option-questions-are.md)
{% endcontent-ref %}

### Set up application panels for staff applications

If you take staff applications, a dedicated application panel collects every answer in one place instead of asking members to DM you.

{% content-ref url="/pages/XQsrUSeSCzERWqbhESgi" %}
[Applications overview](/docs/applications/overview.md)
{% endcontent-ref %}

### Configure inactivity rules

Tickets that go silent for days pile up. Set an inactivity timeout (Premium) or close-on-leave so inactive tickets close automatically.

{% content-ref url="/pages/IF5BZ0r8Id5ZekK1gryx" %}
[Inactivity rules](/docs/tickets/inactivity-rules.md)
{% endcontent-ref %}

## Premium upgrades worth considering

These are the premium features servers add most often:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-crown">:crown:</i> <strong>Bot Personalizer</strong></td><td>Custom name, avatar, banner, and bio in your server only.</td><td><a href="/pages/1KVKhZQLKnflXKfP29XF">Bot Personalizer</a></td></tr><tr><td><i class="fa-crown">:crown:</i> <strong>Ticket Rating</strong></td><td>A post-close rating prompt for members, so you can see how each staff member is doing.</td><td><a href="/pages/ZJP01LC6EVKd946UMthw">What ticket ratings are</a></td></tr><tr><td><i class="fa-crown">:crown:</i> <strong>Statistics</strong></td><td>Charts and numbers on ticket volume, resolution time, and staff workload.</td><td><a href="/pages/FbKCvUVzdQTcW1xoif1r">The Statistics page</a></td></tr><tr><td><i class="fa-crown">:crown:</i> <strong>Custom Commands</strong></td><td>Commands the bot replies to with a saved message, useful for FAQ answers.</td><td><a href="/pages/ubV1L6dUEUGdjD9IyaxC">What custom commands are</a></td></tr></tbody></table>

## Get help when you need it

If you hit something that is not covered here, there are three places to look:

1. [Troubleshooting](/docs/troubleshooting/bot-didnt-respond.md) for common problems and their fixes.
2. [FAQ](/docs/faq/general.md) for short answers to common questions.
3. [Support Discord](https://ticketking.xyz/support) to reach the team.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/getting-started/where-to-go-next.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.