Tickets Module

The Tickets module gives members a private place to ask for help. You can create separate ticket options for support, reports, appeals, billing, or any other team.

Most setup and ticket management happens inside Discord. Members choose an option from a panel, and Discortics creates a private text channel with the right staff, users, welcome message, and controls.

Features

Create multiple ticket panels for different channels or purposes.
Show ticket options as buttons or a select menu.
Give each option its own category, staff roles, log channel, and welcome message.
Ping selected roles and add selected users when a ticket opens.
Control whether members can open more than one ticket.
Require staff to claim a ticket before its creator can enter.
Hide claimed tickets from other manager roles.
Claim, assign, rename, move, close, reopen, and delete tickets.
Add or remove users from an open ticket.
Generate text transcripts and download recent attachments.

Before You Begin

Staff need the Administrator permission to run /ticket panels. The other /ticket management commands require Manage Channels.

Discortics needs View Channel, Send Messages, Embed Links, and Manage Channels to set up panels and create ticket channels. It also needs Read Message History and Attach Files to generate transcripts.

Place the Discortics role high enough to manage the ticket channels it creates. Make sure Discortics can view and send messages in the panel channel, ticket category, and log channel.

Ticket Limits

Limits depend on which Discortics bot serves your server.

Resource	Public	Prime	Custom
Panels per server	2	5	15
Options per panel	2	5	10
Ping roles per option	3	7	15
Manager roles per option	3	7	15
Auto-added users per option	3	7	15

Prime and Custom bots use the same ticket features as the Public bot with higher limits.

Create Your First Ticket Panel

Run /ticket panels.
Choose Create New Panel.
Select Channel, then choose the text channel where members will see the panel.
Select Mode, then choose Buttons or Select Menu.
Select Embed. Choose a saved embed, or select Create New Embed to use the default ticket panel message.
Select Options, then open the default General Support option.
Configure the option through Block A, Block B, and Block C.
Return to the panel editor and confirm the panel and at least one option are enabled.
Select Send to post the panel.

After deployment, the button changes to Edit. Use it after changing the panel, embed, display mode, or options to update the existing message.

Panel Settings Explained

Status

The first button in the panel editor enables or disables the panel.

Enabled: Members can use enabled options on the deployed panel.
Disabled: The saved panel remains configured, but it cannot be sent and members cannot create tickets from it.

Disabling a panel does not close or delete existing ticket channels.

Channel

Choose the text channel where Discortics will post the panel. Changing this setting clears the previous deployed-message link when you choose a different channel. Select Send to deploy the panel in the new channel.

Mode

Choose how members select a ticket option.

Buttons: Each enabled option appears as a button. Discord places up to five buttons on each row.
Select Menu: Every enabled option appears in one dropdown with a Cancel choice.

Embed

The embed is the message shown above the ticket buttons or select menu. You can choose one of the server's saved embeds or create the default Open a Ticket embed from the panel editor.

Discortics uses the latest version of the selected saved embed when you send or edit the panel. If that embed was deleted, the panel keeps its last saved copy until you select another one.

Options

Each option creates a different type of ticket. For example, one panel can contain General Support, Billing, and Report a User, with different staff and channel settings for each.

Only enabled options appear on a deployed panel. A panel must have at least one enabled option before it can be sent. You cannot delete the last option from a panel.

Ticket Option Settings

Open /ticket panels, choose a panel, select Options, then choose an option.

Block A: Name and Channels

Label is the option name shown on its button or select-menu entry. It is required and supports up to 80 characters.

Description adds helper text below an option in select-menu mode. It is optional and supports up to 100 characters.

Ticket Category decides which Discord category receives new ticket channels. Leave it empty to create them without a category. You can also select Create Category from the option editor and send a category name within 60 seconds. The new category is private by default.

Log Channel receives a record when a ticket is created, claimed, assigned, unclaimed, renamed, moved, closed, reopened, transcribed, or deleted. Transcript files are also copied there. Leave this empty to disable ticket logs for the option.

Naming Scheme controls new ticket channel names. It supports:

{{count}}: A four-digit counter for that option, such as 0001.
{{username}}: The ticket creator's Discord username.

For example, support-{{username}}-{{count}} can create support-alex-0001. Channel names are converted to lowercase, unsupported characters become hyphens, and the final name is limited to 100 characters.

Block B: Staff and Messages

Ping Roles are mentioned in the first message when a ticket opens. Use this to alert the team responsible for that option.

Manager Roles can view new tickets and use the built-in ticket buttons. These buttons let them claim, close, reopen, transcribe, and delete tickets created from the option. Slash commands such as assign, add, remove, rename, and move still require Manage Channels.

Additional Users are automatically given access to every new ticket from the option. Use this for individual staff members or supervisors who always need access.

Welcome Message Title and Welcome Message Description create the embed posted inside every new ticket. Use it to tell members what information to provide or how long a response may take.

The Public, Prime, and Custom limits for these lists are shown in Ticket Limits.

Block C: Ticket Behaviour

Allow Simultaneous Tickets lets one member keep up to two open tickets from this exact panel option. When disabled, a member can have only one open ticket from the option. Tickets from other options are checked separately.

Require Claim Before Entry hides the new ticket from its creator until a manager claims or assigns it. Claiming gives the creator access. Unclaiming removes their access again.

