Ticket Topics
Features
- Create different ticket topics to better categorize different kinds of requests.
- Transfer a ticket to a different category if the user selected the wrong one.
- Override global settings such as ticket roles, the category for new tickets, the ticket message, and much more per ticket topic.
- Change the channel name format to quickly recognize ticket topics at a glance (for example, by using different emojis).
- Decide whether users must submit a configured form before creating a ticket for a specific topic.
Images coming soon ✨
Setup
If you want to override (certain) settings:
- Create a category for new tickets on your Discord server.
- Create the required roles for team members on your Discord server that should get access to tickets.
- Create a private text channel on your Discord server that you want to use as the log channel.
- Visit the Ticket topics page in your dashboard.
- Configure the available options.
- Create a new ticket topic by clicking the “Add ticket topic” button.
- Configure the available options for the respective ticket topic.
Commands
Understand the documentation
In these docs,
name:<Type> is an option of a slash-command with name name and the type Type. Options that not required, are described as [name:<Type>]. If the action of a command is vastly different between required and not-required options, we might list them separately.Examples
/moderate ban user:<Member>: This command (/moderate ban) has an required option with the name "user" that only accepts one member as a value./moderate ban victim:<Member> reason:<Text>: This command (/moderate ban) has an required option with the name "victim" that only accepts one member as a value and another required option with the name "reason" that accepts any text as an value./moderate ban victim:<Member> reason:<Text> [proof:<Attachment>]: This command (/moderate ban) has an required option with the name "victim" that only accepts one member as a value, another required option with the name "reason" that accepts any text as an value and a not-required option with the name "proof" which allows one attachment as its value.
| Command | Description |
|---|---|
/ticket transfer | Only available if “Team members can transfer tickets to another topic” is enabled. Moves the current ticket to the selected topic. |
Configuration
Main configuration
| Field | Description |
|---|---|
| Enable ticket topics | Enables or disables the feature for your Modmail system. |
| Team members can transfer tickets to another topic | If enabled, team members can transfer a ticket to a different ticket topic. |
| Users must confirm their topic selection | If enabled, a confirmation message is sent after selecting a topic. |
| Confirmation message | Only available if “Users must confirm their topic selection” is enabled. This message is sent as the confirmation message. |
Manage ticket topics
| Field | Description |
|---|---|
| Topic name | This name is used for the ticket topic and shown to users. |
| Topic description | This text is used as the description for the ticket topic and shown to users. |
| Topic emoji | This emoji is used for the ticket topic and shown to users. |
| Category | New tickets for this topic are created in this category. |
| Users can open tickets with this topic | If enabled, this ticket topic is available to users when creating a ticket. |
| Show topic only for users with a specific role | If enabled, only users with the configured roles can see this ticket topic. |
| Required roles | These roles will be able to see the ticket topic. |
| Use as FAQ option | If enabled, your bot will only send an information message when this topic is selected, instead of creating a ticket. |
| Message sent to the user when opening a ticket | This message is sent to the user when a ticket is created with this topic. |
| Override channel access | These roles get access to tickets for this topic. By default, your configured roles are used. |
| Override ping roles | These roles are mentioned when a ticket is created with this topic. By default, your configured roles are used. |
| Send transfer message | Only available if “Team members can transfer tickets to another topic” is enabled. This message is sent when a team member transfers a user’s ticket to another topic. |
| Transfer message | Only available if “Team members can transfer tickets to another topic” and “Send transfer message” are enabled. This message is sent into the ticket channel when a ticket is moved to another topic. |
| Ping roles again when transferring | Only available if “Team members can transfer tickets to another topic” is enabled. If enabled, the configured roles are mentioned again when transferring the ticket to another topic. |
| Require form submission before opening | If enabled, the user must first fill out a form before they can create a ticket for this topic. |
| Form that must be completed | Only available if “Require form submission before opening” is enabled. This form must be completed before opening the ticket. |
| Override log channel | This channel is used as the log channel for this topic. By default, your configured log channel is used. |
| Override ticket channel name? | If enabled, you can define a custom ticket channel name for this topic. |
| Ticket channel name format | This text is used for the channel name of tickets with this topic. By default, your configured ticket channel name format is used. |