> For the complete documentation index, see [llms.txt](https://logix.gitbook.io/logix-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logix.gitbook.io/logix-docs/logix-ticket-system-setup.md).
# Logix - Ticket System Setup
1. **Run the command /config > Select Ticket System**
* It is important you **choose a transcript channel** - this is to ensure you keep a log of what is said and done in tickets
Identify which categories you need to make *example* Support, Purchase
\
Once you have made the categories you need for your ticket panel
\
A ticket prefix is for example 'donation-1' the keyword on the ticket channel
\
To use custom emojis, it must be uploaded to the server and you must use a emoji breakdown. Example of what this looks like is <:CROWN:1340501979989803209>
2. **Choose 'Select a Category'**
For instance - we will use the '**Support**' Category
\
First thing you want to do in here, is to setup permissions to ensure people can talk, read message history
I recommend giving the same permissions for '**Ticket Owner Permissions**' and '**Additional User Permissions**'
\
The standard permissions I recommend giving are '**View Channel**' '**Send Message**' '**Attach Files**' '**Read Message History**'
For **Support Permissions** - these are your choice but this will lead your support team to having full reign inside tickets depending what is provided
Once your permissions have been setup, next up you want to choose who can view these tickets from your team - Recommendations are '**Admin**' '**Moderator**' '**Owner**' and any other **administration** role you may use or have
The final thing you want to do for the setup of a category is where the ticket will go once opened - I recommend making a category named '**Support**' or relevant to the category you make;
\
Then just simply select the option from the dropdown
That is your ticket panel setup for the '**Support**' Category - now just replicate this onto your other panels
If you wish to edit the information on the panel - simple run the command /manage-messages and select the box then edit the embed description to fit the category
## *Question Set Up for Categories*
If you wish to add questions to your bot - similar to the other widely known bots. Please fully read through these before making any changes
To start this process of adding questions, follow the step by step below
1. Run the command /config then select the **Ticket System**
2. Choose your ticket category you wish to add questions too
3. Create up to 4 questions for each category (example - What is your discord name?)
4. Personally preference - to always choose the required and enter the word 'yes' so its forced to answer
5. Once this is done for each category - follow the next set of steps
6. Run the command /manage-messages
7. Choose the panel you wish to update (i.e General Support)
By default the panel message will be as shown below
8. After you have got your questions setup for the steps above. You will change the description of the category to include these
9. The identifier for a question is {question.1} vice versa - just change the digit to the question number
10. Personal preference, we put these symbols to make it into a field \`\`\` but this is not required
11. We recommend following a similar format to the screenshot attached
12. Once you have got this, make sure you submit and then save the message for it to work
13. After you are happy with it all - go ahead and run the command /post-ticket-panel to finally update it all
14. Now you are done and your panel looks amazing!
---
# 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://logix.gitbook.io/logix-docs/logix-ticket-system-setup.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.