How to report someone in a Discord server

The short version: report privately, include what happened, who was involved, when, and any evidence. Do not do it in public. The route matters less than the detail — a vague report in the right channel is harder to act on than a precise one in the wrong one.

The three routes, fastest first

1. The ticket command

Type $ticket anywhere in the server. It opens a private channel with admins immediately, without you having to work out who is on duty. This is the fastest route and the one we would suggest for anything urgent.

2. Tagging staff

Tag @mod or @help for direct assistance from staff or the wider community. Useful when the issue is live — something happening in a channel right now — because it gets attention without leaving the conversation.

3. The Complaint Box

The formal route. A written report that stays on record, which is what you want for anything that is not urgent: a pattern of behaviour, something that happened days ago, or a complaint about how a previous report was handled.

What to actually include

Moderators cannot act on "X is being weird". They can act on this:

• What happened — the specific messages or behaviour, not a characterisation of the person.
• Who was involved — usernames, including anyone else affected.
• When — a rough date and time, or the channel it happened in, so the messages can be found.
• Evidence — screenshots, message links, or the channel name. Discord keeps message history, so a link is often enough.

What you do not need: a theory about why they did it, or a proposed punishment. Both are staff's job, and a report that arrives with a demanded outcome is harder to assess fairly.

What happens after you file one

The report goes to staff, not to the channel. Your identity stays confidential by default — the person reported is not told who raised it.

A moderator reviews the evidence and the context, which includes intent. An honest mistake gets education rather than punishment; recklessness or malice is treated more seriously. Whatever the outcome, the person on the receiving end is told why a moderation action was taken — that is one of the rules, not a courtesy.

Nothing is resolved through public call-outs, by design. If you post about it in the main channel, you will usually be asked to move it to a private route — not because the complaint is unwelcome, but because public handling turns every case into a performance.

If it involves a moderator

Report it anyway, and escalate. Staff are held to the same standards as members, and there is a department for exactly this — Issue Resolution covers how staff are held to account.

If a complaint does not go your way, there is a real escalation path to senior staff and, if needed, directly to bangwings@zohomail.in. That route exists because the first decision is made by a person, and people get things wrong.

What not to do

Do not DM a random moderator and expect it to be tracked. Do not post screenshots of someone in a public channel as a way of gathering support — that is a call-out, and it makes the case harder to handle cleanly. Do not report the same thing to five staff members; one route, filed properly, is faster than five parallel conversations.

If you are the one being reported

You will be told which rule was broken, specifically. If you disagree, you can appeal — the appeal process explains how. If you want to understand the difference between the outcomes you might receive, mute versus ban covers it. The full policy is on Safety & Guidelines.