Isolate on Claim removes the configured manager roles from the channel after a ticket is claimed or assigned. Only the assigned staff member and individually added users retain access. Unclaiming restores the manager roles.

Emoji

Select Emoji, then send a Unicode emoji or a custom emoji string within 60 seconds. Enter clear to remove the current emoji or cancel to keep it unchanged.

The emoji appears beside the option label on the deployed panel.

Open a Ticket

Find the ticket panel in the server.
Select the required button or select-menu option.
Wait for Discortics to create the private channel.
Open the channel link in the confirmation message.
Read the welcome message and describe what you need.

Discortics pins a ticket information message with Claim and Close buttons. It also posts the configured welcome message and pings any selected roles.

If simultaneous tickets are disabled, you must close your existing ticket from that option before opening another. If they are enabled, the maximum is two open tickets from that option.

Manage an Open Ticket

Manager-role members can use the pinned ticket buttons even if they do not have Manage Channels. Slash commands require Manage Channels. The server owner and administrators can also manage tickets.

Claim or Assign Staff

Select Claim in the pinned message or run /ticket claim to assign the ticket to yourself.
Run /ticket assign user:@member to assign it directly to another user.
Run /ticket unclaim to remove the current assignment.

A ticket can have one assignee. Reassigning it replaces the previous assignee.

Add or Remove People

/ticket add user:@member gives a user access to the current open ticket.
/ticket remove user:@member removes a user's channel overwrite.

You cannot remove the current assignee. Unclaim or reassign the ticket first.

Rename or Move a Ticket

/ticket rename name:new-name changes the current ticket channel name. Names are limited to 100 characters.
/ticket move category:Support moves the current ticket into another Discord category.

Close a Ticket

The ticket creator can select Close in the pinned message to close their own ticket. Managers can use the same button or run /ticket close.

Closing a ticket:

Adds closed- to the channel name.
Hides the channel from the ticket creator.
Keeps the channel available to ticket managers.
Shows Open, Transcript, and Delete controls.

Closing does not delete the channel or its messages.

Reopen, Transcribe, or Delete a Ticket

Only a ticket manager, the assignee, the server owner, or someone with Manage Channels can perform these actions.

Reopen

Select Open on the closed-ticket message or run /ticket open. Discortics removes the closed- prefix and restores access according to the option's claim settings.

Create a Transcript

Select Transcript on the closed-ticket message or run /ticket transcript in any ticket channel.

The transcript contains the latest 100 messages in a text file. If those messages contain downloadable attachments, Discortics also creates a ZIP file. The ZIP is omitted if no attachments can be downloaded and is skipped when it would exceed 8 MiB.

The files are posted in the ticket channel. If the option has a log channel, Discortics also sends the files there.

Delete

Close the ticket, then select Delete. Discortics deletes the ticket channel after five seconds.

Warning: Deleting a ticket channel permanently removes its messages. Generate and download any required transcript before selecting Delete.

There is no /ticket delete slash command.

Use the Dashboard

Open Dashboard → Tickets to configure the same panels through a form. The Dashboard also provides:

An internal panel name.
A preview of the selected embed.
Deployment-status checks.
Separate Send, Edit deployed message, and Refresh status actions.

Save Dashboard changes before sending or editing a deployed panel. Deleting a panel configuration does not affect ticket channels that already exist.

Command Reference

Command	Purpose	Required user permission
`/ticket panels`	Create, configure, deploy, or delete panels	Administrator
`/ticket add user:`	Add a user to the current open ticket	Manage Channels
`/ticket remove user:`	Remove a user from the current open ticket	Manage Channels
`/ticket rename name:`	Rename the current open ticket	Manage Channels
`/ticket move category:`	Move the current open ticket to a category	Manage Channels
`/ticket close`	Close the current ticket	Manage Channels
`/ticket open`	Reopen the current closed ticket	Manage Channels
`/ticket claim`	Assign the current open ticket to yourself	Manage Channels
`/ticket unclaim`	Remove the current ticket assignment	Manage Channels
`/ticket assign user:`	Assign the current open ticket to a user	Manage Channels
`/ticket transcript`	Export the latest messages and attachments	Manage Channels

Options ending in : are required slash-command fields.

Frequently Asked Questions

Why can I not send my panel?

Make sure the panel is enabled, has a deployment channel, and contains at least one enabled option. On the Dashboard, save all changes and select a valid saved embed before using Send.

Why does a deployed option no longer work?

The panel or option may have been disabled or removed after deployment. Open /ticket panels, enable it, then select Edit to update the deployed message.

Why can a member not open another ticket?

Ticket limits are checked per panel option. When Allow Simultaneous Tickets is disabled, the member can have one open ticket from that option. When enabled, they can have two. Close an existing ticket before creating another.

Why can the ticket creator not see their new ticket?

The option probably has Require Claim Before Entry enabled. A manager must claim or assign the ticket before the creator receives access.

Why did other staff lose access after a claim?

The option has Isolate on Claim enabled. This removes manager-role access while the ticket is assigned. Unclaim the ticket to restore those roles, or assign it to the staff member who should handle it.

Who can close a ticket?

The ticket creator can use the Close button on their own open ticket. Manager-role members, the assignee, the server owner, administrators, and members with Manage Channels can also close it. The /ticket close command itself requires Manage Channels.