Appeals

A public page where a banned user can put their case, and a queue where your staff answer it. Each server gets its own.

#Why it is worth setting up

Without one, an appeal is a DM to whichever staff member the user can still reach. That means no record, no second opinion, and one person carrying an argument alone.

With one, the appeal arrives in a queue, every staff member sees the same thing, and the conversation is kept.

#Setting it up

Appeals live at appeals.tides.cx under your server's own address. Turn the module on, then set the form up.

Brand wording supports ${servername}, so the default copy names your server rather than someone else's.

#The queue

Submissions arrive in the dashboard with tabs for pending, accepted, rejected and closed, each with a count, twelve to a page.

Each submission shows who it is from, what they were punished for, the case it relates to, and their answers.

#Answering

Staff reply from the dashboard or from Discord with /reply-to-appeal. Either way the user gets the message in their DMs and can answer with /reply, so it is a conversation rather than a form and a verdict.

Accepting or rejecting closes the appeal and tells the user.

#Blocking

Someone who submits ten appeals a day can be blocked from submitting.

Rejection does not block anyone by default. A rejected appeal is a decision about one punishment. It is not a reason to take away someone's ability to ask again, so blocking on rejection is a switch you turn on yourself.

Blocks can be permanent or time-limited.

#Commands

/reply-to-appeal answers an open appeal from Discord. Users answer with /reply in the bot's DMs.