How do I stop spam tickets in Discord?

Blacklist repeat offenders by user or by role, require a short form before the ticket opens, and set a loose per-user rate limit as a backstop. Blacklisting by role scales best, because blocking a role you already apply during moderation stops ticket abuse automatically with no extra step.

What is ticket sniping on Discord?

Scam bots watch for new ticket channels and correlate the creation event with which member just gained access, working out who opened a support ticket. They then DM that person impersonating staff while the member is actively waiting for help. Anti-sniping protection breaks the correlation by adding the opener a few randomised seconds after the channel is created.

How do I stop people impersonating my Discord staff?

Publish that your staff never DM first, and then never DM first. Put it in your rules, your panel description and your ticket welcome message. Once members know the rule, an unsolicited DM is obviously a scam regardless of how convincing the profile is. This works better than technical controls because it removes the scammer opening move.

Should I rate limit ticket creation?

Loosely, as a backstop rather than a primary defence. Aggressive limits punish legitimate members, and since closed tickets cannot be reopened, someone with a genuine urgent problem who is throttled becomes a support problem you created.

Playbook4 min read

How to Stop Spam and Scam Tickets in Discord

Practical defences against spam tickets, ticket sniping, scam DMs triggered by ticket activity, and members who open tickets to advertise. What actually works and what only looks like it does.

Published: July 15, 2026
Author: Dani, Founder, AI Ticket Bot

Short answer: four defences cover almost all of it. Blacklist repeat offenders by user or by role, turn on anti-sniping protection so scammers cannot detect who opened a ticket, require a form before the ticket opens, and make sure your staff never DM first so impersonation is obvious. Rate limits help too, but they punish legitimate members if set aggressively.

The four problems, which need different fixes

They get lumped together as "spam" and they are not the same:

Ticket spam. One person opening ticket after ticket, or a raid doing it at scale.
Ticket sniping. Scammers watching for new tickets so they can DM the opener pretending to be staff.
Advertising tickets. People opening a ticket to pitch you something.
Impersonation. Someone with a copied name and avatar DMing your members "about their ticket".

Defence 1: blacklist, by user and by role

The obvious one, with a less obvious capability. On AI Ticket Bot the blacklist works by user or by role. Blocking a role blocks every member holding it.

Role blacklisting is the one that scales. If you have a "muted" or "restricted" role that moderation already applies, blacklisting that role means every moderation action automatically stops ticket abuse too, with no second step and nothing to remember.

Blocking an entire guild is an owner-level global action, not something a server admin does.

Defence 2: anti-sniping protection

This one deserves explaining because the attack is not obvious.

When a ticket channel is created, that event is visible. A scam self-bot watching your server can correlate "channel created" with "which member just became able to see it" and work out who opened a support ticket. It then DMs that person, pretending to be staff, while they are actively waiting for help. That is the moment people are most likely to fall for it.

The defence is to break the correlation. AI Ticket Bot has an anti-DM setting: the ticket channel is created without the opener's view permission, then the opener is added a few seconds later, randomised. The event a scam bot is watching no longer identifies anybody.

The trade-off is honest: the opener waits those seconds before seeing their ticket. It is off by default for that reason, it is free on every plan, and it applies to channel-mode tickets (thread mode is already member-scoped). It works best when your channel naming does not include the username, since a channel called ticket-someuser defeats the whole thing.

Defence 3: a form before the ticket opens

Requiring a short form does two things. It filters low-effort spam, because bots and drive-by advertisers do not fill in forms. And it improves the tickets you do get, because you have the information before the first reply.

Keep it to two or three fields. A long form deters legitimate members with a real problem, which is a worse outcome than the spam you stopped.

Modal forms at ticket open are a paid feature on our plans.

Defence 4: make impersonation obvious

The most effective anti-scam measure costs nothing: publish that your staff never DM first, and then never DM first.

Put it in your rules, in your panel description, and in the ticket welcome message. Once members know the rule, an unsolicited DM is self-evidently a scam regardless of how convincing the profile looks.

This works better than any technical control because it does not depend on catching the scammer. It removes their opening move.

What about rate limits?

Per-user throttles exist and help against the crude version of ticket spam. Set them loosely.

The reason: a member with a genuine urgent problem who accidentally closes their ticket and cannot reopen one is now a support problem you created. Note that closed tickets cannot be reopened, so a rate limit interacts badly with that. Rate limiting is a backstop, not a primary defence.

Defences ranked

Defence	Effort	Effect	Trade-off
Publish "staff never DM first"	Minutes	High against impersonation	None
Blacklist by role	Minutes	High against repeat abuse	None
Anti-sniping protection	One toggle	High against DM scams	Opener waits seconds
Form before opening	15 minutes	Moderate against low-effort spam	Deters some real members
Per-user rate limit	Minutes	Moderate against raids	Punishes legitimate members

What does not work

Deleting the tickets and moving on. Without a blacklist entry the same account is back in an hour.
Making the panel hard to find. It stops legitimate members far more effectively than it stops spammers, who are looking for it deliberately.
Relying on your AI to spot scams. A support AI answers questions; it is not a moderation system. Use a moderation bot for content filtering.

Frequently asked questions

How do I stop spam tickets in Discord?: Blacklist repeat offenders by user or by role, require a short form before the ticket opens, and set a loose per-user rate limit as a backstop. Blacklisting by role scales best, because blocking a role you already apply during moderation stops ticket abuse automatically with no extra step.
What is ticket sniping on Discord?: Scam bots watch for new ticket channels and correlate the creation event with which member just gained access, working out who opened a support ticket. They then DM that person impersonating staff while the member is actively waiting for help. Anti-sniping protection breaks the correlation by adding the opener a few randomised seconds after the channel is created.
How do I stop people impersonating my Discord staff?: Publish that your staff never DM first, and then never DM first. Put it in your rules, your panel description and your ticket welcome message. Once members know the rule, an unsolicited DM is obviously a scam regardless of how convincing the profile is. This works better than technical controls because it removes the scammer opening move.
Should I rate limit ticket creation?: Loosely, as a backstop rather than a primary defence. Aggressive limits punish legitimate members, and since closed tickets cannot be reopened, someone with a genuine urgent problem who is throttled becomes a support problem you created.

See it on your own server.

Add AI Ticket Bot free, teach the brain a few of your most common answers, and watch it clear the repetitive tickets on its own.

Add to Discord See pricing

Keep reading

All articles