Fluxer Ticket Bot
Netrcol turns support requests on your Fluxer server into private channels between the member and your staff role. Run up to 3 ticket panels, let each member keep 1 to 10 tickets open, ping staff when a ticket opens, and keep every finished ticket as a transcript you can read in the dashboard.
The most-voted bot on FluxerList (171 votes, all time) and on Fluxer Bot List (45 votes in October 2026), rated 4.8/5 from 5 FluxerList reviews.
Keep support out of busy public chat
Questions, reports and individual requests are easier to follow in a dedicated conversation. Netrcol creates a private support channel for a member and the configured staff role. Use separate panels for general help, reports or other requests so members have a clear entry point and your team knows where to respond.
Explore the ticket systemBuild panels for different needs
Configure panel messages, names and emojis, then choose the support role and open and closed categories for each panel. Write the first ticket message to explain what information a member should provide. An optional ping role can notify staff when a new conversation opens, while a log channel records ticket activity.
Learn about ticket panelsFollow the conversation from open to close
A member opens a ticket through a panel or a ticket command. Netrcol creates the channel and gives the configured participants access. Staff and the member discuss the request, then an authorized participant closes the ticket. Configure a closed category and review the close behavior before using the system for real support.
See ticket commandsReview saved transcripts
When enabled, transcripts preserve a readable record of ticket messages with authors, timestamps, attachments and emojis. Review saved conversations from the dashboard transcript viewer instead of relying on a channel remaining open. Treat transcripts as member data: limit staff access and avoid requesting passwords, access tokens or other secrets in support tickets.
Read about transcriptsSet limits that fit your support team
Per-user limits control how many tickets a member can keep open at once. A single open ticket can help a small staff team keep requests together; a higher limit may suit communities with different support departments. Test the opening and closing flow with your selected roles so a configuration mistake does not expose conversations to unintended members.
Review ticket configurationGive the bot the access it needs
Netrcol needs Manage Channels to create and organize ticket channels, plus the relevant viewing, messaging and history permissions in the panel, ticket and log destinations. Private channels are governed by Fluxer permissions, including administrator access. Confirm the support role and category configuration rather than assuming a panel alone establishes the access policy.
Check ticket permissionsHow many tickets can a member have open?
You choose per panel, from 1 to 10. The default is 1, which keeps each member's requests in one conversation.
Set per-user limitsWhat happens when a ticket is closed?
Closing moves the channel to the closed category you chose, and the ticket can be reopened from there. Deleting it removes the channel and saves the conversation as a transcript you can read in the dashboard.
See the ticket commandsHow many ticket panels can I set up?
Up to 3, for example one for help and one for reports. Each has its own support role, open and closed categories, first message and optional staff ping role.
Build ticket panels