Ban, Kick or Timeout: Choosing the Right Discord Moderation Action
Three buttons, three very different outcomes, and one of them is reversible in a way the others are not. What each action actually does and how to pick the right one in ten seconds.
Most bad moderation decisions are not harsh or lenient, they are just the wrong tool. A kick used where a timeout belonged achieves nothing. A ban used where a kick belonged creates an appeal you will be arguing about next month.
What each one actually does
Timeout requires the Timeout Members permission (Moderate Members in the API). The member stays in the server and can still read channels, but cannot send messages, react, join voice, or start threads for the duration you set. The maximum is 28 days. They see a banner telling them they are timed out, so it is never a mystery to them. Members with Administrator cannot be timed out, and role hierarchy applies: you cannot action anyone whose highest role sits at or above yours.
Kick requires Kick Members. It removes the member from the server immediately. It does not block them, so they can walk back in through any working invite thirty seconds later. Their messages stay where they are.
Ban requires Ban Members. It removes the member and blocks that account from rejoining. You can delete their recent message history as part of the ban, covering anywhere from the previous hour to the last 7 days. Bans are listed in Server Settings and can be reversed at any time.
The useful mental model: timeout is a pause, kick is a door slam, ban is a lock. Only one of the three actually keeps someone out.
The decision table
| Situation | Action | Why |
|---|---|---|
| Two regulars arguing, escalating fast | Timeout, 1 hour | Cools it down, both keep their place in the community |
| Newcomer breaks a rule they clearly did not read | Warn, no action | The rule break is an onboarding failure, not a member problem |
| Repeat minor offender, third time this month | Timeout, 1 day, plus a DM explaining the next step | Creates a visible escalation path before removal |
| Spam bot or advertising account | Ban with message deletion | It is not a member, do not negotiate with it |
| Slurs, harassment, targeted abuse | Ban with message deletion | No warning ladder for this category, ever |
| Compromised account posting scam links | Softban, with the shortest deletion window that covers the compromise | Removes the links and lets them back in once they recover the account |
| Underage user | Ban and report the account to Discord Trust & Safety | Discord's minimum age is 13, and higher in some countries |
| Someone who will not stop after being asked, but broke nothing serious | Kick | Interrupts the pattern, leaves the door open |
| Raid participants | Mass ban with message deletion | Speed matters more than individual assessment |
Kick is the weakest tool, and that is the point
Kick exists for one narrow case: you want the person gone right now, but you do not want to say they can never come back. That covers someone in a bad mood who will not disengage, or an account you suspect but cannot confirm is a problem.
What kick is not is a lighter ban. Against anyone determined, it is a five second inconvenience. If your reason for kicking instead of banning is "a ban feels too harsh", the honest choices are a timeout or a ban, not a kick that will be undone before you finish typing the mod-log entry.
Timeout durations that map to something real
Discord's menu offers presets from 60 seconds to a week; bots and the API can set up to 28 days. Pick from a short list and stick to it so your team stays consistent:
- 5 minutes: stop a heated exchange, no further action expected.
- 1 hour: someone needs to leave the conversation and come back different.
- 1 day: a real offence, recorded, with the next step spelled out.
- 1 week: last stop before a ban. Say so explicitly when you issue it.
Do not stack timeouts silently. A member who gets timed out four times without ever being told they are on a path to removal has been failed by you, not by the rules.
Message deletion and the softban
Deleting message history is part of the ban dialog, not a separate step, and it is the reason ban is the correct action for spam and scam links even when you intend to unban later. Choose the shortest window that covers the damage. Deleting seven days of someone's messages removes their side of every conversation they were in, which is disorienting for everyone else in the channel.
A softban is ban followed immediately by unban. The ban purges the recent messages, the unban lets the person return. It is the right tool when the content has to go but the person does not, most commonly a member whose account was compromised for twenty minutes.
Discord's ban list is per-account, not per-person. Someone with a second account walks straight past it. If ban evasion becomes a pattern, the fix is at the door, higher verification level and a screening gate, not more bans.
Record every action, or none of them count
Escalation only works if the previous steps exist somewhere. Discord's audit log keeps actions for 45 days and does not store your reasoning, which is why a bot from the moderation category with numbered warning cases is worth more than any single feature you could add to your server. The case number is what turns "I think we warned them once" into a decision anyone on the team can review in five seconds.
Pair it with something from the logging category so the deleted messages behind a ban still exist when the appeal arrives three weeks later. Without that, every appeal is one person's memory against another's.

A ticket bot gives appeals a private, logged channel instead of a moderator's DMs.
Appeals
Decide the policy once and publish it. A workable default: bans can be appealed after 30 days, through a form or a ticket, reviewed by a moderator who was not involved in the original decision. A bot from the tickets category keeps appeals in a queue instead of in one moderator's DMs.
Unban when the original reason no longer applies, when the action was wrong, or when the person has plainly changed. Do not unban because they were persistent. Rewarding pressure teaches everyone watching exactly the wrong lesson.
Audit your last twenty moderation actions this week and check whether each one has a recorded reason. If most do not, install a moderation bot with case logging before you make the twenty-first.