> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/ticket-king-documentation.md).

# Welcome

The Discord ticket bot made for serious support teams.

**Ticket King** is a Discord ticket bot. Your members open tickets by clicking a button. Your staff handles those tickets in private channels. The bot keeps logs, transcripts, and statistics.

This documentation covers every feature, every setting, and every action you can take in the bot or on the web dashboard.

<a href="https://ticketking.xyz/invite?via=docs" class="button primary" data-icon="robot">Add Ticket King to your server</a> <a href="https://ticketking.xyz/dashboard" class="button secondary" data-icon="right-to-bracket">Open your dashboard</a>

## Watch the setup

Prefer to follow along? These walk through the whole setup from start to finish.

{% tabs %}
{% tab title="Desktop" %}
{% embed url="<https://youtu.be/d0XUE9yMNrM>" %}
{% endtab %}

{% tab title="Mobile" %}
{% embed url="<https://youtu.be/dLm5rdcF1Es>" %}
{% endtab %}
{% endtabs %}

## Get started

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-robot">:robot:</i> <strong>1. Invite the bot</strong></td><td>Add Ticket King to your server.</td><td><a href="https://ticketking.xyz/docs/getting-started/invite-ticket-king.md">Invite Ticket King</a></td></tr><tr><td><i class="fa-right-to-bracket">:right-to-bracket:</i> <strong>2. Open your dashboard</strong></td><td>Sign in at ticketking.xyz with Discord and pick the server you added the bot to.</td><td><a href="https://ticketking.xyz/docs/getting-started/open-your-dashboard.md">Open your dashboard</a></td></tr><tr><td><i class="fa-ticket">:ticket:</i> <strong>3. Build your first panel</strong></td><td>Create the message your members click to open a ticket.</td><td><a href="https://ticketking.xyz/docs/getting-started/build-your-first-panel.md">Build your first panel</a></td></tr></tbody></table>

## What you get

* **A free plan that covers most servers.** Many features other ticket bots put behind a subscription are free in Ticket King, including multiple panels, custom support roles, transcripts, and audit logs.
* **A web dashboard.** You configure everything from [ticketking.xyz](https://ticketking.xyz) instead of from chat commands.
* **Built for teams.** Separate dashboard permission areas, support roles set per panel and per option, blocked roles, and audit logs for every change.
* **Multiple languages.** The bot speaks 40 languages. Each server picks one.

## Find what you need

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-rocket">:rocket:</i> <strong>Getting Started</strong></td><td>For your first setup.</td><td><a href="https://ticketking.xyz/docs/getting-started/invite-ticket-king.md">Invite Ticket King</a></td></tr><tr><td><i class="fa-ticket">:ticket:</i> <strong>Panels</strong></td><td>The messages your members click to open a ticket.</td><td><a href="https://ticketking.xyz/docs/panels/overview.md">Panels overview</a></td></tr><tr><td><i class="fa-clipboard-list">:clipboard-list:</i> <strong>Forms</strong></td><td>Ask members questions before a ticket opens.</td><td><a href="https://ticketking.xyz/docs/forms/what-option-questions-are.md">Option questions</a></td></tr><tr><td><i class="fa-users">:users:</i> <strong>Permissions</strong></td><td>Who on your team can do what.</td><td><a href="https://ticketking.xyz/docs/permissions-and-your-support-team/two-layers.md">Two layers of permissions</a></td></tr><tr><td><i class="fa-palette">:palette:</i> <strong>Customization</strong></td><td>Change how Ticket King looks in your server.</td><td><a href="https://ticketking.xyz/docs/customization-and-branding/server-embed-color.md">Server embed color</a></td></tr><tr><td><i class="fa-crown">:crown:</i> <strong>Premium</strong></td><td>What Premium includes and how to subscribe.</td><td><a href="https://ticketking.xyz/docs/premium/plans-and-pricing.md">Plans and pricing</a></td></tr><tr><td><i class="fa-life-ring">:life-ring:</i> <strong>Troubleshooting</strong></td><td>Common problems and their fixes.</td><td><a href="https://ticketking.xyz/docs/troubleshooting/bot-didnt-respond.md">Bot didn't respond</a></td></tr><tr><td><i class="fa-circle-question">:circle-question:</i> <strong>FAQ</strong></td><td>Short answers to common questions.</td><td><a href="https://ticketking.xyz/docs/faq/general.md">General FAQ</a></td></tr></tbody></table>

## Need help?

{% hint style="info" %}
**Stuck on something?** Join the [Ticket King support Discord](https://ticketking.xyz/discord).
{% endhint %}

## About Ticket King

For background on the bot and the developer:

{% content-ref url="/pages/xMlIsJA04fGe1vfcXu2S" %}
[About](https://ticketking.xyz/docs/about.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/ticket-king-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
