Skip to main content

Member reports through private Discord tickets

How to handle Discord member reports through private tickets: a moderator-only topic, a form with a member picker, closing rules and protection from abuse.

Discord Tickets team6 min read

When reports land in general chat, moderation turns into a public trial: the reporter is exposed to the person they reported, onlookers argue, and the moderator decides with the whole server watching. DMs to moderators are not much better — there is no shared queue, and if the right person is offline, the report just sits there.

A private ticket fixes both. Only the reporter and moderators see it, it goes into one queue, and it closes with a recorded outcome. Here is how to set it up.

Why reports do not belong in general chat

  • Pressure on the reporter. A public report invites retaliation, and some people will stay silent instead.
  • The offender may find out first. They can see the report before a moderator does and delete their messages.
  • Evidence gets buried under new messages, and the discussion drifts.
  • No record. A month later nobody remembers who was reported or how it ended.

A dedicated Report a member topic

If your support panel uses a Select menu trigger, add a topic:

  • Label: Report a member.
  • Description: Rule breaking, insults, DM spam — shown under the label in the menu.
  • Admin roles: Moderators. The role gets access to reports, a mention when one opens, and the right to close. Support helpers without that role do not see reports.

One caveat: closing rules, limits and quick close reasons are set for the whole panel. If your support panel lets openers close their own tickets, reporters can close reports too. When reports need strict rules and support does not, create a separate Reports panel — a server can have up to 3. How to split access between moderators and support is covered in support team roles and access.

Reports can open as private channels or private threads. A thread is locked on close and stays as an archive. For channels, leave Delete the channel on close off: a read-only archive helps when the same person is reported again.

Tip. Make the reports panel’s log channel visible to moderators only. And make sure the bot can see it, the panel channel and the ticket category: from November 16, 2026, channels a bot cannot view (no View Channel permission) will be hidden from it.

The report form

Question Field type Settings
Who broke the rules? Pick members Required
Where did it happen? Pick channels Optional: leave empty if it was in DMs
What happened? Text, paragraph, placeholder: Briefly, what they said or did Required, min 30 characters
Message link Text, short, placeholder: Paste a link if you have one Optional
— Static text: Attach screenshots in the ticket. Knowingly false reports break the rules too —

Why Pick members instead of text? The reporter picks an exact account, so moderators do not have to guess which of two people called Alex was meant, or whether someone changed their name.

The Pick channels list can be restricted — keep the channels where members actually talk and leave out staff channels. A message link can be copied from the message menu in Discord, and it jumps straight to the spot even after hundreds of newer messages.

Required fields and a minimum length filter out one-word reports. More on picking questions and field types in intake form questions.

Welcome message

{opener}, report #{number} received.
Moderators will review it in order. Attach any screenshots or recordings here, and please do not discuss the situation in general chat.

The bot adds the form answers to the ticket when Include the intake answers is on, so the moderator sees everything at once. Keep the channel name neutral, for example report-{counter}.

How a moderator handles a report

  1. Click Claim under the welcome message. Claimed by … appears, so two moderators do not work the same case.
  2. Check the evidence: follow the link, look at screenshots and the channel history.
  3. Ask the reporter follow-up questions in the ticket if needed.
  4. Take action with your usual Discord moderation tools.
  5. Close the ticket with a reason.

Closing rules

Setting Value Why
Who can close Admins only The moderator records the outcome, not the reporter
Require a close reason On Every report has a recorded result
Delete the channel on close Off Report history stays
DM the opener why it was closed Your call The reporter learns the outcome

Quick close reasons work with exactly these settings: admins-only closing and a required reason. A set for reports:

  • Confirmed, action taken
  • Not enough evidence
  • No violation
  • False report
  • Duplicate

Five reasons show as radio buttons in the close form, with Other as the sixth option. If the reason is sent to the reporter by DM, decide in advance whether you disclose specific punishments. If not, action taken reads better than banned for 7 days.

Protection from abuse

A report channel also attracts people who use it as a weapon: waves of reports against someone they dislike, or plain spam.

  • Max tickets per member: 1. The limit counts all of the member’s open tickets on the server, so with 1, someone with an open support ticket can’t report until it’s closed — 2 avoids that. Reporting someone else can go in the same ticket.
  • Cooldown between tickets, for example 1800 seconds: at least half an hour between new reports.
  • Max tickets on this panel. No limit by default. You can set one for floods, but once it is reached, nobody can open a report.
  • Topic blocked roles. If you have a role for people who abused reports, add it to the topic’s blocked roles. They lose access to reports only; support stays open.
  • /ticket ban — for systematic spam. It takes a member, a duration (30m, 12h, 7d, 2w or permanent) and a reason. The bot gives the ticket-ban role from Settings and removes it when the time is up. Keep in mind that with this role the member cannot open a ticket anywhere on the server, support included.

The command is available to people with the /ticket ban permission on the Access tab or the Discord Manage Roles permission. More on limits and bans in spam protection: limits, cooldowns and bans.

What you see in Discord Tickets

On the Tickets tab, each report has a card: who opened and closed it, when, first response, duration and close reason. On Overview, By topic shows how many reports came in over 30 days, and When tickets arrive shows which days and hours are busiest. Step-by-step with video: the form in the Intake form section of the docs, closing rules and limits in Rules, limits and closing.

Checklist

  • A dedicated topic or Reports panel, with moderators as the only admin roles.
  • The offender is chosen with Pick members.
  • Admins-only closing, required reason.
  • Quick reasons cover common outcomes, including False report.
  • Channels are not deleted on close.
  • Max tickets per member (counted per panel) and a cooldown between tickets.
  • /ticket ban only for systematic abuse.

Read next

All posts →