Vyral
Home➕SupportResourcesDashboard
  • Welcome to Vyral.bot!
  • Guidelines & Privacy
  • Changelogs
  • Support
    • Standard Practices
    • Additional Settings
  • Variables
  • Server Management
    • Auto-React
    • Emoji Manager
    • Moderation
    • Polls Filter
    • Statistic Channels
    • Sticky Roles
    • Tickets
    • Welcomer
  • Messages
    • Autoresponder
    • Global Chat
    • Media Channels
    • Polls
    • Reaction Roles
    • Sticky Messages
  • Timed Messages
  • Social Integrations
    • Twitch
    • Youtube
  • Community Engagement
    • Invite Tracker
    • Leveling
    • Question Of The Day
    • Starboard
    • Suggestions
    • Temp Voice Channels
  • Fun
    • Birthdays
    • Counting
  • Economy & Minigames
  • Utilities
  • Translation
  • Weather
  • AI
    • ChatGPT
  • Image Generation
  • Game Integrations
    • Roblox Verification
Powered by GitBook
On this page
  • Settings
  • Panels
  • Create a Panel
  • Active Panels
  • /ticket create Command
  • Transcripts
  • Active Transcripts
  • Limits
  • Active Limits
  • Automations
  • Active Automations
  • Variables
  • Commands
  • Events
  1. Server Management

Tickets

Let server members contact staff through a ticket!

Last updated 1 month ago

With the module you can setup a system that allows users to privately contact a role in your server through a temporary channel. Users can create tickets, close tickets, and more. Your server's moderators may add or remove users from your server's tickets.

Settings

Here you can find the settings for the Tickets module and modify them to your liking.

Panels

Manager Roles

Embeds Color

Here you may choose the color of all embeds in the panel messages.

Cooldown

Here you may choose the number of seconds users must wait between creating tickets. The minimum number of seconds you can make this cooldown is 10.

Create a Panel

Panel Name

Here you may choose the name of the panel. This will be used to identify it during setup, transcripts, and automations, and can only contain letters and numbers.

Panel Message

Layout

Button Color

Select Menu Placeholder

Button / Select Menu Label

Select Menu Description

Emoji

Connected Panels

Support Roles

Here you may choose roles from your server which will have access to all created tickets on this panel, even when they're closed.

Blacklisted Roles

Here you may choose roles from your server which cannot create tickets on this panel.

Send Form

Here you may toggle whether or not to send a form or modal which will allow users to answer up to two questions with text responses before creating a ticket.

Question 1 Type

Question 1 Text

Question 2 Type

Question 2 Text

Ticket Name

Ping Support Members

Ticket Creation Message

Logging Channel

Here you may choose a channel from your server which will receive logs for ticket creation, closure, reopening, deletion, transcription, automation updates, member additions and removals, and errors from this panel. Leave this option empty to disable logs.

DM Ticket Creator

Here you may toggle whether the bot will direct message logs for ticket creation, closure, reopening, and member additions and removals from this panel to the creator of the logged ticket.

Ticket Mode

Two Step Close

Open Category

Close Category

Channel for Tickets

To save the panel's settings, you need to click "Add" in the bottom-right corner of the settings. This will reset the fields so you can set up another panel.

Active Panels

/ticket create Command

/ticket create

Panel Name

Channel Restrictions

Restriction Type
Restriction Details

No channel restrictions

Users will be able to use the command everywhere.

Disable for these channels...

Set this blacklist type if you want the command to work in all channels except the channels provided in the menu below.

Enable for these channels...

Set this blacklist type if you want the command to work only in the channels provided in the menu below.

Role Restrictions

Restriction Type
Restriction Details

No role restrictions

Everyone will be able to use the command.

Disable for these channels...

Set this blacklist type if you want the command to work for all users, except users with at least one of the roles provided in the menu below.

Enable for these channels...

Set this blacklist type if you want the command to work only for users with at least one of the roles provided in the menu below.

Transcripts

Affected Panels

Transcripts Channel

Here you may choose a channel from your server which transcript threads will be stored in. This will only apply to new transcripts.

Thread Privacy

Option
Details

Public Thread

Private Thread

Add Support Members to Transcript

Add Creator of Ticket to Transcript

To save the transcript's settings, you need to click "Add" in the bottom-right corner of the settings. This will reset the fields so you can set up another transcript.

Active Transcripts

