> 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/troubleshooting/ticket-name-not-allowed.md).

# A ticket name isn't allowed

Discord rejected this ticket's name because it contains a word that isn't allowed.

A member clicks your panel button and, instead of a ticket, gets:

> Discord rejected this ticket's name because it contains a word that isn't allowed in this server's channel names. Please contact a server administrator.

Nothing is wrong with your permissions or your panel. Discord refused to create a channel with that particular name.

## Why it happens

Servers with **Community** enabled are eligible for Server Discovery, and Discord runs their channel names through a blocked-word filter. If a generated ticket name contains one of those words, Discord rejects the channel with "Contains words not allowed for servers in Server Discovery" and the ticket is never created.

The name that gets filtered is your custom ticket name with its variables filled in. So the blocked word can come from either half:

* The fixed text you typed into the format, or
* A variable that resolves to something a member controls, most often `{USER_NAME}`.

Because the word usually arrives through the member's own username, this hits a small number of members at random while everyone else opens tickets normally.

This applies to thread tickets too, since Discord validates thread names the same way.

## 1. Find the offending name

The ticket name is built from the format set on the panel option, or the panel-wide default if the option has no override.

Look at that format with the member's username substituted in. If your format is `ticket-{USER_NAME}` and the member's username is the problem, every ticket they open will fail while other members are unaffected.

→ [Custom ticket name](/docs/customization-and-branding/ticket-name-format.md)

## 2. Change the custom ticket name

The reliable fix is to stop putting member-controlled text in the channel name. Any of these avoid the filter entirely:

| Format                   | Result                |
| ------------------------ | --------------------- |
| `ticket-{TICKET_NUMBER}` | `ticket-42`           |
| `{TYPE}-{TICKET_NUMBER}` | `bug-report-42`       |
| `ticket-{USER_ID}`       | `ticket-274837845234` |

Set it in Panel Defaults under **Default Custom Ticket Name**, or per option in the Advanced tab under **Custom Ticket Name**. Changes apply to future tickets; tickets that are already open keep their name.

The member's identity is still shown inside the ticket — the welcome embed names them and pings them — so nothing is lost by keeping it out of the channel name.

## 3. If the word is in your own format text

If your format contains a word Discord blocks (some ordinary words are on the list), rewrite that part of the format. The rest of the format can stay as it is.

## 4. Server nicknames don't help

`{USER_NAME}` resolves to the member's Discord account username, not their nickname in your server. Changing their nickname will not change the ticket name.

## 5. Community servers only

If your server does not have Community enabled, this filter does not apply to you and this message points at something else — check that the custom ticket name is within Discord's limits (100 characters, no spaces).

Turning Community off would also lift the filter, but it removes Server Discovery, the welcome screen, and the other Community features, so changing the custom ticket name is almost always the better trade.

## Related

{% content-ref url="/pages/EqvfVPSum3JqDjq3shlP" %}
[Custom ticket name](/docs/customization-and-branding/ticket-name-format.md)
{% endcontent-ref %}

{% content-ref url="/pages/aHGH6BOJh48aZHUVoiWW" %}
[Per-option settings](/docs/panels/per-option-settings.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/troubleshooting/ticket-name-not-allowed.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.