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.
Visible structure, private conversation
The case appears beneath Support without exposing its contents.
The configured Support channel remains the public starting point. A new request creates a clearly named private thread nested beneath that channel, so the requester can find the conversation from Discord's normal channel list while unrelated members cannot enter it.
The thread carries the complete conversation and attachments. Luminox keeps the operational metadata needed for access, status, claims and navigation rather than creating a duplicate transcript database.
- The requester enters automatically.
- Only the responsible category staff and invited participants receive access.
- Claim ownership remains visible without removing administrator oversight.
- Closure locks and archives the thread immediately.
└Complaint about userPrivate
●RequesterIncluded
◆Responsible staffRole-aware
✓Resolved conversationArchived
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.
The private My Tickets view separates requests the member opened, tickets handled as staff and conversations joined as an invited participant. Pagination stays inside the same private response, and every result links back to its active or archived Discord thread.
Opened
Shows tickets created by the current account, ordered by their most recent activity.
Staff
Identifies tickets in which the viewer acted as support staff, including resolved cases.
Joined
Keeps invited-participant conversations separate from creator and staff history.
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.