To save the edits you made on the ticket transcript's settings, you need to click "Edit" in the bottom-right corner of the settings.

Limits

Affected Panels

Maximum of Open Tickets

Maximum of Active Tickets (Open + Closed)

Maximum of Open Tickets by User

Maximum of Active Tickets by User (Open + Closed)

To save the limit's settings, you need to click "Add" in the bottom-right corner of the settings. This will reset the fields so you can set up another limit.

Active Limits

To save the edits you made on the ticket limit's settings, you need to click "Edit" in the bottom-right corner of the settings.

Automations

Affected Panels

Action on Leave

Auto Close

Hours of Inactivity

Ignore Inactivity by Supporter

Auto Delete

To save the automation's settings, you need to click "Add" in the bottom-right corner of the settings. This will reset the fields so you can set up another automation.

Active Automations

To save the edits you made on the ticket automation's settings, you need to click "Edit" in the bottom-right corner of the settings.


Variables

Variable Reference
Variable Details

{ticket}

Returns a channel link to the current ticket

{ticket_name}

Returns the name of the current ticket

{ticket_id}

Returns the channel ID of the current ticket

{controls}

{form}

{ping}

{total_count}

Returns the number of created tickets on your bot. You can optionally set a specific number of digits for the variable to return with {total_count[DIGITS]}, replacing DIGITS with the number of digits to return. Example: {total_count[3]} = 007

{panel_count}

Returns the number of created tickets on the current panel. You can optionally set a specific number of digits for the variable to return with {panel_count[DIGITS]}, replacing DIGITS with the number of digits to return. Example: {panel_count[3]} = 007


Commands

Here you can find the commands for the Tickets module and modify them to your liking.

/ticket add

The /ticket add command allows you to add a user to an open ticket. The user will be able to see and send messages in the channel.

/ticket automation
/ticket close

The /ticket close command allows you to close the ticket in which it is run in. This will lock the ticket to everyone except staff, allowing staff with a new set of controls to use on the closed ticket.

/ticket create
/ticket delete
/ticket remove

The /ticket remove command allows you to remove a user from an open ticket. The user will no longer be able to see and send messages in the channel.

/ticket reopen
/ticket setup
/ticket update-counts

Events

Below you may find some information on each event of the module.

Inactive Tickets Handler
Creator Leaves Handler
Thread Closure Handler
Transcripts Handler - New Messages

The Transcripts Handler - New Messages event adds new messages from tickets to their saved transcripts.

Transcripts Handler - Updated Messages

The Transcripts Handler - Updated Messages event updates edited messages from tickets to their saved transcripts.

Transcripts Handler - Deleted Messages

The Transcripts Handler - Deleted Messages event removes deleted messages from tickets to their saved transcripts.

Here you may choose roles from your server which will have access to .

Here you may setup a ticket panel that can be sent to a channel in your server using the /ticket setup command. Use the settings below to customize the panel, then click "Add" to save the panel. The new panel will appear in .

Here you may customize a plain text or embed message that will be sent to the channel in which the panel is setup, along with a button to create a ticket. All can be used.

Here you may choose whether users can create a ticket with a or a . Your choice will be attached to the .

Here you may choose the color for your button, which will show in the background of the Label text you customized. The setting is only visible if is set to Button.

Here you may customize the text that is displayed before selecting an option from your select menu. The setting is only visible if is set to Select Menu.

Here you may customize the text users will click to create a ticket, which will be shown on the option you chose.

Here you may customize the text that will be displayed below the in your select menu. The setting is only visible if is set to Select Menu.

Here you may choose the emoji, if any, should be displayed to the left of the text you customized.

Here you may choose the names of the panels that should have their ticket creation button or select menu included on this panel. Use a name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

Here you may choose the size of the input box for the first question in the form or modal. The setting is only visible if is toggled on.

Here you may customize the label for the first question in the form or modal. The setting is only visible if Send Form is toggled on.

Here you may choose the size of the input box for the second question in the form or modal, or choose None if you would not like to add a second question. The setting is only visible if Send Form is toggled on.

Here you may customize the label for the second question in the form or modal, or leave it empty if you would not like to add a second question. The setting is only visible if is set to Short Text Input or Long Text Input.

Here you may customize the channel name for each created ticket on this panel. All that are correctly formatted for can be used.

Here you may toggle whether the bot will send a separate message before the , which pings the you chose. This can also be done using the anywhere in the , if it is a plain text message.

