Tickets
Members open a private ticket from a panel; your staff answer in a channel or private thread. Closed tickets keep a transcript members can read on the web.
Set it up
Open the dashboard and pick your server. Sign in with Discord if you haven’t.
Find Tickets in the sidebar (or press ⌘K and type its name) and turn it on.
Go through the settings below. Simple mode shows the essentials; switch to Advanced for the rest.
Try it in Discord:
/ticket. Staff can restrict or turn off each command in Commands.
Tips
- Add an intake form so the first message already has the details you need.
- Members find their tickets and transcripts on their Kovu profile.
Settings
What you’ll find on the Tickets page of the dashboard. Settings marked Advanced only show in Advanced mode.
Logs and transcripts
- Ticket log channel
- ChannelKovu posts when tickets open, get claimed, close, get rated or get deleted.
- Transcript channel
- ChannelWhere transcripts go when a ticket closes.
- Save transcripts
- On/offKeep an HTML copy of every ticket when it closes: messages, attachments, embeds and avatars. Staff and the member can read it on kovu.gg.
- Attach the transcript fileAdvanced
- On/offAdds the HTML file to the transcript post, next to the web link.
- DM the transcript to the member
- On/offSends the member who opened the ticket a link to its transcript.
Handling tickets
- Claiming
- On/offStaff can claim a ticket so everyone knows who is handling it.
- Ask for a rating
- On/offWhen a ticket closes, Kovu DMs the member a 1–5 rating. Ratings go to the ticket log.
- Ask before closingAdvanced
- On/offPressing Close asks for a confirmation first.
- Members can close their own ticketsAdvanced
- On/off
- Moderators are staff everywhereAdvanced
- On/offMembers with a mod role or moderation permissions handle every panel’s tickets. Off: only each panel’s staff roles do.
- Show the priority in the channel nameAdvanced
- On/offAdds 🟢 🟡 🟠 🔴 in front of the name. Discord allows two renames per 10 minutes.
Closing and cleanup
- Delete closed tickets after
- DurationThe channel or thread is deleted this long after closing. 0 keeps closed tickets.
- Close inactive tickets
- On/offTickets nobody writes in are closed automatically.
- Close after this long without messages
- Duration
- Warn this long before closingAdvanced
- Duration0 closes without a warning.
- Close tickets when the member leavesAdvanced
- On/off
Commands
/ticket
EveryoneOpen and handle support tickets
/ticket open [panel] [reason]/ticket close [reason]/ticket reopen/ticket claim/ticket unclaim/ticket assign <user>/ticket add <user>/ticket remove <user>/ticket rename <name>/ticket priority <level>/ticket info/ticket transcript/ticket delete?ticket <open|close|reopen|claim|unclaim|assign|add|remove|rename|priority|info|transcript|delete>Options
- open panel (optional)
- The kind of ticket (default: the first panel)
- open reason (optional)
- What you need help with
- close reason (optional)
- Why it is closed
- assign user
- The staff member
- add user
- Who to add
- remove user
- Who to remove
- rename name
- New name
- priority level
- Priority
/tickets
ModeratorsTicket lists and panels for staff
/tickets list [status] [user]/tickets panels/tickets stats [days] [user]/tickets post <panel>?tickets [list|panels|post|stats] …Options
- list status (optional)
- Which tickets (default: open)
- list user (optional)
- Only tickets this member opened
- stats days (optional)
- How far back (default: 30 days)
- stats user (optional)
- Only this staff member
- post panel
- The panel (name or number)
Related modules
Ready to try Tickets?
Open the dashboard