Whitelisting Ticket Tool in Security Bots
Anti-nuke bots exist to stop a compromised account from wrecking a server. They watch for bursts of channel creation, channel deletion, mass mentions, and permission changes, then act fast when they see one.
Ticket Tool does all of those things by design. Every ticket it opens is a new channel, every ticket it closes removes one, and a busy server can produce dozens in a minute. To a security bot with default settings, that pattern is indistinguishable from an attack.
The fix is to tell your security bot that Ticket Tool is trusted. This guide covers the general approach, then walks through Wick as a worked example.
Whitelist before you configure, not after
If a security bot removes Ticket Tool's roles or bans it partway through setup, you are left with a half configured server and orphaned channels. Add the whitelist first, then create your panels and categories.
Signs a security bot is the problem
If Ticket Tool worked and then suddenly stopped, and nothing changed on the dashboard, suspect the security bot before anything else.
| What you see | What is usually happening |
|---|---|
| The bot loses its roles for no clear reason | An anti-nuke rule stripped them after a burst of channel activity |
| The bot is kicked or banned during a busy period | Channel creation or deletion crossed a rate threshold |
| Tickets stop opening, with permission errors | The bot's role was removed or its permissions were quarantined |
| The first few tickets work, then everything stops | A per minute threshold was reached |
| Ticket messages that mention roles are deleted | A mention or spam filter caught the ping |
Check the security bot's audit log
Discord's own audit log will show the security bot as the actor when it removes a role or bans. That is the quickest way to confirm the cause rather than guessing.
The general approach
The details differ between bots, but the shape is the same everywhere.
Whitelist by role, not just by user
Give Ticket Tool its own role and whitelist that role. Most security bots resolve trust through roles, and a role survives the bot being re-invited.
Cover every filter, not only the obvious one
Whitelisting a bot for mentions does not whitelist it for spam, invites, or channel actions. Security bots keep these as separate lists, so work through each one.
Check the anti-nuke module separately
Anti-nuke is usually distinct from automod and often has its own trust list. This is the module that bans for mass channel activity, so it is the one that matters most for a ticket bot.
Open a test ticket
Open and close a ticket, then confirm Ticket Tool still holds its roles. Do this before you announce the panel to your members.
Wick
Wick is the security bot we are asked about most, so here is the specific path. Wick changes its dashboard from time to time, so treat this as a guide to what you are looking for rather than a fixed set of clicks.
Open your Wick dashboard
Sign in to Wick's dashboard and select your server.
Find Whitelist under Auto Mod
Open the Auto Mod category and choose Whitelist.
Pick the filter you want to whitelist
The whitelist is split across separate tabs, one per filter: Mentions, Spam, Invite Links, and @Everyone.
Add Ticket Tool's role
Open the dropdown under Roles and select the role assigned to Ticket Tool, then save.
Repeat for the remaining tabs
Each tab keeps its own list. Adding the role to Mentions does nothing for Spam, so repeat the step on every tab you want Ticket Tool exempt from.
Wick Premium: check Anti-Nuke Protection first
Wick Premium includes Anti-Nuke Protection, which is separate from the Auto Mod whitelist above. It reacts to mass channel creation and deletion, which is exactly what a ticket bot does all day. Make sure it will not act on Ticket Tool before you install or configure the bot, or it can ban Ticket Tool mid setup.
This is not a Wick tutorial
We cannot support Wick's own configuration. If the whitelist does not take effect, some part of Wick's setup is likely incomplete, and Wick's documentation and support server are the right place to resolve that.
Other security bots
The same reasoning applies to any bot that polices destructive actions. Look for a trusted, whitelisted, or ignored list, and add Ticket Tool's role to it.
| Bot type | What to look for |
|---|---|
| Anti-nuke and anti-raid bots | A trusted bots or whitelist list in the anti-nuke module |
| Automod bots | Per filter ignore lists for mentions, spam, invites, and links |
| Logging or moderation suites | A bot immunity or ignore roles setting |
| Discord's built in AutoMod | Exempt roles on each rule, set in Server Settings -> AutoMod |
Do not solve this by giving Administrator
Administrator does not exempt a bot from another bot's rules, so it will not fix this, and it hands over far more access than tickets need. Whitelisting is the correct fix. See Permissions for what Ticket Tool actually requires.
Confirm it worked
Open a ticket, close it, and check that Ticket Tool still has its role afterwards. If your server is busy, open a few in quick succession, since rate based rules only trigger under load.
If tickets still fail, the Permission Checker in Dashboard -> Settings -> Diagnostics will tell you whether the problem is a missing Discord permission rather than a security bot.