How to collect feature requests from Discord without losing them

Discord is where your most engaged users talk, which makes it a great source of ideas and a bad place to keep them. Messages scroll away and threads auto-archive.

Why do feature requests get lost in Discord?

Chat is sorted by time, not topic. A request posted on Tuesday is buried by Thursday. It gets worse because:

• Requests land everywhere. Users mention ideas in #general, #help, voice-chat recaps and DMs, not just the channel you made for them.
• Reactions look like votes but don't add up. Ten reactions on one post and six on a reworded copy are never combined.
• Nobody owns it. "Good idea, we'll look at it" is the last anyone hears.

How should you set up Discord for feature requests?

1. Create one requests channel. A forum channel works well because each post becomes its own thread with a title, which makes requests searchable.
2. Pin a short prompt. Ask what they're trying to do, what they do today instead, and how often it comes up.
3. Add a few forum tags. Keep it to something like Request, Bug, Planned and Shipped. More tags than that go unused.
4. Decide who captures stray requests. Don't tell users to repost in the right channel. A moderator or teammate copies it over instead.
5. Pick a home outside Discord. A feedback board, an issue tracker or a spreadsheet. Discord is where requests arrive; the tracker is where they're counted and decided.

What should you record for each request?

Capture enough to act on it and to reply to the person months later.

Write the title as the outcome the user wants. Keep the quote exactly as written, because the original phrasing often reveals the real problem.

How do you triage Discord feedback each week?

Pick a fixed time and one owner, then work in order:

1. Sweep since the last session. Read the requests channel, then search other channels for phrases like "would be nice", "can you add", "wish" and "feature".
2. Sort each message. Request, bug, question or chatter. Skip chatter. Send bugs to your bug process (see how to triage community bug reports).
3. Search before you create. If the request already exists, add the user as a vote and attach their quote. If you have a pile of new ones, paste them into the duplicate request finder to group them first. More on this in how to handle duplicate feature requests.
4. Answer questions in place. "Is dark mode coming?" is a roadmap question, not a request. Reply in the thread with the current status.
5. Acknowledge every captured request. One line is enough.

An acknowledgment can be as short as this:

Logged this as "Export streak history as CSV." Two other people asked for it too. I'll post here when it moves.

What are the common mistakes?

• Counting reactions as demand. They're a quick pulse, but they don't merge across duplicate posts and they don't tell you who to notify later.
• Sending users to a form. Every extra step loses people. Capture it for them.
• Letting one loud member count as many. Five posts from @theo about the same thing is one request with one strong supporter.
• Paraphrasing instead of quoting. "Wants export" loses the screenshot detail, which hints that the real job is sharing progress.
• Never going back. The payoff of capturing requests is the reply when you ship. See how to close the feedback loop.

Doing this with Sikia

Sikia listens in the Discord channels you pick, sorts each message into request, bug, question or chatter, writes a clean title, and suggests merging duplicates as votes with the user's quote attached. Nothing goes public until a teammate approves it in the inbox. You can also capture feedback with the /sikia ask slash command or send any message in with the "Add to Sikia" message action, and Sikia replies in the original thread when a changelog entry ships the request.

FAQ

Should I use a forum channel or a text channel for feature requests?

A forum channel is usually better because each request gets its own titled, searchable thread. Capture ideas from normal chat channels yourself.

Are Discord reactions good enough for voting?

They work as a quick signal on a single post. They fall short once the same idea is posted twice, because the counts never combine and you can't easily notify everyone who reacted.

How often should I triage Discord feedback?

Weekly is enough for most small communities. If the server is busy, skim daily and do the full pass weekly.

Do I need a bot to collect feature requests from Discord?

No. A moderator and a spreadsheet work at low volume. A bot pays off when requests arrive faster than one person can sweep them.