Starts with a button
Simple tickets
If five people a week need help, a full ticket system is more than you need. A button in #support opens a private thread for the member and your team, and /close locks it when the question is answered.
Illustration. The real interface may look different.
How it works
The button on the panel opens a private thread and adds the member and your team role.
The bot saves who opened the ticket.
/close only works for that member or your team. It locks the thread and archives it.
How to make a ticket system with threads on Discord
Tickets here are private threads under your support channel. The bot remembers who opened each one under the thread's own ID, which is how /close knows whom to trust.
Describe it to your AI assistant
We get a handful of support questions a week and they end up all over #general. Build a small ticket module: /ticket-panel, for members with Manage Server, posts a panel in #support with an "Open a ticket" button. The button opens a private thread for the member and mentions the Crew role in it. Add /close that only the opener or the Crew can use inside a ticket. It should post a closing note, then lock and archive the thread. Make the channel, the role and the panel text settings.
Copy it and swap in your own channel and role names. Your assistant has a tested version of this example to start from.
Build it in the editor
Three flows: /ticket-panel posts the panel once, the button opens a ticket and /close ends it. The button names the flow it starts, so the panel keeps working for months.
The 3 flows, step by stepStep names are the ones the editor shows.
Flow 1/ticket-panel
Trigger: Slash command/ticket-panel, limited to members with "Manage server". You run it once.
- Create messageBuilds the panel from your panel text, with the "Open a ticket" button.
- Send messagePosts it in the panel channel.
- Reply to interactionConfirms to you privately.
Flow 2Open a ticket
Trigger: Button clickedfrom the button on the panel.
- Create messageBuilds the first message of the ticket, which mentions the member and your staff role.
- Create threadOpens a private thread under the panel channel with that message. The mentions pull both sides in.
- Store a valueStores who opened the ticket, under the thread's ID.
- Increase a stored numberAdds 1 to the count of open tickets.
- Reply to interactionTells the member that their ticket is open.
Flow 3/close
Trigger: Slash command/close, used inside the ticket thread.
- Read a stored valueReads the opener for this thread. In any other channel the command answers "This channel is not a ticket."
- EqualsChecks whether the caller is the opener.
- Member has roleChecks for your staff role. One of the two is enough.
- Delete a stored valueRemoves the stored opener and lowers the open count.
- Lock threadLocks the thread so nobody can post in it again.
- Archive threadArchives it. It stays readable in the archived threads list.
For transcripts, claiming and ratings, our Support Bot has a full ticket system. See the ticket system
Test it, change it
What it stores
- Ticket openerBy custom keyWho opened a ticket, filed under the thread's ID. Deleted when the ticket closes.
- Open ticketsWhole serverOne number for the server: how many tickets are open right now.
How to test it
- Open a flow in the editor and click "Test run". Choose the member under "Run as" and click "Run test". The run uses your real server data but sends, changes and deletes nothing, and shows what each step would have done.
- A new flow is a "Draft" and does not run in Discord. Switch it on and click "Save & activate".
- In Discord, run /ticket-panel, open a ticket with a second account and check that your team role was pulled into the thread. Then try /close from a third account without the role.
- Each real run then shows up under "Executions", with the reason if it failed or was skipped.
What to change
- Channel
- The panel channel is a setting in the module's "Configuration" tab. Run /ticket-panel again after changing it.
- Team role
- The "Staff role" setting decides who is pulled in and who may close.
- Panel text
- The "Panel text" setting. Post a fresh panel to see it.
- Thread name
- Built at the start of the open flow. The tested version names it after the member.
Watch out for
- Your bot needs "Create private threads" and "Send messages in threads" in the panel channel.
- A member can open several tickets at once. If that gets abused, ask for a check on an open ticket before the thread is created.
- Members with "Manage threads" can see every private thread in the channel. That is how Discord handles private threads.
Questions about this build
Who can see a ticket thread?
The member who opened it, everyone with your staff role once the bot has mentioned it, and anyone with the "Manage threads" permission. Other members do not see the thread.
Can a closed ticket be read later?
Yes. Closed tickets are locked and archived, and Discord keeps archived threads. Your team finds them under the channel's thread list.
When is this too small for my server?
When you want categories, transcripts, claiming or ratings. The ticket module that comes with your bot has categories and transcripts, and our Support Bot adds claiming and ratings. Both are linked below.
More examples
- 21:14Staff applicationsAn /apply form for applicants, Approve and Deny buttons for your team.staff-applications
- 13:05SuggestionsMembers post ideas, everyone votes, and your mods get a ping when one takes off.suggestions
- 14:31Welcome and goodbyeA greeting for new members, and a log of who left and how long they stayed.welcome
Szeretnéd a szervered a bétában?
A V3 nagy rendszer, és még gyorsan változik, ezért a szerverek egyesével érkeznek, nem egyszerre. Minden jelentkezést ember olvas el, és pár napon belül visszajelzünk.
A bétában lévő szerverek döntik el nagyrészt, mit építünk legközelebb. Amit megépítesz, az a tiéd: a flow-k és a modulok a béta végén is megmaradnak.