Server configuration
Tickets
Create and manage support ticket channels with customizable workflows and staff roles.
Slash commands for this page
Set this up in Discord with /configure feature:Tickets, or on the dashboard under Moderation › Tickets.
Use the slash version of each command below. Prefix commands keep working until March 5, 2027. What is changing
,ticket claim→/ticket claim,ticket unclaim→/ticket unclaim,ticket close→/ticket close,ticket reopen→/ticket reopen,ticket delete→/ticket delete,ticket transcript→/ticket transcript
,ticket analytics→/ticket analytics,ticket blacklist→/configure feature:Tickets,ticket profiles→/configure feature:Tickets,ticket all→/configure feature:Tickets,ticket stats→/configure feature:Tickets,ticket panel→/configure feature:Tickets,ticket panel create→/configure feature:Tickets,ticket panel send→/configure feature:Tickets,ticket panel list→/configure feature:Tickets,ticket panel delete→/configure feature:Tickets,ticket panel channel→/configure feature:Tickets,ticket panel maxopen→/configure feature:Tickets,ticket panel category→/configure feature:Tickets,ticket panel logs→/configure feature:Tickets,ticket option add→/configure feature:Tickets,ticket option list→/configure feature:Tickets,ticket option remove→/configure feature:Tickets,ticket option category→/configure feature:Tickets,ticket option form→/configure feature:Tickets,ticket option closeonleave→/configure feature:Tickets,ticket option support→/configure feature:Tickets,ticket form create→/configure feature:Tickets,ticket form list→/configure feature:Tickets,ticket form delete→/configure feature:Tickets,ticket list open→/configure feature:Tickets,ticket list claimed→/configure feature:Tickets,ticket list closed→/configure feature:Tickets,ticket list user→/configure feature:Tickets,ticket→@greed ticket,ticket reason→@greed ticket reason,ticket profile→@greed ticket profile,ticket status→@greed ticket status,ticket trainee grant→@greed ticket trainee grant,ticket trainee revoke→@greed ticket trainee revoke,ticket trainee list→@greed ticket trainee list
Overview
The ticket system allows servers to create dedicated support channels for users. Administrators set up panels with button or dropdown menus, and members create tickets by selecting an option. Staff can claim, manage, and track tickets with full customization.
Getting Started
Run one command:
/ticket setupThen choose one of two ways:
- Quick setup creates everything for you: a Ticket Support role (unless you pick one of your own), an #open-a-ticket channel with the panel already posted, a private #ticket-logs channel, and for channel tickets a Tickets category. Hand the support role to your staff and you're done. greed needs View Channels, Manage Channels, Manage Roles, Send Messages and Embed Links for this (plus Create Private Threads, Send Messages in Threads and Manage Threads for thread tickets), and tells you if one is missing.
- Create panel uses a channel and support role you already have. A category is optional; without one, tickets open at the top level.
You can also set tickets up when you first add greed: pick Tickets in Automatic Setup in your server, or on the onboarding page of the dashboard. The dashboard's Tickets page has a Quick setup button too.
Everything else has a sensible default you can change later. Run /ticket setup again to change the basics, or press Advanced for every setting.
Prefer to do it by hand? ,ticket panel create (name) [mode] and ,ticket panel send (name) still work, along with every other subcommand.
Panels can use button or dropdown mode (default). Free servers get 1 panel; Server Premium removes the limit.
Channels or private threads
Every panel opens tickets one of two ways. You pick it in /ticket setup, in Advanced → Overview, or in the panel editor on the dashboard.
Each ticket gets its own text channel, inside the panel's category. Staff can move, hide, rename and re-permission it, and closed tickets can move to a separate category.
Each ticket is a private thread under the panel's channel. Only the person who opened it, your support roles and members with Manage Threads can see it. Threads never count toward Discord's 500-channel limit, so they suit busy servers.
Closing a ticket archives and locks its thread; reopening unlocks it. Threads can't be moved to a category, and roles can't be removed from a thread once added, so take people out one by one with /ticket remove.
greed needs Create Private Threads and Manage Threads in the panel's channel. Members need to be able to see that channel.
Before sending a panel, you must add at least one option to it. The panel message requires Send Messages and Manage Webhooks bot permissions in the destination channel.
Panel Setup
Configure where and how ticket panels appear.
,ticket panel create (name) [mode]: Create a new panel (button or dropdown).,ticket panel list: View all configured panels.,ticket panel delete (name): Remove a panel and its message.,ticket panel send (name): Publish or refresh the panel message.
,ticket panel channel (name) (channel): Set where the panel is posted.,ticket panel maxopen (name) (count): Limit how many open tickets per user per panel (0 = unlimited).,ticket panel category (name) (category): Set the default category for new tickets.,ticket panel logs (name) (channel): Set the channel where ticket logs are sent.
Panel names can contain spaces: ,ticket panel maxopen Sukoon Support 2 works as written.
Options & Categories
Options are the buttons or dropdown choices users click to create a ticket. Each option can route to its own category.
,ticket option add (panel) (name) (label): Add an option to a panel.,ticket option list (panel): View all options in a panel.,ticket option remove (panel) (name): Delete an option.
Options can create tickets in different channels. Tickets inherit the option's category or fall back to the panel's default.
,ticket option category (panel) (name) (category): Set where tickets from this option open.
Attach a form to an option so users fill out a modal when they select it.
,ticket option form (panel) (name) (form): Attach a form (ornoneto remove).
Automatically close or notify if the ticket creator leaves the server.
,ticket option closeonleave (panel) (name) (state): Enable/disable auto-close on leave.
Support Roles & Access
Control which roles can see, claim, and manage tickets.
Set the roles that can claim and manage tickets from an option.
,ticket option support (panel) (name) (roles): Assign support roles to an option.,ticket allow (target): Grant a member or role access to the current ticket.,ticket deny (target): Revoke access to the current ticket.
Trainees can view and optionally participate in tickets for training purposes.
,ticket trainee grant (target): Grant a member/role read-only access to this ticket.,ticket trainee revoke (target): Remove trainee access.,ticket trainee list: List trainee roles configured for this option.
Forms & Fields
Forms collect structured data from users when they create a ticket. Each panel can have multiple forms, and each form can have up to 5 fields.
,ticket form create (name) (title): Create a new form.,ticket form list: View all forms.,ticket form delete (name): Delete a form.
Add fields to a form. Available types: short_text, long_text, checkbox, select, role_select, user_select, channel_select.
,ticket fieldadd (form) (type) (label): Add a field to a form (max 5 per form).,ticket fieldremove (form) (key): Remove a field by its key.,ticket fields (form): View a form's fields.
Ticket Lifecycle
Commands for creating, claiming, and managing open tickets.
,ticket claim [reason]: Claim the current ticket (staff only).,ticket unclaim: Release your claim on the ticket.
,ticket close [reason]: Close the current ticket (staff or creator).,ticket reopen [reason]: Reopen a closed ticket (staff only).
,ticket delete [reason]: Delete the ticket and send a transcript to the log channel.,ticket transcript: Manually generate and send a transcript.- Every transcript comes as a file plus a View on web button. The web page shows the ticket the way it looked in Discord: embeds, buttons, attachments, reactions and replies. Only the person who opened the ticket, the server's ticket staff (support and trainee roles) and members with Manage Server can open it, after signing in with Discord.
Asking to close
When a problem looks solved, ask the member instead of closing on them:
/ticket requestclose
/ticket requestclose 24h Refund sentThe member gets Close ticket and Keep open buttons. Only they can accept; they, the staff member who asked, or any support staff can keep it open. With a timeout, the ticket closes on its own if nobody answers. Every open ticket also has a Request close button next to Claim and Close.
Ticket Management
Rename, move, and edit metadata on tickets.
/ticket rename (name): Rename the ticket (staff only)./ticket move (category): Move the ticket to a different category (staff only, channel tickets)./ticket transfer (option) [move]: Hand the ticket to another ticket option. Its support roles get access, the old option's roles lose it, and by default the channel moves to that option's category.
/ticket add (member or role): Let someone into the ticket./ticket remove (member or role): Take them out.
The old ,ticket allow and ,ticket deny still work.
/ticket open (member) [reason]: Open a ticket for someone, for example to pull a conversation out of a public channel. It skips the member's open-ticket limit and cooldown./ticket request (member) [reason]: DM a member a button that opens a ticket. Useful when you need to talk to someone privately./ticket new: Shows every ticket type as buttons, so members can open one without finding the panel.
Staff on the first ticket option, or anyone with Manage Channels, can use open and request.
Store or update reasons for any ticket action (claim, close, reopen, delete).
,ticket reason (action) (text): Edit a stored reason (staff only).
Blacklist
Prevent users or roles from creating tickets.
,ticket blacklist: List all blacklisted users and roles.,ticket blacklist (target): Toggle a user or role on/off the blacklist.
Blacklisted users cannot create tickets but can still be added to existing tickets manually.
Claim Profiles
Members can set a personalized greeting message that displays when they claim a ticket.
,ticket profile: View your current greeting message.,ticket profile (message): Set your claim greeting.,ticket profiles: List all members with set greetings (admin only).,ticket profiles (member): View a specific member's greeting.
Listing & Statistics
View ticket history and statistics.
,ticket list open: Show open tickets (paginated).,ticket list claimed: Show claimed tickets.,ticket list closed: Show closed tickets.,ticket list user (member): List all tickets for a member.,ticket all: Show all open tickets with full details.
,ticket status [member]: Show a member's ticket count (created, claimed, open).,ticket stats: Show server-wide statistics (admin only).
Priorities, Ratings & Notes
Tools your staff use inside a ticket.
Mark how urgent a ticket is.
,ticket priority highLevels: low, normal, high, urgent
Give the ticket a one-line summary.
,ticket subject refund for order 41Notes only your team can see: never shown to the person who opened the ticket.
,ticket note refunded manually, awaiting confirmation
,ticket notesAnswers you send over and over, stored once.
,ticket savedreply add refund We have issued your refund.
,ticket reply refund
,ticket savedreply listSaved replies support the same variables as any other ticket message.
5 saved replies on the free plan, 50 with Server Premium.
Link the case a ticket is about, so context is one click away.
,ticket case 42Only cases belonging to the person who opened the ticket can be attached.
Ratings & Analytics
Turn on Ask for a rating in ,ticket panel → Automation, and the bot DMs a 1–5 star row when a ticket closes. Each ticket can be rated once.
See how your team is doing.
,ticket analytics
,ticket analytics 7Shows tickets opened, closed and currently open; average first response and resolution time; average satisfaction; and a per-staff breakdown of claims and closes.
Ticket analytics is a Server Premium feature.
Turn on Auto-assign staff and each new ticket is claimed automatically by whichever member of your support role currently has the fewest open tickets.
/ticket leaderboard [days]: Your staff ranked by tickets closed and claimed (Manage Server)./ticket history (member): Every ticket a member has opened in this server (Manage Server).
Who can open tickets
Set these per option in Advanced → Access, or in the option editor on the dashboard.
Required roles limit an option to members with any (or all) of those roles. Blocked roles stop members with any of them from opening a ticket there.
Refuse tickets from Discord accounts younger than a set age, or from members who joined the server too recently. Useful against throwaway accounts.
Max open per user caps how many tickets one member can have open on a panel. Max open tickets in total caps the whole panel at once, so a raid can't flood your queue. Both say exactly why the member was refused.
Support hours
Tell members when your team is around. Set it in Advanced → Hours & reminders, or in the panel editor on the dashboard.
mon-fri 09:00-17:00; sat 10:00-14:00Write days (mon, mon-fri, weekdays, weekends, daily) and a time range, separated by ;. Ranges can run past midnight, like fri 22:00-02:00. Set a timezone such as Europe/London.
Outside those hours a panel can either open tickets with a notice that a reply may take longer, or refuse new tickets until support opens again. Leave the hours empty and support counts as always open.
Reminders and role rewards
Set Remind staff when unanswered for and greed pings the option's support roles once when a ticket has waited that long without a staff reply.
Give the member roles automatically: while a ticket is open (taken back when it closes), when staff claim it, or when it closes. greed only hands out roles below its own highest role.
Automations
Open tickets automatically from what members say, so they get help before they ask for it.
,ticket automation add crashes keyword support crash, keeps closing
,ticket automation add bugs channel support #bug-reports
,ticket automation list
,ticket automation toggle crashes off
,ticket automation remove crashes- Keywords fire when a message contains one of your comma-separated words (whole words only).
- Pattern fires on a regular expression. Patterns that could slow greed down are refused.
- Whole channel fires on any message in the channels you pick.
greed opens the ticket on the option you chose, tells the member where it is, and can post an alert in a staff channel. Each member gets at most one automatic ticket every five minutes per automation. Manage them all on the dashboard under Tickets → Automations, where you can also set a priority, a custom reply and an alert channel.
Free servers can have 3 ticket automations. Server Premium raises that to 25.
Status board
/ticket statusboard post #support
/ticket statusboard removePosts a live message showing how many tickets are open, how many are still waiting for a reply, today's totals, the average first reply time, your rating and whether each panel is inside its support hours. It updates itself every minute. You can also post it from Tickets → Automations on the dashboard.
AI help
/ticket resolveReads the ticket and its form answers and tells staff, privately, what it's about, what details are still missing and the next step. Handy when you pick up a long ticket someone else started.
Turn on AI asks for missing details on an option. When the member's first message is too vague to act on, greed asks up to three short follow-up questions in the ticket, so staff start with real information.
AI summaries and follow-up questions are Server Premium features. To write them, greed sends the ticket's form answers and messages (for follow-up questions, only the member's first message) to its AI provider. Leave them off if your tickets hold information that shouldn't leave Discord.
On the dashboard
Everything above is configurable from Discord, and the parts you are most likely to want on a screen are on the dashboard too, under Tickets.
No panels yet? Press Quick setup on the Panels tab, choose channels or private threads, and optionally pick your support role. greed creates the rest and posts the panel.
A live list of every ticket currently open: case number, subject, who opened it, priority, who claimed it, and how long it has been waiting.
Tickets nobody has replied to yet are marked Awaiting first reply, and ones the inactivity timer has already nudged are marked Inactivity warned, so the queue tells you where to look first.
Press Reply to read the ticket and answer it from the browser. Your reply is posted in the ticket with your name, and the conversation refreshes every few seconds. Anyone who can open the dashboard for your server (Manage Server) can read and reply to every ticket this way, even ones they can't see in Discord.
The Automations tab lists your ticket automations, lets you add and edit them, and posts or removes the status board.
Add, edit and delete saved replies without leaving the dashboard. Each one shows how many times staff have used it, so you can see which answers are actually pulling their weight.
Saved replies use the same scripting as ticket messages, and the same limit applies whether you add them here or in Discord.
The same figures as ,ticket analytics: tickets opened and closed, how many are open now, average first response and resolution time, satisfaction, and a per-staff breakdown of claims, closes and ratings.
Ticket analytics is a Server Premium feature, on the dashboard as well as in Discord.
Satisfaction ratings, auto-assign and the per-option open cooldown are all editable from the option editor on the dashboard, alongside the settings that were already there.
Channel name formats
An option can name its ticket channels one of three ways:
- Case number:
ticket-0001, the default. - Username:
someone-ticket. - Option name:
support-0001, useful when one panel offers several very different options.
You can also type your own format instead of picking one of the three.
Appeal a punishment with a form
Add a case field to a form and the person opening the ticket picks which punishment they're appealing from a dropdown of their own cases: no typing an ID, and no way to reference someone else's.
If they have no cases on record, the field is skipped automatically rather than showing an empty dropdown.
Troubleshooting
When greed can't open a ticket it tells the member why, privately:
| What the member sees | What to do |
|---|---|
| One of your roles isn't allowed | They have a blocked role on that option. |
| Your account must be at least … old | The option's minimum account age. |
| You need to have been in this server for … | The option's minimum time in the server. |
| Support is closed right now | The panel refuses tickets outside its support hours. |
| Too many tickets are open on this panel | The panel's total open-ticket limit. |
| I'm missing permissions to create your ticket | Give greed Manage Channels in the ticket category, or Create Private Threads and Manage Threads in the panel's channel for thread tickets. |
| This server has reached Discord's 500 channel limit | Delete old channels, or switch the panel to private threads. |
| This server has too many active threads | Close old threads. |
If a panel's category was deleted or is full, greed creates a new Tickets category and keeps opening tickets instead of failing.
If the panel message doesn't post, check that the bot has Send Messages and Manage Webhooks permissions in the destination channel.
A panel must have at least one option before it can be published. Use ,ticket option add to add options first.
If no category is set for an option, tickets will use the panel's default category. If neither is set, tickets create in the guild root.
Support roles are required for staff to claim tickets. If no roles are set on an option, only users with Administrator permission can interact with those tickets.
Deleted panels cannot be recovered. Transcripts are sent to the log channel before deletion.