How to collect feature requests in a Discord community (without sending people to a website)

Every growing Discord server hits the same wall: good ideas arrive faster than anyone can track them. A #suggestions channel fills with messages, the best ones scroll away, and you have no idea which requests people actually care about. The usual fix — a separate feedback website — trades one problem for another: you now ask members to leave chat, make an account somewhere else, and remember to come back. Most never do.

Why the #suggestions channel breaks down

A plain channel has no notion of a “request” as an object. There’s nothing to upvote, no status, no dedup, and no way to tell the room “we shipped this.” Three failure modes show up quickly:

• Duplicates pile up — the same idea gets posted five times because nobody scrolls back far enough to find the original.
• No signal — a reaction emoji is not a vote count you can sort by, so you can’t see what the community actually wants most.
• No follow-through — once you build something, there’s no trail back to the people who asked, so they never hear that it shipped.

Keep the whole loop inside Discord

The alternative is to treat each request as a first-class item that lives where your community already is. With Quillboard, members run a slash command to post an idea, everyone upvotes with a click, and the board sorts by real demand — all without leaving Discord. Admins triage from a web dashboard or from chat, move items across a public roadmap, and post a changelog entry when something ships.

Because the bot understands what a request is, it can also collapse near-duplicates for you. Quillboard’s free, local AI groups similar submissions so you review one item instead of five — and it runs on your own instance at no per-call cost, so there’s no AI bill to watch.

A setup that scales

• Add the bot and pick the channel where members post ideas — that’s the whole install.
• Members use /suggest to submit and upvote to signal; the top of the board is always what people want most.
• Admins drag items across roadmap columns (Planned → In progress → Done) that anyone can follow.
• Ship it, then post a changelog entry — the members who upvoted get told it landed, which pulls them back in.

The point isn’t “collect more feedback.” It’s to close the loop — request, vote, roadmap, ship, tell everyone — without a single hop out of chat.

What about tools like Canny?

Web-first feedback tools are capable, but they’re built around a separate site your members have to visit, and several bill per tracked user — so the price climbs exactly as engagement grows. If most of your community lives in Discord (or Telegram), a community-native board keeps participation where it already happens. We break the differences down in Quillboard vs Canny and the full comparison table.

Try it on your server

It’s free forever for one community — unlimited members, with a generous monthly idea limit. Add the bot, point it at a channel, and your next feature request becomes something you can actually act on. Add Quillboard to Discord, or see the pricing if you run several communities.