Discord Report Tickets: How Members Report Someone to Your Mods

Every server needs a way for members to say "this person is a problem". A harassment campaign in DMs, a scam link, a moderator abusing their role. If the only option is pinging a mod in public or DMing one at random, most members say nothing, and the ones who speak up do it where the reported person can read it. A Discord ticket bot gives reports a private room instead.

Why does a public #reports channel fail?

Because everyone can read it, including the person being reported. A public channel turns a report into a scene: the accused replies, friends pile on, and the next victim decides it is not worth it.

Is this the same as Discord's Report button?

No, and the two do different jobs. The Report option in a message or profile menu is built to reach Discord's Trust and Safety team, about Discord's own rules. It is not a way to reach your server's moderators.

A report ticket reaches your mods about your server's rules. For a scam DM or a threat, a member can do both: report it to Discord, then open a ticket so your moderators can act inside the server.

How do you set up a report ticket?

One category, one staff role, and the AI decision made on purpose. Everything below is free on every plan except the form.

In the dashboard, the category's Advanced tab holds all four settings. Use a panel that opens tickets as channels: access in a thread is per person, not per role, so a moderator-only category does not work there. Ticket categories covers wording the panel so members pick the right one.

What should a report form ask?

Who, what, when, and where the proof is. A form holds at most five questions per category, which is Discord's limit, and forms are on paid plans.

A form takes text only, so ask for screenshots in the ticket's opening message. On the free plan there is no form, so the opening message carries the whole ask. Ticket form questions goes through every limit.

Message links beat screenshots for anything in your server, because a mod can jump straight to it. A scam DM is the exception: your mods cannot see a member's DMs, so a screenshot is the only proof. Tell reporters to send it before the scammer deletes the conversation.

Who can see a report ticket?

The reporter, the category's staff, and the people you have set to see everything.

Anonymity here means the reported member does not learn who reported them. Your staff always see who opened a ticket. Never add the reported member to the reporter's ticket, because adding someone gives them the whole conversation from the first message. Talk to the reported member somewhere else. Adding someone to a ticket explains why that cannot be undone.

If you log new tickets to a channel, the post names who opened it and in which category, so keep that channel staff-only. Ticket logs covers what each post carries.

How do you handle a report about a staff member?

Give it a category of its own, routed to senior roles only. A member will not report a moderator if that moderator can read the report.

Add a second category named something like "Report a staff member" and set its staff role to your admins or owners. Then check See every ticket: a role with it sees this category too, and a new staff role gets it by default. Untick it on your ordinary staff roles, in Settings, then Staff roles, or with /staff roles in Discord. Each category then needs its own staff role, because a role without it only sees the categories it is set for.

Administrators still see everything. A report about an administrator is for the owner, and no bot setting changes that.

Should the AI answer reports?

Gathering is not deciding. For most servers, switch the AI off for the Report category so every report opens straight to a person. Then nothing written there is sent to the AI.

If you leave it on, it can ask for the missing link or screenshot and read an image the reporter attaches. It cannot act against the person reported, because it only ever acts for the member who opened the ticket. A reported threat or harassment is handed to your staff with a short summary, and a threat of harm is marked Urgent. Turning the AI off covers the switch.

How long is a report kept?

As long as the transcript: 90 days on Free, 730 days on paid plans. At close, the channel is deleted and the conversation is saved as a transcript.

Form answers expire on the same clock. A server that leaves a paid plan drops to 90 days, and older conversations are removed that night. Export a report you may need later. Exporting tickets covers both export modes.

How do you close the loop with the reporter?

Tell them it was handled, not what happened to the other person. The reported member deserves privacy about their punishment, and a reporter told "we banned them" may repeat it.

The close reason is not a private note: the reporter reads it in their DM. Write something like "Reviewed by the mod team. Thanks for reporting, open another ticket if it happens again." Discuss the case in a staff channel too, because the reporter can read every message in their own ticket.

To count repeat reports about one person, start each close reason with their user ID. Ticket search matches text in close reasons, so one search lists every report about them. Set the period to all time, because it starts at the last 30 days. Ticket search covers the filters.

What a report ticket cannot do