# Ticket Tool Docs
Ticketing without Clutter
Welcome to Ticket Tool's Documentation Site. Here you'll find all the information you'll need to set up the best ticket system for your Discord server!
## What is Ticket Tool?
Ticket Tool is a highly versatile support bot for [Discord](https://discord.com/) which started development in 2019.
It allows for private support channels, which we call tickets, between your staff team and individuals who look for help.
Itβs **highly customizable**, giving you the freedom for it to be the perfect fit for your server.
There is no need for a complex setup, or multiple commands to make simple actions, you can easily interact with the bot using both the Dashboard and the Discord chat commands.
With over 4,630,000+ active servers, and 435+ Million tickets to date, you can trust Ticket Tool is going to be a great addition to your server.
## About our Docs
In this website you will be able to find detailed descriptions of the whole workflow of the bot. For that purpose, we have made three categories for you to check:
* In **General** you will find the basic setup for the bot, as well as information on its commands.
* **Debugging** contains the most common error messages, basic troubleshooting steps and our FAQs section!
* **Dashboard** has a full and exhaustive explanation on all the Dashboard features
## Important Links:
* [Invite Ticket Tool!](https://tickettool.xyz/invite)
* [Dashboard](https://tickettool.xyz/manage-servers)
* [Support Server](https://tickettool.xyz/support)
* [Status Page](https://status.tickettool.xyz/)
* [Our YouTube Channel](https://www.youtube.com/channel/UC4dVpwfQLcuoIjwkPHg1xNQ)
* [Our Twitter](https://twitter.com/Ticket_Tool)
# Changelog
## February 2025
* Google Drive integration
* DM Ticket Owner for Custom Commands
* New shard manager
## August 2024
* New payment provider and updated [Premium](https://tickettool.xyz) pricing
* Updated Subscriptions page
* Dynamically generated transcripts
* Deprecation of Votes
* Full Dashboard rewrite!
## February 2023
* New Bot Switcher command for switching between Premium and non Premium Ticket Tool!
* New [Custom Command Arguments](/dashboard/custom-commands)!
* New [Automation Options](/dashboard/panel-configs/automation-options#automation-editor)!
* Improved dashboard speeds!
* Various bug fixes and QOL feature additions!
## January 2023
* New [Automation Options](/dashboard/panel-configs/automation-options#automation-editor)!
* New [Variables](/dashboard/panel-configs/variables), i.e `{random}`, `{claim.user}` and `{ticket.owner}`!
* New [Variable Modifiers](/dashboard/panel-configs/variables#modifiers), i.e `?clean`, and modifiers unique to `{random}`: `?rlist`, `?rmax` and `?rmin`
* Added a tab for [Messages Options](/dashboard/panel-configs/messages-options)
* Added a tab for [Button Options](/dashboard/panel-configs/button-options)
* New Sync and Refresh button for your dashboard!
* Tags are now [Custom Commands](/dashboard/custom-commands)!
* New [Claiming features](/dashboard/panel-configs/claiming-options#overwrite-the-claimed-user-instead-of-unclaiming-if-already-claimed)!
## October 2022
* Slash commands are here!
* [Thread Stlye Tickets](/dashboard/panel-configs/thread-style) **BETA** feature
* [Variable](/dashboard/panel-configs/variables) tracking, `{create.form.X}`, `{roblox.X}`, and `{reason}` can be used across all your ticket messsages!
* Whole set of new [Variables' Modifiers](/dashboard/panel-configs/variables#modifiers)!
* Statistics enhancement, leaderboard of claim stats now include avatars and usernames
* [Ticket Open/Closed Roles](/dashboard/panel-configs/ticket-options#ticket-opened-roles)
## September 2022
* Brand New [Panel Configs](/dashboard/panel-configs)!
* [Forms](/dashboard/panel-configs/form-options), Discord Modals support
* [Dropdowns](/dashboard/panel-configs/dropdown-style), Select Menu support
* Multiple embed support
* [Thread support](/dashboard/panel-configs/ticket-options#attach-a-private-thread-to-each-ticket)
* [**Statistics**](/dashboard/statistics) have arrived!
* New [`$closeRequest`](/general/commands#ticket-commands) command
* [Custom Commands](/dashboard/custom-commands) now support the [{ticket.user}](/dashboard/panel-configs/variables) variables!
* Full Discord [Permission](/dashboard/panel-configs/permission-options) support!
* [Scheduled Panel Availability](/dashboard/panel-configs/limit-options#enable-schedule)
* Extended Ticket Limits for both [Opened](/dashboard/panel-configs/limit-options#tickets-open) and [Closed](/dashboard/panel-configs/limit-options#tickets-closed) tickets.
* [Bloxlink Integration](/dashboard/panel-configs/integration-options#bloxlink-for-roblox)
# Setup
Instructions on setting up Ticket Tool in your server.
In order for Ticket Tool to work properly on your server, there are a few basic steps you must follow:
{% hint style="info" %}
Doing this process requires two elements:\
βΈ A [Discord](https://support.discord.com/hc/en-us/articles/204849977-How-do-I-create-a-server-) Server\
βΈ Having `Administrator` permission in that server
{% endhint %}
### Step One:
Invite the bot using the [Official Invite](https://tickettool.xyz/invite). Make sure you do **not edit** the permissions the web page will ask for, as they are completely needed for the bot to function properly.
### Step Two:
You will need a role which will be able to answer your tickets, this is called a **Support Team role**. If you don't have a defined role for this, such as a Staff role or a Moderator role, you can create one by going into your **Server Settings** in your **Discord** server, then clicking on **Roles**, and create a new role, you can name this role anything youd like to name it. Remember to **Save Changes** after you're done editing the role settings.
### Step Three:
Log in to the [Dashboard](https://tickettool.xyz/manage-servers) on a new tab. Click on the **Manage** button that you will find under your server profile picture and name. After that, on the left part of your screen you should see the **Navigation** bar, click on **Panel Configs**
{% hint style="info" %}
**Note:** If you are on mobile, you should click on the three line menu you will find on the left top corner to display the **Navigation** menu.
{% endhint %}
### Step Four:
Let's create the core of your ticket, the panel. While being on the Panel Configs page, click on the green button labeled Create Panel, this will display a pop-up as shown:
**Panel Name** β Can be whatever you want, examples of common names are: Support, Report a User, Shop, it's up to you to decide on this field.
### Step Five:
Using the blue Send button, select the channel you want your panel to be sent to and confirm the action by clicking on the green Send button:
#### Which channel should I use?
A common practice most servers have is to create a specific channel to send their panel(s) to. Most of them make it a read-only channel in order to make it easier for users to find the ticket panel in the server. Common names used for this channel include Support, Tickets, Contact Staff, Support Tickets, or named the same as the Support Team Role. It's your decision on what the channel should be named
And with this, you are all set up to use Ticket Tool! π Feel free to test it out by clicking on the Create Ticket button to create your first ticket!
### What's Next?
If you want to customize the panel message, the ticket message, the support team roles, or any other aspect, go into the [Panel Configs Documentation](/dashboard/panel-configs) to get additional information on customizing the bot.
### Need Further Help?
{% hint style="success" %}
Feel free to open a ticket in our [Support Server](https://discord.gg/tickettool) and one of our Support Team Members will help you out.
{% endhint %}
# Commands
A list of Ticket Tool's commands
{% hint style="warning" %}
* Ticket Tool now also supports [Slash Commands](https://discord.com/blog/welcome-to-the-new-era-of-discord-apps)!
* The default prefix for Ticket Tool is `$`. Pinging Ticket Tool before the command would also work: `@Ticket Tool#4843 help`
* If you've changed the default prefix for Ticket Tool in your server, replace the `$` with the prefix you set.
{% endhint %}
{% hint style="info" %}
Commands will have 2 "arguments", which is a piece of information that can be used by the command to execute a special action:
1. The **Required** Argument, written in `[]`
2. The **Optional** Argument, written in `{}`
{% endhint %}
### General Commands
| Command | Usage | Description |
| ---------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $help | $help
$help commands
$help setup
$help faq
| Provides some basic documentation and assistance about the bot: its commands, how to set it up, and a list of frequently asked questions. |
| $debug | $debug | Provides useful troubleshooting information about your server, the channel $debug is used in, and your own permissions on the server. Support team members may ask you to run this command and provide them with the link it generates to get the information they need to assist you. |
| $permissionlevel | $permissionlevel {User ID}
$level {User ID}
| Ticket Tool responds with your own permission level on this server, or the permission level of the user whose ID you inputted after the command. This is useful for permission issues regarding accessing your server's dashboard. |
| $botswitcher | $botswitcher | Switches the active bot between the white and premium versions. |
| $ping | $ping | Provides the current latency between your server, the bot, and the Discord API. This might be used while troubleshooting. |
| $panel | $panel \[ID] | Send a panel to the current channel. The ID of a panel is in [Panel Configs](/dashboard/panel-configs), to the left of the panel name. |
| $id | $id
$id {#channel}
$id {@role}
$id {@user}
$id {:emoji:}
| Provides your server ID. You can also get the ID of things like channels, roles, users, and custom emojis by including the channel/role/user mention or the emoji itself after the command. |
### Ticket Commands
| Command | Usage | Description |
| ------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $close | $close | Closes a ticket channel that is in the `Opened` state. |
| $open | $open | Re-opens a ticket channel that is in the `Closed` state. |
| $delete | $delete | Deletes a ticket channel, no matter if it's in the `Opened` or `Closed` states. |
| $rename | $rename \[Name] | Renames the ticket channel. |
| $transcript | $transcript {#channel} {X Amount of lines} | - Creates a transcript of the last 1000 messages in the current channel, which is then uploaded as a .html file.
- If no send channel is chosen, then the transcript will be sent to your defined Transcript Channel.
- π Premium Users will have the ability to use this command in all channels, regardless if it's a ticket or not.
|
| $add | $add \[@User#1234]
$add \[User ID]
$add \[@Role]
$add \[Role ID]
| Gives an additional user or role access to the current ticket channel. They are given the same permissions as the [User Opened Permissions](/dashboard/panel-configs/permission-options#user-opened-permissions). |
| $remove | $remove \[@User#1234] $remove \[User ID]
$remove \[@Role]
$remove \[Role ID]
| Removes a userβs or role's access to the ticket channel if they had access to the ticket when it was created, or if they had been added with the `$add` command. |
| $claim | $claim {@User}
$claim {User ID}
| **Premium Only Command.** If [Ticket Claiming](/dashboard/panel-configs/claiming-options) is enabled, then this allows a support team member to claim the ticket. |
| $unclaim | $claim {@User}
$claim {User ID}
| **Premium Only Command.** This allows a support team member to unclaim the ticket if someone had previously claimed it. |
| $closeRequest | $closeRequest / $ca | Sends the [Close Ask Message](/dashboard/panel-configs/ticket-options#close-ask-message) to the ticket channel. |
| $escalate | $escalate {reason} | Escalates the ticket to another panel. Must have the [Escalate feature](/dashboard/panel-configs/escalate-options) configured. |
| $automation | $automation {start/stop} | **π Premium Only** Manages configured automations, including starting or stopping them, for the selected ticketβs panel. |
### Command Style Tickets
{% hint style="info" %}
To use these commands, [Command Style Tickets](/dashboard/panel-configs/command-style-tickets) must be enabled, and the command must be performed in the monitored channel.
{% endhint %}
| Command | Usage | Description |
| ------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $new | $new
$new {Reason}
$new {@User#1234}
$new {@User#1234 Reason}
$new {User ID}
$new {User ID Reason}
| - Creates a new ticket in the specified channel, with an optional reason, or setting a specific user as the ticket owner (Support team only).
- If a reason is included, the variable {reason} can be used in the ticket message.
|
# Errors
Troubleshooting common errors by their hashes!
### Introduction
On July 2023, Ticket Tool introduced a new error handler aiming to help users troubleshoot common situations and/or errors within their servers! Below you can find a guide depicting almost all errors you can face while using Ticket Tool!
### Known Errors
* [Failed to Create - 5169a0fe-f50c-11ed-a05b-0242ac120003](/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003)
* [Missing Panel - 51699a14-f50c-11ed-a05b-0242ac120003](/debugging/errors/51699a14-f50c-11ed-a05b-0242ac120003)
* [Channel Limit - 4f11290a-f4d3-11ed-a05b-0242ac120003](/debugging/errors/4f11290a-f4d3-11ed-a05b-0242ac120003)
* [Category Issues - 51699b5e-f50c-11ed-a05b-0242ac120003](/debugging/errors/51699b5e-f50c-11ed-a05b-0242ac120003)
* [Category Permission Issues - ff941d18-0ee3-46fa-86d1-ebadb1ef0015](/debugging/errors/ff941d18-0ee3-46fa-86d1-ebadb1ef0015)
* [Storage mode error - 5169a4c8-f50c-11ed-a05b-0242ac120003](/debugging/errors/5169a4c8-f50c-11ed-a05b-0242ac120003)
* [Thread Error - 5169a266-f50c-11ed-a05b-0242ac120003](/debugging/errors/5169a266-f50c-11ed-a05b-0242ac120003)
* [Thread Permission Error - 5169a39c-f50c-11ed-a05b-0242ac120003](/debugging/errors/5169a39c-f50c-11ed-a05b-0242ac120003)
* [Ratelimit - 4f112fae-f4d3-11ed-a05b-0242ac120003](/debugging/errors/4f112fae-f4d3-11ed-a05b-0242ac120003)
* [Invalid Modal - 4f111f96-f4d3-11ed-a05b-0242ac120003](/debugging/errors/4f111f96-f4d3-11ed-a05b-0242ac120003)
* [Rate Limit (Too many errors) - 4f112fae-f4d3-11ed-a05d-0242ac120003](/debugging/errors/4f112fae-f4d3-11ed-a05d-0242ac120003)
* [Major Config Mismatch](/debugging/errors/major-mismatch)
# Failed to Create
5169a0fe-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused by Ticket Tool being unable to create the ticket properly:
This error is likely caused by Ticket Tool lacking permissions:
* It can be missing one of the essential permissions on its role, the given category or a specific channel
* It is missing a permission you assigned using the [Permission Options](/dashboard/panel-configs/permission-options) in your [Dashboard Settings](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-permissions)
### Solutions
To solve this you can:
1. Use the `/debug` command to diagnose which permissions the bot requires, the permissions marked with `β` are the ones the bot is missing:
2. Visit the Dashboard and go into the [Permission Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-permissions) tab to identify which permissions the bot is trying to assign. Set some to null in order to figure out which permission is causing the conflict!
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Missing Panel
51699a14-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when the panel you tried creating a ticket from, has been deleted:
### Solutions
To solve this you can:
1. Head to your [Panel Configs](https://tickettool.xyz/dashboard/server_id/configs#pc-menu) in your Dashboard and create a new panel to create tickets from!
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Channel Limit
4f11290a-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when your server has reached the 500 channel limit Discord has per server:
### Solutions
To solve this issue you can:
1. Delete tickets, or other channels, on your server
2. Use the [Thread Style Ticket System](/dashboard/panel-configs/thread-style) since threads have a separate channel limit
3. Enable [Storage Mode](/dashboard/server-configs#server-storage-options) to recycle tickets
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Category Issues
51699b5e-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when the bot has issues locating the category you picked or is unable to add a new channel in the category, resulting in the ticket being created at the top of the channel list:
{% hint style="info" %}
Ticket Tool limits categories at 45 channels instead of Discord's limit of 50, so if your category has 45 or more channels in it, the ticket will appear at the top of the server
{% endhint %}
### Solutions
To solve this you can:
1. Visit your [Category Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-category) in your Dashboard and look for a `~ Deleted ~` category in order to replace it with a valid category
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Category Permission Issues
ff941d18-0ee3-46fa-86d1-ebadb1ef0015 hash errors, causes and solutions
### About the Error
This error takes place when your categories' permissions interfere with Ticket Tool:
### Solutions
To solve this you can:
1. Check the category's permission-overrides and ensure none of Ticket Tool's required permissions are denied. The error message will indicate you which permission(s) is causing issues.
2. Select a different category in the [Category Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-category) that doesn't restrict Ticket Tool
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Storage mode error
5169a4c8-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when you have enabled the [Storage Mode](/dashboard/server-configs#server-storage-options) but did not indicate a category:
### Solutions
To solve this you can:
1. Visit your [Server Configs](https://tickettool.xyz/dashboard/server_id/configs#sc-serverConfigs) and choose a category under **Storage Categories**
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Thread Error
5169a266-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when Ticket Tool doesn't have the required permissions to manage threads
### Solutions
To solve this you can:
1. Check Ticket Tool's role permissions and make sure it has `Manage Threads` enabled
2. Confirm the thread parent channel you choose in your [Thread Style Settings](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-threadStyle) has no override blocking Ticket Tool
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Thread Permission Error
5169a39c-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when Thread Style tickets are enabled, and the ticket owner has no access to the parent channel for the thread:
### Solutions
To solve this you can:
1. Grant the Ticket Owner permission to access the parent channel for the thread style tickets.
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Rate Limit
4f112fae-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when you are creating tickets too fast:
### Solutions
To solve this you can:
1. Wait for the time indicated in the error message!
2. If your server does not have premium, please note that you will have a server limit of 10 tickets every 10 seconds, and 1 ticket per 10 seconds per user. You can remove these limits by purchasing [Ticket Tool Premium](https://tickettool.xyz/premium)
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Invalid Modal
4f111f96-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error usually takes place when you have enabled the [Form Options](/dashboard/panel-configs/form-options) (Modals) but did not set it up properly
### Solutions
To solve this issue you can:
1. Head to your [Dashboard's Form Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-form_create) and ensure the modal has the questions properly configured.
2. If not, add some and then make sure to save changes
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Too Many Errors
4f112fae-f4d3-11ed-a05d-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when your server has generated too many [Failed to Create](/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003) errors in a short time:
### Solutions
To solve this issue you can:
1. Wait for the rate limit to expire in order to create more tickets
2. Check the solutions to [Failed to Create](/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003) errors so you can prevent this error to happen again
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Major Config Mismatch
Major Config Mismatch errors, causes and solutions
### About the Error
This error takes place when you attempt to delete all the custom commands or panels from your server:
### Solutions
To solve this you can:
1. Create a sample custom command (or panel) so you are able to delete the rest.
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Troubleshooting
Solving the most frequent issues
This page covers the most common issues you can face while using Ticket Tool
### Ticket Tool doesn't answer
1. Run **`$debug`** on the channel you are trying to run Ticket Tool commands, if the bot has minimum perms it will either send a embed marking with `β` the permissions it's missing to work properly. If it can't send it to the channel due to permissions, but it received the command it will DM you the debug embed.
2. Go to your [Server Configs](/dashboard/server-configs) and look at your [Blacklisted Roles](/dashboard/server-configs#blacklist-roles), Ticket Tool will ignore anyone who has any of those roles.
{% hint style="warning" %}
Blacklisting **`@everyone`** will result in Ticket Tool being unresponsive to commands to any user.
{% endhint %}
3. Within the [Server Configs](/dashboard/server-configs) tab check that the bot you have enabled is the one you have on your server. If you selected the premium bot you must count with an active [premium](https://tickettool.xyz/premium) subscription.
### Ticket Tool leaves my server as soon as I add it
The most common cause for this situation is having a security bot target Ticket Tool, which leads to Ticket Tool being removed or having its permissions removed. To solve this, reach out to the support team of your security bot in order to whitelist Ticket Tool.
### Everyone can see my tickets!
There are two possible reasons for this issue:
1. The **`@everyone`** role being selected as a [Support Team Role](/dashboard/panel-configs/general-options#support-team-roles), this by default will grant access to the tickets. To fix it you can simply remove the role from this set of roles and new tickets should be private again.
2. The [**`@everyone`** role opened permissions](/dashboard/panel-configs/permission-options#everyone-role-permissions) have granted access to tickets. To fix it mark as `β` the **`View Channel`** permission and new tickets will be private.
### I can't see my ticket
Discord's integrated `View As Role` feature allows you to see the way different set of roles have access to your server's channels. While this is a useful feature, it's not reliable enough for thorough Ticket Tool testing - As tickets are created based on User permissions, while Role permissions are used for [Support Team Roles](/dashboard/panel-configs/general-options#support-team-roles), and [Additional Roles](/dashboard/panel-configs/general-options#additional-roles).
To test Ticket Tool as a user, we suggest you ask a friend to open a ticket for you as a regular member would do, or use an alternative account to simulate the same process to make sure everything is set properly.
# FAQs
Common questions and troubleshooting.
## Table of Contents
| **Number** | **Question** |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `1` | [Warning: You don't have permissions to use this](#warning-you-dont-have-permissions-to-use-this) |
| `2` | [The bot doesn't respond to my commands](#the-bot-doesnt-respond-to-my-commands) |
| `3` | [I can't see my server on the Dashboard](#i-cant-see-my-server-on-the-dashboard) |
| `4` | [What is the prefix and how do I change it?](#what-is-the-prefix-and-how-do-i-change-it) |
| `5` | [How do I let my support team see into a ticket?](#how-do-i-let-my-support-team-see-into-a-ticket) |
| `6` | [How do I make a ticket ping my support when it's created?](#how-do-i-make-a-ticket-ping-my-support-when-its-created) |
| `7` | [How do I set a transcript channel?](#how-do-i-set-a-transcript-channel) |
| `8` | [How do I limit the number of tickets a user can create?](#how-do-i-limit-the-number-of-tickets-a-user-can-create) |
| `9` | [How do I set what category tickets are created in?](#how-do-i-set-what-category-tickets-are-created-in) |
| `10` | [How do I set what category tickets are moved to when closed?](#how-do-i-set-what-category-tickets-are-moved-to-when-closed) |
| `11` | [How do I set the permissions for tickets?](#how-do-i-set-the-permissions-for-tickets) |
| `12` | [How do I create a panel?](#how-do-i-create-a-panel) |
| `13` | [How do I send a panel to my Discord?](#how-do-i-send-a-panel-to-my-discord) |
| `14` | [How do I add or remove users from a ticket?](#how-do-i-add-or-remove-users-from-a-ticket) |
| `15` | [How does claiming work?](#how-does-the-claim-command-work) |
| `16` | [How much is premium and how many servers can I use it on?](#how-much-is-premium-and-how-many-servers-can-i-use-it-on) |
| `17` | [How can I select or transfer the server for my premium subscription?](#how-can-i-select-or-transfer-the-server-for-my-premium-subscription) |
| `18` | [I've lost access to my discord account, how do I get my subscriptions back?](#ive-lost-access-to-my-discord-account-how-do-i-get-my-subscriptions-back) |
| `19` | [I have a premium key, how do I use it?](#i-have-a-premium-key-how-do-i-use-it) |
| `20` | [How can I subscribe to premium and which payment methods can I use?](#how-can-i-subscribe-to-premium-and-which-payment-methods-can-i-use) |
| `21` | [How does Ticket Tool store transcripts?](#how-does-ticket-tool-store-transcripts) |
| `22` | [How do I set a custom emoji in my buttons?](#how-do-i-set-a-custom-emoji-in-my-buttons) |
### Warning: You don't have permissions to use this
If you receive this error when trying to use a command or button, it can be caused by one of the following reasons:
* You have a blacklisted role, go ahead and log into the [Dashboard](https://tickettool.xyz/manage-servers), then head to the **`Server Configs`** and check which are the **Blacklisted Roles**. Remove any unwanted role and **Save** changes.
{% hint style="warning" %}
If **`@everyone`** role is blacklisted, no one will be able to use the buttons or commands in your server.
{% endhint %}
* Check the permissions of the button by going to the **`Panel Configs`**, open the **`Button Option`** - Create ticket, and check which roles have been selected as **`Disabled Roles`**, a user with one of these roles will not be able to use this feature. If the **`Support Team role`** option is enabled then your staff and only your staff will be able to interact with this button, not your server users.
***
### The bot doesn't respond to my commands
Try these solutions:
* Run **`$debug`** in the channel you are trying to use the commands, the bot will answer with an embed, if it doesn't, check the bot has all required permissions in its role, the category and the channel.
* Make sure you have selected the proper bot in your **`Server Configs`**, if you see something such as **BOT ERROR** fix it by following this process:
* Refer to Question #1, [Warning: You don't have permissions to use this](#warning-you-dont-have-permissions-to-use-this), check you don't have any **Blacklisted Role**.
* Double check the prefix you are using for your commands, do this by going into your [Dashboard](https://tickettool.xyz/manage-servers) and opening the **`Server Configs`**:
* If none of these solutions work, visit our [Support Server](https://tickettool.xyz/support) and open a ticket so our Support Team can assist you.
***
### I can't see my server on the Dashboard
Firstly, double check you have the required permissions to access the Dashboard, you need one out of the following things:
* A [Dashboard Role](/dashboard/server-configs#general-options)
* Having **`Administrator`** permission on the server
* Being the **Owner** of the server
{% hint style="info" %}
Although having the **`Manage Server`** permission allows you to invite Ticket Tool to your server, you need the **`Administrator`** permission to edit its configuration in the Dashboard.
{% endhint %}
To check your level, run `$level` in a text channel of your server, the bot should send a response similar to one of these:
If the response of the bot looks something like this:
It means you can't actually edit the configurations of the bot, ask the Server Owner or the Administrators to give you the needed permissions.
{% hint style="info" %}
If the bot is not responding to the level command, check our FAQ about this [topic](#the-bot-doesnt-respond-to-my-commands)
{% endhint %}
***
### What is the prefix and how do I change it?
By default the prefix of the bot is **`$`**, to modify it follow these steps:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Server Configs**
3. Update the prefix editing the **Command Prefix** field
4. **Save** changes
***
### How do I let my support team see into a ticket?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **General section**
4. Select the Support Team roles you want to be able to see into your tickets
5. **Save** changes
For more information on the topic, check the [Support Team Roles Documentation](/dashboard/panel-configs/general-options#support-team-roles)
{% hint style="warning" %}
Take into account that your new Support Team Roles will only be able to see new tickets, the settings won't apply to old tickets.
{% endhint %}
***
### How do I make a ticket ping my support when it's created?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the Panel's **Settings**
4. Open the **Ticket Options** menu
5. Click on **Edit Ticket Message**
6. In the **Message Text** field place one of this two options
* `{@Role Name}` (Case Sensitive)
* `{Role ID}`
7. **Save** changes
{% hint style="info" %}
Make sure to replace the `Role Name` or `Role ID` with the Name or ID of the role you want to ping
{% endhint %}
***
### How do I set a transcript channel?
A transcript is the HTML file that contains the messages of the ticket, for more information on what transcripts are, check our [documentation on it](/dashboard/panel-configs/logging-options#transcript-channel)
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Go into the **Transcript section**
4. Select a **Transcript Channel**
5. **Save** changes
***
### How do I limit the number of tickets a user can create?
To prevent a single user from opening several tickets on your server at once, you can restrict the amount of tickets they can create in two ways:
#### Global Limit
You can restrict the amount a user can open across all your panels, to update this limit follow this process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Server Configs**
3. Update the **Global Ticket Limit** field
4. **Save** changes
#### Panel's Ticket Limit
The second alternative is to limit the amount of ticket a user can create per each panel, for that do these steps:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Go into the **Limits Option**
4. Update the **Ticket Limit** counter
5. **Save** changes
***
### How do I set what category tickets are created in?
By default all of your tickets will be placed at the top of your server, to change this:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Category Options**
4. Select a category at the **Category Open** picker
5. **Save** changes
***
### How do I set what category tickets are moved to when closed?
If no category is set, whenever the tickets are closed they will be placed on the top of the server, to change that follow this process:
If no category is set, whenever a ticket is closed, it will remain in the category selected for [opened tickets](/dashboard/panel-configs/category-options#category-createdopened). If no category is set there, tickets will remain at the top of the channel list. To change that follow this process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Category Options**
4. Select a category at the **Category Closed** picker
5. **Save** changes
***
### How do I set the permissions for tickets?
You can modify the set of permissions Ticket Tool will apply whenever tickets are opened or closed, to do so:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Permission Options**
4. Select what type of permissions you want to change
5. Modify permissions using the    buttons
6. **Save** changes
***
### How do I create a panel?
This is the core of Ticket Tool, so its important to do the adequate process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Click on the **green plus button** at the top right of the screen
3. Give your panel a **name**
4. Click once on **Create**
{% hint style="info" %}
We highly recommend to check our [Setup Documentation](https://github.com/Ticket-Tool/TTDocs/blob/master/debugging/setup.md) in order to set the bot
{% endhint %}
***
### How do I send a panel to my Discord?
Once you have created a panel make sure to send it:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Identify a panel to send
4. Choose the channel from the picker
5. **Send** the panel
***
### How do I add or remove users from a ticket?
For such purpose Ticket Tool counts with two commands:
* `$add User / Role`
* `$remove User / Role`
Or, the slash version of both commands:
* `/add User / Role`
* `/remove User / Role`
You can also add the specific ticket you want to add or remove a user/role from at the end of the prefixed command. Use the ticket option when using slash commands. This is particularly useful if you don't want to execute the commands in the same ticket channel but rather in a private channel. Example:
* `$add User / Role #channel`
* `$remove User / Role #channel`
{% hint style="info" %}
You can either mention the user or role you want to add/remove, or use its ID
{% endhint %}
***
### How does claiming work?
{% hint style="info" %}
This feature is exclusive from the [Premium System](https://tickettool.xyz/premium)
{% endhint %}
Claiming allows your Support Team to claim and be assigned to a ticket, for more information on how this module works please check out our [Claiming Documentation](/dashboard/panel-configs/claiming-options)
***
### How much is premium and how many servers can I use it on?
Our premium subscriptions are $8 per month or $66 yearly and can be purchased directly through [our website](https://tickettool.xyz/premium). For any billing question join our [Support Server](https://tickettool.xyz/support)
{% hint style="warning" %}
Please note that users purchasing premium from Discord's app store have limited control over managing it. You cannot purchase annual subscriptions nor transfer them to any other server. We strongly recommend you purchase premium through our dashboard. For more information, please visit our [Premium page](https://tickettool.xyz/premium).
{% endhint %}
***
### How can I select or transfer the server for my premium subscription?
1. Head to our [Subscriptions Page](https://tickettool.xyz/billing)
2. Click **Manage** under your active subscription
3. On the left side of the panel, click on **Add Server** or use the transfer icon to select a new server
{% hint style="warning" %}
Please note that changing the server your subscription is redeemed on can not be done for Discord subscriptions. To purchase premium directly with us please, visit our [Premium Page](https://tickettool.xyz/premium).
{% endhint %}
***
### I've lost access to my Discord account, how do I get my subscriptions back?
It is important to note that your subscription is **not directly linked** to your Discord account, but rather it is linked to the email that you purchased premium with. In order to change the account that can manage your subscriptions, please open a billing ticket in our [Support Server](https://tickettool.xyz/support) and request the change by providing us:
* The email you created the subscription with
* The ID and username of the account that will manage the subscriptions
* The latest invoice for the subscription
***
### I have a premium key, how do I use it?
To use, redeem or transfer a premium key, please reach out to our Billing Team in our [Support Server](https://tickettool.xyz/support).
***
### How can I subscribe to premium and which payment methods can I use?
You can subscribe using by visiting the [Premium tab](https://tickettool.xyz/dashboard/server_id/premium) in your server's dashboard or by going into the [premium purchase page](https://tickettool.xyz/premium-purchase) directly. We accept the following payment methods:
* All major debit & credit card
* PayPal
* Google Pay (Chrome Only)
* Apple Pay (Safari Only)
***
### How does Ticket Tool store transcripts?
Ticket Tool does **not** store any transcripts at all, once it generates the transcript it's sent as a message to your Discord server, (we delete it from our systems to keep your data's privacy). All of our transcripts are stored directly on Discord's servers, we don't have any kind of access to them, once you delete the message in which the bot sent the HTML file Discord will remove it from it's cache and won't be accessible any longer. The URL to our website is just a rendering of the file stored in Discord's CDN.
***
### How do I set a custom emoji in my buttons?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Button Options** page
4. Select a button and open it's **Settings**
5. Click the **Select** button in the **Button Emoji** field
6. Head to the β³ section inside the Emoji picker
7. Select the new emoji
8. **Save** changes
# About
General information on how to use the dashboard to set the bot.
The Dashboard is the main place through which you are going to edit the settings of the bot in your server. You can access to your dashboard by [clicking here](https://tickettool.xyz/manage-servers) or following these steps:
When you click on **Manage** under a server name, it will send you to that server's Dashboard homepage - which is the [Panel Configs](/dashboard/panel-configs). This is where you can start configurating your support tickets!
On your left side you'll be able to see the navigation bar with the following options:
{% hint style="info" %}
**Note:** If you are on mobile, you should click on the three line menu you will find on the **left top corner** to display the **Navigation** menu.
{% endhint %}
Now, go ahead and check the rest of the documentation on each one of the Dashboard sections:
* [Server Info](/dashboard/server-info)
* [Server Configs](/dashboard/server-configs)
* [Command Configs](/dashboard/command-configs)
* [Panel Configs](/dashboard/panel-configs)
* [Custom Commands](/dashboard/custom-commands)
* [Dashboard History](/dashboard/dashboard-history)
* [Statistics](https://docs.tickettool.xyz/dashboard/statistics)
# Server Info
Information given by the Server Info page.
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Server Info** Tab
This part of the dashboard will show you a brief resume of your server's Ticket System information. But, first of all:
{% hint style="info" %}
**How can I access my Server Info?**\
By default whenever you open your server's dashboard, it will get you here. As reference:
{% endhint %}
Once you are in the Server Info you can see three panels: Ticket Info, Bot Permission Info and Server Info.
### Server Info
Finally you'll be able to see general stats of your server as shown above.
# Customize Bot
**Customizing your bot's appearance!**
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/dashboard)\
> Select your server\
> Go to the **Customize Tab** Tab
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Here you will be able to further customize several aspects of Ticket Tool for your server. Please note this only changes the profile of Ticket Tool within **your server only** and is not a whitelabeled instance of the bot. It will continue to behave and appear as Ticket Tool in Direct Messages.
## Avatar
This is the profile picture. You can upload an image or GIF to replace the default Ticket Tool profile logo for your active bot. The recommended dimensions are 1024 x 1024 pixels.
## Banner
You can upload an image or GIF to replace the default Ticket Tool banner. The recommended dimensions are 680 x 240 pixels.
## Bio
You can edit the bot's about me section here. You can leave it blank if you would like to have no about me listed. There is a character limit is 190 characters.
{% hint style="info" %}
You can use the red π icon to revert back to the default Ticket Tool profile
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Command Configs
Customizing your commands' permissions
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Command Configs** Tab
## Command Configs
{% hint style="info" %}
Here, you can enable or disable specific commands. You can also set which channels these commands should be used in, and who can use the commands.
{% endhint %}
This is how you navigate the dashboard to get to `Command Configs`:
## Enabling and Disabling Commands
Use the slider by each command to turn it on or off. When it is green, the command is enabled. When red, it is disabled.
When a command is disabled, it can no longer be used by anybody on your server.
### Support Team Only
When enabled, the command can only be run by users with a [Support Role](/dashboard/panel-configs/general-options#support-team-roles) in a ticket.
### Allowed Channels
A list of whitelisted channels the command can be run in.
{% hint style="info" %}
Overrides [**Disabled Channels**](#disabled-channels)
{% endhint %}
### Disabled Channels
A list of channels the command cannot be used in.
### Allowed Roles
A list of roles that can run the command.
{% hint style="info" %}
Overrides [**Disabled Roles**](#disabled-roles)
{% endhint %}
### Disabled Roles
A list of roles that cannot run the command.
{% hint style="success" %}
Now youβve edited some settings, make sure to press the green βSaveβ button
{% endhint %}
# Server Configs
Modifying the core settings of your server.
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Server Configs** Tab
## Server Configs
Here you will be able to edit the core settings of Ticket Tool in your server. To get to the Server Configs page, log into the Dashboard, and click on **Server Configs** in the left sidebar. As shown below:
### General Options
#### Command Prefix
* The prefix for **all** of the bot's commands. By default the bot's prefix will be `$`.
{% hint style="info" %}
If you update your prefix to `!` then your help command will be `!help`.
{% endhint %}
#### Dashboard Roles
* Select the roles that will be able to edit the whole dashboard settings, this is different from a Support Team Role as explained in the [General Options Documentation](/dashboard/panel-configs/general-options)
#### Blacklist Roles
* Users with one of this roles won't be able to use any command nor interact with Ticket Tool's buttons.
{% hint style="info" %}
A common practice is to blacklist roles related to sanctions in the server, such as **Muted** role, this in order to prevent moderation problems.
{% endhint %}
#### Global Ticket Limit
* This is the maximum amount of tickets a single user can have opened across all your panels simultaneously.
### Premium Bot
Ticket Tool is a free Discord bot! Nonetheless you can access to more features by subscribing to our [Premium Plan here](https://tickettool.xyz/premium), being a Premium User will give you the possibility to use the premium bot! Which will have better response times as it is used in a fewer amount of servers than the primary bot.
If you want to use the premium bot, make sure to invite it using the **Invite Premium Bot** button in your Server Configs and selecting `Ticket Tool#6207 (Premium Required)` in the bot selector, finally, **Save** changes and you are good to go!
{% hint style="success" %}
If you have an active premium subscription in your server, you can choose between using the Free bot or the Premium one! All features will work in any of the bots as long as you keep your subscription.
{% endhint %}
{% hint style="warning" %}
If you moved from the free bot to the premium one, make sure to resend your panels with the premium one as the free one won't be able to communicate with the premium one.
{% endhint %}
### Server Storage Options
Discord has a 2,000 channel creation limit per server, per day. On the other side your server can only have 500 channels at the same time! If your server has a massive usage of our bot you should consider using this feature to avoid reaching theses limits!
Storage will clear your deleted tickets and place them into a category waiting to be used as part of new tickets, once a ticket is deleted all the messages are purged as well as the settings in order to make it usable for the bot in a potential new ticket!
#### Storage Categories
All the channels belonging to these categories will be recycled by the bot to be used as new tickets!
{% hint style="warning" %}
**All channels**, regardless if tickets or not will be recycled as long as they are in a Storage Category
{% endhint %}
### Bot
By default, Ticket Tool ignores commands sent by other bots. Any bot whose ID you introduce in this field, will bypass this restriction. Allowing Ticket Tool to listen and react to commands actioned by such bots. Separate IDs with a comma if you're introducing multiple IDs.
### Google Drive Transcripts (Server Owner Only)
For further customization, Ticket Tool allows you to save your server's transcripts to your Google Drive! In this part of the dashboard you will be able to select the Google account to which Ticket Tool will save the transcripts, to customize the folder to which each panel's transcripts are saved, review your [Transcript Options](/dashboard/panel-configs/transcript-options#store-transcript-on-google-drive)
{% hint style="danger" %}
**In order to use this feature you must be the server owner**
{% endhint %}
### Config Backup & Restore (Server Owner Only)
One of the most special features Ticket Tool counts with is the ability to transfer the bot's configuration on one of your servers to a new one with out the need of going manually setting by setting, this is what we call **Backup and Restore**. You can transfer your panels and custom commands!
{% hint style="warning" %}
If you had a timed premium key you will need to contact our [Support Team](https://discord.gg/TicketTool) to transfer the remaining time into your new server
{% endhint %}
{% hint style="warning" %}
Take into account that your tickets will **NOT** be transfered to the new server, you should save the transcripts of the tickets if you want to keep their contents.
{% endhint %}
{% hint style="danger" %}
**In order to use this feature you must be the server owner**
{% endhint %}
#### Creating a backup
Follow these steps to properly create a backup:
1. Log into the [Dashboard](https://tickettool.xyz/dashboard)
2. Click on **Manage** under the server you want to create a backup for
3. Open the **Server Configs**
4. Scroll to the bottom of the page and go into the **Config Backup & Restore (Server Owner Only)** section and click on **Backup and Restore**
5. Finally click on **Generate New Key** and copy the new key!
You should only create a key once, the bot will copy the active settings of the key whenever it's used, you should only consider to create a new key if you think it has been compromised.
{% hint style="danger" %}
Keep this key safe, we recommend to have it **outside** of your Discord server in case it gets deleted.
{% endhint %}
This process is also explained as shown here:
#### Restoring backups
To use a backup key, you need to go to the [**Dashboard**](https://tickettool.xyz/dashboard) of the server to which you want to transfer the information, after which you will need to go to **Config Backup & Restore (Server Owner Only)** and click on the **Backup and restore** hyperlink, then place the restore key in **Restore from backup key**, then select the settings you want to copy into the new server, and finally click **Restore Configs.**
With that, all the selected configurations will be taken into the new server without you doing it one by one, enjoy the bot in your new server π
Restoring a Backup illustrative GIF:
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Panel Configs
What are panels, how do I customize them?
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab (Will be the default land page)
### What are Panels?
Panels are Ticket Tool's core, through them your users will be able to create tickets! A panel can have [Buttons](/dashboard/panel-configs/panel-options), or a [Dropdown](/dashboard/panel-configs/dropdown-style).
#### How to create a panel?
Click the **`+`** emoji on your panel selector and give it a name!
### Panel Settings
#### Clone
Create a duplicate of the currently selected panel, the new panel will work as a new separate panel, meaning that settings from the original panel won't be updated on the duplicate panel once the cloning has been done.
#### Rename
Change the name panel you are editing. You can't change the number value or rearrange it.
#### Send
Select a channel to send your panel to, make sure Ticket Tool has the needed permissions to carry on this aciton.
#### Set Count
Set the ticket count of the panel to a custom value.
#### Update
Update a sent panel previously sent to the current version of it, copy the message URL and paste it to do so.
#### Delete
Delete the selected panel
{% hint style="danger" %}
This is an irreversible action so be sure before doing it.
{% endhint %}
{% hint style="info" %}
You must always have at least one panel on the dashboard. If you plan on deleting your last panel, create a new panel first to avoid an error.
{% endhint %}
### Frequently Used Configs
Here you can find a quick access to common settings:
* [Support Team Roles](/dashboard/panel-configs/general-options#support-team-roles)
* [Category Created/Opened](/dashboard/panel-configs/category-options#category-created-opened)
* [Panel Message](/dashboard/panel-configs/panel-options#panel-message)
* [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message)
# General Options
The core settings of every panel
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **General** Options
### Role Settings
#### Support Team Roles
In this field you'll be able to select the roles that, by default, will have access to tickets as well as to commands and buttons that have been marked to be Support Team Only.
#### Additional Roles
This fields allows you to pick a different group of roles to get assigned different permissions from your support team roles. One of the most common uses given to this feature is having an observer role, i.e. someone who can see the ticket but doesn't have the permission to talk on it.
{% hint style="info" %}
To edit the permissions both groups are assigned whenever the ticket is opened or closed visit the [Permissions Options](/dashboard/panel-configs/permission-options)
{% endhint %}
### Ticket Value Settings
#### Ticket Padding
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Ticket padding will modify the length of the [Ticket Count](/dashboard/panel-configs#set-count) (i.e. the ticket's "serial" number, also known as the [{count}](/dashboard/panel-configs/variables) variable) by padding out the length with zeroes in order to fit the specified length. For a clearer explanation see the examples of how the ticket padding will work when the panel has different [Ticket Count](/dashboard/panel-configs#set-count) values:
**Padding for a {count} of 57**
| Padding Value | {count} output |
| -------------- | -------------- |
| 0 | 57 |
| 1 | 57 |
| 2 | 57 |
| 3 | 057 |
| 4 *\[Default]* | 0057 |
| 5 | 00057 |
**Padding for a {count} of 7**
| Padding Value | {count} output |
| -------------- | -------------- |
| 0 | 7 |
| 1 | 7 |
| 2 | 07 |
| 3 | 007 |
| 4 *\[Default]* | 0007 |
| 5 | 00007 |
{% hint style="info" %}
The maximum padding you will be able to set is 20, if you try to set further than that the dashboard will automatically adjust it.
{% endhint %}
### Other Settings
#### Two Step Close
When **enabled**, upon pressing the close button Ticket Tool will give the users the option to confirm they are willing to close the ticket or cancel this action.
If you want tickets to be closed as soon as the close button is pressed you should **disable** this option.
#### Two Step Ticket
When **enabled**, upon pressing the close button Ticket Tool will allow the ticket to have a closed state in which you'll have access to the [Moderator Message](/dashboard/panel-configs/moderator-options#moderator-message) which includes the reopen, delete and save transcript options.
If you want tickets to be **deleted** as soon as the close button is pressed you should **disable** this option.
#### Auto Pin Ticket
When enabled, this option will make Ticket Tool to automatically pin the [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message) as soon as the ticket is created and the core message sent, this allows your team to quickly access to the Close and Claim buttons, if they have been enabled.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Category Options
The categories in which tickets live
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Category** Options
### Category Created/Opened
Select a category for tickets belonging to this panel to be created on.
### Category Closed
Likewise to the previous setting, pick a category for tickets to be moved when closed, leave this option empty if you want the tickets to stay in the same category they were created on, if any. Note that if you have disabled the [Two Step Ticket](/dashboard/panel-configs/general-options#two-step-ticket) feature, tickets will be directly deleted instead of moved to the assigned category here.
### Overflow Categories
Discord only allows to stack up to 50 channels per category. Meaning, if you already have 50 tickets in one category, Ticket Tool will not be able to place a new ticket in that category. To prevent that, Ticket Tool counts with overflow categories, which are additional categories. Once your main category is full, the bot will go ahead and place the new ticket in the next one available. Simply select multiple categories in the category picker.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Ticket Options
Settings related to the Tickets belonging a given panel
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/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.
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](/dashboard/panel-configs/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**](/dashboard/panel-configs/general-options#two-step-ticket) within your panel's [**General Options**](/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](/dashboard/panel-configs/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.
{% hint style="info" %}
You can use our [Supported Variables](/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.
{% 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](/dashboard/panel-configs/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 %}
# Moderator Options
Moderator messages and their customization
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Moderator** Options
### Premium Features
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
#### Closed Message
Here you'll be able to customize the message sent by Ticket Tool whenever a ticket is closed, by default the message will be:
#### Opened Message
Here you can edit the message sent by Ticket Tool whenever a ticket is reopened, by default the message will be:
### More customization
#### Moderator Message
Whenever a ticket is closed Ticket Tool will send a moderator message containing by default the **\[`Reopen`]**, **\[`Delete`]** and **\[`Transcript`]** buttons, to customize them check our [Message Buttons documentation](/dashboard/panel-configs/button-options#message-buttons). The default moderator message is shown below:
#### Delete Message
As soon as a ticket is set to be deleted Ticket Tool will send the following default deletion message, which you can customize:
{% hint style="info" %}
Both the Moderator and Delete messages can be widely customized by being [Premium](https://tickettool.xyz/premium) server, nonetheless you can edit the embeds' description up to **250 characters** for free!
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Permission Options
Editing the permissions for roles and users in tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Permission** Options
{% hint style="info" %}
#### General Rules
* **Opened Permissions** are applied to each group whenever a ticket is **opened**, or **reopened**.
* **Closed Permissions** are applied to each group whenever a ticket is **closed**.
{% endhint %}
{% hint style="warning" %}
#### Important Note
Ticket Tool is not able to set a permission override if the bot does not count with that permission globally (server-wise). Therefore, if you have set a permission but it is not being applied on your tickets, make sure Ticket Tool has that permission. Any permission marked as orange π on your dashboard will be ignored by Ticket Tool when opening and closing tickets.
{% endhint %}
### Support Team Permissions
The permissions you set on these menus will be granted to the [Support Team Roles](/dashboard/panel-configs/general-options#support-team-roles).
### User Permissions
The permissions set here will be applied to:
* The user who opened the ticket
* Users added when using the `$add` command
### Additional Roles Permissions
The permissions you set on these menus will be granted to the [Additional Roles](/dashboard/panel-configs/general-options#additional-roles).
### Everyone Role Permissions
The permissions set here will be applied to the **`@everyone`** role of your server.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Button Options
All buttons in a single place!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Buttons** Options
On this tab of your dashboard you'll be able to access all of the buttons Ticket Tool offers you! Here you'll find a list of all buttons as well as the message you can find them:
* Create Ticket - [Panel Message](/dashboard/panel-configs/panel-options#panel-message)
* Close Ticket - [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message)
* Cancel Close - [Close Ask Message](/dashboard/panel-configs/ticket-options#close-ask-message)
* Re-Open Ticket - [Moderator Message](/dashboard/panel-configs/moderator-options#moderator-message)
* Confirm Close - [Close Ask Message](/dashboard/panel-configs/ticket-options#close-ask-message)
* Delete Ticket - [Moderator Message](/dashboard/panel-configs/moderator-options#moderator-message)
* Transcript - [Moderator Message](/dashboard/panel-configs/moderator-options#moderator-message)
* Claim Ticket - [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message)
### Message Buttons
Below you'll find all of the settings a Ticket Tool button can possibly have across messages.
#### Show this button
If **disabled** this button won't be added to your Close Ask Message.
#### Button Emoji
When **enabled**, the button will include indicated emoji. You can pick the emoji by using our selector or by indicating one of the following manual inputs:
* For custom Discord emojis use `` or `` for animated emojis
* For regular emojis use their unicode value, **not** their Discord name
#### Button Text
Enter button text here, if left empty the button will be emoji-only
{% hint style="warning" %}
All buttons **must** have either the text label or the button emoji.
{% endhint %}
#### Button Color
Select one of the four button colors **supported by Discord** to further customize your buttons! The default color for all buttons is gray.
#### Support Team Only
Enabling this option will make the button only being actionable by members who have a [Support Team Role](/dashboard/panel-configs/general-options#support-team-roles).
#### Allowed Roles
Users that have a role from this selector will be able to use this button.
#### Disabled Roles
Any user with a role from this set won't be able to use the button you are editing.
{% hint style="info" %}
If a user has both `Allowed` and `Disabled` roles, they will be able to use the button. `Allowed` roles override `Disabled` ones.
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Message Options
All messages in a single place!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Messages** Options
On this tab you'll have a list to quickly access all messages you are able to edit with Ticket Tool!
* [Panel Message](/dashboard/panel-configs/panel-options#panel-message)
* [Closed DM](/dashboard/panel-configs/automation-options#send-direct-message-when-ticket-closed)
* [Created DM](/dashboard/panel-configs/automation-options#send-direct-message-when-ticket-created)
* [Claimed Message](/dashboard/panel-configs/claiming-options#claimed-message)
* [Unclaimed Message](/dashboard/panel-configs/claiming-options#unclaimed-message)
* [Closed Message](/dashboard/panel-configs/moderator-options#closed-message)
* [Opened Message](/dashboard/panel-configs/moderator-options#opened-message)
* [Moderator Message](/dashboard/panel-configs/moderator-options#moderator-message)
* [Delete Message](/dashboard/panel-configs/moderator-options#delete-message)
* [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message)
* [Close Question](/dashboard/panel-configs/ticket-options#close-ask-message)
* [Transcript Message](/dashboard/panel-configs/transcript-options#transcript-message)
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Escalate Options
Transferring tickets between panels
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **General Ticket**, click on **Escalate** Options
With escalation, you can transfer a ticket between different panels
### Panel List
You can select up to 25 panels to which a ticket can be transferred to.
{% hint style="warning" %}
Thread Style tickets can not be escalated into a different panel
{% endhint %}
### Update Options
Here you will be able to select which options are to be updated once the ticket is transferred:
* **Category:** If the category limit allows it, the ticket will be moved to the target panel [configured category](/dashboard/panel-configs/category-options).
* **Name:** If there is no renaming cooldown, the ticket will be renamed following the [Ticket Name options](/dashboard/panel-configs/ticket-options#ticket-opened-channel-name) of the target panel.
* **Permissions:** All [Permission Options](/dashboard/panel-configs/permission-options) will be set as new within the target panel.
* **Automatically unclaim ticket:** Requires the panel to have enabled the [Claiming Options](/dashboard/panel-configs/claiming-options).
### Additional Settings
* **Send Custom Message:** Allows you to create a custom message to be sent along on the ticket. Supports [special escalation variables](/dashboard/panel-configs/variables#special-variables)
* **Send Ticket Message:** This will send the target panel's [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message) in the transferred ticket
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
### Available Variables
| **Variable** | **Description** |
| -------------------- | ------------------------------------------------------------------------------------ |
| `{escalate.reason}` | The reason that was given when using the `/escalate` command |
| `{escalate.panel}` | The number of the panel the ticket was escalated to |
| `{escalate.panel.X}` | Replacing `X` with the number of the selected panel will return the text `escalated` |
# Transcript Options
Settings for saving your transcripts
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Transcript** Options
{% hint style="info" %}
#### Important Notes about Transcripts
Transcripts are capped at **1000 messages**. Having a [Premium subscription](https://tickettool.xyz/premium) will allow you to use the `$transcript` command in non-ticket channels and will allow you to embed **up to 8mb** worth of attachments on your transcripts.
{% endhint %}
### Transcript Channel
This setting allows you to pick the channel to which transcripts will be sent when using the **`Transcript`** button, when using the `$transcript` command and when doing an automatic save as we'll see later.
### Store Transcript on Google Drive
{% hint style="danger" %}
**In order to customize these settings you must be the server owner**
{% endhint %}
Here you can choose the folder under which the transcripts of this panel will be saved. Transcripts will be saved to your drive upon any of these actions:
* When someone runs the `/transcript` command
* When a transcript is automatically saved to your **transcript channel**
* When a transcript is automatically DMed to the **ticket owner**
Transcripts on your Drive folder will follow this naming convention: `ServerID:ChannelId:TicketName`
{% hint style="warning" %}
Every time a transcript is saved, even if it's 2 transcripts for the same ticket, it will be saved to your Drive!
{% endhint %}
#### Disable attaching an HTML copy to the transcripts message.
Enabling this option will remove the HTML from your transcript embeds and will save it exclusively to Google Drive.
{% hint style="danger" %}
Deleting a transcript from your Drive will effectively delete the transcript! This will make it inaccessible from Discord, so be careful when deleting any files.
{% endhint %}
### Premium Features
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
#### Transcript Message
This setting will allow you to customize the message that gets sent along the transcript once it's saved.
#### Direct Message Transcript
Enabling this options will make the transcript to be DMed to the ticket creator upon closure and/or deletion, you can choose which option should trigger it.
#### Auto Save Transcript
Enabling this options will make the transcript to be saved into your Transcript Channel upon closure and/or deletion, you can choose which option should trigger it.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Logging Options
Setting up the action logging for your tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Logging** Options
### Logging Channel
Choose a channel to which the log-enabled actions should be logged into.
### Logged Actions
You can enable all of the following ticket actions in your settings for them to be logged on your Logging Channel:
* Ticket Created
* Ticket Closed
* Ticket (Re)Opened
* Ticket Renamed
* Ticket Deleted
* Transcript Saved
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Automation Options
Automate your ticket system!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Automation** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
### Missing user check
When enabled, this setting allows you to decide what should be done if the ticket creator leaves the server: deleting or closing the ticket.
### Send Direct Message when ticket closed
If enabled, the ticket creator will be DMed the set message whenever the ticket is **closed**.
### Send Direct Message when ticket created
If enabled, the ticket creator will be DMed the set message once the ticket is **opened**.
### Automation Editor
{% hint style="warning" %}
* Automations stop running after 7 days or whenever the ticket is closed (if the ticket is reopened automations will run again)
* You can have up to 10 automations per panel
{% endhint %}
{% hint style="info" %}
All details that are unlocked by enabling the **`Show Advanced Automation`** are indicated by a π§ emoji.
{% endhint %}
#### Check for message
* **Check to see if a message** β is found within X time **or** not found within X time
* **From** β This setting refers to whose message needs to be found, or not, within the ticket; Anyone, the Ticket Owner (the user who created the ticket / [**`{ticket.user}`** variable](/dashboard/panel-configs/variables#ticket-variables)) or the [Support Team](/dashboard/panel-configs/general-options#support-team-roles).
* **For** β The time frame in which the message should be looked for, you can choose a preset or insert a custom number in the right box (in seconds).
* **It should check** β Once and stop **or** until stopped. You can stop it by using the `/automation` command or by closing the ticket.
* **π§ If a message is found in x time** β Either if the timer you choose should **restart** or **continue**. Note that this will setting will only appear when you have selected the `not found within X time` check type.
* **If a message is (NOT) found** β You can choose between sending a [Custom Command](/dashboard/custom-commands), Closing **or** Deleting the ticket.
* **π§ After the action runs it should** β Choose if the bot should **keep** or **continue** checking for messages or the abscense of them.
{% hint style="info" %}
**Important:** This automation's minimum **`For`** condition is 5 minutes, anything below that will default to 5 minutes.
{% endhint %}
#### Triggers
{% hint style="info" %}
These settings apply for all of these automation triggers:
* Ticket Closed
* Ticket Re-Opened
* Ticket Created
* Ticket Owner Left Server
* Close Ask Message
{% endhint %}
* **Once triggered run the action** β You can choose between sending a [Custom Command](/dashboard/custom-commands), Closing **or** Deleting the ticket.
* **π§ Delay running the action for** β Choose how long after the trigger should the selected action be executed, you can choose a preset or insert a custom number in the right box (in seconds.)
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Limit Options
Limits for Ticket Panels!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Limit** Options
### Tickets Open
#### Open tickets each user
This number stands for the amount of tickets a single user can have **opened** at once in the panel you are currently editing, i.e. **only open tickets are counted** towards this limit.
#### Open tickets all users
The amount of tickets this panel can have **opened** simultaneously.
#### Roles that bypass open limits
The set of roles that will be able to skip the given limits for open tickets.
### Tickets Closed
{% hint style="warning" %}
* The limits you'll find below are the limits for tickets that are closed but not deleted.
* These limits are checked when the ticket is about to be **created**, i.e there can be more closed tickets than your limit depending on your currently opened tickets.
{% endhint %}
#### Closed tickets each user
The amount of **closed** tickets that each user can have at once in the selected panel.
#### Closed tickets all users
The limit of tickets that can be **closed** at once simultaneously by all your users in **this panel**.
#### Roles that bypass closed limits
The set of roles which will be able to skip the given closed limits.
### Time Schedule
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
This feature will allow you to set time frames, in a given timezone, for which your panels should be available to be used by your server members
#### Enable Schedule
**Enabling** this feature will apply the schedule availability to your panel. Make sure to select the corresponding timezone for your server to prevent any discordance with the selected time frames.
#### Roles that bypass the schedule
Select the roles that should be exempt from this setting and be able to open tickets regardless of the availability set by the schedule.
#### Schedule Notification Message
Here you can customize the message the bot will answer with whenever users try to open a ticket out of the times you've selected.
Below this option you can select the custom times using a table.
{% hint style="info" %}
**Note:** Although the table is given in 24h format, we've included AM and PM headers to make it easier to select the time frames of your prefence in case you aren't used to this format.
{% endhint %}
#### Replace Ticket Message with Schedule Notification Message
Enabling this feature will replace your [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message) with the Schedule Notification Message you set earlier. Note that enabling this won't stop the ticket from being created, instead it will create it with a whole different message but the rest of settings will work the same.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Claiming Options
Customize ticket claiming settings, permissions, actions, and messages
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Claiming** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Ticket Tool allows your [Support Team](/dashboard/panel-configs/general-options#support-team-roles) to claim or be assigned to a given ticket. This menu allows full customization related to this feature!
### Enable Claiming
If this setting is disabled, the rest of customizations done within this menu won't take any effect.
### Ticket Actions
#### Only the user who claimed can un-claim
When enabled, only the ticket claimer will be able to unclaim the ticket.
#### Only the user who claimed and ticket owner can use ticket actions (Does not include claim/un-claim)
When enabled, only the ticket claimer and the owner will be able to use all of the ticket actions (open, delete, transcript), this doesn't include the claiming ones.
{% hint style="info" %}
These settings won't affect users who have a [Dashboard Role](/dashboard/server-configs#dashboard-roles) or the **`Administrator`** permission on your server.
{% endhint %}
#### Overwrite the claimed user instead of unclaiming if already claimed
When enabled, if the ticket has been already claimed, and another user tries to claim, it won't unclaim but will change the ticket claimer.
#### Allow ticket owner to claim the ticket, if permission changes are disabled.
This will allow the ticket creator ([`{ticket.owner}`](/dashboard/panel-configs/variables#ticket-variables)) to claim its own ticket. Note that this feature will only be usable when the [Change other support team permissions when claimed](#change-other-support-team-permissions-when-claimed) feature is **disabled**.
### Enable claim name
If enabled, the text placed here will be the name given to the ticket channel whenever it's claimed, you can use our [Supported Variables](/dashboard/panel-configs/variables) in this field. If the ticket is unclaimed, then it will revert back to the [Ticket Opened Channel Name](/dashboard/panel-configs/ticket-options#ticket-opened-channel-name).
### Enable claim category
Choose a category for tickets to be moved to once they are claimed, you can select more than a single category to apply [Overflow Categories](/dashboard/panel-configs/category-options#overflow-categories).
### Ticket Claimed Roles
Select a set of roles that should be added and/or removed from the ticket owner once the ticket is **claimed**.
### Ticket Un-claimed Roles
Select a set of roles that should be added and/or removed from the ticket owner once the ticket is **unclaimed**.
### Change other support team permissions when claimed
Within this setting you can modify the permissions the support team roles get applied once a ticket is claimed. The ticket claimer will receive the [Support Opened Permissions](/dashboard/panel-configs/permission-options#support-team-permissions). This is often used to make tickets a read only channel for the rest of the team or to hide it.
### Claimed Message
Customize the message sent by Ticket Tool once the ticket has been claimed.
### Unclaimed Message
Edit the message sent by Ticket Tool once the ticket is unclaimed.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Form Options
Questionaries for ticket opening!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Form** Options
### Enable form
When **enabled**, before the ticket is created the user will receive a prompt to fill up your customized questionary.
### Auto display results
Enable this feature to attach an embed automatically to your [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message) which includes the responses summary for this form.
 
### Form Options
* Form Title β The title that will be displayed at the top of the form interaction.
* Question Title β The question or phrase the user will input an answer based on.
* Question Placeholder β The placeholder, or guide text, for the input field
* Required β Whether responding to the selected question should be mandatory before sending the form, or not.
* Multi-line Input β Whether to display the input field as a multi-line field, or not.
* Minimum Input β The minimum required amount of characters to be taken as a valid response, leave empty for 0.
* Maximum Input β The maximum amount of characters that should be used when responding to a form, leave empty for the maximum, which is 4000
{% hint style="info" %}
Note that you'll be able to add up to 5 individual questions per each form
{% endhint %}
### Cheatsheet
If you are new to Discord's application commands and its terminology, you may find this quick visual guide useful to better understand how the different sections will appear from a user's point of view
 
### Displaying Form Answers
To access the user's response to your question(s), you can either enable the automatic embed with the form results, as previously shown above or you can also use form variables!
You will need to use its corresponding `{create.form.x}` variable in your [Ticket Message](/dashboard/panel-configs/ticket-options#ticket-message)!
 
{% hint style="success" %}
For servers using the free plan, there is a limit of **250 characters** for your Ticket Message's embed description. If that's the case, then we would strongly recommend using the [Auto Display Results](#auto-display-results) feature to display your form answers ensuring no limit affects the response content.
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Integration Options
Add integrations to your tickets!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Integrations** Options
### Bloxlink for Roblox
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
This feature allows you to integrate the [Bloxlink Discord Bot](https://blox.link/) within Ticket Tool!
#### Roblox user integration using Bloxlink
Enabling this feature will enable access to Bloxlink variables within the selected panel as well as the auto display feature explained below.
#### Auto display roblox user on the Ticket Message as an additional embed
When enabled, this setting will add an embed containing the user's Roblox ID, the author field includes the URL to the Roblox profile.
{% hint style="info" %}
When having multiple accounts linked on [Bloxlink](https://blox.link/), the variables will show the information for the main account.
{% endhint %}
{% hint style="warning" %}
If the user doesn't have a Roblox account linked to Bloxlink the bot will skip adding the embed even if this feature has been enabled.
{% endhint %}
#### Bloxlink Variables
| **Variable** | **Description** |
| ----------------------- | ------------------------------------------------------ |
| `{roblox.name}` | The Roblox username |
| `{roblox.display.name}` | The Roblox user's display name |
| `{roblox.id}` | The ID of the Roblox account |
| `{roblox.url}` | Direct URL to the Roblox user url |
| `{roblox.created}` | The date in which the Roblox account was created |
| `{roblox.age}` | The age of the account given in days, months and years |
| `{roblox.verified}` | Wether this user has the verified badge or not |
| `{roblox.banned}` | Wether this user has been banned or not |
The [{ticket.user}](/dashboard/panel-configs/variables#ticket-variables) is the user whose account will be checked within Bloxlink for a linked roblox user.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Panel Options
Customizing your panel!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Panel** Options
### Attached Panels (Multi Panels)
### Multipanels
Multipanels are panels with multiple buttons attached to them - they can be set up using attached panels.
Here are the steps to create multipanels:
**Step 1:** Create a panel for each button you wish to have displayed under your panel. For example you might want a user report panel, a general support panel, etc.
**Step 2:** Attach your panels by adding them via the selection box in the attached panels section.
{% hint style="warning" %}
**Note:** if you're attaching all the panels to a panel called **English**, don't include **English** in the attached panels box (If you do this, it will create a duplicate button)
{% endhint %}
**Step 3:** Send the original panel (the one you are editing - it will be shown at the panel selection dropdown at the top of your screen) to the channel you wish.
Now you should have your own multi-panel!
{% hint style="info" %}
* Up to 25 panels can be combined into a single panel!
* The first panel will be sent to the channel like it was sent to the channel on its own, while the others will only have their buttons added to this panel. When a user clicks one of the buttons, a ticket is made through the corresponding panel.
{% endhint %}
The multipanels can be used for many things, such as using them to create tickets for a specific language, like in our [Support Server](https://tickettool.xyz/support)
### Buttons Per Row
When setting up multipanels you can choose what the maximum amount of buttons per row will be, this value must be between 1 and 5, i.e. the exceeding buttons from attached panels will be moved to the next row.
### Panel Message
Here you can customize the message your panel will have once it's sent by Ticket Tool, as well as the settings for your **\[`Create`]** ticket button, to know more about the settings of a button check our documentation on [Message Buttons](/dashboard/panel-configs/button-options#message-buttons).
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Command Style Tickets
Tickets created via commands!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Command Style** Options
Ticket Tool not only offers you the possibility to use [Panel Buttons](/dashboard/panel-configs/panel-options) and [DropDowns](/dashboard/panel-configs/dropdown-style) to create tickets, but it also allows you to use Commands!
#### Enable Command Style ticket creation
If this option is disabled the rest of the settings won't sort any effect. Once you have enabled this module, you'll be able to use the `$new` and `$ticket` commands! These commands have two **optional** arguments you can use when executing them:
> `$new User Reason`
{% hint style="info" %}
Note that **`User`** can be either the ID or a mention to the user you want to open a ticket in behalf of. These two commands allow you to use the **`{reason}`** variable inside your tickets!
{% endhint %}
So for example if I used:
> `$new 518666147441278998 Testing`
Ticket Tool would open a ticket for the user with ID **`518666147441278998`** with the **`{reason}`** variable being "Testing"
#### Delete command after creating ticket
If enabled, once the ticket has been created the trigger command will be deleted by the bot.
#### Bypass channel list and watch all of them
Whenever someone uses the `$new` or the `$ticket` command in **any channel** the bot has access to, it will create a ticket!
#### Channel to monitor for command $new and $ticket
This is the opposite of the previous option, you can actually select in which channels Ticket Tool should look for the **`$new`** command instead of looking in the whole server. For this option to be effective the **bypass must be off**.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# DropDown Style
Using Dropdowns for ticket creation!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **DropDown Style** Options
Dropdowns allow you to display several panels in the same select menu.
### Enable Select Style
In order to use dropdowns instead of [panel buttons](/dashboard/panel-configs/panel-options) this option must be on, otherwise regardless the rest of settings of the menu, buttons will be still used.
### Dropdown Editor
#### Display
The shown text on the select option, this is a **required** field.
#### Panel
The panel this option should open a ticket for, this is a **required** field.
{% hint style="danger" %}
Do **not** select twice the same panel, each option needs its own panel.
{% endhint %}
\### Emoji The emoji that the option should be displayed, leave this field empty for no emoji.
#### Description
The text shown below the Display on the select option, leave this field empty for no description.
#### Placeholder Text
The text the select menu will display before selecting a panel option.
### Cheatsheet
For a clearer view of what a single panel looks like both in your Dashboard and Discord check the following example:
 
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Thread Style Tickets
Using threads instead of channels for your tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Thread Style** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
To implement this feature you'll server must grant Ticket Tool the following permissions:
1. **`Create Private Threads`**
2. **`Send Messages in Threads`**
3. **`Manage Threads`**
### Enable thread style ticket creation
This setting will make the rest of the settings below to be usable by your ticket panel.
### Can non-mods invite people to this ticket?
When enabled, users that don't count with any of the [Support Team Roles](/dashboard/panel-configs/general-options#support-team-roles) will be able to also invite users to the thread.
### Auto add team to thread
Enabling this setting will automatically mention your [Support Team Roles](/dashboard/panel-configs/general-options#support-team-roles) in order to add them to the thread
### Channel to create your ticket threads under
The channel selected here wil be the parent channel for all of the thread tickets created for the selected panel.
{% hint style="danger" %}
The following features **aren't compatible** with the Thread Style Ticket options:
* The usage of **`/add`** and **`/remove`** commands
* [Claiming Options](/dashboard/panel-configs/claiming-options)
* [Permission Options](/dashboard/panel-configs/permission-options)
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Supported Variables
Description of the variables you can use across your ticket system
A variable, just as in math, is something that can have a changing state. In your tickets you have access to certain variables whose value will vary among tickets, you can use these variables on the different fields of your ticket messages!!
Let's see a bit more about what each variable works for
### General Variables
| **Variable** | **Description** |
| --------------------- | ------------------------------------------------------------------ |
| `{server.name}` | Will display the server's name |
| `{server.id}` | The server's ID |
| `{server.icon}` | Direct URL to the server's icon |
| `{server.banner}` | Direct URL to the server's banner |
| `{channel.name}` | Name of the channel in which the variable is being used |
| `{channel.id}` | The ID of that channel |
| `{panel.count}` | The current count of the panel in which this message was triggered |
| `{panel.name}` | The name of the panel in which the variable is being used |
| `{panel.ticketLimit}` | The Ticket Limit for the current panel |
### Ticket Variables
| **Variable** | **Description** |
| ---------------------------------- | ----------------------------------------------------------- |
| `{ticket}` | Mention to the ticket channel in which the variable is used |
| `{ticket.id}` | The ID for the `{ticket}` channel |
| `{ticket.user}` / `{ticket.owner}` | The mention to the user who created the ticket |
| `{ticket.user.name}` | The name of `{ticket.user}` |
| `{ticket.user.id}` | The ID of `{ticket.user}` |
| `{ticket.user.nickname}` | The nickname of `{ticket.user}` |
| `{ticket.user.icon}` | Direct Url of the profile picture of the `{ticket.user}` |
| `{ticket.user.tag}` | The 4 digit discriminator, of the `{ticket.user}` |
| `{ticket.user.full}` | The username + the 4 digit discriminator of `{ticket.user}` |
{% hint style="info" %}
* `{ticket.owner}` is just an alias of `{ticket.user}` meaning it has all of it's sub-variables `{ticket.owner.name}` and so on.
* This set of variables as it name tells, will only work within tickets, if you use it within a tag it will only render when used within a ticket.
{% endhint %}
### Author Variables
Let's talk about the **`{author}`** variable. Any action, such as opening, closing, claiming, deleting etc, a ticket, will have the **`{author}`** variable, which refers to the user who triggered the action.
| **Variable** | **Description** |
| ------------------- | --------------------------------------------------------------------- |
| `{author}` | The mention to the user who triggered the message |
| `{author.name}` | The name of the `{author}` |
| `{author.id}` | The ID of the `{author}` |
| `{author.nickname}` | The nickname of the `{author}` |
| `{author.icon}` | Direct Url of the profile picture of the user triggering this message |
| `{author.tag}` | The 4 digit discriminator, of the `{author}` |
| `{author.full}` | The username + the 4 digit discriminator of `{author}` |
{% hint style="danger" %}
The **`{author}`** variable has the same as usage as **`{user}`**. Take into account that **`{ticket.user}`** refers to the user creating a ticket, so if for example you want to ping the user of your ticket in the claiming, **do not** use **`{user}`** as it will ping the user who claimed, if you want to ping use **`{ticket.user}`**.\
**`{user}`** β **`{ticket.user}`**
{% endhint %}
### Special Variables
| **Variable** | **Description** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `{empty}` | Places an empty-like character on a required field of an embed |
| `{reason}` | The given reason for the action triggered |
| `{create.reason}` | Reason given for a ticket **creation** when using [Command Style Tickets](/dashboard/panel-configs/command-style-tickets) |
| `{close.reason}` | Reason given for a ticket **closure** |
| `{delete.reason}` | Reason given for a ticket **deletion** |
| `{claim.reason}` | Reason given for a ticket **claim** |
| `{claim.user}` | The **last** user who claimed a ticket, has the same sub-variables as [`{ticket.user}`](#ticket-variables) |
| `{@Role Name}` | **Replace** `Role Name` with the name of your role and it will ping that role |
| `{Role ID}` | **Replace** `Role ID` with the ID of your role and it will ping that role |
| `{random}` | Will provide you with a random number (by default lower than 0), use [variable modifiers](#modifiers) to customize this behavior |
| `{regex.X}` | Named group support variables for Regex, only works for [**Custom Commands**](/dashboard/custom-commands#regex) |
| `{create.form.X}` | Displays the user's answer for question #`X` in a [Form](/dashboard/panel-configs/form-options#displaying-form-answers) |
| Escalate Variables | Visit the [Escalate documentation](/dashboard/panel-configs/escalate-options#available-variables) for a full list of variables. |
| Roblox/Bloxlink Variables | Visit the [Integrations documentation](/dashboard/panel-configs/integration-options#bloxlink-variables) for a full list of variables. |
### Time Variables
| **Variable** | **Description** |
| -------------------- | ------------------------------------------------------------------------------------------------------------- |
| `{time}` | Sends the current unix time in seconds |
| `` | Will send the unix time using Discord's timestamp native feature |
| `{time.created.age}` | A human-readable **text** that indicates how long ago was the ticket **created** |
| `{time.claimed.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **claimed** |
| `{time.closed.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **closed** |
| `{time.opened.age}` | A human-readable **text** that indicates the time **between** the ticket's closure and it being **re-opened** |
| `{time.deleted.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **deleted** |
| `{time.created}` | A unix **timestamp** pointing to the time when the ticket was **opened** |
| `{time.claimed}` | A unix **timestamp** pointing to the time when the ticket was **claimed** |
| `{time.closed}` | A unix **timestamp** pointing to the time when the ticket was **closed** |
| `{time.opened}` | A unix **timestamp** pointing to the time when the ticket was **re-opened** |
| `{time.deleted}` | A unix **timestamp** pointing to the time when the ticket was **deleted** |
{% hint style="info" %}
The time-action variables that point to actions that can take place more than once (e.g claiming, closure, re-opening), will take the value of the last moment the action took place.
{% endhint %}
{% hint style="info" %}
For a more convinient use on Discord's Dynamic Timestamps we recommend you checking [HammerTime](https://hammertime.djdavid98.art/), here you can replace the actual unix time for the `{time}` variable to make custom messages!
{% endhint %}
### Modifiers
Since [October 2022](/ticket-tool-changelog#october-2022), you can customize even more your variables! These are all the modifiers you can apply at the end of your variables, remember that to use them you must prefix them using **`?`**, check the [cheatsheet](#cheatsheet) for a sample.
| **Modifier** | **Aliases** | **Description** |
| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `?uppercase` | `?uc` | Will make the variable to be upper case |
| `?lowercase` | `?lc` | Will make the variable to be lower case |
| `?maxLength=` | `?ml=` | Set the maximum lenght for a variable, if it's exceeded, the variable will be truncated |
| `?padLeft=` | `?pl=` | Pad the variable to the left with zeros |
| `?padRight=` | `?pr=` | Pad the variable to the right with zeros |
| `?fallback=` | `?fb=` | If the variable you attach this modifier to is empty, the fallback text (anything placed after the `=`) will be displayed instead. You can also use variables for a fallback text. |
| `?notfallback=` | `?nfb=` | If the variable you attach this modifier to contains information, the fallback text (anything placed after the `=`) will be displayed instead. You can also use variables for a fallback text. |
| `?math=` | `?m=` | Use algebra operators (`+`, `-`, `*`, `/`,) to perform operations on variables such as [`{time}`](#time-variables) |
| `?clean` | None | Replaces the \` character to prevent breaking in variables such as [`{create.form}`](/dashboard/panel-configs/form-options#response-usage) |
| `?rlist=` | None | Add this modifier to the [`{random}`](#special-variables) followed by the items you want the bot to choose from, separated by a pipe (\|) character |
| `?rmin=` | None | Set the **minimum** value [`{random}`](#special-variables) can return |
| `?rmax=` | None | Set the **maximum** value [`{random}`](#special-variables) can return |
#### Cheatsheet
Here you'll find some examples when using this modifiers, if you have questions around them, don't hesitate to contact our [Support Team](https://tickettool.xyz/support)
 
# Custom Commands
Adding predifined messages to your server
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Custom Commands** Tab
Custom Commands are used to send a predefined response to your channels using a text command. Common uses are FAQs, Help Commands, and/or General information.
The Custom Commands tab shows currently configured Custom Commands and allows you to create and edit Custom Commands.
### Creating a Custom Command
To create a Custom Command, press the green `+ New` button in the top left corner of the Custom Commands page. When creating a Custom Command, give it a name to identify your Custom Command.
{% hint style="info" %}
\- To delete a custom commands click the Bin icon that's next to the command name.
* You can clone custom commands by clicking the Copy icon next to delete button.
* You must always have at least one custom command on the dashboard. If you plan on deleting your last custom command, create a new custom command first to avoid an error.
{% endhint %}
{% hint style="warning" %}
\- You must have at least one custom command in your server.
* For more information please look at our [Error Documentation](/debugging/errors/major-mismatch)
{% endhint %}
\## Customizing a Custom Command
#### Command Name
You can always set a new name for your Custom Command by editing it on the top left corner of it's settings
#### Command Group
You can create groups to categorize your Custom Commands! Type a name in the box to look for already made groups or click in the name you typed to create a new one!
#### Command Description/Notes
Here you can insert a custom description you had like the command to have, this is only visible on your dashboard and does not affect in any way the output on your Discord server.
#### Dm Ticket Owner instead
If **enabled**, triggering this custom command **in a ticket** will DM the custom command message to the Ticket Owner instead of sending it to the channel.
{% hint style="warning" %}
If the custom command is triggered **outside** of a ticket, the message will **not** be sent to the channel.
{% endhint %}
\### Dm response instead If **enabled**, the user who triggers the custom command will receive the Message on its Direct Messages (DMs)
#### Admin Only
When **enabled**, only users with a [Dashboard Role](/dashboard/server-configs#dashboard-roles), `Administrator` Permission, and the `Server Owner` will be able to trigger this custom command.
#### Command Trigger
You can choose one of 3 trigger types for your commands:
* Strict
* Wildcard
* Regex
Note that the server's prefix won't affect the command trigger at all!
$help
$help commands
$help setup
$help faq
| Provides some basic documentation and assistance about the bot: its commands, how to set it up, and a list of frequently asked questions. |
| $debug | $debug | Provides useful troubleshooting information about your server, the channel $debug is used in, and your own permissions on the server. Support team members may ask you to run this command and provide them with the link it generates to get the information they need to assist you. |
| $permissionlevel | $permissionlevel {User ID}
$level {User ID}
| Ticket Tool responds with your own permission level on this server, or the permission level of the user whose ID you inputted after the command. This is useful for permission issues regarding accessing your server's dashboard. |
| $botswitcher | $botswitcher | Switches the active bot between the white and premium versions. |
| $ping | $ping | Provides the current latency between your server, the bot, and the Discord API. This might be used while troubleshooting. |
| $panel | $panel \[ID] | Send a panel to the current channel. The ID of a panel is in [Panel Configs](/beta-docs/dashboard/panel-configs), to the left of the panel name. |
| $id | $id
$id {#channel}
$id {@role}
$id {@user}
$id {:emoji:}
| Provides your server ID. You can also get the ID of things like channels, roles, users, and custom emojis by including the channel/role/user mention or the emoji itself after the command. |
### Ticket Commands
| Command | Usage | Description |
| ------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $close | $close | Closes a ticket channel that is in the `Opened` state. |
| $open | $open | Re-opens a ticket channel that is in the `Closed` state. |
| $delete | $delete | Deletes a ticket channel, no matter if it's in the `Opened` or `Closed` states. |
| $rename | $rename \[Name] | Renames the ticket channel. |
| $transcript | $transcript {#channel} {X Amount of lines} | - Creates a transcript of the last 1000 messages in the current channel, which is then uploaded as a .html file.
- If no send channel is chosen, then the transcript will be sent to your defined Transcript Channel.
- π Premium Users will have the ability to use this command in all channels, regardless if it's a ticket or not.
|
| $add | $add \[@User#1234]
$add \[User ID]
$add \[@Role]
$add \[Role ID]
| Gives an additional user or role access to the current ticket channel. They are given the same permissions as the [User Opened Permissions](/beta-docs/dashboard/panel-configs/permission-options#user-opened-permissions). |
| $remove | $remove \[@User#1234] $remove \[User ID]
$remove \[@Role]
$remove \[Role ID]
| Removes a userβs or role's access to the ticket channel if they had access to the ticket when it was created, or if they had been added with the `$add` command. |
| $claim | $claim {@User}
$claim {User ID}
| **Premium Only Command.** If [Ticket Claiming](/beta-docs/dashboard/panel-configs/claiming-options) is enabled, then this allows a support team member to claim the ticket. |
| $unclaim | $claim {@User}
$claim {User ID}
| **Premium Only Command.** This allows a support team member to unclaim the ticket if someone had previously claimed it. |
| $closeRequest | $closeRequest / $ca | Sends the [Close Ask Message](/beta-docs/dashboard/panel-configs/ticket-options#close-ask-message) to the ticket channel. |
| $escalate | $escalate {reason} | Escalates the ticket to another panel. Must have the [Escalate feature](/beta-docs/dashboard/panel-configs/escalate-options) configured. |
| $automation | $automation {start/stop} | **π Premium Only** Manages configured automations, including starting or stopping them, for the selected ticketβs panel. |
### Command Style Tickets
{% hint style="info" %}
To use these commands, [Command Style Tickets](/beta-docs/dashboard/panel-configs/command-style-tickets) must be enabled, and the command must be performed in the monitored channel.
{% endhint %}
| Command | Usage | Description |
| ------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $new | $new
$new {Reason}
$new {@User#1234}
$new {@User#1234 Reason}
$new {User ID}
$new {User ID Reason}
| - Creates a new ticket in the specified channel, with an optional reason, or setting a specific user as the ticket owner (Support team only).
- If a reason is included, the variable {reason} can be used in the ticket message.
|
# Errors
Troubleshooting common errors by their hashes!
### Introduction
On July 2023, Ticket Tool introduced a new error handler aiming to help users troubleshoot common situations and/or errors within their servers! Below you can find a guide depicting almost all errors you can face while using Ticket Tool!
### Known Errors
* [Failed to Create - 5169a0fe-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003)
* [Missing Panel - 51699a14-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/51699a14-f50c-11ed-a05b-0242ac120003)
* [Channel Limit - 4f11290a-f4d3-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/4f11290a-f4d3-11ed-a05b-0242ac120003)
* [Category Issues - 51699b5e-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/51699b5e-f50c-11ed-a05b-0242ac120003)
* [Category Permission Issues - ff941d18-0ee3-46fa-86d1-ebadb1ef0015](/beta-docs/debugging/errors/ff941d18-0ee3-46fa-86d1-ebadb1ef0015)
* [Storage mode error - 5169a4c8-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/5169a4c8-f50c-11ed-a05b-0242ac120003)
* [Thread Error - 5169a266-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/5169a266-f50c-11ed-a05b-0242ac120003)
* [Thread Permission Error - 5169a39c-f50c-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/5169a39c-f50c-11ed-a05b-0242ac120003)
* [Ratelimit - 4f112fae-f4d3-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/4f112fae-f4d3-11ed-a05b-0242ac120003)
* [Invalid Modal - 4f111f96-f4d3-11ed-a05b-0242ac120003](/beta-docs/debugging/errors/4f111f96-f4d3-11ed-a05b-0242ac120003)
* [Rate Limit (Too many errors) - 4f112fae-f4d3-11ed-a05d-0242ac120003](/beta-docs/debugging/errors/4f112fae-f4d3-11ed-a05d-0242ac120003)
* [Major Config Mismatch](https://github.com/Ticket-Tool/TTDocs/blob/beta-docs/debugging/errors/major-mismatch.md)
# Failed to Create
5169a0fe-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused by Ticket Tool being unable to create the ticket properly:
This error is likely caused by Ticket Tool lacking permissions:
* It can be missing one of the essential permissions on its role, the given category or a specific channel
* It is missing a permission you assigned using the [Permission Options](/beta-docs/dashboard/panel-configs/permission-options) in your [Dashboard Settings](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-permissions)
### Solutions
To solve this you can:
1. Use the `/debug` command to diagnose which permissions the bot requires, the permissions marked with `β` are the ones the bot is missing:
2. Visit the Dashboard and go into the [Permission Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-permissions) tab to identify which permissions the bot is trying to assign. Set some to null in order to figure out which permission is causing the conflict!
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Missing Panel
51699a14-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when the panel you tried creating a ticket from, has been deleted:
### Solutions
To solve this you can:
1. Head to your [Panel Configs](https://tickettool.xyz/dashboard/server_id/configs#pc-menu) in your Dashboard and create a new panel to create tickets from!
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Channel Limit
4f11290a-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when your server has reached the 500 channel limit Discord has per server:
### Solutions
To solve this issue you can:
1. Delete tickets, or other channels, on your server
2. Use the [Thread Style Ticket System](/beta-docs/dashboard/panel-configs/thread-style) since threads have a separate channel limit
3. Enable [Storage Mode](/beta-docs/dashboard/server-configs#server-storage-options) to recycle tickets
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Category Issues
51699b5e-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when the bot has issues locating the category you picked or is unable to add a new channel in the category, resulting in the ticket being created at the top of the channel list:
{% hint style="info" %}
Ticket Tool limits categories at 45 channels instead of Discord's limit of 50, so if your category has 45 or more channels in it, the ticket will appear at the top of the server
{% endhint %}
### Solutions
To solve this you can:
1. Visit your [Category Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-category) in your Dashboard and look for a `~ Deleted ~` category in order to replace it with a valid category
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Category Permission Issues
ff941d18-0ee3-46fa-86d1-ebadb1ef0015 hash errors, causes and solutions
### About the Error
This error takes place when your categories' permissions interfere with Ticket Tool:
### Solutions
To solve this you can:
1. Check the category's permission-overrides and ensure none of Ticket Tool's required permissions are denied. The error message will indicate you which permission(s) is causing issues.
2. Select a different category in the [Category Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-category) that doesn't restrict Ticket Tool
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Storage mode error
5169a4c8-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when you have enabled the [Storage Mode](/beta-docs/dashboard/server-configs#server-storage-options) but did not indicate a category:
### Solutions
To solve this you can:
1. Visit your [Server Configs](https://tickettool.xyz/dashboard/server_id/configs#sc-serverConfigs) and choose a category under **Storage Categories**
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Thread Error
5169a266-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error is caused when Ticket Tool doesn't have the required permissions to manage threads
### Solutions
To solve this you can:
1. Check Ticket Tool's role permissions and make sure it has `Manage Threads` enabled
2. Confirm the thread parent channel you choose in your [Thread Style Settings](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-threadStyle) has no override blocking Ticket Tool
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Thread Permission Error
5169a39c-f50c-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when Thread Style tickets are enabled, and the ticket owner has no access to the parent channel for the thread:
### Solutions
To solve this you can:
1. Grant the Ticket Owner permission to access the parent channel for the thread style tickets.
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Rate Limit
4f112fae-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when you are creating tickets too fast:
### Solutions
To solve this you can:
1. Wait for the time indicated in the error message!
2. If your server does not have premium, please note that you will have a server limit of 10 tickets every 10 seconds, and 1 ticket per 10 seconds per user. You can remove these limits by purchasing [Ticket Tool Premium](https://tickettool.xyz/premium)
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Invalid Modal
4f111f96-f4d3-11ed-a05b-0242ac120003 hash errors, causes and solutions
### About the Error
This error usually takes place when you have enabled the [Form Options](/beta-docs/dashboard/panel-configs/form-options) (Modals) but did not set it up properly
### Solutions
To solve this issue you can:
1. Head to your [Dashboard's Form Options](https://tickettool.xyz/dashboard/server_id/configs#pc-menu/pc-form_create) and ensure the modal has the questions properly configured.
2. If not, add some and then make sure to save changes
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Too Many Errors
4f112fae-f4d3-11ed-a05d-0242ac120003 hash errors, causes and solutions
### About the Error
This error takes place when your server has generated too many [Failed to Create](/beta-docs/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003) errors in a short time:
### Solutions
To solve this issue you can:
1. Wait for the rate limit to expire in order to create more tickets
2. Check the solutions to [Failed to Create](/beta-docs/debugging/errors/5169a0fe-f50c-11ed-a05b-0242ac120003) errors so you can prevent this error to happen again
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Major Config Mismatch
Major Config Mismatch errors, causes and solutions
### About the Error
This error takes place when you attempt to delete all the custom commands or panels from your server:
### Solutions
To solve this you can:
1. Create a sample custom command (or panel) so you are able to delete the rest.
{% hint style="info" %}
If after this you haven't been able to solve the error, reach out to our [Support Team](https://discord.gg/TicketTool)
{% endhint %}
# Troubleshooting
Solving the most frequent issues
This page covers the most common issues you can face while using Ticket Tool
### Ticket Tool doesn't answer
1. Run **`$debug`** on the channel you are trying to run Ticket Tool commands, if the bot has minimum perms it will either send a embed marking with `β` the permissions it's missing to work properly. If it can't send it to the channel due to permissions, but it received the command it will DM you the debug embed.
2. Go to your [Server Configs](/beta-docs/dashboard/server-configs) and look at your [Blacklisted Roles](/beta-docs/dashboard/server-configs#blacklist-roles), Ticket Tool will ignore anyone who has any of those roles.
{% hint style="warning" %}
Blacklisting **`@everyone`** will result in Ticket Tool being unresponsive to commands to any user.
{% endhint %}
3. Within the [Server Configs](/beta-docs/dashboard/server-configs) tab check that the bot you have enabled is the one you have on your server. If you selected the premium bot you must count with an active [premium](https://tickettool.xyz/premium) subscription.
### Ticket Tool leaves my server as soon as I add it
The most common cause for this situation is having a security bot target Ticket Tool, which leads to Ticket Tool being removed or having its permissions removed. To solve this, reach out to the support team of your security bot in order to whitelist Ticket Tool.
### Everyone can see my tickets!
There are two possible reasons for this issue:
1. The **`@everyone`** role being selected as a [Support Team Role](/beta-docs/dashboard/panel-configs/general-options#support-team-roles), this by default will grant access to the tickets. To fix it you can simply remove the role from this set of roles and new tickets should be private again.
2. The [**`@everyone`** role opened permissions](/beta-docs/dashboard/panel-configs/permission-options#everyone-role-permissions) have granted access to tickets. To fix it mark as `β` the **`View Channel`** permission and new tickets will be private.
### I can't see my ticket
Discord's integrated `View As Role` feature allows you to see the way different set of roles have access to your server's channels. While this is a useful feature, it's not reliable enough for thorough Ticket Tool testing - As tickets are created based on User permissions, while Role permissions are used for [Support Team Roles](/beta-docs/dashboard/panel-configs/general-options#support-team-roles), and [Additional Roles](/beta-docs/dashboard/panel-configs/general-options#additional-roles).
To test Ticket Tool as a user, we suggest you ask a friend to open a ticket for you as a regular member would do, or use an alternative account to simulate the same process to make sure everything is set properly.
# FAQs
Common questions and troubleshooting.
## Table of Contents
| **Number** | **Question** |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `1` | [Warning: You don't have permissions to use this](#warning-you-dont-have-permissions-to-use-this) |
| `2` | [The bot doesn't respond to my commands](#the-bot-doesnt-respond-to-my-commands) |
| `3` | [I can't see my server on the Dashboard](#i-cant-see-my-server-on-the-dashboard) |
| `4` | [What is the prefix and how do I change it?](#what-is-the-prefix-and-how-do-i-change-it) |
| `5` | [How do I let my support team see into a ticket?](#how-do-i-let-my-support-team-see-into-a-ticket) |
| `6` | [How do I make a ticket ping my support when it's created?](#how-do-i-make-a-ticket-ping-my-support-when-its-created) |
| `7` | [How do I set a transcript channel?](#how-do-i-set-a-transcript-channel) |
| `8` | [How do I limit the number of tickets a user can create?](#how-do-i-limit-the-number-of-tickets-a-user-can-create) |
| `9` | [How do I set what category tickets are created in?](#how-do-i-set-what-category-tickets-are-created-in) |
| `10` | [How do I set what category tickets are moved to when closed?](#how-do-i-set-what-category-tickets-are-moved-to-when-closed) |
| `11` | [How do I set the permissions for tickets?](#how-do-i-set-the-permissions-for-tickets) |
| `12` | [How do I create a panel?](#how-do-i-create-a-panel) |
| `13` | [How do I send a panel to my Discord?](#how-do-i-send-a-panel-to-my-discord) |
| `14` | [How do I add or remove users from a ticket?](#how-do-i-add-or-remove-users-from-a-ticket) |
| `15` | [How does claiming work?](#how-does-the-claim-command-work) |
| `16` | [How much is premium and how many servers can I use it on?](#how-much-is-premium-and-how-many-servers-can-i-use-it-on) |
| `17` | [How can I select or transfer the server for my premium subscription?](#how-can-i-select-or-transfer-the-server-for-my-premium-subscription) |
| `18` | [I've lost access to my discord account, how do I get my subscriptions back?](#ive-lost-access-to-my-discord-account-how-do-i-get-my-subscriptions-back) |
| `19` | [I have a premium key, how do I use it?](#i-have-a-premium-key-how-do-i-use-it) |
| `20` | [How can I subscribe to premium and which payment methods can I use?](#how-can-i-subscribe-to-premium-and-which-payment-methods-can-i-use) |
| `21` | [How does Ticket Tool store transcripts?](#how-does-ticket-tool-store-transcripts) |
| `22` | [How do I set a custom emoji in my buttons?](#how-do-i-set-a-custom-emoji-in-my-buttons) |
### Warning: You don't have permissions to use this
If you receive this error when trying to use a command or button, it can be caused by one of the following reasons:
* You have a blacklisted role, go ahead and log into the [Dashboard](https://tickettool.xyz/manage-servers), then head to the **`Server Configs`** and check which are the **Blacklisted Roles**. Remove any unwanted role and **Save** changes.
{% hint style="warning" %}
If **`@everyone`** role is blacklisted, no one will be able to use the buttons or commands in your server.
{% endhint %}
* Check the permissions of the button by going to the **`Panel Configs`**, open the **`Button Option`** - Create ticket, and check which roles have been selected as **`Disabled Roles`**, a user with one of these roles will not be able to use this feature. If the **`Support Team role`** option is enabled then your staff and only your staff will be able to interact with this button, not your server users.
***
### The bot doesn't respond to my commands
Try these solutions:
* Run **`$debug`** in the channel you are trying to use the commands, the bot will answer with an embed, if it doesn't, check the bot has all required permissions in its role, the category and the channel.
* Make sure you have selected the proper bot in your **`Server Configs`**, if you see something such as **BOT ERROR** fix it by following this process:
* Refer to Question #1, [Warning: You don't have permissions to use this](#warning-you-dont-have-permissions-to-use-this), check you don't have any **Blacklisted Role**.
* Double check the prefix you are using for your commands, do this by going into your [Dashboard](https://tickettool.xyz/manage-servers) and opening the **`Server Configs`**:
* If none of these solutions work, visit our [Support Server](https://tickettool.xyz/support) and open a ticket so our Support Team can assist you.
***
### I can't see my server on the Dashboard
Firstly, double check you have the required permissions to access the Dashboard, you need one out of the following things:
* A [Dashboard Role](/beta-docs/dashboard/server-configs#general-options)
* Having **`Administrator`** permission on the server
* Being the **Owner** of the server
{% hint style="info" %}
Although having the **`Manage Server`** permission allows you to invite Ticket Tool to your server, you need the **`Administrator`** permission to edit its configuration in the Dashboard.
{% endhint %}
To check your level, run `$level` in a text channel of your server, the bot should send a response similar to one of these:
If the response of the bot looks something like this:
It means you can't actually edit the configurations of the bot, ask the Server Owner or the Administrators to give you the needed permissions.
{% hint style="info" %}
If the bot is not responding to the level command, check our FAQ about this [topic](#the-bot-doesnt-respond-to-my-commands)
{% endhint %}
***
### What is the prefix and how do I change it?
By default the prefix of the bot is **`$`**, to modify it follow these steps:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Server Configs**
3. Update the prefix editing the **Command Prefix** field
4. **Save** changes
***
### How do I let my support team see into a ticket?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **General section**
4. Select the Support Team roles you want to be able to see into your tickets
5. **Save** changes
For more information on the topic, check the [Support Team Roles Documentation](/beta-docs/dashboard/panel-configs/general-options#support-team-roles)
{% hint style="warning" %}
Take into account that your new Support Team Roles will only be able to see new tickets, the settings won't apply to old tickets.
{% endhint %}
***
### How do I make a ticket ping my support when it's created?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the Panel's **Settings**
4. Open the **Ticket Options** menu
5. Click on **Edit Ticket Message**
6. In the **Message Text** field place one of this two options
* `{@Role Name}` (Case Sensitive)
* `{Role ID}`
7. **Save** changes
{% hint style="info" %}
Make sure to replace the `Role Name` or `Role ID` with the Name or ID of the role you want to ping
{% endhint %}
***
### How do I set a transcript channel?
A transcript is the HTML file that contains the messages of the ticket, for more information on what transcripts are, check our [documentation on it](/beta-docs/dashboard/panel-configs/logging-options#transcript-channel)
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Go into the **Transcript section**
4. Select a **Transcript Channel**
5. **Save** changes
***
### How do I limit the number of tickets a user can create?
To prevent a single user from opening several tickets on your server at once, you can restrict the amount of tickets they can create in two ways:
#### Global Limit
You can restrict the amount a user can open across all your panels, to update this limit follow this process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Server Configs**
3. Update the **Global Ticket Limit** field
4. **Save** changes
#### Panel's Ticket Limit
The second alternative is to limit the amount of ticket a user can create per each panel, for that do these steps:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Go into the **Limits Option**
4. Update the **Ticket Limit** counter
5. **Save** changes
***
### How do I set what category tickets are created in?
By default all of your tickets will be placed at the top of your server, to change this:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Category Options**
4. Select a category at the **Category Open** picker
5. **Save** changes
***
### How do I set what category tickets are moved to when closed?
If no category is set, whenever the tickets are closed they will be placed on the top of the server, to change that follow this process:
If no category is set, whenever a ticket is closed, it will remain in the category selected for [opened tickets](/beta-docs/dashboard/panel-configs/category-options#category-createdopened). If no category is set there, tickets will remain at the top of the channel list. To change that follow this process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Category Options**
4. Select a category at the **Category Closed** picker
5. **Save** changes
***
### How do I set the permissions for tickets?
You can modify the set of permissions Ticket Tool will apply whenever tickets are opened or closed, to do so:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Permission Options**
4. Select what type of permissions you want to change
5. Modify permissions using the    buttons
6. **Save** changes
***
### How do I create a panel?
This is the core of Ticket Tool, so its important to do the adequate process:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Click on the **green plus button** at the top right of the screen
3. Give your panel a **name**
4. Click once on **Create**
{% hint style="info" %}
We highly recommend to check our [Setup Documentation](https://github.com/Ticket-Tool/TTDocs/blob/beta-docs/debugging/setup.md) in order to set the bot
{% endhint %}
***
### How do I send a panel to my Discord?
Once you have created a panel make sure to send it:
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Identify a panel to send
4. Choose the channel from the picker
5. **Send** the panel
***
### How do I add or remove users from a ticket?
For such purpose Ticket Tool counts with two commands:
* `$add User / Role`
* `$remove User / Role`
Or, the slash version of both commands:
* `/add User / Role`
* `/remove User / Role`
You can also add the specific ticket you want to add or remove a user/role from at the end of the prefixed command. Use the ticket option when using slash commands. This is particularly useful if you don't want to execute the commands in the same ticket channel but rather in a private channel. Example:
* `$add User / Role #channel`
* `$remove User / Role #channel`
{% hint style="info" %}
You can either mention the user or role you want to add/remove, or use its ID
{% endhint %}
***
### How does claiming work?
{% hint style="info" %}
This feature is exclusive from the [Premium System](https://tickettool.xyz/premium)
{% endhint %}
Claiming allows your Support Team to claim and be assigned to a ticket, for more information on how this module works please check out our [Claiming Documentation](/beta-docs/dashboard/panel-configs/claiming-options)
***
### How much is premium and how many servers can I use it on?
Our premium subscriptions are $8 per month or $66 yearly and can be purchased directly through [our website](https://tickettool.xyz/premium). For any billing question join our [Support Server](https://tickettool.xyz/support)
{% hint style="warning" %}
Please note that users purchasing premium from Discord's app store have limited control over managing it. You cannot purchase annual subscriptions nor transfer them to any other server. We strongly recommend you purchase premium through our dashboard. For more information, please visit our [Premium page](https://tickettool.xyz/premium).
{% endhint %}
***
### How can I select or transfer the server for my premium subscription?
1. Head to our [Subscriptions Page](https://tickettool.xyz/billing)
2. Click **Manage** under your active subscription
3. On the left side of the panel, click on **Add Server** or use the transfer icon to select a new server
{% hint style="warning" %}
Please note that changing the server your subscription is redeemed on can not be done for Discord subscriptions. To purchase premium directly with us please, visit our [Premium Page](https://tickettool.xyz/premium).
{% endhint %}
***
### I've lost access to my Discord account, how do I get my subscriptions back?
It is important to note that your subscription is **not directly linked** to your Discord account, but rather it is linked to the email that you purchased premium with. In order to change the account that can manage your subscriptions, please open a billing ticket in our [Support Server](https://tickettool.xyz/support) and request the change by providing us:
* The email you created the subscription with
* The ID and username of the account that will manage the subscriptions
* The latest invoice for the subscription
***
### I have a premium key, how do I use it?
To use, redeem or transfer a premium key, please reach out to our Billing Team in our [Support Server](https://tickettool.xyz/support).
***
### How can I subscribe to premium and which payment methods can I use?
You can subscribe using by visiting the [Premium tab](https://tickettool.xyz/dashboard/server_id/premium) in your server's dashboard or by going into the [premium purchase page](https://tickettool.xyz/premium-purchase) directly. We accept the following payment methods:
* All major debit & credit card
* PayPal
* Google Pay (Chrome Only)
* Apple Pay (Safari Only)
***
### How does Ticket Tool store transcripts?
Ticket Tool does **not** store any transcripts at all, once it generates the transcript it's sent as a message to your Discord server, (we delete it from our systems to keep your data's privacy). All of our transcripts are stored directly on Discord's servers, we don't have any kind of access to them, once you delete the message in which the bot sent the HTML file Discord will remove it from it's cache and won't be accessible any longer. The URL to our website is just a rendering of the file stored in Discord's CDN.
***
### How do I set a custom emoji in my buttons?
1. Go into the [Dashboard](https://tickettool.xyz/manage-servers)
2. Open the **Panel Configs**
3. Open the **Button Options** page
4. Select a button and open it's **Settings**
5. Click the **Select** button in the **Button Emoji** field
6. Head to the β³ section inside the Emoji picker
7. Select the new emoji
8. **Save** changes
# About
General information on how to use the dashboard to set the bot.
The Dashboard is the main place through which you are going to edit the settings of the bot in your server. You can access to your dashboard by [clicking here](https://tickettool.xyz/manage-servers) or following these steps:
When you click on **Manage** under a server name, it will send you to that server's Dashboard homepage - which is the [Panel Configs](/beta-docs/dashboard/panel-configs). This is where you can start configurating your support tickets!
On your left side you'll be able to see the navigation bar with the following options:
{% hint style="info" %}
**Note:** If you are on mobile, you should click on the three line menu you will find on the **left top corner** to display the **Navigation** menu.
{% endhint %}
Now, go ahead and check the rest of the documentation on each one of the Dashboard sections:
* [Server Info](/beta-docs/dashboard/server-info)
* [Server Configs](/beta-docs/dashboard/server-configs)
* [Command Configs](/beta-docs/dashboard/command-configs)
* [Panel Configs](/beta-docs/dashboard/panel-configs)
* [Custom Commands](/beta-docs/dashboard/custom-commands)
* [Dashboard History](/beta-docs/dashboard/dashboard-history)
* [Statistics](https://docs.tickettool.xyz/dashboard/statistics)
# Server Info
Information given by the Server Info page.
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Server Info** Tab
This part of the dashboard will show you a brief resume of your server's Ticket System information. But, first of all:
{% hint style="info" %}
**How can I access my Server Info?**\
By default whenever you open your server's dashboard, it will get you here. As reference:
{% endhint %}
Once you are in the Server Info you can see three panels: Ticket Info, Bot Permission Info and Server Info.
### Server Info
Finally you'll be able to see general stats of your server as shown above.
# Customize Bot
**Customizing your bot's appearance!**
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/dashboard)\
> Select your server\
> Go to the **Customize Tab** Tab
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Here you will be able to further customize several aspects of Ticket Tool for your server. Please note this only changes the profile of Ticket Tool within **your server only** and is not a whitelabeled instance of the bot. It will continue to behave and appear as Ticket Tool in Direct Messages.
## Avatar
This is the profile picture. You can upload an image or GIF to replace the default Ticket Tool profile logo for your active bot. The recommended dimensions are 1024 x 1024 pixels.
## Banner
You can upload an image or GIF to replace the default Ticket Tool banner. The recommended dimensions are 680 x 240 pixels.
## Bio
You can edit the bot's about me section here. You can leave it blank if you would like to have no about me listed. There is a character limit is 190 characters.
{% hint style="info" %}
You can use the red π icon to revert back to the default Ticket Tool profile
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Command Configs
Customizing your commands' permissions
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Command Configs** Tab
## Command Configs
{% hint style="info" %}
Here, you can enable or disable specific commands. You can also set which channels these commands should be used in, and who can use the commands.
{% endhint %}
This is how you navigate the dashboard to get to `Command Configs`:
## Enabling and Disabling Commands
Use the slider by each command to turn it on or off. When it is green, the command is enabled. When red, it is disabled.
When a command is disabled, it can no longer be used by anybody on your server.
### Support Team Only
When enabled, the command can only be run by users with a [Support Role](/beta-docs/dashboard/panel-configs/general-options#support-team-roles) in a ticket.
### Allowed Channels
A list of whitelisted channels the command can be run in.
{% hint style="info" %}
Overrides [**Disabled Channels**](#disabled-channels)
{% endhint %}
### Disabled Channels
A list of channels the command cannot be used in.
### Allowed Roles
A list of roles that can run the command.
{% hint style="info" %}
Overrides [**Disabled Roles**](#disabled-roles)
{% endhint %}
### Disabled Roles
A list of roles that cannot run the command.
{% hint style="success" %}
Now youβve edited some settings, make sure to press the green βSaveβ button
{% endhint %}
# Server Configs
Modifying the core settings of your server.
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Server Configs** Tab
## Server Configs
Here you will be able to edit the core settings of Ticket Tool in your server. To get to the Server Configs page, log into the Dashboard, and click on **Server Configs** in the left sidebar. As shown below:
### General Options
#### Command Prefix
* The prefix for **all** of the bot's commands. By default the bot's prefix will be `$`.
{% hint style="info" %}
If you update your prefix to `!` then your help command will be `!help`.
{% endhint %}
#### Dashboard Roles
* Select the roles that will be able to edit the whole dashboard settings, this is different from a Support Team Role as explained in the [General Options Documentation](/beta-docs/dashboard/panel-configs/general-options)
#### Blacklist Roles
* Users with one of this roles won't be able to use any command nor interact with Ticket Tool's buttons.
{% hint style="info" %}
A common practice is to blacklist roles related to sanctions in the server, such as **Muted** role, this in order to prevent moderation problems.
{% endhint %}
#### Global Ticket Limit
* This is the maximum amount of tickets a single user can have opened across all your panels simultaneously.
### Premium Bot
Ticket Tool is a free Discord bot! Nonetheless you can access to more features by subscribing to our [Premium Plan here](https://tickettool.xyz/premium), being a Premium User will give you the possibility to use the premium bot! Which will have better response times as it is used in a fewer amount of servers than the primary bot.
If you want to use the premium bot, make sure to invite it using the **Invite Premium Bot** button in your Server Configs and selecting `Ticket Tool#6207 (Premium Required)` in the bot selector, finally, **Save** changes and you are good to go!
{% hint style="success" %}
If you have an active premium subscription in your server, you can choose between using the Free bot or the Premium one! All features will work in any of the bots as long as you keep your subscription.
{% endhint %}
{% hint style="warning" %}
If you moved from the free bot to the premium one, make sure to resend your panels with the premium one as the free one won't be able to communicate with the premium one.
{% endhint %}
### Server Storage Options
Discord has a 2,000 channel creation limit per server, per day. On the other side your server can only have 500 channels at the same time! If your server has a massive usage of our bot you should consider using this feature to avoid reaching theses limits!
Storage will clear your deleted tickets and place them into a category waiting to be used as part of new tickets, once a ticket is deleted all the messages are purged as well as the settings in order to make it usable for the bot in a potential new ticket!
#### Storage Categories
All the channels belonging to these categories will be recycled by the bot to be used as new tickets!
{% hint style="warning" %}
**All channels**, regardless if tickets or not will be recycled as long as they are in a Storage Category
{% endhint %}
### Bot
By default, Ticket Tool ignores commands sent by other bots. Any bot whose ID you introduce in this field, will bypass this restriction. Allowing Ticket Tool to listen and react to commands actioned by such bots. Separate IDs with a comma if you're introducing multiple IDs.
### Google Drive Transcripts (Server Owner Only)
For further customization, Ticket Tool allows you to save your server's transcripts to your Google Drive! In this part of the dashboard you will be able to select the Google account to which Ticket Tool will save the transcripts, to customize the folder to which each panel's transcripts are saved, review your [Transcript Options](/beta-docs/dashboard/panel-configs/transcript-options#store-transcript-on-google-drive)
{% hint style="danger" %}
**In order to use this feature you must be the server owner**
{% endhint %}
### Config Backup & Restore (Server Owner Only)
One of the most special features Ticket Tool counts with is the ability to transfer the bot's configuration on one of your servers to a new one with out the need of going manually setting by setting, this is what we call **Backup and Restore**. You can transfer your panels and custom commands!
{% hint style="warning" %}
If you had a timed premium key you will need to contact our [Support Team](https://discord.gg/TicketTool) to transfer the remaining time into your new server
{% endhint %}
{% hint style="warning" %}
Take into account that your tickets will **NOT** be transfered to the new server, you should save the transcripts of the tickets if you want to keep their contents.
{% endhint %}
{% hint style="danger" %}
**In order to use this feature you must be the server owner**
{% endhint %}
#### Creating a backup
Follow these steps to properly create a backup:
1. Log into the [Dashboard](https://tickettool.xyz/dashboard)
2. Click on **Manage** under the server you want to create a backup for
3. Open the **Server Configs**
4. Scroll to the bottom of the page and go into the **Config Backup & Restore (Server Owner Only)** section and click on **Backup and Restore**
5. Finally click on **Generate New Key** and copy the new key!
You should only create a key once, the bot will copy the active settings of the key whenever it's used, you should only consider to create a new key if you think it has been compromised.
{% hint style="danger" %}
Keep this key safe, we recommend to have it **outside** of your Discord server in case it gets deleted.
{% endhint %}
This process is also explained as shown here:
#### Restoring backups
To use a backup key, you need to go to the [**Dashboard**](https://tickettool.xyz/dashboard) of the server to which you want to transfer the information, after which you will need to go to **Config Backup & Restore (Server Owner Only)** and click on the **Backup and restore** hyperlink, then place the restore key in **Restore from backup key**, then select the settings you want to copy into the new server, and finally click **Restore Configs.**
With that, all the selected configurations will be taken into the new server without you doing it one by one, enjoy the bot in your new server π
Restoring a Backup illustrative GIF:
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Panel Configs
What are panels, how do I customize them?
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab (Will be the default land page)
### What are Panels?
Panels are Ticket Tool's core, through them your users will be able to create tickets! A panel can have [Buttons](/beta-docs/dashboard/panel-configs/panel-options), or a [Dropdown](/beta-docs/dashboard/panel-configs/dropdown-style).
#### How to create a panel?
Click the **`+`** emoji on your panel selector and give it a name!
### Panel Settings
#### Clone
Create a duplicate of the currently selected panel, the new panel will work as a new separate panel, meaning that settings from the original panel won't be updated on the duplicate panel once the cloning has been done.
#### Rename
Change the name panel you are editing. You can't change the number value or rearrange it.
#### Send
Select a channel to send your panel to, make sure Ticket Tool has the needed permissions to carry on this aciton.
#### Set Count
Set the ticket count of the panel to a custom value.
#### Update
Update a sent panel previously sent to the current version of it, copy the message URL and paste it to do so.
#### Delete
Delete the selected panel
{% hint style="danger" %}
This is an irreversible action so be sure before doing it.
{% endhint %}
{% hint style="info" %}
You must always have at least one panel on the dashboard. If you plan on deleting your last panel, create a new panel first to avoid an error.
{% endhint %}
### Frequently Used Configs
Here you can find a quick access to common settings:
* [Support Team Roles](/beta-docs/dashboard/panel-configs/general-options#support-team-roles)
* [Category Created/Opened](/beta-docs/dashboard/panel-configs/category-options#category-created-opened)
* [Panel Message](/beta-docs/dashboard/panel-configs/panel-options#panel-message)
* [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message)
# General Options
The core settings of every panel
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **General** Options
### Role Settings
#### Support Team Roles
In this field you'll be able to select the roles that, by default, will have access to tickets as well as to commands and buttons that have been marked to be Support Team Only.
#### Additional Roles
This fields allows you to pick a different group of roles to get assigned different permissions from your support team roles. One of the most common uses given to this feature is having an observer role, i.e. someone who can see the ticket but doesn't have the permission to talk on it.
{% hint style="info" %}
To edit the permissions both groups are assigned whenever the ticket is opened or closed visit the [Permissions Options](/beta-docs/dashboard/panel-configs/permission-options)
{% endhint %}
### Ticket Value Settings
#### Ticket Padding
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Ticket padding will modify the length of the [Ticket Count](/beta-docs/dashboard/panel-configs#set-count) (i.e. the ticket's "serial" number, also known as the [{count}](/beta-docs/dashboard/panel-configs/variables) variable) by padding out the length with zeroes in order to fit the specified length. For a clearer explanation see the examples of how the ticket padding will work when the panel has different [Ticket Count](/beta-docs/dashboard/panel-configs#set-count) values:
**Padding for a {count} of 57**
| Padding Value | {count} output |
| -------------- | -------------- |
| 0 | 57 |
| 1 | 57 |
| 2 | 57 |
| 3 | 057 |
| 4 *\[Default]* | 0057 |
| 5 | 00057 |
**Padding for a {count} of 7**
| Padding Value | {count} output |
| -------------- | -------------- |
| 0 | 7 |
| 1 | 7 |
| 2 | 07 |
| 3 | 007 |
| 4 *\[Default]* | 0007 |
| 5 | 00007 |
{% hint style="info" %}
The maximum padding you will be able to set is 20, if you try to set further than that the dashboard will automatically adjust it.
{% endhint %}
### Other Settings
#### Two Step Close
When **enabled**, upon pressing the close button Ticket Tool will give the users the option to confirm they are willing to close the ticket or cancel this action.
If you want tickets to be closed as soon as the close button is pressed you should **disable** this option.
#### Two Step Ticket
When **enabled**, upon pressing the close button Ticket Tool will allow the ticket to have a closed state in which you'll have access to the [Moderator Message](/beta-docs/dashboard/panel-configs/moderator-options#moderator-message) which includes the reopen, delete and save transcript options.
If you want tickets to be **deleted** as soon as the close button is pressed you should **disable** this option.
#### Auto Pin Ticket
When enabled, this option will make Ticket Tool to automatically pin the [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message) as soon as the ticket is created and the core message sent, this allows your team to quickly access to the Close and Claim buttons, if they have been enabled.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Category Options
The categories in which tickets live
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Category** Options
### Category Created/Opened
Select a category for tickets belonging to this panel to be created on.
### Category Closed
Likewise to the previous setting, pick a category for tickets to be moved when closed, leave this option empty if you want the tickets to stay in the same category they were created on, if any. Note that if you have disabled the [Two Step Ticket](/beta-docs/dashboard/panel-configs/general-options#two-step-ticket) feature, tickets will be directly deleted instead of moved to the assigned category here.
### Overflow Categories
Discord only allows to stack up to 50 channels per category. Meaning, if you already have 50 tickets in one category, Ticket Tool will not be able to place a new ticket in that category. To prevent that, Ticket Tool counts with overflow categories, which are additional categories. Once your main category is full, the bot will go ahead and place the new ticket in the next one available. Simply select multiple categories in the category picker.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Ticket Options
Settings related to the Tickets belonging a given panel
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/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.
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](/beta-docs/dashboard/panel-configs/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**](/beta-docs/dashboard/panel-configs/general-options#two-step-ticket) within your panel's [**General Options**](/beta-docs/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](/beta-docs/dashboard/panel-configs/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.
{% hint style="info" %}
You can use our [Supported Variables](/beta-docs/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.
{% 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](/beta-docs/dashboard/panel-configs/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 %}
# Moderator Options
Moderator messages and their customization
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Moderator** Options
### Premium Features
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
#### Closed Message
Here you'll be able to customize the message sent by Ticket Tool whenever a ticket is closed, by default the message will be:
#### Opened Message
Here you can edit the message sent by Ticket Tool whenever a ticket is reopened, by default the message will be:
### More customization
#### Moderator Message
Whenever a ticket is closed Ticket Tool will send a moderator message containing by default the **\[`Reopen`]**, **\[`Delete`]** and **\[`Transcript`]** buttons, to customize them check our [Message Buttons documentation](/beta-docs/dashboard/panel-configs/button-options#message-buttons). The default moderator message is shown below:
#### Delete Message
As soon as a ticket is set to be deleted Ticket Tool will send the following default deletion message, which you can customize:
{% hint style="info" %}
Both the Moderator and Delete messages can be widely customized by being [Premium](https://tickettool.xyz/premium) server, nonetheless you can edit the embeds' description up to **250 characters** for free!
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Permission Options
Editing the permissions for roles and users in tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Permission** Options
{% hint style="info" %}
#### General Rules
* **Opened Permissions** are applied to each group whenever a ticket is **opened**, or **reopened**.
* **Closed Permissions** are applied to each group whenever a ticket is **closed**.
{% endhint %}
{% hint style="warning" %}
#### Important Note
Ticket Tool is not able to set a permission override if the bot does not count with that permission globally (server-wise). Therefore, if you have set a permission but it is not being applied on your tickets, make sure Ticket Tool has that permission. Any permission marked as orange π on your dashboard will be ignored by Ticket Tool when opening and closing tickets.
{% endhint %}
### Support Team Permissions
The permissions you set on these menus will be granted to the [Support Team Roles](/beta-docs/dashboard/panel-configs/general-options#support-team-roles).
### User Permissions
The permissions set here will be applied to:
* The user who opened the ticket
* Users added when using the `$add` command
### Additional Roles Permissions
The permissions you set on these menus will be granted to the [Additional Roles](/beta-docs/dashboard/panel-configs/general-options#additional-roles).
### Everyone Role Permissions
The permissions set here will be applied to the **`@everyone`** role of your server.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Button Options
All buttons in a single place!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Buttons** Options
On this tab of your dashboard you'll be able to access all of the buttons Ticket Tool offers you! Here you'll find a list of all buttons as well as the message you can find them:
* Create Ticket - [Panel Message](/beta-docs/dashboard/panel-configs/panel-options#panel-message)
* Close Ticket - [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message)
* Cancel Close - [Close Ask Message](/beta-docs/dashboard/panel-configs/ticket-options#close-ask-message)
* Re-Open Ticket - [Moderator Message](/beta-docs/dashboard/panel-configs/moderator-options#moderator-message)
* Confirm Close - [Close Ask Message](/beta-docs/dashboard/panel-configs/ticket-options#close-ask-message)
* Delete Ticket - [Moderator Message](/beta-docs/dashboard/panel-configs/moderator-options#moderator-message)
* Transcript - [Moderator Message](/beta-docs/dashboard/panel-configs/moderator-options#moderator-message)
* Claim Ticket - [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message)
### Message Buttons
Below you'll find all of the settings a Ticket Tool button can possibly have across messages.
#### Show this button
If **disabled** this button won't be added to your Close Ask Message.
#### Button Emoji
When **enabled**, the button will include indicated emoji. You can pick the emoji by using our selector or by indicating one of the following manual inputs:
* For custom Discord emojis use `` or `` for animated emojis
* For regular emojis use their unicode value, **not** their Discord name
#### Button Text
Enter button text here, if left empty the button will be emoji-only
{% hint style="warning" %}
All buttons **must** have either the text label or the button emoji.
{% endhint %}
#### Button Color
Select one of the four button colors **supported by Discord** to further customize your buttons! The default color for all buttons is gray.
#### Support Team Only
Enabling this option will make the button only being actionable by members who have a [Support Team Role](/beta-docs/dashboard/panel-configs/general-options#support-team-roles).
#### Allowed Roles
Users that have a role from this selector will be able to use this button.
#### Disabled Roles
Any user with a role from this set won't be able to use the button you are editing.
{% hint style="info" %}
If a user has both `Allowed` and `Disabled` roles, they will be able to use the button. `Allowed` roles override `Disabled` ones.
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Message Options
All messages in a single place!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket Options**, click on **Messages** Options
On this tab you'll have a list to quickly access all messages you are able to edit with Ticket Tool!
* [Panel Message](/beta-docs/dashboard/panel-configs/panel-options#panel-message)
* [Closed DM](/beta-docs/dashboard/panel-configs/automation-options#send-direct-message-when-ticket-closed)
* [Created DM](/beta-docs/dashboard/panel-configs/automation-options#send-direct-message-when-ticket-created)
* [Claimed Message](/beta-docs/dashboard/panel-configs/claiming-options#claimed-message)
* [Unclaimed Message](/beta-docs/dashboard/panel-configs/claiming-options#unclaimed-message)
* [Closed Message](/beta-docs/dashboard/panel-configs/moderator-options#closed-message)
* [Opened Message](/beta-docs/dashboard/panel-configs/moderator-options#opened-message)
* [Moderator Message](/beta-docs/dashboard/panel-configs/moderator-options#moderator-message)
* [Delete Message](/beta-docs/dashboard/panel-configs/moderator-options#delete-message)
* [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message)
* [Close Question](/beta-docs/dashboard/panel-configs/ticket-options#close-ask-message)
* [Transcript Message](/beta-docs/dashboard/panel-configs/transcript-options#transcript-message)
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Escalate Options
Transferring tickets between panels
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **General Ticket**, click on **Escalate** Options
With escalation, you can transfer a ticket between different panels
### Panel List
You can select up to 25 panels to which a ticket can be transferred to.
{% hint style="warning" %}
Thread Style tickets can not be escalated into a different panel
{% endhint %}
### Update Options
Here you will be able to select which options are to be updated once the ticket is transferred:
* **Category:** If the category limit allows it, the ticket will be moved to the target panel [configured category](/beta-docs/dashboard/panel-configs/category-options).
* **Name:** If there is no renaming cooldown, the ticket will be renamed following the [Ticket Name options](/beta-docs/dashboard/panel-configs/ticket-options#ticket-opened-channel-name) of the target panel.
* **Permissions:** All [Permission Options](/beta-docs/dashboard/panel-configs/permission-options) will be set as new within the target panel.
* **Automatically unclaim ticket:** Requires the panel to have enabled the [Claiming Options](/beta-docs/dashboard/panel-configs/claiming-options).
### Additional Settings
* **Send Custom Message:** Allows you to create a custom message to be sent along on the ticket. Supports [special escalation variables](/beta-docs/dashboard/panel-configs/variables#special-variables)
* **Send Ticket Message:** This will send the target panel's [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message) in the transferred ticket
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
### Available Variables
| **Variable** | **Description** |
| -------------------- | ------------------------------------------------------------------------------------ |
| `{escalate.reason}` | The reason that was given when using the `/escalate` command |
| `{escalate.panel}` | The number of the panel the ticket was escalated to |
| `{escalate.panel.X}` | Replacing `X` with the number of the selected panel will return the text `escalated` |
# Transcript Options
Settings for saving your transcripts
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Transcript** Options
{% hint style="info" %}
#### Important Notes about Transcripts
Transcripts are capped at **1000 messages**. Having a [Premium subscription](https://tickettool.xyz/premium) will allow you to use the `$transcript` command in non-ticket channels and will allow you to embed **up to 8mb** worth of attachments on your transcripts.
{% endhint %}
### Transcript Channel
This setting allows you to pick the channel to which transcripts will be sent when using the **`Transcript`** button, when using the `$transcript` command and when doing an automatic save as we'll see later.
### Store Transcript on Google Drive
{% hint style="danger" %}
**In order to customize these settings you must be the server owner**
{% endhint %}
Here you can choose the folder under which the transcripts of this panel will be saved. Transcripts will be saved to your drive upon any of these actions:
* When someone runs the `/transcript` command
* When a transcript is automatically saved to your **transcript channel**
* When a transcript is automatically DMed to the **ticket owner**
Transcripts on your Drive folder will follow this naming convention: `ServerID:ChannelId:TicketName`
{% hint style="warning" %}
Every time a transcript is saved, even if it's 2 transcripts for the same ticket, it will be saved to your Drive!
{% endhint %}
#### Disable attaching an HTML copy to the transcripts message.
Enabling this option will remove the HTML from your transcript embeds and will save it exclusively to Google Drive.
{% hint style="danger" %}
Deleting a transcript from your Drive will effectively delete the transcript! This will make it inaccessible from Discord, so be careful when deleting any files.
{% endhint %}
### Premium Features
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
#### Transcript Message
This setting will allow you to customize the message that gets sent along the transcript once it's saved.
#### Direct Message Transcript
Enabling this options will make the transcript to be DMed to the ticket creator upon closure and/or deletion, you can choose which option should trigger it.
#### Auto Save Transcript
Enabling this options will make the transcript to be saved into your Transcript Channel upon closure and/or deletion, you can choose which option should trigger it.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Logging Options
Setting up the action logging for your tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Logging** Options
### Logging Channel
Choose a channel to which the log-enabled actions should be logged into.
### Logged Actions
You can enable all of the following ticket actions in your settings for them to be logged on your Logging Channel:
* Ticket Created
* Ticket Closed
* Ticket (Re)Opened
* Ticket Renamed
* Ticket Deleted
* Transcript Saved
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Automation Options
Automate your ticket system!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Automation** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
### Missing user check
When enabled, this setting allows you to decide what should be done if the ticket creator leaves the server: deleting or closing the ticket.
### Send Direct Message when ticket closed
If enabled, the ticket creator will be DMed the set message whenever the ticket is **closed**.
### Send Direct Message when ticket created
If enabled, the ticket creator will be DMed the set message once the ticket is **opened**.
### Automation Editor
{% hint style="warning" %}
* Automations stop running after 7 days or whenever the ticket is closed (if the ticket is reopened automations will run again)
* You can have up to 10 automations per panel
{% endhint %}
{% hint style="info" %}
All details that are unlocked by enabling the **`Show Advanced Automation`** are indicated by a π§ emoji.
{% endhint %}
#### Check for message
* **Check to see if a message** β is found within X time **or** not found within X time
* **From** β This setting refers to whose message needs to be found, or not, within the ticket; Anyone, the Ticket Owner (the user who created the ticket / [**`{ticket.user}`** variable](/beta-docs/dashboard/panel-configs/variables#ticket-variables)) or the [Support Team](/beta-docs/dashboard/panel-configs/general-options#support-team-roles).
* **For** β The time frame in which the message should be looked for, you can choose a preset or insert a custom number in the right box (in seconds).
* **It should check** β Once and stop **or** until stopped. You can stop it by using the `/automation` command or by closing the ticket.
* **π§ If a message is found in x time** β Either if the timer you choose should **restart** or **continue**. Note that this will setting will only appear when you have selected the `not found within X time` check type.
* **If a message is (NOT) found** β You can choose between sending a [Custom Command](/beta-docs/dashboard/custom-commands), Closing **or** Deleting the ticket.
* **π§ After the action runs it should** β Choose if the bot should **keep** or **continue** checking for messages or the abscense of them.
{% hint style="info" %}
**Important:** This automation's minimum **`For`** condition is 5 minutes, anything below that will default to 5 minutes.
{% endhint %}
#### Triggers
{% hint style="info" %}
These settings apply for all of these automation triggers:
* Ticket Closed
* Ticket Re-Opened
* Ticket Created
* Ticket Owner Left Server
* Close Ask Message
{% endhint %}
* **Once triggered run the action** β You can choose between sending a [Custom Command](/beta-docs/dashboard/custom-commands), Closing **or** Deleting the ticket.
* **π§ Delay running the action for** β Choose how long after the trigger should the selected action be executed, you can choose a preset or insert a custom number in the right box (in seconds.)
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Limit Options
Limits for Ticket Panels!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Limit** Options
### Tickets Open
#### Open tickets each user
This number stands for the amount of tickets a single user can have **opened** at once in the panel you are currently editing, i.e. **only open tickets are counted** towards this limit.
#### Open tickets all users
The amount of tickets this panel can have **opened** simultaneously.
#### Roles that bypass open limits
The set of roles that will be able to skip the given limits for open tickets.
### Tickets Closed
{% hint style="warning" %}
* The limits you'll find below are the limits for tickets that are closed but not deleted.
* These limits are checked when the ticket is about to be **created**, i.e there can be more closed tickets than your limit depending on your currently opened tickets.
{% endhint %}
#### Closed tickets each user
The amount of **closed** tickets that each user can have at once in the selected panel.
#### Closed tickets all users
The limit of tickets that can be **closed** at once simultaneously by all your users in **this panel**.
#### Roles that bypass closed limits
The set of roles which will be able to skip the given closed limits.
### Time Schedule
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
This feature will allow you to set time frames, in a given timezone, for which your panels should be available to be used by your server members
#### Enable Schedule
**Enabling** this feature will apply the schedule availability to your panel. Make sure to select the corresponding timezone for your server to prevent any discordance with the selected time frames.
#### Roles that bypass the schedule
Select the roles that should be exempt from this setting and be able to open tickets regardless of the availability set by the schedule.
#### Schedule Notification Message
Here you can customize the message the bot will answer with whenever users try to open a ticket out of the times you've selected.
Below this option you can select the custom times using a table.
{% hint style="info" %}
**Note:** Although the table is given in 24h format, we've included AM and PM headers to make it easier to select the time frames of your prefence in case you aren't used to this format.
{% endhint %}
#### Replace Ticket Message with Schedule Notification Message
Enabling this feature will replace your [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message) with the Schedule Notification Message you set earlier. Note that enabling this won't stop the ticket from being created, instead it will create it with a whole different message but the rest of settings will work the same.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Claiming Options
Customize ticket claiming settings, permissions, actions, and messages
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Claiming** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
Ticket Tool allows your [Support Team](/beta-docs/dashboard/panel-configs/general-options#support-team-roles) to claim or be assigned to a given ticket. This menu allows full customization related to this feature!
### Enable Claiming
If this setting is disabled, the rest of customizations done within this menu won't take any effect.
### Ticket Actions
#### Only the user who claimed can un-claim
When enabled, only the ticket claimer will be able to unclaim the ticket.
#### Only the user who claimed and ticket owner can use ticket actions (Does not include claim/un-claim)
When enabled, only the ticket claimer and the owner will be able to use all of the ticket actions (open, delete, transcript), this doesn't include the claiming ones.
{% hint style="info" %}
These settings won't affect users who have a [Dashboard Role](/beta-docs/dashboard/server-configs#dashboard-roles) or the **`Administrator`** permission on your server.
{% endhint %}
#### Overwrite the claimed user instead of unclaiming if already claimed
When enabled, if the ticket has been already claimed, and another user tries to claim, it won't unclaim but will change the ticket claimer.
#### Allow ticket owner to claim the ticket, if permission changes are disabled.
This will allow the ticket creator ([`{ticket.owner}`](/beta-docs/dashboard/panel-configs/variables#ticket-variables)) to claim its own ticket. Note that this feature will only be usable when the [Change other support team permissions when claimed](#change-other-support-team-permissions-when-claimed) feature is **disabled**.
### Enable claim name
If enabled, the text placed here will be the name given to the ticket channel whenever it's claimed, you can use our [Supported Variables](/beta-docs/dashboard/panel-configs/variables) in this field. If the ticket is unclaimed, then it will revert back to the [Ticket Opened Channel Name](/beta-docs/dashboard/panel-configs/ticket-options#ticket-opened-channel-name).
### Enable claim category
Choose a category for tickets to be moved to once they are claimed, you can select more than a single category to apply [Overflow Categories](/beta-docs/dashboard/panel-configs/category-options#overflow-categories).
### Ticket Claimed Roles
Select a set of roles that should be added and/or removed from the ticket owner once the ticket is **claimed**.
### Ticket Un-claimed Roles
Select a set of roles that should be added and/or removed from the ticket owner once the ticket is **unclaimed**.
### Change other support team permissions when claimed
Within this setting you can modify the permissions the support team roles get applied once a ticket is claimed. The ticket claimer will receive the [Support Opened Permissions](/beta-docs/dashboard/panel-configs/permission-options#support-team-permissions). This is often used to make tickets a read only channel for the rest of the team or to hide it.
### Claimed Message
Customize the message sent by Ticket Tool once the ticket has been claimed.
### Unclaimed Message
Edit the message sent by Ticket Tool once the ticket is unclaimed.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Form Options
Questionaries for ticket opening!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Form** Options
### Enable form
When **enabled**, before the ticket is created the user will receive a prompt to fill up your customized questionary.
### Auto display results
Enable this feature to attach an embed automatically to your [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message) which includes the responses summary for this form.
 
### Form Options
* Form Title β The title that will be displayed at the top of the form interaction.
* Question Title β The question or phrase the user will input an answer based on.
* Question Placeholder β The placeholder, or guide text, for the input field
* Required β Whether responding to the selected question should be mandatory before sending the form, or not.
* Multi-line Input β Whether to display the input field as a multi-line field, or not.
* Minimum Input β The minimum required amount of characters to be taken as a valid response, leave empty for 0.
* Maximum Input β The maximum amount of characters that should be used when responding to a form, leave empty for the maximum, which is 4000
{% hint style="info" %}
Note that you'll be able to add up to 5 individual questions per each form
{% endhint %}
### Cheatsheet
If you are new to Discord's application commands and its terminology, you may find this quick visual guide useful to better understand how the different sections will appear from a user's point of view
 
### Displaying Form Answers
To access the user's response to your question(s), you can either enable the automatic embed with the form results, as previously shown above or you can also use form variables!
You will need to use its corresponding `{create.form.x}` variable in your [Ticket Message](/beta-docs/dashboard/panel-configs/ticket-options#ticket-message)!
 
{% hint style="success" %}
For servers using the free plan, there is a limit of **250 characters** for your Ticket Message's embed description. If that's the case, then we would strongly recommend using the [Auto Display Results](#auto-display-results) feature to display your form answers ensuring no limit affects the response content.
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Integration Options
Add integrations to your tickets!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Advanced Settings**, click on **Integrations** Options
### Bloxlink for Roblox
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
This feature allows you to integrate the [Bloxlink Discord Bot](https://blox.link/) within Ticket Tool!
#### Roblox user integration using Bloxlink
Enabling this feature will enable access to Bloxlink variables within the selected panel as well as the auto display feature explained below.
#### Auto display roblox user on the Ticket Message as an additional embed
When enabled, this setting will add an embed containing the user's Roblox ID, the author field includes the URL to the Roblox profile.
{% hint style="info" %}
When having multiple accounts linked on [Bloxlink](https://blox.link/), the variables will show the information for the main account.
{% endhint %}
{% hint style="warning" %}
If the user doesn't have a Roblox account linked to Bloxlink the bot will skip adding the embed even if this feature has been enabled.
{% endhint %}
#### Bloxlink Variables
| **Variable** | **Description** |
| ----------------------- | ------------------------------------------------------ |
| `{roblox.name}` | The Roblox username |
| `{roblox.display.name}` | The Roblox user's display name |
| `{roblox.id}` | The ID of the Roblox account |
| `{roblox.url}` | Direct URL to the Roblox user url |
| `{roblox.created}` | The date in which the Roblox account was created |
| `{roblox.age}` | The age of the account given in days, months and years |
| `{roblox.verified}` | Wether this user has the verified badge or not |
| `{roblox.banned}` | Wether this user has been banned or not |
The [{ticket.user}](/beta-docs/dashboard/panel-configs/variables#ticket-variables) is the user whose account will be checked within Bloxlink for a linked roblox user.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Panel Options
Customizing your panel!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Panel** Options
### Attached Panels (Multi Panels)
### Multipanels
Multipanels are panels with multiple buttons attached to them - they can be set up using attached panels.
Here are the steps to create multipanels:
**Step 1:** Create a panel for each button you wish to have displayed under your panel. For example you might want a user report panel, a general support panel, etc.
**Step 2:** Attach your panels by adding them via the selection box in the attached panels section.
{% hint style="warning" %}
**Note:** if you're attaching all the panels to a panel called **English**, don't include **English** in the attached panels box (If you do this, it will create a duplicate button)
{% endhint %}
**Step 3:** Send the original panel (the one you are editing - it will be shown at the panel selection dropdown at the top of your screen) to the channel you wish.
Now you should have your own multi-panel!
{% hint style="info" %}
* Up to 25 panels can be combined into a single panel!
* The first panel will be sent to the channel like it was sent to the channel on its own, while the others will only have their buttons added to this panel. When a user clicks one of the buttons, a ticket is made through the corresponding panel.
{% endhint %}
The multipanels can be used for many things, such as using them to create tickets for a specific language, like in our [Support Server](https://tickettool.xyz/support)
### Buttons Per Row
When setting up multipanels you can choose what the maximum amount of buttons per row will be, this value must be between 1 and 5, i.e. the exceeding buttons from attached panels will be moved to the next row.
### Panel Message
Here you can customize the message your panel will have once it's sent by Ticket Tool, as well as the settings for your **\[`Create`]** ticket button, to know more about the settings of a button check our documentation on [Message Buttons](/beta-docs/dashboard/panel-configs/button-options#message-buttons).
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Command Style Tickets
Tickets created via commands!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Command Style** Options
Ticket Tool not only offers you the possibility to use [Panel Buttons](/beta-docs/dashboard/panel-configs/panel-options) and [DropDowns](/beta-docs/dashboard/panel-configs/dropdown-style) to create tickets, but it also allows you to use Commands!
#### Enable Command Style ticket creation
If this option is disabled the rest of the settings won't sort any effect. Once you have enabled this module, you'll be able to use the `$new` and `$ticket` commands! These commands have two **optional** arguments you can use when executing them:
> `$new User Reason`
{% hint style="info" %}
Note that **`User`** can be either the ID or a mention to the user you want to open a ticket in behalf of. These two commands allow you to use the **`{reason}`** variable inside your tickets!
{% endhint %}
So for example if I used:
> `$new 518666147441278998 Testing`
Ticket Tool would open a ticket for the user with ID **`518666147441278998`** with the **`{reason}`** variable being "Testing"
#### Delete command after creating ticket
If enabled, once the ticket has been created the trigger command will be deleted by the bot.
#### Bypass channel list and watch all of them
Whenever someone uses the `$new` or the `$ticket` command in **any channel** the bot has access to, it will create a ticket!
#### Channel to monitor for command $new and $ticket
This is the opposite of the previous option, you can actually select in which channels Ticket Tool should look for the **`$new`** command instead of looking in the whole server. For this option to be effective the **bypass must be off**.
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# DropDown Style
Using Dropdowns for ticket creation!
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **DropDown Style** Options
Dropdowns allow you to display several panels in the same select menu.
### Enable Select Style
In order to use dropwdons instead of [panel buttons](/beta-docs/dashboard/panel-configs/panel-options) this option must be on, otherwise regardless the rest of settings of the menu, buttons will be still used.
### Dropdown Editor
#### Display
The shown text on the select option, this is a **required** field.
#### Panel
The panel this option should open a ticket for, this is a **required** field.
{% hint style="danger" %}
Do **not** select twice the same panel, each option needs its own panel.
{% endhint %}
#### Emoji
The emoji that the option should be displayed, leave this field empty for no emoji.
#### Description
The text shown below the Display on the select option, leave this field empty for no description.
#### Placeholder Text
The text the select menu will display before selecting a panel option.
### Cheatsheet
For a clearer view of what a single panel looks like both in your Dashboard and Discord check the following example:
 
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Thread Style Tickets
Using threads instead of channels for your tickets
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs) Tab\
> Under **Panel Settings**, click on **Thread Style** Options
{% hint style="success" %}
Hey! You've came across a [Premium](https://tickettool.xyz/premium) exclusive setting π
{% endhint %}
To implement this feature you'll server must grant Ticket Tool the following permissions:
1. **`Create Private Threads`**
2. **`Send Messages in Threads`**
3. **`Manage Threads`**
### Enable thread style ticket creation
This setting will make the rest of the settings below to be usable by your ticket panel.
### Can non-mods invite people to this ticket?
When enabled, users that don't count with any of the [Support Team Roles](/beta-docs/dashboard/panel-configs/general-options#support-team-roles) will be able to also invite users to the thread.
### Auto add team to thread
Enabling this setting will automatically mention your [Support Team Roles](/beta-docs/dashboard/panel-configs/general-options#support-team-roles) in order to add them to the thread
### Channel to create your ticket threads under
The channel selected here wil be the parent channel for all of the thread tickets created for the selected panel.
{% hint style="danger" %}
The following features **aren't compatible** with the Thread Style Ticket options:
* The usage of **`/add`** and **`/remove`** commands
* [Claiming Options](/beta-docs/dashboard/panel-configs/claiming-options)
* [Permission Options](/beta-docs/dashboard/panel-configs/permission-options)
{% endhint %}
{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% endhint %}
# Supported Variables
Description of the variables you can use across your ticket system
A variable, just as in math, is something that can have a changing state. In your tickets you have access to certain variables whose value will vary among tickets, you can use these variables on the different fields of your ticket messages!!
Let's see a bit more about what each variable works for
### General Variables
| **Variable** | **Description** |
| --------------------- | ------------------------------------------------------------------ |
| `{server.name}` | Will display the server's name |
| `{server.id}` | The server's ID |
| `{server.icon}` | Direct URL to the server's icon |
| `{server.banner}` | Direct URL to the server's banner |
| `{channel.name}` | Name of the channel in which the variable is being used |
| `{channel.id}` | The ID of that channel |
| `{panel.count}` | The current count of the panel in which this message was triggered |
| `{panel.name}` | The name of the panel in which the variable is being used |
| `{panel.ticketLimit}` | The Ticket Limit for the current panel |
### Ticket Variables
| **Variable** | **Description** |
| ---------------------------------- | ----------------------------------------------------------- |
| `{ticket}` | Mention to the ticket channel in which the variable is used |
| `{ticket.id}` | The ID for the `{ticket}` channel |
| `{ticket.user}` / `{ticket.owner}` | The mention to the user who created the ticket |
| `{ticket.user.name}` | The name of `{ticket.user}` |
| `{ticket.user.id}` | The ID of `{ticket.user}` |
| `{ticket.user.nickname}` | The nickname of `{ticket.user}` |
| `{ticket.user.icon}` | Direct Url of the profile picture of the `{ticket.user}` |
| `{ticket.user.tag}` | The 4 digit discriminator, of the `{ticket.user}` |
| `{ticket.user.full}` | The username + the 4 digit discriminator of `{ticket.user}` |
{% hint style="info" %}
* `{ticket.owner}` is just an alias of `{ticket.user}` meaning it has all of it's sub-variables `{ticket.owner.name}` and so on.
* This set of variables as it name tells, will only work within tickets, if you use it within a tag it will only render when used within a ticket.
{% endhint %}
### Author Variables
Let's talk about the **`{author}`** variable. Any action, such as opening, closing, claiming, deleting etc, a ticket, will have the **`{author}`** variable, which refers to the user who triggered the action.
| **Variable** | **Description** |
| ------------------- | --------------------------------------------------------------------- |
| `{author}` | The mention to the user who triggered the message |
| `{author.name}` | The name of the `{author}` |
| `{author.id}` | The ID of the `{author}` |
| `{author.nickname}` | The nickname of the `{author}` |
| `{author.icon}` | Direct Url of the profile picture of the user triggering this message |
| `{author.tag}` | The 4 digit discriminator, of the `{author}` |
| `{author.full}` | The username + the 4 digit discriminator of `{author}` |
{% hint style="danger" %}
The **`{author}`** variable has the same as usage as **`{user}`**. Take into account that **`{ticket.user}`** refers to the user creating a ticket, so if for example you want to ping the user of your ticket in the claiming, **do not** use **`{user}`** as it will ping the user who claimed, if you want to ping use **`{ticket.user}`**.\
**`{user}`** β **`{ticket.user}`**
{% endhint %}
### Special Variables
| **Variable** | **Description** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `{empty}` | Places an empty-like character on a required field of an embed |
| `{reason}` | The given reason for the action triggered |
| `{create.reason}` | Reason given for a ticket **creation** when using [Command Style Tickets](/beta-docs/dashboard/panel-configs/command-style-tickets) |
| `{close.reason}` | Reason given for a ticket **closure** |
| `{delete.reason}` | Reason given for a ticket **deletion** |
| `{claim.reason}` | Reason given for a ticket **claim** |
| `{claim.user}` | The **last** user who claimed a ticket, has the same sub-variables as [`{ticket.user}`](#ticket-variables) |
| `{@Role Name}` | **Replace** `Role Name` with the name of your role and it will ping that role |
| `{Role ID}` | **Replace** `Role ID` with the ID of your role and it will ping that role |
| `{random}` | Will provide you with a random number (by default lower than 0), use [variable modifiers](#modifiers) to customize this behavior |
| `{regex.X}` | Named group support variables for Regex, only works for [**Custom Commands**](/beta-docs/dashboard/custom-commands#regex) |
| `{create.form.X}` | Displays the user's answer for question #`X` in a [Form](/beta-docs/dashboard/panel-configs/form-options#displaying-form-answers) |
| Escalate Variables | Visit the [Escalate documentation](/beta-docs/dashboard/panel-configs/escalate-options#available-variables) for a full list of variables. |
| Roblox/Bloxlink Variables | Visit the [Integrations documentation](/beta-docs/dashboard/panel-configs/integration-options#bloxlink-variables) for a full list of variables. |
### Time Variables
| **Variable** | **Description** |
| -------------------- | ------------------------------------------------------------------------------------------------------------ |
| `{time}` | Sends the current unix time in seconds |
| `` | Will send the unix time using Discord's timestamp native feature |
| `{time.created.age}` | A human-readable **text** that indicates how long ago was the ticket **created** |
| `{time.claimed.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **claimed** |
| `{time.closed.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **closed** |
| `{time.deleted.age}` | A human-readable **text** that indicates the time **between** the ticket's creation and it being **deleted** |
| `{time.created}` | A unix **timestamp** pointing to the time when the ticket was **opened** |
| `{time.claimed}` | A unix **timestamp** pointing to the time when the ticket was **claimed** |
| `{time.closed}` | A unix **timestamp** pointing to the time when the ticket was **closed** |
| `{time.opened}` | A unix **timestamp** pointing to the time when the ticket was **re-opened** |
| `{time.deleted}` | A unix **timestamp** pointing to the time when the ticket was **deleted** |
{% hint style="info" %}
The time-action variables that point to actions that can take place more than once (e.g claiming, closure, re-opening), will take the value of the last moment the action took place.
{% endhint %}
{% hint style="info" %}
For a more convinient use on Discord's Dynamic Timestamps we recommend you checking [HammerTime](https://hammertime.djdavid98.art/), here you can replace the actual unix time for the `{time}` variable to make custom messages!
{% endhint %}
### Modifiers
Since [October 2022](/beta-docs/ticket-tool-changelog#october-2022), you can customize even more your variables! These are all the modifiers you can apply at the end of your variables, remember that to use them you must prefix them using **`?`**, check the [cheatsheet](#cheatsheet) for a sample.
| **Modifier** | **Aliases** | **Description** |
| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `?uppercase` | `?uc` | Will make the variable to be upper case |
| `?lowercase` | `?lc` | Will make the variable to be lower case |
| `?maxLength=` | `?ml=` | Set the maximum lenght for a variable, if it's exceeded, the variable will be truncated |
| `?padLeft=` | `?pl=` | Pad the variable to the left with zeros |
| `?padRight=` | `?pr=` | Pad the variable to the right with zeros |
| `?fallback=` | `?fb=` | If the variable you attach this modifier to is empty, the fallback text (anything placed after the `=`) will be displayed instead. You can also use variables for a fallback text. |
| `?notfallback=` | `?nfb=` | If the variable you attach this modifier to contains information, the fallback text (anything placed after the `=`) will be displayed instead. You can also use variables for a fallback text. |
| `?math=` | `?m=` | Use algebra operators (`+`, `-`, `*`, `/`,) to perform operations on variables such as [`{time}`](#time-variables) |
| `?clean` | None | Replaces the \` character to prevent breaking in variables such as [`{create.form}`](/beta-docs/dashboard/panel-configs/form-options#response-usage) |
| `?rlist=` | None | Add this modifier to the [`{random}`](#special-variables) followed by the items you want the bot to choose from, separated by a pipe (\|) character |
| `?rmin=` | None | Set the **minimum** value [`{random}`](#special-variables) can return |
| `?rmax=` | None | Set the **maximum** value [`{random}`](#special-variables) can return |
#### Cheatsheet
Here you'll find some examples when using this modifiers, if you have questions around them, don't hesitate to contact our [Support Team](https://tickettool.xyz/support)
 
# Custom Commands
Adding predifined messages to your server
To access these settings:
> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the **Custom Commands** Tab
Custom Commands are used to send a predefined response to your channels using a text command. Common uses are FAQs, Help Commands, and/or General information.
The Custom Commands tab shows currently configured Custom Commands and allows you to create and edit Custom Commands.
### Creating a Custom Command
To create a Custom Command, press the green `+ New` button in the top left corner of the Custom Commands page. When creating a Custom Command, give it a name to identify your Custom Command.
{% hint style="info" %}
\- To delete a custom commands click the Bin icon that's next to the command name.
* You can clone custom commands by clicking the Copy icon next to delete button.
* You must always have at least one custom command on the dashboard. If you plan on deleting your last custom command, create a new custom command first to avoid an error.
{% endhint %}
{% hint style="warning" %}
\- You must have at least one custom command in your server.
* For more information please look at our [Error Documentation](/beta-docs/debugging/errors/major-mismatch)
{% endhint %}
\## Customizing a Custom Command
#### Command Name
You can always set a new name for your Custom Command by editing it on the top left corner of it's settings
#### Command Group
You can create groups to categorize your Custom Commands! Type a name in the box to look for already made groups or click in the name you typed to create a new one!
#### Command Description/Notes
Here you can insert a custom description you had like the command to have, this is only visible on your dashboard and does not affect in any way the output on your Discord server.
#### Dm Ticket Owner instead
If **enabled**, triggering this custom command **in a ticket** will DM the custom command message to the Ticket Owner instead of sending it to the channel.
{% hint style="warning" %}
If the custom command is triggered **outside** of a ticket, the message will **not** be sent to the channel.
{% endhint %}
\### Dm response instead If **enabled**, the user who triggers the custom command will receive the Message on its Direct Messages (DMs)
#### Admin Only
When **enabled**, only users with a [Dashboard Role](/beta-docs/dashboard/server-configs#dashboard-roles), `Administrator` Permission, and the `Server Owner` will be able to trigger this custom command.
#### Command Trigger
You can choose one of 3 trigger types for your commands:
* Strict
* Wildcard
* Regex
Note that the server's prefix won't affect the command trigger at all!