How to Set Up a Discord Suggestions Channel with Upvote/Downvote Voting 2026
To set up a Discord suggestions channel with voting, create a locked #suggestions channel where members post ideas, add upvote/downvote reactions (👍/👎) or voting buttons via a bot, then tag each suggestion as approved, planned, denied, or shipped and move accepted ones to a roadmap channel. The whole setup takes about ten minutes and gives your community a clear, fair way to be heard instead of ideas vanishing into general chat.
A suggestions board turns scattered feedback into a system you can actually act on. Members vote, you triage, and the best ideas rise to the top on their own. Below is the exact channel structure, the voting mechanics, the status tags, and the housekeeping rules that keep the board from turning into a graveyard of dead requests.
Why a suggestions board beats random feedback in chat
When feedback lives in general chat, three things go wrong. Good ideas get buried under memes within minutes, the same suggestion gets posted ten times, and you have no way to tell whether one person wants a feature or fifty people do. A dedicated board fixes all three.
The single most useful thing a board adds is vote signal. A suggestion sitting at 47 upvotes and 3 downvotes is a different decision than one at 4 upvotes and 30 downvotes. You stop guessing what the community wants and start reading it directly off the channel. That alone is worth the setup.
A board also creates a paper trail. Six months later you can scroll back and see what you approved, what you shipped, and what you turned down and why. New members can read it before re-asking for something you already decided on.
Step 1: Create and lock the suggestions channel
Make a new text channel called #suggestions (or #ideas, or #feature-requests — pick one and stick to it). Put it in a category members already check, like a Community or Feedback group, not buried at the bottom of the server.
Now lock it down so it stays a board and not a chat room. Edit the channel permissions for the @everyone role:
- View Channel — On (everyone should see the board)
- Send Messages — On if you want members posting directly, Off if you want submissions to go through a bot command or a forum-post flow
- Add Reactions — Off for @everyone if you use bot-driven voting, On if you use plain emoji voting (more on this in Step 2)
- Create Public Threads — On, so each suggestion gets its own discussion thread
- Manage Messages — Off for everyone except staff
The cleanest modern option is to make #suggestions a Forum channel instead of a standard text channel. Each suggestion becomes its own post with its own thread, its own reactions, and its own tags — which makes the status-tag step later effortless. Set the forum's default layout to "List" so the most active suggestions surface first.
If you let members post freely, add a pinned message at the top with the rules: one idea per post, search before posting, no "+1" spam, keep it constructive. A short, clear pin prevents most of the moderation work before it starts.
Step 2: Set up upvote/downvote reactions or buttons
You have two ways to collect votes, and the right one depends on how much structure you want.
Option A — Plain emoji reactions. The fastest setup. When a suggestion is posted, react to it with 👍 and 👎 yourself, or have a bot auto-react to every new message in the channel. Members click the reactions to vote. This works on day one with zero configuration beyond auto-reactions, and it's genuinely fine for small servers.
The downside: emoji reactions are easy to game (one person, multiple votes via alt accounts), they don't enforce one-vote-per-person across up and down, and they don't produce a tally you can sort by.
Option B — Bot voting buttons. A bot posts each suggestion as an embed with real Upvote / Downvote buttons and a live vote count. This is cleaner: the count is visible, votes are tracked per user, and many bots let you sort suggestions by score. If you want to run more interactive votes elsewhere too, our guide on how to run Discord polls and giveaways covers the full polling toolkit.
With PeakBot you can set up auto-reactions on the suggestions channel so every new post gets 👍/👎 instantly, and you can present submissions as clean embeds. If you want those submission embeds to look sharp — title, description, author, color bar — our walkthrough on how to build a Discord embed shows the exact fields. PeakBot is free for these core features with no time limit, so you can run a real suggestions board without paying for a premium voting add-on.
A note on fairness: whichever option you pick, decide up front whether downvotes are visible. Some communities hide the downvote count to keep the tone positive and only show net score or upvotes. Both are valid — just be consistent.
Step 3: Add status tags — approved, planned, denied, shipped
Voting tells you what people want. Status tags tell people what you decided. This is the step most servers skip, and it's the one that builds the most trust, because members can see their idea was actually read.
Use a small, fixed set of tags so the board stays scannable:
- 🟡 Under Review — default for every new suggestion
- 🟢 Approved — you're going to do it
- 🔵 Planned — approved and scheduled, on the roadmap
- 🟣 Shipped — it's live, done
- 🔴 Denied — not happening, ideally with a one-line reason
- ⚪ Duplicate — already suggested, link to the original
If you used a Forum channel in Step 1, these become native forum tags you can apply with two clicks, and members can filter the board by tag — "show me everything Shipped" or "what's Planned." That filtering is the single biggest reason to use a forum for suggestions.
If you're on a standard text channel, apply status by editing the suggestion's embed (if a bot posts it) or by adding a staff reaction and a short reply. Either way, always leave a trace of the decision. A denied suggestion with no explanation feels like being ignored; a denied suggestion with "Good idea but it conflicts with X" feels like being heard.
Step 4: Route accepted ideas to a roadmap channel
Once a suggestion is Approved or Planned, move it out of the noise and into a #roadmap channel. This is a read-only channel (members can view and react, only staff can post) where you keep a tidy list of what's coming.
The flow looks like this:
- Idea posted in #suggestions, gets votes.
- You tag it Approved.
- You post a clean summary card in #roadmap — what it is, status, and a link back to the original suggestion thread so the discussion and vote history stay attached.
- When it's done, update the roadmap card to Shipped and post an announcement.
A visible roadmap is one of the strongest retention tools you have. Members who can see their suggestion moving from Approved to Planned to Shipped stick around to watch it land. It pairs naturally with the broader tactics in our list of Discord engagement ideas to keep members active — a living roadmap gives people a reason to keep checking in.
Keep the roadmap short. Three to five items "In Progress" and a handful "Up Next" is far more credible than a wall of fifty promises you'll never reach.
Step 5: Keep the board clean with thresholds and auto-archiving
A suggestions channel that's never pruned becomes a wall of dead, half-voted ideas nobody reads. Set rules that clear it automatically.
Vote thresholds. Decide a minimum score for an idea to even reach staff review — for example, a suggestion needs net +15 votes before you'll formally consider it. This filters low-effort posts without you lifting a finger; the community does the first pass. Post the threshold in your pinned rules so it's not a surprise.
Auto-archiving. If you used a Forum channel, set thread auto-archive to a sensible window (Discord offers up to 7 days of inactivity). Suggestions that get no traction quietly archive themselves. For text channels, do a monthly sweep: anything Denied, Duplicate, or Shipped older than 30 days gets cleared, with the decisions preserved in your roadmap log.
Cap the active board. Aim to keep no more than a few dozen live, un-triaged suggestions visible at once. If submissions outpace your triage, temporarily close new submissions (toggle Send Messages off) until you catch up. A board you actually respond to beats a busy board you ignore.
Frequently asked questions
Should I allow anonymous suggestions on Discord?
Anonymous suggestions get you more honest feedback, especially criticism people won't attach their name to, but they also invite spam and trolling. The middle ground most servers use is a bot command or modmail-style flow that posts the suggestion under the bot's name while staff can still see who submitted it — honest to the public, accountable behind the scenes. PeakBot's ticket system can serve as that private intake channel if you want a paper trail without naming the submitter publicly.
How do I stop spam in my suggestions channel?
Three layers handle nearly all of it: require a minimum account age or server tenure to post, use a vote threshold so low-effort ideas never reach review, and run AI moderation on the channel. PeakBot's context-aware AI moderation reads message intent and adapts per channel rather than matching a fixed keyword list, so it catches spam and off-topic posts in a suggestions board without flagging genuine feature requests. You can read more about the free moderation and core features that come with it.
Who should be allowed to vote on suggestions?
Restrict voting to members who've passed verification or reached a basic level (for example, a "Member" role earned after onboarding or a few days in the server). This stops fresh alt accounts from stacking votes and means the signal reflects your actual community. With reaction-based or button-based voting tied to a role, you can gate the Add Reactions permission to that role only.
Do I need a paid bot to run a suggestions board?
No. A locked channel plus emoji reactions costs nothing and works. A bot adds auto-reactions, vote tallies, status embeds, and forum-tag filtering that make the board far easier to manage at scale. PeakBot includes auto-reactions, embeds, polls, AI moderation, and a ticket system free with no time limit, so you can run a full board without a premium tier — and if you later want the AI Server Builder to generate a whole feedback category for you, that's the one Pro feature in the mix.
Standard channel or Forum channel for suggestions — which is better?
For most servers in 2026, a Forum channel is the better choice. Every suggestion becomes its own threaded post with native tags and reactions, members can filter by status, and the board stays organized without manual cleanup. Use a standard text channel only if your community is small enough that a simple emoji-voting list is all you need.
