Skip to main content

Stopping ticket spam: limits, cooldowns and bans

How to protect Discord tickets from spam and floods: per-member and per-panel limits, cooldowns, the intake form as a filter, blocked roles and /ticket ban.

Discord Tickets team6 min read

A ticket is a private line straight to your team, and sooner or later someone abuses it: five tickets for the same question, a lone “hello” followed by silence, or a flood because nobody answered within a minute. One person like that can tie up the queue for half a day.

Most of it is handled by settings you configure once. Below: each tool, what it stops, and values to start with.

Kinds of abuse

What happens What helps
Duplicates: one question, three tickets Per-member limit
Empty tickets: “hi”, “test”, “anyone?” Intake form with required fields
Close one, open another right away Cooldown between tickets
A wave of tickets from fresh accounts Per-panel limit, blocked roles
Insults and trolling in tickets /ticket ban with a duration
Using tickets as a chat room Panel copy, the form, a warning, then a ban

No single tool covers everything, so you combine them. Start with the simple ones — limits.

Max tickets per member

How many open tickets one member can hold at the same time. The range is 0 to 50, the default is 1, and 0 means no limit. The value is set on the panel and counts the member’s open tickets on that panel only — tickets on your other panels don’t use it up.

A value of 1 suits most servers: one question, one ticket, and the next one opens once this one is closed. That alone kills duplicates and the “maybe another topic answers faster” move.

Raise it to 2 or 3 if your topics are truly independent and a member could legitimately have, say, an open report and a billing question at the same time. We don’t recommend 0 on a public server.

Max tickets on this panel

A ceiling on open tickets across one panel. The range is 0 to 500, and the default is 0 — no ceiling.

This is an emergency brake, not an everyday setting. When a wave of new accounts each opens one ticket, the per-member limit can’t help, but a ceiling keeps the queue from growing to hundreds of channels.

The downside: once it’s reached, nobody can open a ticket, honest members included, until the team closes some. Set it with headroom, several times your normal load — check Open now and the Tickets opened chart on the Overview tab.

Cooldown between tickets

How many seconds a member has to wait before opening another ticket on this panel. The maximum is 86,400 seconds, a full day.

The cooldown closes the loophole the per-member limit leaves open: close a ticket, open a new one immediately. It counts from when the previous ticket was opened, so closing a ticket doesn’t reset it.

Starting points:

  • 60–300 seconds — regular support: honest members barely notice, serial flooding stops;
  • 3,600 seconds (an hour) — a reports panel, if people try to use reports to pressure others;
  • 86,400 seconds (a day) — a staff applications panel: one application a day is more than enough.

All three settings apply to the whole panel and live under Advanced settings. If different flows need different values, split them across panels — up to three per server. See Rules, limits and closing in the docs.

The intake form as a filter

A ticket is created only after the member submits the form, so many idle clicks end with a closed window.

What makes the filter stronger:

  • A required field with a minimum length. “Describe the problem”, at least 30 characters — a bare “help” won’t get through.
  • A confirmation checkbox. “I’ve read #faq and didn’t find an answer.” A single Checkbox can’t be made required in Discord, so it won’t stop anyone — it’s a reminder that filters out people whose question is already answered. A required field with a minimum length does the real filtering.
  • Static text. An explanation right in the window: what to include and what to leave out.
  • Specific questions. “In-game name” and “When did this happen” are harder to answer with junk than “Your question”.

You get up to five fields — that’s a Discord limit. Which questions to ask for different topics is covered in intake form questions that work.

Blocked roles on a topic

Each topic can list roles that can’t open it. It’s a targeted block: that one topic is off-limits, the rest stay available.

Examples:

  • Unverified is blocked on every topic except Verification problem;
  • Muted is blocked on Join the team;
  • Newcomer is blocked on Partnership request.

More on topic roles in building a Discord support team.

Ticket-banned roles

This one works server-wide. Under Settings you list roles, and a member with any of them can’t open a ticket anywhere on the server — not on any panel, not in any topic.

Create a dedicated role, such as Ticket banned, and put it first in the list: /ticket ban assigns the first role from Ticket-banned roles. Roles your moderators already hand out to rule breakers can go below it. How to set the roles is in the Settings section of the docs.

The /ticket ban command

It takes a member, a duration and a reason. The duration is 30m, 12h, 7d, 2w, or permanent. The bot assigns the ticket ban role and removes it on its own when the time is up, so nobody has to remember to lift it.

The command is available to anyone with the /ticket ban permission in the Access tab, or with the Discord permission Manage Roles. A moderator doesn’t need dashboard access for this.

Always give a reason, even a short one: “ticket flooding”, “insults in a ticket”. It keeps the decision clear for you and your colleagues.

An escalation ladder — a guideline, not a rule:

  1. First offense — a warning in the ticket, no ban.
  2. Second — 12h.
  3. Third — 7d.
  4. Serious or repeated abuse — 2w or permanent.

Treat this table as a starting point, not a standard. Tune it to your own flow using Open now and When tickets arrive on the Overview tab.

Server Per member Per panel Cooldown, sec Intake form
Small community, one or two topics 1 0 60 1–2 fields, description required
Large public server 1 Headroom over normal load 300 3–5 fields, minimum description length
Several teams, many topics 2 0 or with headroom 120 A separate form per topic
Dedicated staff applications panel 1 0 86,400 Full form, up to 5 fields
Server that gets raided 1 Headroom over normal load 300–600 Required fields and a rules checkbox

Checklist

  • Max tickets per member — 1, or 2–3 if topics are independent.
  • Max tickets on this panel — 0, or a ceiling with headroom if you get raids.
  • Cooldown — from a minute for support to a day for applications.
  • Intake form — at least one required field with a minimum length.
  • Blocked roles — on topics not everyone needs.
  • Ticket-banned roles — a dedicated ban role created and added in Settings.
  • The /ticket ban permission granted to moderators in the Access tab.

If something doesn’t fit your server, drop by our support server and we’ll help you pick values.

Read next

All posts →