Ticket System
Set up Netrcol support tickets on Fluxer with panels, private channels, support roles, per-user limits, closing rules and saved conversation transcripts.
Topics: tickets, support, transcript, panel
Give members a private, on-demand channel to reach your staff — with multiple ticket types, a welcome message, per-user limits, and saved transcripts.
Overview
A ticket is a private channel a member opens to get help. Netrcol creates the channel, gives access to the member and your support role, and keeps the conversation out of busy public chat. When the issue is resolved, the ticket is closed and an optional transcript is saved.
Set everything up on Dashboard → Ticket, or use the ticket commands for a quick single-category setup. Netrcol needs the Manage Channels permission to create and move ticket channels.
Ticket panels
A panel is a published message members use to open a ticket. You can run several panels for different purposes (for example *Support*, *Reports*, *Billing*), each with its own settings:
| Setting | Purpose |
|---|---|
| Name & emoji | Identifies the panel and the button/reaction members use |
| Panel title & welcome message | The embed shown on the panel and the first message inside a new ticket |
| Support role | The staff role that can see and close tickets from this panel |
| Open category | Category where new ticket channels are created |
| Closed category | Category tickets are moved to when closed |
| Log channel | Receives open/close logs |
| Ping role | Optionally pinged when a new ticket opens |
| Limit per user | How many tickets one member can have open at once (default 1) |
The panel editor is organized into Settings, Messages, and Transcripts tabs so you can configure, write copy, and review history in one place.
Opening and handling tickets
- A member opens a ticket from a panel (or with
!ticket-open). - Netrcol creates a private channel under the open category and notifies staff.
- Staff and the member discuss the issue in the channel.
- Anyone with the support role — or the ticket owner — closes it with
!ticket-close. The channel moves to the closed category, and a transcript is saved.
Tip: Some servers require a reason when closing. If so, Netrcol will ask for one — for example
!ticket-close issue resolved.
Transcripts
When a ticket closes, Netrcol can save a full transcript — a readable archive of every message, with authors, timestamps, attachments, and emojis. Transcripts appear in the Transcripts tab of the panel editor and open in a slide-in viewer, so you can review past tickets even after the channel is gone.
Per-user limits
The Limit per user setting caps how many tickets a single member can have open at once (default 1). This stops one person from flooding your support queue. Increase it if your community needs multiple concurrent tickets.
Permissions
- Netrcol needs Manage Channels to create, move, and close ticket channels.
- In the panel and log channels it also needs the baseline View Channel, Send Messages, Embed Links, and Read Message History — see Permissions & Roles.
Quick setup from chat
For a single support category without panels:
!ticket-setup 123456789012345678 987654321098765432 111222333444555666That sets the category, support role, and (optional) log channel. See the ticket commands for the full list.
Next steps
- Build panels on Dashboard → Ticket
- Review the ticket commands
- Confirm Netrcol’s permissions