> For the complete documentation index, see [llms.txt](https://allinone-discord-bot.gitbook.io/allinone-discord-bot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://allinone-discord-bot.gitbook.io/allinone-discord-bot-docs/features/dashboard/tickets.md).
# Tickets
Here is a guide on how to setup tickets within AllinOne!
### Before we get started:
Here is some info before we get started
1. All transcripts are saved for 7 days and automatically delete from the dashboard. Keep in mind, this does **not** delete the ones sent to your Discord channel. If you are trying to find older transcripts you will have to find them in your Transcripts channel.
### Setup
1. First head to our dashboard [here](https://dashboard.allinonebot.cc/).
2. Once signed in through Discord, select the guild where you would like the tickets setup
3. Once there, click on the Tickets module\
4. From there you are going to click "Enable Tickets"\
\- Head to your Discord server\
\- Create a channel for transcripts\
\- Create a channel for ticket logs\
\- Create a default ticket catagory (we can change this later)\
\- Create a "open a ticket" channel
5. Scroll down and select your staff roles
6. Configure settings\
\- How many tickets per user (default: 3)\
\- Enable Ticket Ratings will send a dm to the user and have them rate the support 1-5 stars\
\- Send a copy of transcript to user upon ticket being closed
### Creating a panel
With AllinOne, you can have as many panels as you would like. With this setup, we will just configure one
1. After doing the basic setup, at the top select the "Panels", and click "Create New Panel"
2. From there you are going to fill out all the information\
\- Panel Name: What appears on the top of the embed \
\- Panel Description: The main body text within the embed\
\- Target Channel: The channel the embed is sent to (use the channel you made in setup > step 4)\
\- Ticket Catagory: Just a default catagory tickets are sent to (you can change this later)\
\- Embed Color: Select which color you want for the embed\
\- Display Mode: Do you want the panel to have buttons or a drop down box, for this example we will be using the drop down box\
\- Placeholder text for the drop down box\
\- Panel Embed Content: Panel Title (leave blank) \
\- Welcome Message: The first message that appears when a user opens a ticket\
\- Footer text: The text at the bottom of the panel embed\
### Creating Buttons and forms
1. After filling all the above information scroll down to "Ticket Options" and select "Add Option"\
\- The first button we are going to make is a General Support button\
\- Label "General Support" \
\- Style: Only applies if you are using **buttons** and **not** dropdown box\
\- Default Priority for the "General Support" button\
\- Catagory override: If you want the this specific button sent to a different Discord catagory. This is used to hide tickets from other staff members\
\- Description (for dropdown): Only applies if you are using the **dropdown** menu **not** buttons\
\- Emoji: Select an emoji from the list that best applies to your button, for this use, we will use the default emoji
2. Creating a form for this specific button\
\- What is a form? When a user clicks on the button to create a ticket, these are the questions you can ask to get information from the user. \
\- Start by clicking "Add Form"\
\- Fill out the "Question Label" form\
\- Placeholder Text: Is the text that appears before a message/charcter has been entered into the box \
\- Click the box if you want that form to be required when submitting a ticket\
\- If the form requires a longer text you can select the "Multi line" box
3. Once you are done editing all the panel & button information, click "Save Panel" option
4. Next you will hit "Deploy"
5. If you want to make future edits to the panel or forms you can do so by clicking edit
### Active Tickets
From the "Active Tickets" tab, this just displays the current tickets that are opened within your Discord server\
\ ***\*There are already planned updates with this, including closing the tickets, responding and viewing\****
### Ticket Transcripts
This tab will show you all the ticket transcripts from the last 7 days, here you can review them, and it shows all messages sent from that specific ticket
### Blacklist
From here, you can blacklist users from using your ticket panel(s), all you need is to copy and paste their userID and add a reason.
### Statistics
This shows all the current Information as far as total tickets, How many are currently opened, How many are claimed, How many are closed, And if you have ratings enabled what the total average rating is.
### Commands
The main command you will be using is `/ticket` within this command there are sub command.\
\
`/ticket` add {user} - Add a user to the ticket (must use in the ticket channel)\
`/ticket` blacklist {user} - Blacklists a user \
`/ticket` unblacklist {user} - Un-blacklist a user\
`/ticket` claim - Claims the current ticket\
`/ticket` unclaim - Un-claims current ticket\
`/ticket` close - Close the current ticket\
`/ticket` priority {level} - Low, Medium, High, Urgent\
`/ticket` remove {user} - Remove a user from the ticket\
`/ticket` rename - Rename the ticket\
`/ticket`transfer {staff user} - Tranfer ticket to another staff member
\
Currently only users with administrator can use these commands. If you would like to change which roles/user can use which commands follow these steps
1. Head to your Discord server and select the server AllinOne is in.
2. Right Click the server name at the topand select "Server Settings"
3. Scroll down to "Apps" > Integrations
4. Under "Bots and Apps" Find AllinOne and click "Manage"
5. Find the "Commands" Box and search for "Ticket"
From here you can edit which roles / members can manage the "ticket" command
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://allinone-discord-bot.gitbook.io/allinone-discord-bot-docs/features/dashboard/tickets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
