1Choose categoryRegistration
2Answer questionsRequired
3Private threadCreated
4Responsible staffRouted
Bot · Private help
Give every request a private, responsible home.
Members choose a support category, answer its required questions and receive a private Discord thread shared only with the right participants and staff.
In plain English
The public channel stays clean.
The support channel contains one permanent panel. When a member opens a ticket, the conversation happens in a private thread instead of posting a visible “thread created” message for everyone.
Each category can ask different required questions, require media, limit which users can see it and require both a global moderator role and one or more specialist support roles.
Ticket process
Responsibility remains visible from opening to archive.
Open
The creator submits category-specific information and optional required media.
Claim
One staff member can take responsibility while administrators retain oversight.
Resolve
Staff or the creator closes the active conversation immediately.
Archive
Discord locks and archives the private thread with messages and attachments intact.
After closure
History remains findable without building a transcript store.
My Tickets
Members see their own tickets; staff see tickets in which they participated, with paginated navigation.
Private participants
Authorized staff can add or remove another person when the case genuinely needs them.
Satisfaction
The creator can mark the result satisfactory or not; an ignored request resolves after the configured period.
Discord archive
Conversation text and attachments remain in the archived thread rather than duplicating media in Luminox storage.
Design your support categories
See permissions, questions, media and staff roles.
The complete guide explains category editing, privacy, claims, participants, closure, satisfaction and retention.