> 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/tickets/limits-on-open-tickets.md).

# Limits on open tickets

Two caps gate ticket creation.

## Per-user cap

How many tickets a single member can have open at once.

| Setting                         | Default | Range     |
| ------------------------------- | ------- | --------- |
| **Max Active Tickets Per User** | **1**   | 1 to 2000 |

The default is **1**, because most servers want one ticket per member at a time. When a member tries to open a second ticket while their first is still open, they get a message listing their existing open tickets.

Configure in **Settings, Server Settings & Logging, Max Active Tickets Per User**.

### When to raise the per-user cap

* **Reseller or VIP servers** where members might have several separate support needs at once.
* **Multi-character game servers** where each character has its own issues.
* **Combined application and support setups** where someone might be applying for staff while also having a support question.

## Server-wide cap

How many tickets can be open across the entire server.

| Setting                | Default | Range     |
| ---------------------- | ------- | --------- |
| **Max Active Tickets** | **500** | 1 to 2000 |

For almost every server the default 500 is effectively no cap. Discord's own server channel cap is also 500, so for text-channel tickets you reach Discord's limit first.

For thread tickets, Discord allows up to 1000 active threads per server, and Ticket King can be set up to 2000.

Configure in **Settings, Server Settings & Logging, Max Active Tickets**.

## What happens when a member hits a limit

The bot replies privately, so only the member sees it:

* Per-user limit hit: a message listing their currently-open ticket channels.
* Server limit hit: a message that the server is at ticket capacity.

## Related Discord-level caps

These come from Discord itself, not Ticket King:

| Cap                               | Value |
| --------------------------------- | ----- |
| Channels per Discord server       | 500   |
| Channels per category             | 50    |
| Active threads per Discord server | 1000  |

When Ticket King tries to create a ticket and Discord rejects it because of a Discord cap, the member sees a message such as that the server has too many channels.

## Per-user ticket-creation cooldown

There is also a 10-second per-user cooldown on opening tickets. It is not configurable. It prevents a member from opening many tickets by spamming a button.

## Per-ticket rename cooldown

A separate cooldown applies to ticket-channel renames, set to **2 renames per 10 minutes**. This is a Discord limit. The member sees a message that renames are limited and to try again later when they hit it.

## Related

{% content-ref url="/pages/0PyHViOuXmoK0zVX0Ukd" %}
[The ticket lifecycle](/docs/tickets/lifecycle.md)
{% endcontent-ref %}

{% content-ref url="/pages/IF5BZ0r8Id5ZekK1gryx" %}
[Inactivity rules](/docs/tickets/inactivity-rules.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/tickets/limits-on-open-tickets.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.