Skip to content

Tickets

You can find the tickets module in the bot’s /config command. You can access it in two different ways:

  1. By using the /config command and selecting the Tickets module in the module option. (/config module:Tickets)
  2. By executing the /config command and selecting the Tickets option from the dropdown menu.

The tickets module allows you to create and manage tickets to track issues, feature requests, and tasks within your project. It offers a simple interface to create tickets and assign them to team members.


The Lyxios ticket system is fully configurable via an interactive dashboard. Once the module is enabled via /config, you will have access to the following button Configurer les Tickets which will allow you to customize all aspects of the ticket system:

Click on the 🛠️ Salons & Rôles button to define the essential infrastructure:

  1. Catégorie Tickets : The Discord category where new ticket channels will be created.
  2. Rôle Manager : The role that will have permission to view and manage tickets (e.g., Support, Moderator). Administrators have access by default. If this role is deleted, only administrators will be able to manage tickets.
  3. Logs : A text channel where the bot will send the history of actions (opening, closing, renaming, etc.).
  4. Panel : The channel where the ticket creation message (the Panel) will be sent to members.

Click on the ✍️ Textes & Options button to customize the user experience via the following sub-menus:

  • Max Tickets: A dropdown menu to limit the number of tickets open simultaneously by the same user (from 1 to 5). (Default 1)
  • 👋 Message Bienvenue: Opens a form to customize the message sent upon ticket opening. Use {user} to mention the member.
  • 🎨 Embed Panel: Opens a form to modify the Title, Description, and Color of the creation panel.
  • 📝 Gérer Motifs: Allows you to add or remove reasons (Motifs) for opening (e.g., Support Technique, Partenariat).
    • If you define multiple reasons, a dropdown menu will be displayed on the panel.
    • If you put no reason or only one, a simple button will be displayed.

On the main menu, you also have these actions:

  • 🚀 Modifier Panel: Sends or updates the ticket creation message in the configured channel.
  • 🔄 Rafraîchir: Updates the dashboard display with the latest saved configurations.
  • ✖️ Désactiver: Deletes the entire ticket configuration from the database.

Once a ticket is open, several features are available to your team and the user.

Staff members (Manager Role) see a 🙋‍♂️ Prendre en charge button in the ticket.

  • Action: When a staff member clicks it, they assign the ticket to themselves.
  • Effect: The bot modifies permissions so that only this staff member (and the user) can reply. Other members of the Manager role will no longer be able to speak in the ticket channel, avoiding confusion. Server administrators can still speak.
  • Release: The button then changes to 🔓 Libérer le ticket to allow the whole team to intervene again.

When a ticket is finished, click on 🔒 Fermer le ticket.

  1. Transcript Generation: The bot generates an .html file containing the entire conversation history. If the file exceeds 8 MB, a lighter version (images as links) is generated.
  2. DM Send: The user who opened the ticket receives this file in a private message, along with a summary.
  3. Logs: The transcript is also sent to the configured logs channel.
  4. Deletion: The ticket channel is deleted after a few seconds.

In addition to buttons, several slash commands are available to manage active tickets:

/ticket-add

Add a member or role Allows adding a person exceptionally to the current ticket. Usage: /ticket-add target:@User

/ticket-remove

Remove a member Removes access to the ticket for a specific user. Usage: /ticket-remove target:@User

/ticket-rename

Rename the ticket Changes the name of the current ticket channel. Useful for organizing requests. Usage: /ticket-rename name:new-name

/ticket-reset

Reset permissions Resets channel permissions to their original state (useful if permissions were manually modified by mistake). Usage: /ticket-reset