> 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/get-help-and-community/joining-support-discord.md).

# Joining the support Discord

Where to get help and meet other Ticket King admins.

The Ticket King support Discord is where you get answers, suggest features, report bugs, and see how other server admins use the bot.

## How to join

Open [ticketking.xyz/discord](https://ticketking.xyz/discord). It takes you to the support server.

## What you'll find

* `#announcements`. Releases, important changes, and planned maintenance.
* `#help`. Open a ticket for help with your server.
* `#feedback`. Feature suggestions and discussion.
* `#bug-reports`. Report bugs.
* `#showcase`. Share your panel designs.
* `#community-presets`. Community panel designs. Some become Public Presets.

## When to come here

* A setting is not behaving the way you expect and you cannot work out why.
* You want a feature.
* You want to suggest a translation change.
* You want to report a bug.
* You want to see how other servers set up Ticket King.

## When not to come here

For data-access requests, data deletion, or billing questions, email <support@ticketking.xyz> instead. A public Discord is not the place for sensitive personal information.

## Search first

Before you ask, search the docs and the `#help` channel for earlier threads. Most common questions have already been answered.

## How to ask well

* **Be specific.** "It is broken" is hard to help with. "When I click button X on panel Y, the bot returns Z" is easy to act on.
* **Include your server ID** for anything about your server.
* **Do not share secrets.** Tokens and billing details go to <support@ticketking.xyz>, not the public Discord.

## Related

{% content-ref url="/pages/X2RSLKZ1mcJ29yoOhGFn" %}
[Reporting bugs](https://ticketking.xyz/docs/get-help-and-community/reporting-bugs.md)
{% endcontent-ref %}

{% content-ref url="/pages/9jDzQPjAcBq7TWsZVZON" %}
[Requesting features](https://ticketking.xyz/docs/get-help-and-community/requesting-features.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/get-help-and-community/joining-support-discord.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.
