​
Tickets

The Tickets system allows you to create a comprehensive support ticket system with customizable topics, roles, categories, logging, inactivity checks, and DM notifications.

The bot requires the Manage Channels permission to create and manage tickets.

​
Setup

​
Basic Setup

To set up the ticket system, use the following command:

,ticket setup #channel

You must have the Manage Server permission to set up tickets.

​
Customizing the Panel

You can customize the ticket panel using the following flags:

# Basic setup with custom embed
,ticket setup #channel --code "{embed}{color: #2b2d31}$v{title: Create a ticket}$v{description: Click the button below to create a ticket}"

# Custom emojis for buttons
,ticket setup #channel --open=🎫 --delete=🗑️

The code parameter uses the Script system syntax. Visit greed.best/embed to create your embed visually.

​
Support Role

Set a default support role for tickets:

,ticket support @role

This role will have access to:

  • Tickets created without a topic
  • Topic tickets that have no specific roles assigned

​
Category

Set a category where tickets will be created:

,ticket category #category

​
Ticket Topics

​
Managing Topics

Access the topics management menu:

,ticket topics

This interactive menu allows you to:

  1. Add new topics
  2. Remove existing topics
  3. Manage topic settings

​
Topic Configuration

For each topic, you can configure:

  1. Access Roles

    • Assign specific roles that can access tickets in this topic
    • Multiple roles can be added per topic
    • If no roles are assigned, default support role is used

  2. Category Channel

    • Set a specific category for tickets in this topic
    • Overrides the default ticket category
    • Useful for organizing different types of tickets

  3. Description

    • Add a description that users see when selecting the topic
    • Helps users choose the correct topic for their issue

​
Ticket Management

​
In-Ticket Controls

Each ticket has the following controls:

  • Close (🔒) - Makes the ticket read-only
  • Transcript (📑) - Creates a transcript of the ticket
  • Delete (🗑️) - Permanently deletes the ticket

​
User Management

# Add a user to a ticket
,ticket add @user

# Remove a user from a ticket
,ticket remove @user

# Rename a ticket
,ticket rename new-name

​
Advanced Features

​
Inactivity Checking

Enable automatic inactivity checking:

# Enable/disable inactivity checking
,ticket inactivity true/false

# Set inactivity timeout (in hours)
,ticket timeout 24

When a ticket is inactive for the specified duration:

  • A warning message is sent
  • Close and Delete buttons are provided
  • Staff is notified through logs if enabled

​
DM Notifications

Configure DM notifications for ticket updates:

,ticket dms true/false

Users will receive DM notifications for:

  • Ticket closure
  • Ticket deletion (including transcript ID)

​
Logging System

Set up ticket logging:

# Set log channel
,ticket logs channel #channel

# Configure log events
,ticket logs events

Available log events:

  • ticket_create
  • ticket_close
  • ticket_delete
  • ticket_transcript
  • ticket_member_leave
  • ticket_inactive

​
Transcripts

Transcripts are automatically created when:

  • Using the Transcript button
  • Deleting a ticket

Each transcript includes:

  • Complete message history
  • Member information (roles, colors)
  • Ticket metadata (opener, staff, topic)
  • Unique transcript ID for reference

​
Settings & Maintenance

​
View Settings

Check your ticket settings:

,ticket settings

Displays:

  • Support role
  • Channel category
  • Topics configuration
  • Opening ticket embed
  • DM notifications status
  • Inactivity check settings
  • Logging configuration

​
Send Panel

Update ticket panel without changing settings:

,ticket send #channel

​
Reset System

Reset the entire ticket system:

,ticket reset

This will:

  • Disable all existing ticket panels
  • Remove all ticket configurations
  • Delete all topic settings

​
Best Practices

  1. Topic Organization

    • Create clear, specific topics
    • Add descriptive explanations
    • Assign appropriate categories

  2. Role Management

    • Use topic-specific roles for specialized support
    • Set up a default support role as fallback
    • Ensure proper role hierarchy

  3. Logging & Monitoring

    • Enable comprehensive logging
    • Set appropriate inactivity timeouts
    • Monitor transcript creation

  4. User Experience

    • Customize embed descriptions
    • Enable DM notifications
    • Organize categories logically

Use the interactive UI at greed.best/embed to create beautiful ticket panels with custom colors and formatting.

​
Troubleshooting

  1. Missing Permissions

    • Bot needs Manage Channels
    • Support roles need proper permissions
    • Check category permissions

  2. Role Hierarchy

    • Bot’s role must be above support roles
    • Check server role order

  3. Category Access

    • Verify bot can manage categories
    • Check category permission syncing

  4. Notifications

    • Users must accept DMs for notifications
    • Check log channel permissions
    • Verify webhook permissions

Always test new configurations in a controlled environment before deploying to production channels.