Help

Frequently Asked Questions

Quick answers about ETH, the Burner Phone bot, plans, and setup.

Getting Started
What exactly is Ends Town Hall?
Two things. First, a Discord community for developers, gamers, cybersecurity learners, and creators — free to join at discord.gg/endstownhall. Second, a Discord security SaaS called Burner Phone — a bot + web dashboard that protects your server with browser fingerprinting, IP intelligence, and AI-powered moderation tools.
How do I add the bot to my server?
Go to My Servers after logging in, click + Add Server, then use the invite link to add Burner Phone. Once the bot is in your server, head back to the wizard and complete the remaining steps — choosing where logs go, mod command location, server type, rules, and optional rank/leveling setup. The bot is silent when it joins; all setup happens from the web wizard.
Do I need to create an account?
Yes — a free account is required to manage your server. Sign up at signup.html. You can optionally connect your Discord account for easier login. The verification page your members see does not require them to have an account.
What does the Free plan include?
1 Discord server · 100 verifications/month · ~280 fingerprint 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. No credit card required.
What's the difference between Auto Setup and Manual Setup?
Auto Setup (10 steps) — the bot creates everything for you: roles (@Verified, @Unverified, @Permanently Banned, @Alternate Account, @Moderator), the #verify channel, log channels in a 🛡️ MOD PANEL category, and rules. Level roles and self-assign roles are created too if you enable those optional steps (XP tracking runs silently either way). Best if you're starting fresh or want zero hassle.

Manual Setup (10 steps) — you pick from your existing roles and channels via dropdowns. Nothing is auto-created. Best if you've already built your server's structure and just want to map it to Burner Phone. Includes the same self-assign roles wizard and rules generation as Auto, but every channel and role is your choice. Includes a bulk log channel picker where you map all 11 log types to existing channels in one screen.

You can use either path, and both produce a fully working server. The choice is just about who's doing the channel creation — the bot or you.
Can I change which channel each log type posts to after setup?
Yes. Go to Server Settings → Log Channels at any time. You'll see a dropdown for each of the 11 log types — pick a different channel, click Save, and the bot uses your new pick within 60 seconds. No need to re-run setup. This works whether your initial setup was Auto or Manual.
What log channels does the bot use?
There are 11 log types, each with its own dedicated channel:
security-logs — verifications, alt detection, threat flags, ban appeals
audit-log — message edits and deletes, role changes, channel changes, server changes
join-leave — member joins and leaves
voice-logs — voice channel join/leave/move/streaming
warn-logs — moderator warnings issued
kick-logs — members kicked
ban-logs — members banned
mute-logs — timeouts and mutes (suspended/unsuspended)
boost-logs — server boosts
appeal-logs — ban appeal submissions
modmail-logs — modmail ticket transcripts

