Tickets
Create private support channels, claim Cases, change priority, add staff notes and tags, control access, transfer ownership, create transcripts and close completed Cases.
Case documentation
Case Docs
Everything you need to set up, configure, troubleshoot and use Case.
Overview
Case is a Discord support and application platform. Members open tickets or applications from panels, staff manage them with Case's tools, and server owners configure everything from the dashboard.
Applications
Create custom questions, route submissions to reviewers, accept or decline applicants, keep status history and automate result roles or messages.
Dashboard
Configure panels, destinations, application routing, questions, transcript settings, permissions and logs without editing bot code.
Transcripts
Save ticket history as a permanent read-only record after the Discord channel is closed.
Setup
1. Give Case the required Discord permissions
Case normally needs View Channels, Send Messages, Embed Links, Read Message History, Attach Files and Manage Channels. Manage Roles is also required if you use application role automation.
2. Run /setup
Choose the support role, ticket category and logging channel. These are the core server settings used by the ticket system.
3. Configure the dashboard
Build your ticket or application panel, set its routing destination, add application questions and configure accepted or declined outcomes.
4. Publish the panel
Post the finished panel into Discord. Members can then start the ticket or application workflow from that message.
Permissions
Manage Channels
Required for creating, renaming, moving, locking, archiving and closing ticket channels.
Manage Roles
Required for application outcome roles. Case's role must also be higher than the roles it needs to manage.
Read Message History
Required for complete ticket transcripts and access to older ticket messages.
Send Messages / Embed Links
Required for ticket controls, application results, logs, reminders and normal bot responses.
Ticket workflow
A member opens a Case from a configured ticket panel. Case creates a private channel and records the opener. Staff can then claim it, set priority, add internal notes and tags, control access, transfer it to another staff member and save a transcript before closing it.
Claiming
Claim a Case when you begin handling it. If another staff member needs to take over, use unclaim or transfer rather than leaving ownership unclear.
Priority and status
Priority describes urgency. Status describes workflow state. They are separate so a ticket can be urgent while still open or pending.
Ticket access
Case can grant or remove explicit ticket access for members and roles without changing their global Discord permissions.
Application workflow
Application questions are created from the dashboard. Completed answers are sent to the configured review workflow, where authorized staff can inspect them and accept or decline the applicant.
Result automation
Accepted and declined outcomes can send custom messages and apply configured roles. Discord role hierarchy still applies.
Review permissions
Only grant reviewer access to people who should be able to read application answers and make decisions.
Transcripts
Case can save ticket history with usernames, avatars, timestamps, messages, attachments, embeds and ticket metadata. Online transcripts are read-only so staff can review a closed Case later.
If a transcript is missing messages, verify that Case could view the channel and read message history before the ticket was closed.
Dashboard
The Case dashboard is the main configuration area. It includes ticket and application builders, routing, questions, role automation, dashboard-user access, audit logs, transcript settings and server settings.
Saving a new panel design does not automatically rewrite an old Discord panel message. Publish a fresh panel when you want Discord to show the latest version.
Every command
Search all 94 Case commands below. Each command has its own explanation, usage guidance and important note.
/applicationaccept
Applications
Accepts the active application and records the reviewer decision.
When to use it: Use this only after reviewing the applicant's submitted answers.
Good to know: Accepted messages and role automation use the dashboard configuration.
/applicationblacklist
Applications
Block a member from applying.
When to use it: Use this when a member should no longer be able to start the relevant workflow.
Good to know: Save a useful reason so staff understand the block.
/applicationclose
Applications
Close and delete an application channel.
When to use it: Use /applicationclose for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationdeny
Applications
Declines the active application and records the reviewer decision.
When to use it: Use this when review is complete and the applicant should not be accepted.
Good to know: Declined messages and role automation use the dashboard configuration.
/applicationfaq
Applications
Show quick guidance for applicants.
When to use it: Use /applicationfaq for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationinfo
Applications
Show information about the application in this channel.
When to use it: Use /applicationinfo for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationlist
Applications
List recent applications.
When to use it: Use /applicationlist for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationpanel
Applications
Posts the configured application panel.
When to use it: Use this after creating the questions and review routing in the dashboard.
Good to know: Preview the panel first if you want to check wording and appearance.
/applicationpanelpreview
Applications
Preview the application panel privately.
When to use it: Use /applicationpanelpreview for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationreset
Applications
Reset a member's open application.
When to use it: Use /applicationreset for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationsetup
Applications
Configures the server's application system.
When to use it: Use this before posting an application panel to set review access, destinations, and role outcomes.
Good to know: For role automation, Case needs Manage Roles and must sit above the roles it manages.
/applicationstats
Applications
Show application statistics.
When to use it: Use /applicationstats for this specific step of the application workflow.
Good to know: Application commands respect reviewer access and dashboard routing/automation.
/applicationunblacklist
Applications
Allow a blocked member to apply again.
When to use it: Use this to restore a member's ability to start the relevant workflow.
Good to know: Removing a blacklist does not reopen old tickets/applications.
/add
Core Ticketing
Add a member to the current Case.
When to use it: Use /add when you need the specific action described above.
Good to know: Discord shows required options before submission.
/claim
Core Ticketing
Assigns the active Case to you.
When to use it: Use this when you begin handling a ticket so staff know who owns it.
Good to know: Use unclaim or transfer when responsibility changes.
/close
Core Ticketing
Finishes the active Case and closes its workflow.
When to use it: Use this once the support issue is complete and the conversation should be archived/closed.
Good to know: Save anything important before closing; transcript behavior follows your Case configuration.
/panel
Core Ticketing
Posts the configured ticket panel into Discord.
When to use it: Use this after designing and routing the panel in the dashboard.
Good to know: Old Discord panel messages are not magically redesigned; publish a fresh one after major changes.
/priority
Core Ticketing
Changes the priority of the active Case.
When to use it: Use this to separate low/normal/high/urgent work for staff.
Good to know: Priority is organizational and does not automatically ping staff.
/remove
Core Ticketing
Remove a member from the current Case.
When to use it: Use /remove when you need the specific action described above.
Good to know: Discord shows required options before submission.
/rename
Core Ticketing
Rename the current Case.
When to use it: Use /rename when you need the specific action described above.
Good to know: Discord shows required options before submission.
/settings
Core Ticketing
View Case settings for this server.
When to use it: Use /settings when you need the specific action described above.
Good to know: Discord shows required options before submission.
/setup
Core Ticketing
Configures the server's core Case ticket settings.
When to use it: Run this first after adding Case so the support role, ticket category, and logs destination are known.
Good to know: If ticket creation fails later, re-check the saved category and Case's Manage Channels permission.
/unclaim
Core Ticketing
Releases the active Case from its current staff owner.
When to use it: Use this when you cannot continue handling the ticket or claimed it by mistake.
Good to know: The ticket stays open.
/botinfo
Information & Diagnostics
Show information about Case.
When to use it: Use /botinfo for a read-only lookup of the relevant Discord/Case object.
Good to know: Information commands do not modify configuration.
/caseabout
Information & Diagnostics
Learn what Case can do.
When to use it: Use /caseabout to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/casehealth
Information & Diagnostics
Run a quick Case configuration health check.
When to use it: Use /casehealth to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/caseinvitecheck
Information & Diagnostics
Check whether Case has key server permissions.
When to use it: Use /caseinvitecheck to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/casepermissions
Information & Diagnostics
Show the important permissions Case needs.
When to use it: Use /casepermissions to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/casesummary
Information & Diagnostics
Show a compact summary of Case configuration.
When to use it: Use /casesummary to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/caseversion
Information & Diagnostics
Show the current Case build.
When to use it: Use /caseversion to inspect Case itself, its health, configuration, version, or permissions.
Good to know: Diagnostics are useful before changing settings.
/channelinfo
Information & Diagnostics
Show information about a channel.
When to use it: Use /channelinfo for a read-only lookup of the relevant Discord/Case object.
Good to know: Information commands do not modify configuration.
/help
Information & Diagnostics
Points users to Case help.
When to use it: Use /help for the short pointer and -help for the interactive Discord command browser.
Good to know: The full website documentation is available at /docs.
/panelpreview
Information & Diagnostics
Preview the ticket panel privately.
When to use it: Use /panelpreview for the corresponding Case panel action.
Good to know: Panel design and routing are primarily configured from the dashboard.
/ping
Information & Diagnostics
Check Case latency.
When to use it: Use this to quickly check whether Case is online and responding normally.
Good to know: High latency can come from Discord/API/network delay.
/roleinfo
Information & Diagnostics
Show information about a role.
When to use it: Use /roleinfo for a read-only lookup of the relevant Discord/Case object.
Good to know: Information commands do not modify configuration.
/serverinfo
Information & Diagnostics
Show basic server information.
When to use it: Use /serverinfo for a read-only lookup of the relevant Discord/Case object.
Good to know: Information commands do not modify configuration.
/userinfo
Information & Diagnostics
Show information about a member.
When to use it: Use /userinfo for a read-only lookup of the relevant Discord/Case object.
Good to know: Information commands do not modify configuration.
/supportrole
Other
Show the configured support role.
When to use it: Use this to confirm which Discord role Case currently treats as support staff.
Good to know: Update the server configuration if the role is wrong.
/blacklistupdate
Ticket Management
Enforce the blacklist against currently open Cases.
When to use it: Use this when a member should no longer be able to start the relevant workflow.
Good to know: Save a useful reason so staff understand the block.
/ticketaddrole
Ticket Management
Give a role access to the current Case.
When to use it: Use this to give a Discord role explicit access to the active Case.
Good to know: Only grant roles that should be able to read the ticket.
/ticketage
Ticket Management
Show how long ago this Case was opened.
When to use it: Use this when staff need exact timing or age information for the Case.
Good to know: This does not modify the ticket.
/ticketarchive
Ticket Management
Archive the current Case without deleting it.
When to use it: Use this when a Case should be preserved but no longer treated as active.
Good to know: Archiving is different from deleting the channel.
/ticketblacklist
Ticket Management
Prevent a member from opening tickets.
When to use it: Use this when a member should no longer be able to start the relevant workflow.
Good to know: Save a useful reason so staff understand the block.
/ticketblacklistcheck
Ticket Management
Check whether a member is ticket-blacklisted.
When to use it: Use this to verify whether a member is currently blocked.
Good to know: This is a read-only check.
/ticketcategory
Ticket Management
Show the configured ticket category.
When to use it: Use /ticketcategory for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketclaimer
Ticket Management
Show who currently owns the Case.
When to use it: Use /ticketclaimer for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketclaimforce
Ticket Management
Force-claim the current Case even if someone else owns it.
When to use it: Use /ticketclaimforce for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketclearnotes
Ticket Management
Delete all staff notes on this Case.
When to use it: Use this only when all saved staff notes should be removed.
Good to know: Clearing notes is destructive.
/ticketcount
Ticket Management
Count a member's recorded tickets.
When to use it: Use /ticketcount for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketcreated
Ticket Management
Show the exact Case creation timestamp.
When to use it: Use this when staff need exact timing or age information for the Case.
Good to know: This does not modify the ticket.
/ticketdm
Ticket Management
DM the ticket opener from Case.
When to use it: Use this when staff need Case to privately message the ticket opener.
Good to know: The user must allow the DM to be delivered.
/ticketduplicate
Ticket Management
Create a linked duplicate Case channel.
When to use it: Use this when staff need a linked second Case for the same issue.
Good to know: Avoid unnecessary duplicates because they split context.
/ticketexport
Ticket Management
Export ticket details as JSON.
When to use it: Use this when staff need ticket metadata in machine-readable JSON.
Good to know: This is separate from the conversation transcript.
/ticketfaq
Ticket Management
Show quick guidance for ticket users.
When to use it: Use /ticketfaq for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketfind
Ticket Management
Find a member's open Case.
When to use it: Use this to locate Case tickets without manually searching channel categories.
Good to know: Results depend on records stored by Case.
/ticketid
Ticket Management
Show the Case/channel ID.
When to use it: Use /ticketid for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketinfo
Ticket Management
Show detailed information about the current Case.
When to use it: Use /ticketinfo for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketlist
Ticket Management
List recent open tickets.
When to use it: Use this to locate Case tickets without manually searching channel categories.
Good to know: Results depend on records stored by Case.
/ticketlock
Ticket Management
Lock the current Case so the opener cannot send messages.
When to use it: Use this when staff need to stop the opener from sending new messages temporarily.
Good to know: Staff can still manage the Case.
/ticketlogs
Ticket Management
Show the configured ticket logs channel.
When to use it: Use /ticketlogs for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketmembers
Ticket Management
List members with explicit access to this Case.
When to use it: Use this to audit members with explicit access to the Case.
Good to know: Helpful for sensitive tickets.
/ticketmentionstaff
Ticket Management
Mention the configured support role in this Case.
When to use it: Use /ticketmentionstaff for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketmove
Ticket Management
Move this Case to another category.
When to use it: Use this to move the active Case to another Discord category.
Good to know: Case needs access to the destination category.
/ticketname
Ticket Management
Show the current Case channel name.
When to use it: Use /ticketname for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketnote
Ticket Management
Add a private staff note to the current Case.
When to use it: Use this to leave internal context for other support staff.
Good to know: Ticket notes are staff workflow data, not a reply to the opener.
/ticketnotes
Ticket Management
View staff notes for the current Case.
When to use it: Use this to review the private notes already saved on the Case.
Good to know: Useful when handing a ticket to another staff member.
/ticketopenstatus
Ticket Management
Mark this Case as open.
When to use it: Use this when the recorded workflow status should match what is happening in support.
Good to know: Status changes are separate from deleting/closing the channel unless stated otherwise.
/ticketowner
Ticket Management
Show who opened the current Case.
When to use it: Use /ticketowner for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketpending
Ticket Management
Mark this Case as pending.
When to use it: Use this when the recorded workflow status should match what is happening in support.
Good to know: Status changes are separate from deleting/closing the channel unless stated otherwise.
/ticketping
Ticket Management
Ping the ticket opener with a support reminder.
When to use it: Use this when the opener needs a reminder that staff are waiting for a response.
Good to know: Avoid repeated pings in a short period.
/ticketpriorityhigh
Ticket Management
Quickly sets the active Case priority to High.
When to use it: Use this shortcut when the ticket should immediately be marked high.
Good to know: This changes the recorded priority only.
/ticketprioritylow
Ticket Management
Quickly sets the active Case priority to Low.
When to use it: Use this shortcut when the ticket should immediately be marked low.
Good to know: This changes the recorded priority only.
/ticketprioritynormal
Ticket Management
Quickly sets the active Case priority to Normal.
When to use it: Use this shortcut when the ticket should immediately be marked normal.
Good to know: This changes the recorded priority only.
/ticketpriorityurgent
Ticket Management
Quickly sets the active Case priority to Urgent.
When to use it: Use this shortcut when the ticket should immediately be marked urgent.
Good to know: This changes the recorded priority only.
/ticketpurge
Ticket Management
Delete a number of recent messages in this Case.
When to use it: Use this to remove a selected number of recent ticket messages.
Good to know: Deleted Discord messages cannot be restored by Case.
/ticketreminder
Ticket Management
Post a standard waiting-for-response reminder.
When to use it: Use this when the opener needs a reminder that staff are waiting for a response.
Good to know: Avoid repeated pings in a short period.
/ticketremoverole
Ticket Management
Remove a role's explicit access to this Case.
When to use it: Use this to remove a role's explicit ticket access.
Good to know: Other permission overwrites may still grant access.
/ticketrenameuser
Ticket Management
Rename this Case using the opener's current name.
When to use it: Use /ticketrenameuser for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketreopen
Ticket Management
Mark the current Case as open again.
When to use it: Use this when the recorded workflow status should match what is happening in support.
Good to know: Status changes are separate from deleting/closing the channel unless stated otherwise.
/ticketrequest
Ticket Management
Create a Case ticket for another member.
When to use it: Use /ticketrequest for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/ticketresolved
Ticket Management
Mark this Case as resolved without closing it.
When to use it: Use this when the recorded workflow status should match what is happening in support.
Good to know: Status changes are separate from deleting/closing the channel unless stated otherwise.
/ticketslowmode
Ticket Management
Set slowmode for the current Case.
When to use it: Use this to control how frequently users can send messages in a busy Case.
Good to know: Set slowmode back to zero to remove it.
/ticketstats
Ticket Management
Show ticket statistics for this server.
When to use it: Use this for a server-wide summary of ticket activity.
Good to know: Statistics are read-only.
/ticketstatus
Ticket Management
Show the current Case status.
When to use it: Use this when the recorded workflow status should match what is happening in support.
Good to know: Status changes are separate from deleting/closing the channel unless stated otherwise.
/tickettag
Ticket Management
Add a tag to the current Case.
When to use it: Use this to label the Case with an internal topic such as billing, report, bug, or appeal.
Good to know: Tags organize tickets; they do not change permissions.
/tickettags
Ticket Management
View tags on the current Case.
When to use it: Use this to review all tags currently attached to the Case.
Good to know: This is read-only.
/tickettopic
Ticket Management
Set the current Case channel topic.
When to use it: Use /tickettopic for this specific ticket-management action.
Good to know: Most ticket-management commands require an active Case and staff access.
/tickettransfer
Ticket Management
Transfer a claimed Case to another staff member.
When to use it: Use this to hand a claimed Case to a different staff member.
Good to know: Best for staff handoffs.
/ticketunblacklist
Ticket Management
Remove a member from the ticket blacklist.
When to use it: Use this to restore a member's ability to start the relevant workflow.
Good to know: Removing a blacklist does not reopen old tickets/applications.
/ticketunlock
Ticket Management
Unlock the current Case for the opener.
When to use it: Use this to let the opener send messages again after a lock.
Good to know: Claim/status are unchanged.
/ticketuntag
Ticket Management
Remove a tag from the current Case.
When to use it: Use this when a tag no longer applies to the current Case.
Good to know: Only the selected tag is removed.
/transcript
Transcripts
Generates a transcript of the active Case.
When to use it: Use this when staff need a permanent record of the ticket conversation.
Good to know: Case needs View Channel and Read Message History for a complete transcript.
/transcriptinfo
Transcripts
Explain Case transcript formats.
When to use it: Use /transcriptinfo when you need transcript information or output.
Good to know: Transcript completeness depends on message-history access.
/transcriptpreview
Transcripts
Generate the improved HTML/TXT transcript without closing.
When to use it: Use /transcriptpreview when you need transcript information or output.
Good to know: Transcript completeness depends on message-history access.
Troubleshooting
Tickets are not being created
Check that the configured category still exists and that Case has Manage Channels and permission to view that category.
Application roles are not being assigned
Check that the role still exists, Case has Manage Roles and the Case bot role is above the target role.
A transcript is incomplete
Case must have View Channel and Read Message History access in the ticket channel.
A panel still looks old
Publish a fresh panel after changing its design. Existing Discord panel messages are not automatically replaced.
A dashboard user cannot access a server
Make sure the user is still in the Discord server and has the required Case dashboard capability.