Skip to main content
These commands are for server administrators and require elevated permissions.

​
/setup

Create the Discord infrastructure needed for your ticket system. 
/setup
Permission: Administrator What it creates:
ResourceDescription
Tickets categoryWhere new tickets are created
Closed Tickets categoryWhere closed tickets are moved
Ticket Admin roleFull ticket management access
Ticket Support roleBasic ticket access
The /setup command only creates Discord resources. You must complete configuration on the dashboard for your bot to work.

​
Handling Existing Resources

If /setup detects existing ticket categories or roles, you’ll see options:
OptionDescription
Create AnywayCreates new resources with unique names
Use ExistingSkip creation - configure existing resources on dashboard
CancelAbort setup

​
After Running Setup

1

Go to the dashboard

Visit ticketcord.net/dashboard
2

Select resources

Choose the categories and roles created by /setup
3

Configure settings

Set up automation, AI features, and other options
4

Create embeds

Build ticket embeds with buttons for users to open tickets

​
/embed

Send a custom embed message to a channel. 
/embed <embed_name> [channel]
OptionTypeRequiredDescription
embed_nameChoiceYesName of the saved embed
channelChannelNoTarget channel (defaults to current)
Permission: Manage Messages What happens:
  • Sends the pre-designed embed to the channel
  • Includes any configured buttons (like “Open Ticket”)
  • Embeds are created in the dashboard

​
Creating Embeds

  1. Go to your dashboard
  2. Navigate to Embeds
  3. Click Create Embed
  4. Design using the visual builder
  5. Save with a name

​
Embed Features

FeatureDescription
Rich formattingTitle, description, fields, images, footer
Custom colorsMatch your server’s branding
ButtonsAdd interactive buttons (Open Ticket, Link, etc.)
Dropdown menusLet users select ticket categories
Example: 
/embed embed_name:support-panel channel:#get-help
Create different embeds for different support types: general support, sales inquiries, bug reports, etc.

​
/approval

Manage approval workflows for sensitive actions. Staff can request approval from senior staff before taking certain actions. 
/approval request <type> <reason> [urgency] [amount] [custom_type]
/approval approve [reason]
/approval reject <reason>
/approval status
Permission: Staff
Plan: Enterprise only

​
Subcommands

SubcommandDescription
requestSubmit an approval request
approveApprove a pending request
rejectReject a pending request
statusView current approval status

​
Request Options

OptionTypeRequiredDescription
typeChoiceYesType of approval
reasonTextYesDetailed reason for request
urgencyChoiceNoHow urgent is this
amountTextNoAmount involved (for refunds)
custom_typeTextNoCustom type name
Type choices:
  • refund - Refund request
  • ban - Ban request
  • policy_exception - Policy exception
  • escalation - Escalation request
  • custom - Custom type

​
Requesting Approval

/approval request type:refund reason:Customer received damaged product amount:$49.99 urgency:high

​
Approving/Rejecting

Only users with approval authority can approve or reject: 
/approval approve reason:Verified damage in photos
/approval reject reason:Outside return window - policy doesn't allow

​
Approval Workflow

1

Staff submits request

Uses /approval request with details
2

Notification sent

Approvers receive notification in configured channel
3

Review and decide

Approver uses /approval approve or /approval reject
4

Action taken

Original staff member is notified of decision
Configure approval roles and notification channels in your dashboard under Enterprise Features → Approvals.

​
/purge

Bulk delete tickets from your server. Use with caution. 
/purge <type> [older_than]
OptionTypeRequiredDescription
typeChoiceYesWhat to purge
older_thanIntegerNoDays threshold
Type choices:
  • closed - Delete closed tickets only
  • all - Delete all tickets
Permission: Server Owner only
This action is irreversible. Deleted tickets cannot be recovered. Transcripts should be generated before purging.

​
Safety Measures

  • Only the server owner can use this command
  • A confirmation dialog is shown before deletion
  • You can limit to tickets older than X days
Example: 
/purge type:closed older_than:30
This deletes all closed tickets older than 30 days.
Set up auto-delete in your dashboard for automatic cleanup instead of manual purging.

Utility Commands

Learn about help, on-call, and user lookups