Here you may customize a plain text or embed message that will be sent to tickets that are created on this panel. All can be used.

Here you may choose whether tickets will be created as new or as new in an existing text channel.

Here you may choose whether tickets, when closed, will be instantly deleted (off) or will close/lock the ticket to only the and allow them to use a new set of controls.

Here you may choose a from your server which will store closed tickets from this panel. The setting is only visible if is set to Channel.

Here you may choose a from your server which will store closed tickets from this panel. The setting is only visible if is set to Channel.

Here you may choose a channel from your server which will store tickets from this panel. The setting is only visible if is set to Thread.

When adding a new ticket panel, it and its settings will appear in this section of the dashboard. All ticket panels will be ordered by the number in which they were created. To view, edit, and delete the settings you selected for that panel, simply click the ticket panel you wish to do so for. You can find detailed information about each of the settings in the section.

To save the edits you made on the ticket panel's settings, you need to click "Edit" in the bottom-right corner of the settings. Additionally, you must re-send the panel with the command for the changes to take effect on a panel. You do not need to re-send the panel if it is used only for the command.

Here you may toggle whether can be used.

Here you may choose the panel that the command will follow the settings for and contribute to its . Use a name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

Here you may customize channel restrictions to allow the usage of the command only in certain channels. Below you can find detailed information about each restriction type and how it can be used.

Here you may customize role restrictions to allow the usage of the command only to certain roles. Below you can find detailed information about each restriction type and how it can be used.

Here you may setup ticket transcripts for specific panels and manage how they are stored. Use the settings below to customize the transcript, then click "Add" to save the transcript. The new transcript will appear in .

Here you may choose the names of the panels that will be subject to this transcript. Use a name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

If the same panel name is included in multiple that have overriding settings, the first listed transcript will be the one that takes effect.

Be cautious about the used in your . Deleting a channel which contains transcript threads will also delete those transcripts. Additionally, modifying or deleting a thread which contains a transcript will modify or delete that transcript respectively. These changes are permanent and cannot be undone.

Here you may choose who can view transcript threads. Your setting choice will only apply to new transcripts, but any changes to will apply to all transcript threads in that channel. Below you can find detailed information about each thread privacy type and how it can be used.

Requires the View Channel permission to be enabled in the to see the transcript. A link may be sent to that channel when a transcript is created. Recommended for private channels.

Requires the Manage Threads permission to be enabled in the to see the transcript. This permission also allows users to modify and delete transcripts. Recommended for public channels.

Here you may toggle whether all members with any of the , if they have the View Channel permission enabled in the , should have access to and be pinged in the transcript thread when the transcript is created.

Here you may toggle whether the creator of the ticket, if they have the View Channel permission enabled in the , should have access to and be pinged in the transcript thread when the ticket is deleted.

When adding a new ticket transcript, it and its settings will appear in this section of the dashboard. All ticket transcripts will be ordered by the number in which they were created. To view, edit, and delete the settings you selected for that transcript, simply click the ticket transcript you wish to do so for. You can find detailed information about each of the settings in the section.

Here you may setup ticket creation limits for specific panels and manage the amount of created tickets. Use the settings below to customize the limit, then click "Add" to save the limit. The new limit will appear in .

Here you may choose the names of the panels that will be subject to this limit. Use a name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

If the same panel name is included in multiple that have overriding settings, the first listed limit will be the one that takes effect.

Here you may choose the number of tickets that can be open at the same time. If a ticket is manually deleted, you may need to use the command to update the module's data.

Here you may choose the number of tickets that can exist, while opened or closed, at the same time. If a ticket is manually deleted, you may need to use the command to update the module's data.

Here you may choose the number of tickets that can be open with the same ticket creator at the same time. If a ticket is manually deleted, you may need to use the command to update the module's data.

Here you may choose the number of tickets that can exist, while opened or closed, with the same ticket creator at the same time. If a ticket is manually deleted, you may need to use the command to update the module's data.

When adding a new ticket limit, it and its settings will appear in this section of the dashboard. All ticket limits will be ordered by the number in which they were created. To view, edit, and delete the settings you selected for that limit, simply click the ticket limit you wish to do so for. You can find detailed information about each of the settings in the section.

Here you may setup ticket auto-closure and auto-deletion for specific panels and manage if and when they are triggered. Use the settings below to customize the automation, then click "Add" to save the automation. The new automation will appear in .

