Ticketing System
This feature is part of the Ticketing Module.
Elyxir's comprehensive ticket system is enhanced for FiveM servers, and is suitable for all levels of experience with optional customisation available throughout the module. This ticket module is not suitable for servers who generate more than 2,000 tickets per day.
OBJECTIVES
REQUIREMENTS
Premium Tier and Deluxe Tier subscriptions have full functionality access to this feature.
Introducing our Ticket System
The ticket system has been a core consideration within the development of our bot, here's some of the highlights worth sharing within this documentation:
Transcripts
Our transcription system, which is (in part) served by Ticket Tool, is sophisticated with automatic attachment-skipping when it would cause the file size of the transcript to exceed the maximum. We use the latest version of their transcript system with permission from their developers, an example transcript message is displayed below.
Reminder System
You can now easily remind your users if they are unresponsive within tickets! To do this, run the /remind command and specify the user to remind. This user can be the owner of the ticket, or any user added to the ticket.
Customisation as Standard
Our ticket system can be tailored to your server's brand guidelines; throughout the setup process, you will be able to customise the responses of the bot.
FiveM Integration
Tired of trying to liaise with your server users to find out when they are in-game to give them their store-bought items? That feeling is a thing of the past with our FiveM-Ticket Integration. By supplying us with a few details about your server, we will automatically display the in-game status of users within their tickets.
Preparing the Ticketing Module
Once you've enabled the module using the /modules enable command, you'll need to run the /tickets config command, specifying certain behaviours such as the transcript channel and the number of stages. You may choose to setup optional behaviours such as the DM User Transcript option, and this is where this can be achieved. You may also choose to enable the FiveM Integration.
Explanation of Close Behaviour
One Step: The ticket will be immediately deleted when closed.
Two Step: The ticket will be closed, and then a subsequent button must be pressed to delete the ticket.
Smart Step: If the ticket is empty, then it will be immediately deleted. Otherwise, it will be closed.
Creating a Panel
Once you've completed the preparation for the Ticketing System, it's time to create a new panel. To do this, you can run the /panel create command, and supply the necessary information. You may be interested in the panel types, which are displayed on the page below.
Once you run the command, you will be presented with a pop-up which will allow you to modify the styling of the panel embed.
Adding roles to the support team
Modifying the permissions of a panel is easy. Just run the /panel permissions command for the desired panel, then select all of the roles which should have support team access to tickets created in that panel.
Generating a Multipanel
Multi-panels allow you to display more than one panel in a single message, and with Elyxir they can be shown in one of two formats; a buttons multipanel or a dropdown multipanel. Fortunately, both of them are easy to generate.
To generate a multi-panel, just run the /panel multi command and select the format of the multi-panel. Then, use the selection menu to specify the panels to display within this panel. Finally, you can customise the style of the multi-panel and now your panel will be displayed!
Customising the Responses
Customisation
Last updated