All posts

How to Collect Feature Requests Without Drowning in Slack

Comparing Feedbakery and Canny on pricing, features, and setup. See why teams switch to flat $20/mo pricing from Canny's tracked-user model.

Feedbakery Team·
How to Collect Feature Requests Without Drowning in Slack

How to Collect Feature Requests Without Drowning in Slack

Feature requests are scattered across your Slack, email, support tickets, and that Google Sheet someone started three months ago. You know the problem. You're here because you want the fix.


Why Slack and Email Fail at This

Quick diagnosis. If any of these sound familiar, your current system is already broken:

  • A customer suggested something great in a DM last month. You can't find it.
  • Three different users requested the same feature in three different channels. You don't know that.
  • You're building features based on whoever talked to you most recently, not actual demand.

Slack is built for conversations, not for collecting and prioritizing structured input. Email creates silos — one person sees each request, there's no voting, no way to gauge demand. Spreadsheets work for about two weeks before they become a graveyard nobody updates.

You need a tool designed for this specific job.

What a Good Feedback System Does

Four things.

One place for everything. Every feature request goes to one board. When users see existing requests before submitting, they vote instead of creating duplicates. You go from 15 versions of "please add dark mode" across 4 channels to one post with 15 votes.

Voting reveals real demand. A request with 40 upvotes is a different signal than one with 2. You stop building for whoever emails you most and start building what your user base actually wants.

Statuses keep users informed. Open, Under Review, Planned, In Progress, Completed — these labels answer "is anyone listening?" without requiring individual responses. Your support team stops fielding "any update?" messages.

The loop closes automatically. When you ship a requested feature, the people who voted for it get notified. They see their input leading to real changes and keep contributing.

How to Set This Up

Pick a dedicated tool

Don't repurpose Notion, Trello, or GitHub Issues — they're missing the user-facing piece. Your customers won't create a Trello account to suggest a feature.

What matters: an embeddable widget (feedback inside your product, not a separate URL), passwordless auth (every extra step costs you submissions), voting, status tracking, and team notifications via Slack/Discord/Telegram.

Feedbakery does all of the above. Free plan to start, $20/month flat when you need more — no per-seat or per-user scaling.

Migrate what you already have

Go through your Slack channels, email threads, and support tickets. Pull out the real requests and add them to your new board. Switching from another tool like Canny? CSV import saves you from re-entering everything manually.

Starting with existing requests gives your board immediate content instead of launching empty — and shows users you haven't forgotten what they've already told you.

Redirect the flow

When someone messages a feature idea in Slack, respond with: "Good idea — can you add it to our feedback board? Other users can vote on it and you'll get notified when we ship it."

Explain the benefit to them, not just paste a link. Within 2–3 weeks, the new behavior sticks.

Update statuses immediately

This is where most teams fail. A feedback board with no status updates is worse than no board — it tells users you collected their input and ignored it. Even a quick "Under Review" takes seconds and creates the trust that keeps users engaged.

Mistakes That Kill Adoption

Launching empty. Seed the board with 10–15 existing requests before inviting users.

Hiding the board. Embed it in your app where users naturally spend time. A feedback tab in your dashboard gets 10x the submissions of a standalone page nobody bookmarks.

Ignoring votes. If you build a 3-vote feature over a 50-vote one, explain why publicly. Users understand business priorities — they don't understand silence.

What Changes After You Do This

A month in: feature requests stop getting lost, prioritization becomes data-informed, users feel heard, and your team stops relaying feedback through Slack. The hard part is the first two weeks. After that, it runs itself.


Ready to give your feature requests a proper home? Feedbakery is free to start — create a board, embed it in your app, and start collecting feedback that doesn't get lost.

Ready to try Feedbakery?

Free plan available. Pro at $20/mo flat. No tracked-user fees.

Start free — no card needed

We use a cookie to understand how you use Feedbakery and improve the experience.