Structured reports
Moderators submit a user, a written reason, and context from your server. The format keeps stories comparable so SellerBeware’s team can decide quickly and fairly.
Everything SellerBeware does today to help serious moderation teams stay coordinated.
Moderators submit a user, a written reason, and context from your server. The format keeps stories comparable so SellerBeware’s team can decide quickly and fairly.
If someone is already waiting in the review queue, new reports about the same person wait until that case closes—so the team never chases two versions of the same story.
Every report is approved or declined by SellerBeware’s developers—the people who run the bot—not by each server’s staff. Nothing becomes a cross-server “signal” until they make that decision.
When an accepted case later joins another participating server, moderators get a clear message in the channel you pick—including who they are, why they’re on file, and quick moderation shortcuts.
Anyone in your community can search a Discord user ID to see what’s on file: status, reasons, and where the original report came from.
Admins connect SellerBeware once, choose where alerts land, and can move that channel later without rebuilding your whole setup.
See the exact order of operations, or jump straight to the command reference.