> 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/requesting-features.md).

# Requesting features

Tell us what would make Ticket King better for your server.

## Where to suggest

Post in the `#feedback` or `#suggestions` channel of the support Discord at [ticketking.xyz/support](https://ticketking.xyz/support).

## How to write a clear request

Use this template:

> **Problem.** What is missing or hard today.
>
> **Use case.** Your situation, with numbers if you have them.
>
> **Proposed solution.** What you would like.
>
> **Why it matters to my server.** How often it would help.

A short, specific request is easier to act on than a long list of complaints.

A few things that help:

1. **A clear use case.** For example, "We run a 10,000-member server and get about 200 tickets a week, and we cannot do X."
2. **A concrete idea.** "I would like setting Z on each panel" is clearer than "make panels better."
3. **Other servers wanting the same thing.** If several admins ask for it, that is useful to know.

## Check for an existing thread

Many ideas already have a thread in `#feedback` or `#suggestions`. Search there first. If a thread already exists, add to it rather than starting a new one.

## Related

{% content-ref url="/pages/dZKa2XV9PIaCVaCgC18j" %}
[Joining the support Discord](/docs/get-help-and-community/joining-support-discord.md)
{% endcontent-ref %}

{% content-ref url="/pages/X2RSLKZ1mcJ29yoOhGFn" %}
[Reporting bugs](/docs/get-help-and-community/reporting-bugs.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 dynamically by asking a question.

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

```
GET https://ticketking.xyz/docs/get-help-and-community/requesting-features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.