Auto Setup creates all 11 in a 🛡️ MOD PANEL category. Manual Setup lets you map each one to any existing channel — your channel can be named anything (the bot reads channel IDs, not names, when you use Manual setup). If a log type isn't configured, that log goes to the dashboard only (still saved, just not posted to Discord).
The Bot & Verification
How does fingerprint verification work?
When a member clicks "Verify Me" in your #verify channel, the bot generates a secure 10-minute token and sends them to the verification page. The page runs a browser fingerprint scan (canvas, WebGL, audio, fonts, CPU, screen, network, storage, and more depending on your plan), plus hCaptcha and IP analysis. The results are scored 0–100. Low risk = Verified role assigned. High risk = blocked and logged.
Can the bot detect alt accounts?
Yes. Every verified member's device fingerprint is stored. If a banned user creates a new Discord account and tries to verify on the same device, the fingerprint match triggers an automatic block and alerts your mods with the original ban details. The accuracy depends on how much the user changes their hardware/browser setup.
What is a "risk score"?
A 0–100 score calculated at verification time. Factors include: account age (under 7 days scores very high), IP velocity, VPN/proxy detection, browser-IP region mismatch, impossible travel (Pro+), and bot/automation signals (Pro+). Scores 50+ trigger a mod alert. Scores 75+ auto-block by default. Blocked members can submit an appeal through the bot's appeal system.
Does the bot store my members' data?
It stores fingerprint hashes, risk scores, IP metadata, and Discord tags — no passwords or payment info. IP and location data is restricted to platform administrators in the dashboard. See the Privacy Policy for full details.
My members are getting false-flagged. What do I do?
Check the Verifications tab in the Mod Panel — it shows the exact risk score and which factors triggered it (VPN, account age, fingerprint match, etc.) so you can confirm whether the flag is genuine. If it's a false positive, you can manually unsuspend the member from the User Lookup tab or via the /unsuspend slash command. Members who were auto-blocked at the verify button can also use the Appeal system — the bot DMs them a "Submit Appeal" button, they answer 5 trap questions, and the AI runs a 10-source investigation that posts to your #appeal-logs channel with an Approve / Deny / Re-investigate decision.
Plans & Billing
How do I upgrade to Pro or Enterprise?
Stripe payment integration is currently in development. To upgrade now, join the Discord server or email support@endstownhall.com and we'll set it up manually. You can also click the upgrade buttons in your dashboard — they'll let you know when billing is live.
What's the difference between Pro and Enterprise?
Pro ($15/mo) adds: 5 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, AI modmail (summary, suggestions, sentiment), 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. Enterprise ($49/mo) adds: 10 servers, 650+ signals (28 categories), GPU/CPU hardware profiling, global threat intelligence (cross-server), custom alerts & raid detection, anti-detect browser detection (Multilogin, GoLogin, AdsPower, Dolphin Anty, Kameleo — 8-signal confidence-scored detection), IoC database, /dig message archaeology, and priority support. REST API access and custom branding are coming soon.
Is there a refund policy?
Yes — 7-day no-questions-asked full refund on first purchase. After that, case-by-case. See the full Refund Policy.
How do I cancel?
Contact us on Discord or by email. Automated cancellation will be available once Stripe billing is live. We process cancellations within 48 hours of request.
Modmail & Dashboard
What is Modmail?
A built-in support ticket system that operates across Discord and the dashboard simultaneously. Members open tickets by DMing the bot. Mods respond from either the Modmail dashboard or directly in Discord — both surfaces 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, click action buttons, and use AI tools — users never see this channel. The support channel (support-{user}-NNNN) is the user-facing surface and a complete transcript record. For DMs-on tickets, the user stays in their DMs and the support channel acts as a read-only mirror that shows 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 and reply 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. Both channels delete when the ticket closes.

Anonymous moderator identity: Every moderator reply in any user-visible Discord surface (DMs, support channel, transcripts) renders as "Server Moderator" with the bot's avatar. Real moderator names never appear to users — but they are preserved in the database, the dashboard, the audit log, and the staff leaderboard for full accountability.

Action buttons: Mod channels include a button row that re-posts after every user reply so mods never have to scroll up. All plans get Claim, Close, Dismiss, Transfer, Notes, Warn, Kick, and Ban. Pro and Enterprise add Priority, AI Summary, and Suggested Replies (AI tools are ephemeral — only visible to the moderator who clicked).

Outbound tickets: Mods can start tickets proactively with the + New button on the dashboard or /modmail-new @user message in Discord. The member receives a DM with 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 support channel becomes their primary surface with an explanation embed.

Auto-close behavior: Inbound tickets (user-opened) auto-close after 24 hours of user inactivity. Outbound tickets (mod-opened) never auto-close — they stay open until the mod closes them. Unclaimed tickets can be silently dismissed without notifying the user (useful for spam or irrelevant messages).

Verification badges and IP intelligence: Every user message in the dashboard shows Verified (with date) or UNVERIFIED next to the author. Platform administrators also see a 🔒 IP intelligence badge with full IP, ISP, country, region, city, VPN/proxy/Tor flags, and risk score. Server owners and moderators do not see this restricted data.

