Discord Bot Support Server

A support server for a bot: setup forums, an error lookup, premium tickets, a changelog and a bug-hunter lane.

8 categories
33 channels
11 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

START

readme
Setup question? #setup-help. Error message? #error-lookup. Bug? #report-a-bug. Idea? #bot-suggestions.
bot-rules
Never share a bot token. One problem per thread. Be patient with helpers, they are volunteers.
invite-and-links
The invite link, the dashboard, the documentation and the status page.
notification-roles
Pick Changelog Pings for releases and Outage Pings for downtime.

DEVELOPER UPDATES

bot-changelog
Every release: new commands, fixes and anything that changes existing behavior.
dev-diary
What is being worked on and why, straight from the developer.
bot-status
Outages, degraded shards and the all-clear. Support Team posts here too.
scheduled-maintenance
Planned restarts and migrations, posted ahead of time.

SETUP HELP

setup-help
One question per thread. Tag the area and say which command or page you are on.
command-questions10s slowmode
Quick questions about a command. Longer problems belong in #setup-help.
permission-issues
The bot cannot see, send or manage something. Post the channel type and the bot's role position.
error-lookup
One error message per thread, titled with the exact text, with the fix as the first reply.
self-help-guides
Written guides for the questions asked most. Read before opening a thread.

PREMIUM SUPPORT

premium-ticketsHidden from @everyone
Priority tickets for Premium Users. The Core Team is pinged on every one.
premium-lounge
Premium Users and the team, without the queue.
early-access-featuresHidden from @everyone
Features Premium Users can try before release, with what to watch for.
Premium Voice

FEATURE REQUESTS

bot-suggestions60s slowmode
One idea per message. Vetox turns each into a suggestion with votes and a status.
request-discussion
Talk about suggestions here, not under them.
accepted-requests
Suggestions the Core Team has accepted, with the release they are planned for.

COMMUNITY

bot-chat
Chat about the bot and about Discord. Support questions go to Setup Help.
showcase-your-setup
Show how you use the bot on your server: welcome cards, panels, automations.
Support Voice
Dev Talk
AFK

BUG HUNTING

report-a-bug
Open a ticket with the command, what you expected and what happened. Screenshots help.
confirmed-bugs
Bugs the team has reproduced, with a status and the release that fixes them.
bug-hunter-loungeHidden from @everyone
For members holding Bug Hunter: early reproduction requests and thanks.

TEAM ROOM

ticket-queue
Open tickets and who has claimed them.
dev-escalationsHidden from @everyone
Bugs that need code changes. Support Team and Core Team only.
ticket-logsHidden from @everyone
Vetox posts ticket transcripts and member logs here.
deploy-notesHidden from @everyone
What was deployed, when, and what to watch. Contributors can read this.
Team Voice

Roles

Bot DeveloperAdministrator
Core TeamAdministrator
Support TeamModerator
HelperModerator
Premium User
Bug Hunter
Contributor
Changelog Pings
Outage Pings
Muted

Overview

A support server for a Discord bot, written for the developer who ships it and the team who answers for it. #readme is the first stop and tells a new member whether their question is a setup question, a bug or a request, because those three go to different places. Setup Help is the busiest category: #setup-help is a forum tagged by area (Permissions, Commands, Dashboard, Welcome, Moderation) and #error-lookup is a second forum where each thread is one error message and its fix, so 'Missing Access' gets answered once. #command-questions and #permission-issues take the quick ones. Developer Updates are read-only: #bot-changelog is the announcement feed, #dev-diary is where the developer writes about what is being built, and #bot-status with #scheduled-maintenance stop the 'is the bot down?' messages. Premium Support is hidden behind the Premium User role and has its own ticket panel, lounge and #early-access-features. Bug Hunting has a public #report-a-bug panel, a read-only #confirmed-bugs list and a hidden lounge for people holding Bug Hunter. The team side is hidden: #ticket-queue, #dev-escalations for the Core Team only, #ticket-logs, and #deploy-notes, which Contributors can also read.

When to use it

You built a bot, it got popular, and now your DMs are full of 'it does not respond' messages that turn out to be missing permissions. This layout answers setup questions in forums that stay searchable, keeps premium customers in a private lane with their own tickets, gives bug reports a panel and a confirmed list, and leaves the developer one read-only channel to talk to everyone at once.

What makes it different

#error-lookup is a forum where each thread is one error message and its fix, searchable by the exact text.
Premium Support is a hidden category with its own ticket panel, so paying users never queue behind free ones.
#bot-changelog, #dev-diary and #bot-status are read-only, so developer updates are never buried in chat.
Bug Hunter is an earned role with a hidden lounge, and #confirmed-bugs shows what the team has verified.
Contributors can read #deploy-notes, so open-source helpers know what shipped without seeing the ticket queue.

Recommended Vetox setup

Tickets
Two panels: a general one in #report-a-bug and a premium-only one in #premium-tickets, with the Support Team on both and the Core Team pinged on the premium one.
Suggestions
Point Suggestions at #bot-suggestions so every request gets a vote and a status, then move accepted ones to #accepted-requests.
Self-Roles
A Self-Roles panel in #notification-roles for Changelog Pings and Outage Pings keeps the announcement channels pingable without annoying everyone.
Notifications
Feed your repository or blog RSS into #dev-diary so development updates post themselves while you keep coding.
Auto-Mod
Auto-Mod in #command-questions and #bot-chat blocks the fake 'bot token' and invite scams that target new server owners.

Questions

Why is there a forum just for error messages?

Because bot errors repeat. 'Missing Access', 'Unknown Interaction' and rate-limit messages each have one cause and one fix, and a thread titled with the exact text is what a member finds when they search. #setup-help is for how-do-I questions; #error-lookup is for what-does-this-mean.

How does someone get Premium User?

Your team grants it once a purchase is verified, usually through a ticket or your own dashboard. The Premium Support category is hidden from everyone else, so the premium panel and #early-access-features are invisible to free users.

What do Helpers see that members do not?

Helpers see the Team Room: #ticket-queue, #ticket-logs and #deploy-notes. They do not see #dev-escalations, which is reserved for the Support Team and the Core Team, so a volunteer helper never reads unreleased fix details.

Common mistakes

Answering every setup question in #bot-chat, where the fix scrolls away and the same question comes back tomorrow.
Mixing premium tickets into the general queue, which is how a paying user waits an hour behind a permissions question.

Consider instead

Product Support Hub The product you support is not a bot and setup questions are a small share of the volume.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages