# Ticket Options

To access these settings:

> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](https://docs.tickettool.xyz/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Ticket** Options

### Ticket Message

This editor will allow you to customize the first message Ticket Tool sends as soon as the ticket is created.

![Editing the Ticket Message](https://i.imgur.com/N6XSlCN.png)

With [Premium](https://tickettool.xyz/premium) you'll be able to add more than a single embed to your ticket message as well adding fields to them. Note that without premium you'll have a restriction of **250 characters** on both your message content and the embed description fields.

#### Message Buttons

Here you'll be able to edit the settings for the **\[`Close`]** and **\[`Claim`]** buttons, to know more about the settings of a button check our documentation on [Message Buttons](https://docs.tickettool.xyz/dashboard/button-options#message-buttons).

### Close Ask Message

Under this editor you will customize the default Close Ask Message that is shown **only** when you have **enabled** the [**Two Step Ticket feature**](https://docs.tickettool.xyz/dashboard/general-options#two-step-ticket) within your panel's [**General Options**](https://docs.tickettool.xyz/dashboard/panel-configs/general-options). To use embeds on this message or to exceed the **250 characters** limit you'll need [Premium](https://tickettool.xyz/premium).

#### Message Buttons

Here you'll be able to edit the settings for the **\[`Cancel Close`]** and **\[`Confirm Close`]** buttons, to know more about the settings of a button check our documentation on [Message Buttons](https://docs.tickettool.xyz/dashboard/button-options#message-buttons).

### Premium Settings

{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting 👀
{% endhint %}

#### Ticket Opened channel name

The name the ticket will be given automatically upon creation.

#### Ticket Closed channel name

The name the ticket will be renamed to automatically once it has been closed.

![Editing the Ticket Names](https://i.imgur.com/KBGsRC4.png)

{% hint style="info" %}
You can use our [Supported Variables](https://docs.tickettool.xyz/dashboard/panel-configs/variables) in both the opened and closed ticket names.
{% endhint %}

{% hint style="warning" %}
Due to [Discord's rate limits](https://i.imgur.com/E2SyNOz.png), bots can only edit a channel's name **twice each 10 minutes**, meaning that if you've hit this limit, Ticket Tool will skip renaming the ticket.
{% endhint %}

#### Ticket Opened Roles

Select a set of roles that should be added and/or removed from the ticket owner once the ticket has been created.

#### Ticket Closed Roles

Similar to the prior setting, this will manage the roles the ticket owner can be granted or removed once the ticket has been closed or deleted.

#### Attach a private thread to each ticket

Enable this for Ticket Tool to automatically create a private thread on your tickets for your staff team to comment the given case in.

![Ticket With Private Thread Attatched](https://i.imgur.com/E5IueIw.png)

{% hint style="info" %}
This feature requires granting the `Create Private Threads` and `Send Messages in Threads` permissions to the bot.
{% endhint %}

**Private Thread Name**

The name this thread should be given upon creation.

**Auto add team to thread**

When **enabled**, Ticket Tool will automatically add the [Support Team](https://docs.tickettool.xyz/dashboard/general-options#support-team-roles) to the thread by pinging them.

**Can non-mods invite users?**

When **disabled**, thread moderators will be the only ones able to add members to the private thread.

{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.tickettool.xyz/dashboard/panel-configs/ticket-options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.