How tickets work
Understand what a ticket is and follow its full lifecycle, from the button a member clicks to the transcript saved when it closes.
A ticket is a private channel where one member talks to your staff. Instead of letting people DM moderators or post in public, Rimpllee gives each request its own space — only the person who opened it and the staff roles you picked can see inside.
The lifecycle of a ticket
- 1
A member opens it
They click a button — or pick an option from a dropdown — on a ticket panel you posted in a channel.
- 2
They answer a few questions (optional)
If you added intake questions, a small popup appears so staff get context right away.
- 3
Rimpllee creates a private channel
A new channel opens inside the Discord category you chose for that button. See Buttons & categories.
- 4
Only the right people see it
The member and the staff roles you assigned to that button can read and reply. Nobody else can.
- 5
- 6
They close it
When the issue is resolved, staff close the ticket with
/close. - 7
A transcript is saved
Rimpllee automatically saves a copy of the whole conversation. See Transcripts.
Just want to get going? The Quick start builds a working panel in about two minutes.
Explore each part
The message with buttons or a dropdown that members use to open tickets.
Each button is one ticket category, with its own staff roles and channel.
Ask a few questions in a popup before the ticket opens.
Take ownership of a ticket and manage it with slash commands.
A saved copy of every closed ticket, created automatically.
Stop specific users from opening tickets.