How to Use

Go to Sign Up and enter your email, username, and password. You'll receive a 6-digit verification code at your email. Enter the code on the verification page to activate your account.

Click "Continue with Discord" on the signup page. You'll authorize through Discord, then receive a verification code at your Discord email. Enter the code to complete signup. Your Discord username and avatar will be imported automatically.

Go to Login and enter your credentials. If you have 2FA enabled, you'll receive a 6-digit code at your email — enter it to complete login.

Click "Continue with Discord" to log in through Discord. If 2FA is enabled, you'll be redirected back to enter a verification code sent to your email.

Go to Forgot Password, enter your email, and you'll receive a reset code. Enter the code and set a new password.

Your Dashboard shows your username, email, account role, and when you joined. This is your home base.

If you haven't linked Discord yet, you'll see a "Connect Discord" button. Connecting imports your Discord username and avatar, and locks your display name to match your Discord identity.

View all devices currently logged into your account. You can see the browser, device type, IP address, and last activity time. Revoke any session you don't recognize, or revoke all sessions at once.

See whether your email is verified and if Two-Factor Authentication is enabled. Both are recommended for full account security.

Update your username and display name. If Discord is connected, these fields are locked to your Discord identity. You can disconnect Discord to regain manual control.

If you signed up with email: Change your password by entering your current password and a new one.
If you signed up with Discord only: Set a password for the first time. Click "Send Verification Code", enter the code from your email, then create your password.

Enter your new email address. A verification code is sent to your current email for security. Enter the code to confirm the change.

Toggle 2FA on to require a 6-digit email code every time you log in (both email/password and Discord login). To enable, you'll first verify with a code sent to your email. To disable, just toggle it off.

Same as the Dashboard sessions view — see and manage all active sessions.

Permanently delete your account and all associated data. This action cannot be undone.

Visit the Demo Page and click "Run Full Scan". The scanner collects 650+ signals from your browser across 28 categories — including your GPU model, fonts, screen resolution, audio fingerprint, WebRTC data, and more. No account required.

The 28 categories are: Navigator, Screen, WebGL (GPU), Canvas, Audio, Fonts, Codecs, Storage, Battery, Network, Permissions, Math, Features, Touch, CPU, WebGPU, WebRTC, CSS, CSS Support, Media, Sensors, Speech, Intl, Text Metrics, Crypto Performance, Event Loop, WASM Performance, and Timing. Each category collects multiple signals that combine into a unique fingerprint hash.

On top of client-side signals, your IP is analyzed server-side for VPN/proxy/Tor detection, fraud scoring (0-100), bot detection, ISP identification, and geolocation. This adds approximately 20 additional server signals.

After a scan, click "View Full JSON" to see all raw data. You can copy and save this for your records.