Here you may choose the names of the panels that will be subject to this limit. Use a name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

If the same panel name is included in multiple that have overriding settings, the first listed automation for that panel will be the one that takes effect.

Here you may choose what action will be taken if the creator of the ticket leaves the server. You can choose None (does nothing), , or .

Here you may toggle whether the ticket should automatically be after a set number of hours of inactivity.

Here you may choose the duration, in hours, of inactivity that should occur before the ticket should automatically be closed. The setting is only visible if is enabled.

Here you may toggle whether the thread should automatically be closed only if the ticket creator is responsible for the inactivity. The setting is only visible if is enabled.

Here you may toggle whether the ticket should automatically be after a set number of hours of inactivity.

When adding a new ticket automation, it and its settings will appear in this section of the dashboard. All ticket automations will be ordered by the number in which they were created. To view, edit, and delete the settings you selected for that automation, simply click the ticket automation you wish to do so for. You can find detailed information about each of the settings in the section.

The Tickets module allows you to use variables to reference data while customizing its , , and . You can use , which are available across Drip Dropper, and Module Variables, which are available specifically for the Tickets module. Below you can find detailed information about each module variable and how it can be used.

Returns the available to be used in the current ticket

Returns the creator's responses for the current ticket, if applicable

Returns an @mention for all of the current panel. A notification will not be sent if placed in an embed

The /ticket automation command allows you to edit a ticket's automatic closure and deletion settings based on its recent activity. The settings must be configured in order for the command to run successfully.

The /ticket create command allows you to create a ticket on any created panel. The settings must be configured in order for the command to run successfully.

The /ticket delete command allows you to delete a ticket that was closed with . This will permanently delete the channel the ticket was created in. If a ticket is manually deleted, you may need to use the command to update the module's data.

The /ticket reopen command allows you to reopen a ticket that was closed with . This will undo all effects of the closure by returning the previous ticket members and controls.

The /ticket setup command allows you to send a ticket creation panel to any channel. The settings must be configured in order for the command to run successfully.

For the panel option, use a panel name from the ones you created in the settings. Do not include the # or the number that follows it at the end.

The /ticket update-counts command allows you to manage the number value for some of the Tickets . Global Counts can be referenced with {total_count}, Panel Specific Counts can be referenced with {panel_count}, and User Specific Counts are used for user rate limits per panel.

The Inactivity Tickets Handler event checks for inactivity in a ticket, and takes action based on the settings you configured in . This event is linked to the Tickets Module - Inactivity System Handler event in the module, which runs on the interval of every hour.

The Creator Leaves Handler event checks if the user who created the ticket is still in the server, and if not, it takes action based on the settings you configured in .

The Thread Closure Handler event checks if a ticket thread has been closed, and if so, removes the creator and members added with from the ticket.

text channels
private threads
channel permissions
/ticket setup
Active Panels
Variables
Button
Select Menu
Panel Message
Button / Select Menu
Button Color
Layout
Select Menu Placeholder
Layout
Layout
Button / Select Menu Label
Select Menu Description
Layout
Button / Select Menu Label
Active Panels
Question 1 Type
Send Form
Question 1 Text
Question 2 Type
Question 2 Text
Question 2 Type
channel names
Variables
Ticket Creation Message
Support Roles
{ping} variable
Ticket Creation Message
Variables
Support Roles
category
Open Category
Ticket Mode
category
Close Category
Ticket Mode
Channel for Tickets
Ticket Mode
Create a Panel
/ticket setup
/ticket create
/ticket create
/ticket create
Active Panels
{panel_count} variable
/ticket create
/ticket create
Active Transcripts
Active Panels
Active Transcripts
channel permissions
Transcripts Channel
Support Roles
Transcripts Channel
Transcripts Channel
Transcripts
Active Limits
Active Panels
Active Limits
/ticket update-counts
/ticket update-counts
/ticket update-counts
/ticket update-counts
Limits
Active Automations
Active Panels
Active Automations
Close Ticket
Delete Ticket
closed
Hours of Inactivity
Auto Close
Ignore Inactivity by Supporter
Auto Close
deleted
Automations
Basic Variables
Settings
Commands
Events
Automations
/ticket create Command
/ticket close
/ticket update-counts
/ticket close
Panels
Active Panels
module variables
Timed Messages
Automations
Automations
/ticket add
Transcripts Channel
Transcripts Channel
Commands
Send Form
Support Roles
Tickets