Build reusable private ticket types, assign staff access, publish a member-facing ticket panel, and verify the complete open-and-close workflow.
How to create a Discord ticket system with GuildPilot
GuildPilot tickets open private Discord channels from reusable ticket types. Each type defines its staff roles, category, channel name, opening message and closing rules, while the ticket panel builder arranges up to five ticket types in a Components V2 message.
Before you start
- Create a public text channel for the ticket panel.
- Create a Discord category for private ticket channels.
- Create the staff roles that should see each ticket type.
- GuildPilot must be able to manage channels, permission overrides, messages and interactive components.
Warning: Ticket staff roles can see member support conversations. Select only trusted roles and review the generated channel permissions with a normal member account.
Create a ticket system
1. Create a reusable ticket type
Open the server dashboard, select Tickets, then choose New type under Ticket buttons. Enter Ticket type name, optional Emoji, and Button color.
2. Configure the private ticket channel
Under Creating tickets, select Staff roles, choose Ticket category, and set the channel-name pattern. The displayed placeholders include values such as the ticket sequence and member identity.
3. Configure the opening and closing behavior
Under Automatic opening message, decide whether GuildPilot posts Message inside new ticket. Under Closing tickets, choose Let members close their own ticket and set Auto-close after inactive days when needed.
4. Publish a ticket panel
Return to Tickets hub and choose New ticket panel. Enter its name and select the destination channel. Use Add component to arrange content, containers, images, files, separators, ticket buttons, link buttons or a ticket select menu. Select each ticket action in the preview and choose its reusable ticket type in the editor on the right.
5. Save the panel
Publish the panel. GuildPilot sends the live Discord message and lists it in Tickets hub.
Recommended configuration
Create separate types when staff roles, questions or destination categories differ. Keep the opening message focused on the next action staff or the member should take.
Test the setup
- Select a panel button with a normal member account.
- Confirm that GuildPilot creates a private channel in the configured category.
- Check that only the ticket owner, selected staff and authorised server roles can view it.
- Close the test ticket and remove any test panel only if it should not remain published.
What a successful setup looks like
The panel remains in the public channel, selecting a type creates one private ticket with the expected name and opening message, and the configured staff roles can respond.
Common problems
No ticket type can be added to a panel
Cause: No reusable ticket type exists yet.
Fix: Create and save a type under Ticket buttons, then reopen the panel editor.
The ticket channel is not private
Cause: The bot could not apply the intended permission overwrites or the tester has Administrator.
Fix: Test with a normal member account and review GuildPilot's channel-management permissions.
The panel cannot be published
Cause: GuildPilot cannot send the live message or use components in the selected channel.
Fix: Review the panel channel permissions and publish again. GuildPilot does not activate a new panel when live delivery fails.