Ticket Panels
Panels are interactive messages that allow users to create tickets. They can display buttons or use reaction emojis for ticket creation.
What are Panels?
A panel is an embed message posted in a Discord channel. When users interact with it (button click or emoji reaction), the bot creates a new ticket channel or starts a support flow.
Panels can:
- Open tickets in specific categories
- Trigger support flows before creating tickets
- Display multiple options with buttons or reactions
- Be fully customized with embeds
Panel Types
Button Panels
Users click Discord buttons to create tickets.
- Up to 5 buttons (more than 5 items switches to a dropdown select menu, category items only)
- 4 style options: Primary (Blue), Secondary (Gray), Success (Green), Danger (Red)
- Optional emoji on each button, custom labels
- Best for 1-5 categories and quick one-click creation
Reaction Panels
Users react with emojis to create tickets.
- Users add emoji reactions
- Each reaction opens a specific category or flow
- Compact single-message design with custom emoji support
- Best for a minimal footprint and a familiar Discord interaction
Creating a Panel
Panel limits
Free servers can create up to 3 ticket panels. Community and Pro servers get unlimited panels. See the pricing page for details.
Access the dashboard and navigate to Panels:
Panel Configuration
Basic Settings:
- Panel Name: Internal identifier (not shown to users)
Embed Customization:
- Title: Main heading of the panel
- Description: Instructions or information for users
- URL: Optional clickable title link
- Color: Hex color for embed border (#5865F2)
- Timestamp: Show current time
- Thumbnail URL: Small image in top-right corner
- Image URL: Large image below description
- Author Name/URL/Icon: Author section at top
- Footer Text/Icon: Footer at bottom
- Embed Fields: Up to 25 custom fields with name/value pairs
Panel Type:
- BUTTON: Discord button interactions
- REACTION: Emoji reaction interactions
Panel Items:
For each item, configure:
- Category or Flow: What happens when clicked
- Select a category to directly open a ticket
- Select a flow to run automation before ticket creation
For BUTTON panels:
- Button Label: Text on the button (max 80 characters)
- Emoji: Optional emoji before label
- Style: PRIMARY, SECONDARY, SUCCESS, or DANGER
For REACTION panels:
- Emoji: Required reaction emoji
Deploying a Panel
Creating a panel in the dashboard saves its configuration but does not post it to Discord. To make a panel live, deploy it from Discord:
- Run the
/setup-panelslash command in your server. - Select the panel you saved.
- Choose the target text channel to post it in.
The bot posts the panel message to that channel. /setup-panel defaults to Administrator-only access.
Button Styles
| Style | Color | Use Case |
|---|---|---|
PRIMARY | Blue | Default, general actions |
SECONDARY | Gray | Alternative or less important options |
SUCCESS | Green | Positive actions, confirmations |
DANGER | Red | Important or urgent issues |
Embed Anatomy
A panel embed can include all of these optional sections:
š” Hover over sections to see labels
Panel Items
Each panel can have multiple items (buttons or reactions). Each item can either:
- Open a Ticket - Directly create a ticket in a category
- Start a Flow - Run a support flow, then optionally create a ticket
Flow Integration
Support flows can:
- Collect information before creating tickets
- Show buttons or select menus
- Run conditional logic
- Trigger webhooks or API calls
- Create tickets with pre-filled information
Flows
Learn more about support flows in the Support Flows guide.
Editing Panels
Panels can be edited anytime from the dashboard. When you save changes, the message in Discord automatically updates.
Editable:
- Embed content (title, description, color, images)
- Button labels and styles
- Panel items (add, remove, reorder)
- Categories and flows
- Panel type (BUTTON vs REACTION) - switching type updates the deployed message on save
To move a deployed panel to another channel, run /setup-panel again and pick the new channel. The bot removes the old message and posts a fresh one in the new channel. There is no need to delete and recreate the panel.
Best Practices
Clear Instructions
Write helpful descriptions that tell users:
- What each option does
- What information to provide
- Expected response times
- Alternative support options (docs, FAQ)
Example:
Need help? Click a button below:
š« General Support - Questions and help
š Bug Reports - Technical issues
š³ Billing - Payment questions
Strategic Placement
Place panels in accessible channels:
- Dedicated #support or #tickets channel
- High-traffic channels like #general (for smaller servers)
- Category-specific channels (#technical-support, #billing)
Appropriate Button Styles
Use colors that match the action:
- Blue (Primary) - General support, default options
- Gray (Secondary) - Less common options
- Green (Success) - Feedback, suggestions
- Red (Danger) - Urgent issues, reports
Emoji Choice
For button panels, emojis make buttons more recognizable:
- š« Ticket/Support
- š Bug reports
- š” Suggestions
- š³ Billing
- ā ļø Urgent/Reports
- š Applications
For reaction panels, use distinct, recognizable emojis.
Common Panel Setups
Simple Support Panel
Type: Button Items: 1 button Label: "Create Support Ticket" Style: Primary Category: Support
Multi-Category Panel
Type: Button Items:
- Support (Blue)
- Bug Reports (Red)
- Suggestions (Green)
Flow-Based Panel
Type: Button Items:
- "Report a User" ā Moderation Flow ā Mod Reports Category
- "Appeal a Ban" ā Appeal Flow ā Appeals Category
Troubleshooting
Panel not appearing
- Check bot has Send Messages and Embed Links permissions
- Verify channel is selected correctly
- Ensure bot is online
Buttons don't work
- Verify categories still exist
- Check bot has necessary permissions
- Ensure bot is online and responding
Panel looks wrong
- Verify embed markdown formatting
- Check image URLs are accessible
- Ensure color is valid hex format
Can't edit panel
- You must have dashboard access
- Panel must not be deleted
- Check browser console for errors