Moderation · Tickets · Safety
SeshBot
Runs your server so you don't have to.
Verification tickets that actually verify. Auto-moderation that catches what you'd have to be awake for. And protection against the one thing most bots ignore — an admin account going bad. Free to add, and nothing is switched on until you say so.
- 370+
- servers
- 440+
- tickets handled
- 23:14:02automodPhishing link removed in #general
- 23:14:37ticketVerification ticket opened — 3 answers submitted
- 23:15:10ticketClaimed by a staff member
- 23:18:44verifyUnverified removed, 18+ added, ticket closed
- 23:41:09insider2 channel deletions in 10s — lockdown, roles stripped
- 23:41:12restore2 channels and 4 permission overwrites restored
What it's for
The situations people actually add it for.
You need to check people are 18+ before they get in
A ticket category with your own intake questions and instructions, staff claiming so two people don't answer at once, and one command that swaps Unverified for Verified when they pass. The transcript is DM'd to them and deletes itself after 18 days.
Someone is posting scam links at 4am
Phishing links, scam payment handles, invite spam and risky attachments get removed without you being awake. Your staff roles and quieter channels can be exempted so the filter never fights your own team.
An admin account gets compromised
Mass channel deletion, role wipes, permission changes and ban waves each have their own threshold. Trip one and the server locks down, the account's dangerous roles come off, and what was deleted is restored from a rolling snapshot.
Someone leaves in a huff and comes back next week
Their roles are saved on the way out and handed back on return — except anything carrying Administrator, which is never stored and never restored, so a rejoin can't be used to climb back up.
You want the server to feel alive without babysitting it
XP from messages and voice time, daily streaks, rendered level-up cards, achievements you define yourself, plus polls and giveaways run from one dashboard.
Your voice channels are either empty or overflowing
One join-to-create channel becomes as many rooms as people need. Whoever made a room owns it — rename, limit, lock, hide, kick, block, or hand it over — and it disappears when they leave.
Everything it does
The whole feature set, not a teaser.
Tickets & verification
Per-category panels
Each category on the panel can have its own welcome message that pings whoever opened it, up to five intake questions asked in a pop-up before the ticket exists, and its own role action.
One-command verification
/verify removes the roles you configured and adds the ones you configured, posts your success message, optionally DMs the member and closes the ticket. It refuses Administrator roles and anything above the bot's own.
Claiming
Staff claim a ticket so nobody doubles up. Optional lock mode makes other support roles read-only while it's claimed.
Transcripts & reviews
A full HTML transcript is DM'd when a ticket closes. Stored copies are optional and expire after 18 days. Members can rate the experience afterwards, and reviews can be posted to a public channel.
Cooldowns & blacklist
A per-user cooldown between tickets and a blacklist for anyone abusing them. Staff bypass the cooldown.
Safety
Auto-moderation
Spam, phishing links, scam payment handles, risky file types, link rules and image nudity detection — each switched on independently, with per-channel and per-role exemptions.
Anti-insider protection
Watches for damage only staff can do. Defaults: 2 channel deletions in 10s, 2 role deletions in 10s, 3 permission changes in 12s, 1 ban in 10s. Every threshold and window is yours to set.
Automatic restore
Rolling snapshots of channels, roles and permissions mean a trip doesn't just stop the damage — it puts back what was deleted, unbans who was banned, and can time the account out for an hour.
Member verifier
New accounts are risk-scored on join. Above your review threshold they're flagged; above the quarantine threshold they're held. Defaults are 50 and 30.
Cross-server reputation
Check whether an account has a violation history elsewhere before you let it in.
Moderation
The usual set, done properly
Ban, kick, timeout, temp-ban with automatic release, purge, and a channel nuke that clones permissions rather than losing them. Bans DM the reason.
Punishment roles
Strip a member back to a single role, then put every one of their roles back later with one command.
Audit logging
Message edits and deletions, member updates, channel and role changes, voice activity and server settings — each type opt-in, to a channel you choose. All off by default.
Community
Levels & achievements
XP from messages and minutes in voice, daily streaks that reset if you miss a day, rendered level-up cards, and achievements you define against XP, messages, voice time or streak.
Polls & giveaways
Both from one dashboard, with timers, entry requirements and automatic winner selection.
Dynamic voice channels
Join-to-create rooms owned by whoever made them: rename, user limit, lock, hide, kick, block, claim an abandoned room, or transfer it.
Reaction roles & welcomes
Self-serve role panels, welcome and leave messages as plain text, embeds or generated image cards, and an automatic role for new joins.
Verification, end to end
From 'how do I get in?' to verified, without a copy-pasted message
Someone picks your verification category and answers your questions before the ticket is even created. It opens with your instructions already pinged at them and your staff notified. When they've done it, one command finishes the job.
- Up to five intake questions per category, answers pinned to the staff embed
- Role swaps refuse Administrator roles and anything above the bot
- Optional DM confirmation and automatic close
- Transcripts DM'd on close; stored copies expire after 18 days
When it goes wrong
The protection you hope never fires
Most bots moderate members. SeshBot also watches staff. If an account starts deleting channels, wiping roles, spawning webhooks or mass-banning, it trips a threshold and acts before anyone wakes up.
- Separate thresholds and time windows per attack type
- Lockdown, role stripping and an optional 60-minute timeout
- Restores deleted channels, roles and permissions from snapshots
- /anti_insider_diagnose reports what it can and can't do in your server
Questions
Before you invite it
Is it free?
Everything above is free except two things: the AI assistant and server backups. Those unlock by boosting The Sesh Shed — the server owner boosting once, two admins boosting once each, or one admin boosting twice. There's no subscription and no card involved.
What permissions does it need?
Only what the features you use require — tickets need Manage Channels, moderation needs Ban/Kick/Moderate Members, role features need Manage Roles. Its own role must sit above any role it manages; that's a Discord rule rather than ours, and /anti_insider_diagnose will tell you if it doesn't.
Does it read or store my server's messages?
It reads messages to run auto-moderation and count XP, but doesn't keep them. The only place message content is written down is a ticket transcript, which is DM'd to the participants and — if you enable stored archives — held for at most 18 days before deleting itself. Audit logging is off unless you turn it on, and you choose which events it keeps.
Will it start moderating the moment I invite it?
No. Auto-moderation, anti-insider, logging, levels, welcomes and archives all start disabled. Inviting the bot changes nothing about your server on its own.
Can it undo a raid?
Partly, and that's the honest answer. Anti-insider restores channels, roles and permissions it had snapshotted, and can unban people banned during a trip. It cannot bring back deleted messages — nothing can.
What's actually in a backup?
Server configuration: channels, roles, permissions and settings like verification level and content filter. No message content is ever included, so restoring a backup rebuilds the structure, not the conversations.
What happens if I remove the bot?
Its data for your server is deleted when it leaves. No retention period, no email required.
Does the dashboard do everything the commands do?
Nearly. Both read and write the same settings, so there's no separate 'dashboard version' of your server that drifts. A couple of things — the ticket setup wizard, restoring a backup — stay command-only because they're interactive.