A Discord ticket blacklist stops a specific user, or everyone with a specific role, from opening new support tickets, without banning or muting them anywhere else in the server. It's built for the member who spams empty tickets, reopens the same resolved complaint every day, or abuses a ticket-based system (like a giveaway support channel) to farm attention. Noxyr's blacklist can target a user or a role, records a reason, and can be lifted at any time. This guide covers how it works, how to set it up, and why it's a narrower tool than a ban.
What blacklisting actually blocks
A blacklisted user (or anyone holding a blacklisted role) is stopped at the moment they try to open a ticket - clicking a panel button does nothing for them, and they get told they're blocked rather than getting a new channel. It does not touch anything else: they can still talk in every other channel, still see the server normally, and any tickets they already have open stay open unless staff close them separately. Blacklisting is scoped to the ticket system, on purpose - it's a tool for one specific kind of abuse, not a substitute for actual moderation.
Setting it up
- Block a user:
/ticketadmin blacklist user:@member reason:"opens duplicate tickets". The reason is stored and shown when you review the list later. - Lift it:
/ticketadmin unblacklist user:@member. - From the dashboard: the Tickets page has a Blacklists section listing every active record with a Remove button, so you don't need to remember a user's ID to undo one.
A blacklist entry can also target a role rather than one person - useful for something like a "muted" or "restricted" role you already apply elsewhere, so anyone who gets that role automatically loses ticket access too without a separate step.
User blacklist vs role blacklist
- User blacklist is for one specific account: the person who's personally abusing the system, independent of what roles they hold now or later.
- Role blacklist is for a category of member: tie it to a role you already assign for other reasons (a warning tier, a restricted-access role) and every current and future holder of that role is blocked from opening tickets automatically, with no per-person action needed.
If you're not sure which to use: block the user directly for a one-off problem, and only reach for a role-based block if you already have a role that represents "this category of member shouldn't have ticket access" for other reasons too.
Blacklist vs a full ban
These solve different problems. A ban removes someone from the server entirely - appropriate for real rule violations, harassment, or anything that shouldn't have any presence in your community. A ticket blacklist leaves someone as a normal member who simply can't open new tickets - appropriate for someone whose behavior is specifically a ticket-system problem (spam tickets, farming a giveaway support channel, repeatedly reopening a settled dispute) but who hasn't done anything that warrants losing server access altogether.
Using a ban for a ticket-spam problem is heavier than the situation usually calls for, and using a blacklist for actual harassment is far too light. Match the tool to what actually happened.
What to check before you blacklist someone
- Is it actually spam, or a legitimate frustrated member? Someone reopening the same ticket repeatedly might be doing it because their original issue was never actually resolved. Check the transcript history before assuming abuse.
- Did you tell them why? A blacklisted member gets a blocked message, not an explanation. Consider a DM or a note from staff so it doesn't look like the bot randomly broke for them.
- Is this permanent or a cooldown? Noxyr's blacklist doesn't expire on its own - it stays active until someone runs unblacklist. If you want a temporary block, set a reminder to lift it, since there's no auto-expiry.
A quick decision checklist
- One person, one incident (spamming empty tickets, reopening a settled complaint) → user blacklist.
- A category of member you already track with a role (a warning tier, a restricted-access role) → role blacklist, so it applies automatically going forward.
- Actual harassment, scamming, or a real rule break → this isn't a blacklist situation at all, it's a ban or a timeout. Blacklisting leaves someone as a full member who simply can't open a ticket, which is far too light a response for genuine abuse.
When in doubt, blacklist the narrower thing. It's easy to lift a blacklist entry with /ticketadmin unblacklist if you were wrong about someone; it's a much bigger deal to walk back a ban.
Common questions
Does blacklisting close their existing open tickets? No, it only prevents opening new ones. Close any existing tickets separately if that's what you want.
Can a blacklisted member still message an FAQ or auto-responder? Yes - the blacklist only blocks opening tickets, not other Tickets-module features like the FAQ or general-scope auto-responders.
Does blacklisting a role affect people who get that role later? Yes, a role-based blacklist applies to whoever currently holds the role and anyone who gets it afterward, until the entry is removed.
Is the blacklist visible to the blocked member? They see that they can't open a ticket; they don't see a formal "you are blacklisted" notice unless staff tell them directly.
Does this feature cost anything? No, blacklisting is part of Noxyr's free ticket system.
Manage blacklists from the dashboard's Tickets page, or see the full command list on the ticket bot page.