1 Discord server, 100 verifications/month, ~280 signals (15 categories), Canvas/WebGL/audio fingerprinting, alt account detection (device-level), hCaptcha protection, VPN/Proxy/Tor detection (basic), 10-step Auto Setup wizard + 10-step Manual Setup wizard, server rules (templates or write your own), self-assign roles (dropdown embed), pre-verification channel visibility, rank channel (#rank-commands + #rank), leveling system (/rank, /leaderboard, 10 level roles), modmail dashboard + response templates, outbound tickets (mod-initiated), file attachments in modmail (images, videos, files + security scan), verify badges (Verified/Unverified) on all messages, quick actions (ban/kick/warn from web), appeal system (AI investigation, 10 sources), audit logs (60+ event types), AutoMod (bad word filter), web chat client (browse & message any channel from dashboard), mod leaderboard, satisfaction survey (1-5 star ratings), dismiss tickets (close silently), transfer tickets between mods, welcome channel setting, modmail notification channel, private threads for alt/ban detection, action buttons re-post in mod channel after every user reply, automatic link scanning (multiple security intelligence services), file attachment scanning (smart background scan), DM fallback channels (auto-created if user blocks bot), help detection (bot guides users to DM), live agent support (website AI chat → modmail ticket), auto-close stale tickets (24h inbound, outbound never), smart DM fallback (private thread if DMs off), notification sounds (new tickets & messages), role position warning, mod role sync ("Servers I Moderate"), boost/join/leave/message edit/delete logs. Good for trying things out.

5 Discord servers, ~470 signals (22 categories), advanced VPN analytics & provider tracking, WebRTC real IP detection, stealth VPN & impossible travel detection, advanced bot & automation detection, AI rules generation (setup wizard), AI modmail tools (summary, reply suggestions, sentiment analysis), SLA timers & response time tracking, live activity feed, AI investigation & security briefing, analytics dashboard & CSV export, daily threat digest, auto-slowmode, trackable links, message sent logging (30-day history), unlimited verifications. For servers that need real protection.

10 Discord servers, 650+ signals across all 28 categories, GPU/CPU hardware profiling, anti-detect browser detection (Multilogin, GoLogin, AdsPower, Dolphin Anty, Kameleo and similar tools — analyzed via 8 fingerprint signals: WebGL brand mismatch, canvas double-render, timezone vs IP, UA vs client hints (with high-entropy architecture/bitness validation), permissions API, plugin tampering, hardware ratio, WebGL parameter consistency), IoC database (IP/ASN/fingerprint threat matching), /dig message archaeology, custom alerts & raid detection, global threat intelligence (cross-server), priority support. REST API access and custom branding are coming soon. Best for large communities and networks.

When a member joins your server, they click a "Verify Me" button in your verification channel. The bot generates a secure 10-minute token and sends them to the Ends Town Hall website. There, they complete an hCaptcha and the fingerprint scanner runs automatically. The bot checks the fingerprint against banned users, runs risk scoring, and either assigns the Verified role or blocks the attempt. Everything is logged to your dashboard (and to #security-logs in Discord if you chose that during setup).

Setup is done entirely from the web dashboard — the bot is silent when it joins (no DMs, no embeds). Head to My Servers, click + Add Server, invite the bot, then choose Auto Setup (10 steps — bot creates everything) or Manual Setup (10 steps — you pick from existing roles and channels you've already built).

Auto Setup wizard:
Step 1 — Enter your Server ID and name
Step 2 — Invite the bot via the provided link. The bot creates core roles (@Verified, @Unverified, @Permanently Banned, @Alternate Account, @Moderator) and the #verify channel
Step 3 — Choose where logs go: Discord, Dashboard (recommended), or Both. Dashboard is recommended because if a mod's Discord account gets hacked, an attacker can't access logs protected behind a separate dashboard login. Choosing Discord or Both creates 11 log channels (security-logs, audit-log, join-leave, voice-logs, warn-logs, kick-logs, ban-logs, mute-logs, boost-logs, appeal-logs, modmail-logs) in a 🛡️ MOD PANEL category
Step 4 — Choose where mod commands work: Discord, Dashboard (recommended), or Both. Same security logic — website mod tools require a separate login. Choosing Discord or Both creates #mod-commands
Step 5 — Server type (Gaming, Community, Study, etc.)
Step 6 — Describe your server for AI-generated rules (Pro+) or get a standard template (Free). Optional — skip if you don't need rules
Step 7 — Rank channel (optional) — creates #rank-commands and #rank in a 📊 INFORMATION category. Can be skipped and set up later in Settings
Step 8 — Leveling system (optional) — creates 10 colored level roles (Lvl 10–100). Can be skipped and set up later in Settings
Step 9 — Review rules & confirm
Step 10 — Self-assign roles (optional) — type role names like "Gamer, Artist, PS5" and the bot creates them + posts a dropdown embed in #self-roles inside 📋 INFORMATION. Members pick their own roles after verifying

If roles or channels get accidentally deleted, go to Server Settings, run a Health Check, and click Re-run Auto Setup.

/setupverify — Posts the verification embed with the "Verify Me" button in the current channel. Mods only.

Manual Setup wizard (10 steps): If you've already built your server's roles and channels and want to map them to Burner Phone instead of letting the bot create new ones, choose Manual Setup. Each step lets you pick from your existing roles and channels via dropdowns — no auto-creation.
Step 1 — Server name and ID
Step 2 — Pick your Verified role (existing dropdown)
Step 3 — Pick your Unverified role
Step 4 — Pick your Verify channel (where the bot posts the "Verify Me" button)
Step 5 — Bulk log channel picker — pick a channel for each of the 11 log types (security, audit, join-leave, voice, warn, kick, ban, mute, boost, appeal, modmail). Skip any you don't want
Step 6 — Mod commands channel (where mod alerts and modmail pings go)
Step 7 — Welcome channel (optional)
Step 8 — Server type (gaming, community, study, art, music, other) — used for rules generation
Step 9 — Server rules (optional) — pick a rules channel and generate a starter ruleset, write your own, or skip
Step 10 — Rank & leveling (optional) — pick a rank-commands channel and choose whether to create the 10 level roles
Step 11 — Preferences (mod_mode and log_destination)
Step 12 — Self-assign roles (optional) — same UI as auto wizard's step 10, with live preview embed
Step 13 — Review and confirm

Editing log channels later: Whether you used Auto or Manual setup, you can change which channel each log type posts to anytime from Server Settings → Log Channels. Picks save instantly and the bot uses them within 60 seconds.

When a user verifies, their device fingerprint is stored. If a banned user tries to verify on a new account using the same device, the bot automatically blocks them and alerts your mod team with the original ban details.

Every verification is scored 0-100 based on multiple signals: account age (< 7 days = blocked at verify button + risk score), IP velocity (5+ verifications/hour flagged), impossible travel (same fingerprint in different countries within 6 hours, Pro+ only), browser language vs IP country mismatch, VPN/proxy detection, and bot/automation detection. High-risk scores (50+) trigger mod alerts.

When a high-risk verification occurs, the bot posts an alert with the user's risk score, VPN/proxy status, and account age. If your log destination includes Discord, alerts go to #security-logs. Alt account blocks generate detailed alerts showing which original account the device is linked to. Full details including IP, ISP, and location are restricted to platform administrators on the dashboard — never shown in Discord for privacy.

Need help? Any user can DM Burner Phone to open a support ticket with the team. This is for contacting the platform — server owners and mods can use it to report issues, ask questions, or get setup help. Tickets include read receipts, queue position, and priority levels.

The bot scans messages for malicious links using a multi-layered security intelligence stack. It detects typosquatting (disc0rd.com), known phishing URLs, social engineering patterns (crypto scams, prize scams), and suspicious file attachments. When a threat is found, the message is deleted automatically. If your log destination includes Discord, Ban/Warn/Dismiss buttons appear in #security-logs for mods to act on.

When a user is blocked during verification (alt detection or banned fingerprint), they land in #alt-accounts or #permanently-banned. Each detection creates a private thread visible only to the detected user and moderators, showing their linked accounts and attempt count. The channel has a permanent Submit Appeal button from setup. Clicking it opens a form with 5 trap questions (different for alts vs bans). After submission, the bot runs an AI investigation pulling 10 data sources — verification history, ban records, fingerprint chains, linked accounts, incident timeline, group bans, last messages, and more. The AI report goes to #appeal-logs with Approve, Deny, and Re-investigate buttons for mods. A private confirmation thread is created for the user (auto-archives after 24h). The AI recommends — mods decide.

From your Server Settings page, you can toggle: Block VPN Users, Block Proxy Users, WebRTC Detection (detect real IP behind VPNs), Auto-Block High Risk (block users with risk score above 70), and Require hCaptcha. Changes take effect immediately for the next verification.

See exactly which of your bot resources are working, missing, or unconfigured — categories, channels, roles, log destinations. If a category or channel was accidentally deleted, click Recreate next to the missing item to rebuild just that one resource, or click Swap to point the bot at an existing channel/role of your choice instead. No need to re-run the entire setup wizard to fix one thing. The Recreate All Missing button restores everything in one click. Click Scan Status to refresh.

Click "Run Check" to verify your server setup is correct. It checks bot permissions, role hierarchy, whether Verified/Unverified roles exist, and verify channel exists. If your logs include Discord, it also checks for #security-logs. If anything is missing, a Re-run Auto Setup button appears to fix it automatically.

Change where your verification logs are sent and where mod commands work — Website Dashboard Only (recommended), Discord Server Only, or Both. Dashboard is recommended because if a moderator's Discord account gets hacked, an attacker can't access logs or use mod tools that are protected behind a separate dashboard login. These are initially set during bot setup but can be changed here anytime.

Select your Welcome Channel (where verified users are greeted) and Main Chat Channel. All plans can configure channel visibility — control which channels @Unverified members can see before they verify. Manage this from the Visible tab in the Mod Panel.

Go to Mod Panel. You need to be logged in with your Discord account linked and have a recognized mod role in the server — Moderator, Mod, Staff, Admin, Management, or Senior Moderator all work. Users with Discord's Manage Guild or Manage Messages permissions also get access automatically. If you moderate multiple servers, you'll see a server picker. The panel URL auto-loads the right server if you click through from Servers page.

Your home base. Shows 4 live stat cards: Total Verifications, Threats Blocked, VPN Detections, and Alt Accounts Found. Below that: Recent Verifications (latest 5 attempts with pass/fail and risk) and Recent Activity (live event feed). Pro/Enterprise servers also see an AI Security Briefing button — click "Generate Report" for an AI-powered 24-hour summary of your server's threat landscape.

Every verification attempt your server has ever had — user, timestamp, pass/fail result, risk score (with color bar), location flag, and active flags (VPN, proxy, alt, new account). Filter by All / Verified / Blocked / Alts. Click any row to jump to that user's lookup. Load More button pages through history.

Enter any Discord User ID to pull their full record: verification history, risk score, device info, and flags. Platform administrators see full IP/ISP/Browser/OS data. Mods see country, risk score, and VPN flags only — no IP addresses. Action buttons below the profile: Warn (DMs the user), Kick (removes from server, must re-verify), Ban (soft ban — strips roles, adds @Permanently Banned, flags fingerprint for alt detection). Pro/Enterprise adds AI Investigate (pulls 10 data sources). All actions require a reason and are permanently logged.

Real-time event feed for your server — verifications, blocks, security alerts, and bot events with timestamps. Useful for watching live during a raid or suspicious activity window. Requires Pro or Enterprise plan.

Charts and trends: Verification Trend over 30 days (line chart), Threat Breakdown by category (pie/doughnut), VPN/Proxy Providers table (provider name, ASN, attempt count, block rate, avg risk score), and Raid Events log. Helps identify patterns, peak attack windows, and top threat sources. Requires Pro or Enterprise plan.

All verified members in one searchable table — username, verification status, risk score, verified date, and device type. Search box filters in real time. Click any member's name to jump to their User Lookup. Export as CSV for offline records. Useful for auditing your member base or checking who verified recently.

Complete history of every mod action taken through the dashboard — bans, kicks, warns, suspensions, unsuspensions. Filter by action type. Shows target user, which moderator took the action, the reason given, and timestamp. Export as CSV. Permanent record — cannot be edited or deleted.

Two sections. Account Integrity Alerts — auto-generated alerts from the bot for suspicious patterns (high risk scores, alt detections, VPN spikes, raid indicators). Custom Alerts — create your own rules: choose a type (Risk Score Above, Alt Detected, Raid, VPN Spike), set a condition/threshold, and enter a Discord webhook URL. The bot will POST to that webhook when the condition is triggered. Enterprise only.

Full server event history captured by the bot: role adds/removes, nickname changes, message edits/deletes, voice joins/leaves/moves/streams, member joins/leaves, channel creates/deletes, and all mod actions (ban, kick, warn, suspend, unsuspend). Filter by event type or a specific User ID. Paginate with Older/Newer buttons. Auto-refreshes every 15 seconds — you can watch events come in live.

Built-in quick reference for your mod team. Covers: all mod actions and what they do, how to take action from dashboard vs Discord, a tab-by-tab explanation of the panel, all 60+ audit event types with color coding, permission tiers (owner vs mod vs member), what the bot does automatically, and what mods cannot do. Shareable link — send it to new mods to get them up to speed.

A complete support ticket system built directly into Discord and the dashboard. Members open tickets by DMing the bot. Mods handle tickets from either the Modmail dashboard or Discord — your team picks the surface they prefer, and both views stay synchronized in real time.

Channel architecture (always-paired): Every modmail ticket creates two channels under the MODMAIL category. The mod channel (mod-{user}-NNNN) is where moderators type replies, click action buttons, view AI tools, and run mod actions — users never see this channel. The support channel (support-{user}-NNNN) is the user-facing surface and a transcript record. For DMs-on tickets, the user stays in their DMs and the support channel acts as a read-only mirror that mirrors every message in both directions for the rest of the staff team to follow along. For DMs-off tickets, the support channel is the user's primary surface — they read replies and send messages there. In both cases, moderators see the support channel but cannot type in it (read-only); they always type in the mod channel and the bot forwards messages anonymously. This eliminates typing-indicator leaks, message-flash leaks, and accidental visible buttons in user-facing channels.

Anonymous moderator identity: Every moderator reply rendered in Discord — DMs, support channels, and transcripts — appears as "Server Moderator" with the bot's avatar. Real moderator names never appear in any user-visible Discord surface. Real identity is preserved in the database, the mod dashboard, the audit log, and the staff leaderboard for full accountability. Users see one consistent voice; staff retain full attribution internally.

Action buttons: Every mod channel includes a button row pinned to the most recent activity. All plans get Claim, Close, Dismiss, Transfer, Notes, Warn, Kick, and Ban. Pro and Enterprise plans add Priority, AI Summary, and Suggested Replies (AI tools are ephemeral — visible only to the moderator who clicked them). The button row is automatically re-posted in the mod channel after every user reply so moderators never have to scroll up to find their controls.

Notification channel: Every new ticket — regardless of source — pings the channel you configure in dashboard Settings → Modmail. The notification embed includes the ticket source label (Discord DM, website live agent, dashboard-initiated, or slash command), the user's tag and ID, the previous ticket count, links to both the mod and support channels, and a deep link into the dashboard. On the main support server, multiple staff roles (Senior Mod, Management, Moderator) are pinged; on your server, only your @Moderator role is pinged. If no notification channel is configured, the system falls back to #mod-commands or #security-logs.

Outbound tickets: Mods can start tickets with any member proactively. Use the + New button in the dashboard sidebar, or run /modmail-new @user message in Discord. The member receives a DM containing the message and a "Verify Identity to Continue" button that captures a fresh IP and fingerprint scan. Both mod and support channels are created immediately. If the member's DMs are off, the system gracefully degrades — the support channel becomes their primary surface with an explanation embed and instructions to re-enable DMs.

Live Agent (Website): Visitors on endstownhall.com can request a human agent through the embedded AI assistant. The system asks for their preferred name (skipped if they're already logged in with Discord), creates a paired ticket, and pings the configured notification channel. Mods respond from either the dashboard or Discord — the visitor sees responses appear in the chat widget in near real time (3-second polling). When the ticket closes, the widget displays a closed-conversation notice.

Dashboard features: Live ticket list with unread badges and source icons, real-time message polling (2-second refresh), claim assignment, mod notes (private — never visible to the member), inline investigation panel showing the member's verification data and risk score, response templates for common replies, quick mod actions (warn/kick/ban from inside the ticket), seen tracking, audible notification on new tickets and messages (toggleable), inline file attachment rendering (images preview, videos with playback controls, downloadable files — all attachments scanned by security intelligence services with malicious files flagged in the mod channel), and a moderator leaderboard ranking tickets resolved per staff member.

Verification badges: Every user message in the dashboard shows Verified (with verification date) or UNVERIFIED next to their name — visible to all moderators on every plan.

IP Intelligence (Restricted): Platform administrators see a 🔒 badge next to messages with full IP, port, ISP, organization, country, region, city, VPN/proxy/Tor flags, WebRTC leak detection, and risk score. Server owners and moderators do not see this data — only the platform administrator does, for cross-server abuse investigation.

Plan gating: All plans include the full ticket lifecycle — list, reply, close, claim, dismiss, outbound, transfer, mod notes, verify badges, file scanning, and notification channel. Pro and Enterprise add AI thread summary, AI reply suggestions, AI sentiment analysis, SLA timers with color-coded escalation, and ticket priority levels (Low/Medium/High/Urgent — channels are renamed and color-tagged accordingly). All Discord button rows include the same eight base actions on every plan; Pro/Enterprise unlocks the three AI buttons.

Automatic Link Scanning: Every link posted by non-staff is checked in real time against multiple security intelligence services using a consensus-based model — two or more services must flag a link before it is deleted. Single-service flags are logged but not removed (prevents false positives that block legitimate content). Trusted domains (Discord, YouTube, Google, GitHub, Steam, PlayStation, etc.) are whitelisted and skip scanning entirely. Deleted links trigger a warning embed in the channel that auto-removes after 15 seconds, plus a permanent entry in #security-logs.

File Attachment Scanning: Every uploaded file from non-staff is checked silently in the background. Dangerous extensions (.exe, .bat, .cmd, .scr, .ps1, .vbs, .jar, .dll, .msi, .apk, .iso, and 10 others), double-extension tricks (photo.jpg.exe), and Unicode filename obfuscation are blocked instantly. Normal files (images, video, audio, PDFs) remain visible to the channel during scanning — the bot performs magic-byte verification, embedded executable detection, PDF JavaScript inspection, and SHA256 hash lookup against threat databases. Only confirmed threats are removed; clean files are never touched. Every scan result is logged for audit.

DM Fallback (Plan B): The bot always attempts DM delivery first. If a member has DMs disabled or has blocked the bot, the system upgrades the existing support channel with user permissions, posts an explanation embed describing why the channel was created, and includes step-by-step instructions for re-enabling DMs. The user can read and reply directly in the support channel; mods continue replying anonymously from the mod channel.

Help Detection: When a member asks for help in chat ("can a mod help", "where are the mods", and similar phrases — about 25 detected variations), the bot replies with a small embed directing them to DM Burner Phone for a ticket or use the AI assistant on the website for live support.

A full Discord-like chat client built into the mod panel. Browse all text channels in a three-column layout (channel sidebar, messages, member list), read message history, send messages, reply to messages, react, pin, delete, and search — all from the browser without opening Discord. Features include: custom emoji rendering, message grouping, date dividers, embed rendering, video/image attachments, @mention autocomplete with role colors, typing indicators, unread dots on channels, and Discord-style profile cards when clicking any member (with Warn/Kick/Ban/Mute/AI Investigate actions).

Verification badges: Every message shows Verified () or UNVERIFIED next to the author name — all mods see this. IP Intelligence (Restricted): Platform administrators see a clickable badge next to each message author. Click it for a tooltip with IP address, port, ISP, country, region, city, VPN/proxy detection, risk score, and WebRTC leak data. Profile cards also include a full IP Intelligence grid for administrators. Member data refreshes every 30 seconds so verification badges update in near real-time. Available on all plans.

Manage a server-wide banned word list. Add words or phrases — the bot will automatically delete any message containing them and log the action. View all active words in a list with one-click delete. Available on all plans.

Create short trackable links that log every click. Enter a destination URL and optional label — the system generates a tracking URL. View click counts per link. Useful for tracking invite sources, measuring campaign reach, or monitoring suspicious links shared in your server. Requires Pro or Enterprise plan.

Review appeals submitted by members through #permanently-banned or #alt-accounts. When a user is detected as an alt or banned device, a private thread is created for them showing their username, linked accounts, and attempt count — only they and mods can see it. The channel has a permanent Submit Appeal button — when clicked, a modal opens with 5 trap questions (different for alts vs bans). After submission, the bot runs an AI investigation pulling 10 data sources and posts the report to #appeal-logs with Approve, Deny, and Re-investigate buttons. A private confirmation thread is created for the user (auto-archives after 24h). Available on all plans.

Control which channels unverified members (@Unverified role) can see before they complete verification. Toggle channels on/off — the bot updates Discord permissions in real time. Useful for hiding community channels while showing rules and verification instructions. Available on all plans.

Platform administrators have full access — all tabs, all actions, can see IP/ISP/location data. Server owners and moderators can access all mod panel tabs and take actions but cannot see IP data. Regular members have no access to the mod panel — only the verification page.

During auto-setup, the bot creates (or expects) these roles in your server: @Verified — assigned after passing verification, grants access to main channels; @Unverified — assigned on join, sees only the verify channel; @Permanently Banned — used by mods to restrict a member and send them to the #permanently-banned appeal channel; @Alternate Account — auto-assigned when alt detection fires. Role hierarchy matters — the bot must be above all of these roles to assign/remove them.

#verify — where unverified members see the verification button (@Unverified only).
11 Log channels (created at Step 3 when log destination = Discord or Both): #security-logs, #audit-log, #join-leave, #voice-logs, #warn-logs, #kick-logs, #ban-logs, #mute-logs, #boost-logs, #appeal-logs, #modmail-logs. Manual setup customers can map each to existing channels via the bulk picker.
#mod-guide — read-only moderation guide auto-posted by the bot when MOD PANEL is created. Explains every action, every log channel, permission tiers, and what mods cannot do.
APPEALS category (auto-created on setup): #permanently-banned (banned device users land here — each detection creates a private thread with linked accounts and attempt count, plus a permanent Submit Appeal button) and #alt-accounts (same for alt-detected users).
#mod-commands — where slash commands /warn /mute /unmute /kick /ban /suspend /unsuspend /modmail-new /modmail-close are restricted to.
#rank-commands + #rank (optional, Step 7) — rank guide and member rank commands, in the 📊 INFORMATION category. Can also be created later from Settings.
Welcome Channel / Main Chat — configured in Settings, used for verified member greetings and bot announcements.
Modmail Notification Channel — when modmail is set to Dashboard Only, the bot pings @Moderator in this channel when a new ticket arrives. Defaults to #mod-commands if not configured.

All plans can designate specific channels as hidden — the bot ensures @Unverified members cannot see or access them until they verify. Configure this from the Visible tab in the Mod Panel, or in Server Settings → Channel Management. Useful for community channels, mod areas, or any content you want to gate behind verification.

During setup (Step 10), you can create self-assign roles for your community. Type role names like "Gamer, Artist, PS5, Xbox" and the bot creates them + posts a dropdown embed in #self-roles. Verified members pick their own roles from the dropdown — these are cosmetic/interest roles with no security permissions. You can also add or update self-assign roles later from Server Settings.

Optional features set up in wizard Steps 7 and 8, or any time from Settings → Rank & Leveling.

Rank Channel (Step 7): Creates #rank-commands (with a guide embed listing all rank commands) and #rank (where members use /rank, /leaderboard). Both go in a 📊 INFORMATION category.

Leveling System (Step 8): Creates 10 colored level roles — Lvl 10, 20, 30 … up to 100. Members earn XP by chatting. Roles are automatically assigned when they hit each threshold. XP tracking runs silently in the background even if you skip the roles — you can add them later.

Slash commands: /rank (check your level), /leaderboard (top members by XP).

Visit status.html to see real-time health of all services. The page monitors six components: Bot API, Discord Gateway, Database, Verification Engine, Modmail, and Website. It auto-refreshes every 30 seconds and displays a 30-day per-service uptime history with percentage bars. No login required — anyone can view it. Link it from your Discord server or website so members can check if the bot is up.

The bot runs an internal health check every 60 seconds. It tests each service (API responding, Discord WebSocket connected, PostgreSQL query works, verification_logs queryable, modmail_tickets queryable). When any service goes down, three things happen automatically:

1. The server owner receives a DM with the service name, error details, and specific instructions on what to check and how to fix it.
2. An incident is created on the public status page with the service name and "Investigating" badge.
3. Every check is logged to the database for the 30-day uptime history.

When the service recovers, the owner gets a recovery DM with downtime duration, and the status page incident auto-resolves. No manual updates needed.

All data (conversations, verifications, tickets, settings, audit logs, fingerprints) is stored in PostgreSQL and survives every restart. During a deploy, the bot is offline for 10-15 seconds. Active verification tokens expire (user clicks Verify again), and dashboard sessions log out (user logs back in). No conversations or user data are lost. The health monitor detects the restart and the status page reflects it automatically.