> 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/bot-commands/rename.md).

# /rename

## Rename Command

### Overview

The `/rename` command changes the name of the current ticket channel. A clear name makes the ticket easier to identify. Run it inside the ticket.

### Usage

```
/rename <name>
```

* **name** *(required text)*: The new name for the ticket channel.

### Description

* **Update the name**: Changes the channel name to match the ticket subject.
* **Better organization**: Helpful when the topic changes or a member opened the wrong ticket type.

### Limits

You can rename a ticket up to 2 times every 10 minutes. This is a Discord limit. If you reach it, the bot tells you when you can rename again.

`/priority` shares this budget, because it also renames the channel.

### Priority markers are kept

If the ticket has a priority set with `/priority`, its colored marker stays in front of the new name. Renaming `🔴┇ticket-42` to `billing-issue` gives `🔴┇billing-issue`. The marker counts towards Discord's 100-character channel-name limit, so a very long name may be rejected on a prioritised ticket.

### When to Use It

* When the topic of the ticket changes or you want a clearer name.
* After you find the real issue, rename the ticket to match it, for example "billing-issue".

### Permissions

* You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions.
* The bot needs `Manage Channels` to rename the channel.

### Example

```
/rename billing-issue
```

Renames the current ticket to "billing-issue".


---

# 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/bot-commands/rename.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.