Plan gating: All plans get the full ticket lifecycle (list, reply, close, claim, dismiss, transfer, outbound, mod notes, verify badges, file scanning, notification channel, response templates, the moderator leaderboard, and the 8 base Discord buttons). Pro and Enterprise add AI thread summary, AI reply suggestions, AI sentiment analysis with real-time gauge, SLA timers with color-coded escalation, ticket priority levels (Low/Medium/High/Urgent — channels are renamed and color-tagged), and the 3 additional AI buttons in Discord.
Who can access the Mod Panel?
The server owner (via their dashboard account) and any Discord user with a recognized mod role: Moderator, Mod, Staff, Admin, Management, or Senior Moderator. Users with Discord's Manage Guild or Manage Messages permissions also get access. Role access is checked in real time against Discord — no separate account linking required for mods.
Why does setup recommend "Dashboard" over Discord?
Security. If a moderator's Discord account gets hacked, an attacker could see all your security logs and use mod commands like /ban and /kick directly in Discord. When you choose "Dashboard," all logs and mod actions are only accessible through the dashboard — which requires a completely separate login. Even if someone's Discord is compromised, your mod tools and security data stay protected. You can change this setting anytime in Server Settings.
What is the Chat tab in the Mod Panel?
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, react, pin, delete, and search — all from the browser without opening Discord. Includes @mention autocomplete with role colors, custom emoji rendering, typing indicators, unread dots on channels, and Discord-style profile cards with mod actions (Warn/Kick/Ban/Mute). Available on all plans.
Status & Monitoring
Can I choose where the welcome message goes?
Yes. Go to Server Settings and click Load Channels under the Welcome Channel card. Pick any text channel from the dropdown and click Save. After someone verifies, the bot sends the welcome message to that channel. If not set, it auto-detects channels named general-chat, general, lounge, or main-chat.
What does /mute do?
The /mute command applies a Discord timeout to a member. You pick a duration (5 minutes to 28 days) and provide a reason. The user cannot send messages, react, or join voice channels for the duration. They receive a DM with the reason and duration. The mute is logged to #mute-logs. It automatically expires when the duration is up, or you can lift it early with /unmute @user [reason] — the user gets a DM that the mute has been lifted and the unmute is also logged.
Can I dismiss a modmail ticket without replying?
Yes. Unclaimed tickets show a Dismiss button. Clicking it closes the ticket silently — no DM is sent to the user, no satisfaction survey, no notification. The ticket is saved in the database as closed with reason "Dismissed without reply." Use this for spam, irrelevant messages, or tickets that don't need a response.
How do I get notified about new modmail tickets?
Every new modmail ticket — regardless of source (Discord DM, website live agent, dashboard + New, or /modmail-new) — pings your configured notification channel. The notification embed includes the ticket source, the user's tag and ID, previous ticket count, links to both the mod and support channels, and a deep link into the dashboard. By default the bot uses #mod-commands, but you can pick any channel under Server Settings → Modmail Notification Channel. On your server, your @Moderator role is pinged. The dashboard also plays a notification sound and shows a red unread count badge on the Modmail tab.
Can I start a modmail ticket from Discord instead of the dashboard?
Yes. Use /modmail-new @user [message] from anywhere in your server. The bot creates the standard paired channel set under MODMAIL — a mod-{user}-NNNN mod channel for your team and a support-{user}-NNNN support channel for the user (or as a transcript mirror if their DMs are on). The user receives your message via DM with a Verify Identity button that captures a fresh IP and fingerprint scan. The mod channel includes the full button row: Claim, Close, Dismiss, Transfer, Notes, Warn, Kick, and Ban on every plan; Pro and Enterprise add Priority, AI Summary, and Suggested Replies (all AI responses are ephemeral — only you see them). Buttons re-post after every user reply so you never have to scroll up. Type your replies in the mod channel — every reply renders to the user as "Server Moderator" with the bot's avatar; your real name is never visible to them. Other modmail slash commands: /modmail-note (private mod note), /modmail-claim (assign to yourself), /modmail-priority (set ticket priority), /modmail-transfer (reassign to another mod), /modmail-history (show ticket history), /modmail-close (close the ticket).
Does the bot scan links automatically?
Yes. Every link posted by non-staff members is scanned in real time using multiple security services. If a link is flagged as malicious, the message is deleted instantly, a warning is shown (auto-deletes after 15 seconds), and the event is logged to #security-logs. Staff and moderators are exempt from scanning. This is always on for all plans — no configuration needed.
Does the bot scan file attachments?
Yes. Every file attachment from non-staff members is scanned silently in the background. Dangerous file types (.exe, .bat, .scr, .ps1, .jar, .dll, .apk) and disguised files (double extensions, Unicode tricks) are instantly blocked. Normal files like images, videos, and documents stay visible while the bot checks them against malware databases. Only confirmed threats are removed — clean files are never touched. Staff and moderators are exempt.
What happens if a member has DMs turned off?
If the bot can't deliver a DM (member's DMs are off or they blocked the bot), it gracefully degrades. Because every modmail ticket already creates a paired support channel, the bot upgrades that existing support-{user}-NNNN channel with user permissions instead of creating a new one. The user can then read and reply directly there. Moderators see the support channel but cannot type — they continue replying anonymously from the paired mod-{user}-NNNN channel and the bot forwards every message as "Server Moderator". The support channel includes an explanation embed describing what happened and step-by-step instructions for re-enabling DMs. Both channels delete when the ticket is closed.
Does the bot detect when members ask for help?
Yes. When a member types something like "can a mod help", "where are the mods", or "I need support" in chat, the bot replies with an embed directing them to DM the bot for a support ticket or visit the AI assistant for live agent support.
How does link scanning work?
Every link posted by non-staff members is scanned using multiple security intelligence services. The bot uses a consensus-based approach — a link is only deleted if two or more services confirm it as malicious. If only one service flags it (possible false positive), the link stays but is logged to #security-logs for staff review. Trusted domains like Discord, YouTube, Google, GitHub, Steam, and others are never scanned. Staff and moderators are exempt.
Can website visitors talk to a live agent?
Yes. Visitors on the website can ask the AI assistant for a live agent. The system asks for their name, then creates a modmail ticket. The ticket appears on the modmail dashboard and in Discord (if preferences include Discord). Mods respond from either place — same system as regular modmail tickets. The visitor doesn't need a Discord account.
Does the bot detect when members need help?
Yes. When someone types something like "can a mod help me" or "where are the mods" in any channel, the bot replies with instructions to DM Burner Phone for a modmail ticket or visit the AI assistant for live support. This is always on.
Is there a status page?
Yes. Visit status.endstownhall.com to see real-time health of all services: Bot API, Discord Gateway, Database, Verification Engine, Modmail, and Website. It auto-refreshes every 30 seconds and shows a 30-day per-service uptime history.
How are incidents handled?
The bot runs an automated health monitor every 60 seconds. If any service goes down, an incident is automatically created on the status page. When the service recovers, the incident is auto-resolved with the downtime duration. No manual updates are needed — the status page always reflects the real-time state of the system.
Will I lose my data if the bot restarts?
No. All conversations, verification scans, modmail tickets, audit logs, settings, and user data are stored in PostgreSQL. Bot restarts only cause a 10-15 second window where DMs and slash commands are temporarily unavailable. Once the bot reconnects, everything picks up exactly where it left off. The only things reset are active verification tokens (the user just clicks Verify again) and dashboard login sessions (just log back in).
Still have questions? Ask in the ETH Discord server or use the ETH Assistant (chat bubble) on any page.