Anonymous Feedback Board for Slack and Teams

Most teams run on Slack or Microsoft Teams. Conversations happen fast, decisions move faster, and somewhere in the middle, honest feedback disappears. People stay quiet in public channels, skip the retrospective, and say nothing in the meeting because saying something feels risky. The feedback that would actually help never surfaces.

An anonymous feedback board fixes this. It gives every person in your organisation a low-pressure way to share what they really think, without attaching their name to it. And when paired with Slack or Microsoft Teams, the feedback lives where your team already works, rather than in a tool nobody opens.

This guide walks through exactly how to set one up, what to watch out for, and how to make sure the feedback you collect actually leads somewhere.

What Is an Anonymous Feedback Board?

An anonymous feedback board is a shared space where team members, clients, or users can submit ideas, concerns, and suggestions without identifying themselves. The board collects submissions in one place, usually with the option for others to upvote, comment, or react to each item.

The key distinction from a standard form or survey is visibility. A feedback board is persistent and ongoing, not a one-time event. Submissions stack up over time, the most important issues rise to the top through votes, and the team can respond or act publicly.

Anonymous boards work in many contexts:

Internal employee feedback at a growing company or agency
Client suggestions for a product or service team
Ideas and concerns at a school, non-profit, or community organisation
Ethics and compliance reporting where psychological safety is critical

The anonymity is what unlocks honesty. Research consistently shows that people share more candid feedback when they know their identity is protected.

Why Standard Slack and Teams Channels Fall Short

Slack and Microsoft Teams are communication tools, not feedback management tools. They are good at broadcasting information and running fast conversations, but they have real structural weaknesses when it comes to capturing and acting on feedback.

Here is what goes wrong:

Problem	Impact
Messages get buried fast	Feedback posted on Monday is invisible by Friday
Named submissions discourage honesty	People self-censor in public or semi-public channels
No voting or prioritisation	Every idea looks equally important or unimportant
No status tracking	Nobody knows if a suggestion was reviewed, accepted, or rejected
Threads scatter context	Related ideas and discussion end up in five different places

A Slack or Teams channel can work as a notification layer, sending alerts when new feedback arrives. But the board itself needs to live somewhere structured, with features built specifically for collecting, organising, and acting on input.

Step 1: Choose a Dedicated Feedback Board Tool

Before touching Slack or Teams, pick the right tool to host your feedback board. The platform needs to support anonymous submissions, voting, and status updates at minimum.

Key features to look for:

Anonymous submission mode so names are hidden from other users and optionally from admins
Upvoting so the team can signal what matters most without needing to post a comment
Status labels such as "Under review", "Planned", or "Completed" so submitters know their input was seen
A public or semi-public board URL that can be shared in any channel or embedded in a pinned message
Webhook or native integration with Slack or Microsoft Teams for notifications

FlagUp, a client feedback and feature voting platform, covers all of these. FlagUp lets teams create anonymous feedback boards with voting, status tracking, and a public roadmap view. Teams receive real-time notifications when new submissions arrive, which can be routed directly into a Slack channel or Teams channel via webhook. FlagUp also gives teams early visibility into client health signals, so problems surface before they quietly become lost relationships.

Other options include purpose-built tools like Canny, Nolt, or Frill, though pricing and anonymous submission support vary across those platforms.

Step 2: Configure Your Board for Anonymity

Once you have chosen a tool, configure it correctly before sharing the link. Anonymity settings are not always the default, and a misconfigured board will undermine trust from the start.

Work through this checklist:

Submission anonymity

Enable anonymous posting so the submitter's name is not shown on the public board
Decide whether admins can see submitter identity internally. Some organisations need this for compliance reasons. Others want full anonymity on both sides. Choose based on your context and communicate it clearly to your team.

Voting anonymity

Check whether votes are public or private. Public voting (where others see who voted) can deter people from voting on sensitive items. Private voting is usually better for internal feedback boards.

Moderation settings

Enable moderation if you want to review submissions before they appear publicly. This reduces noise and filters out anything inappropriate, but it adds a delay that can frustrate contributors if not managed quickly.
Set a moderation SLA. If you use moderation, commit to reviewing new submissions within 24 hours. Slow moderation kills participation.

Board access

Decide whether your board is fully public, link-only, or requires login. For internal employee feedback, a link-only board balances openness with some level of access control. For client feedback, a fully public board with a custom URL works well.

Step 3: Connect Your Board to Slack or Microsoft Teams

With the board live, the next step is making sure submissions surface in the right channels automatically. Nobody should have to remember to check the board manually.

Connecting to Slack

Most feedback tools support Slack via Zapier, webhook, or a native integration. Here is the fastest path:

In your feedback tool, navigate to integrations or notifications.
Select Slack and authenticate with your workspace.
Choose the channel where notifications should appear. A dedicated channel named something like #feedback-board or #team-suggestions keeps things tidy.
Set the trigger events: new submission, new vote milestone (e.g. 10 votes), status change.
Test the connection by submitting a test entry and confirming it appears in Slack.

Pin the feedback board URL in the channel description so any team member can find it without searching.

Connecting to Microsoft Teams

Microsoft Teams uses Power Automate or incoming webhooks for integrations with third-party tools.

In Teams, navigate to the channel where you want notifications.
Select "Connectors" or "Workflows" depending on your Teams version.
Add an Incoming Webhook connector and copy the webhook URL.
Paste the webhook URL into your feedback tool's integration settings.
Map the relevant events (new submission, vote threshold, status update) to the webhook.
Test by submitting a sample entry and checking the Teams channel.

For more advanced routing, Power Automate allows conditional logic. For example, you can route submissions tagged "urgent" to a specific Teams channel while all other items go to a general feedback channel.

Step 4: Introduce the Board to Your Team

A feedback board nobody knows about collects nothing. How you introduce the board determines whether people actually use it.

Write a short message to share in your main channel or company-wide communication. Cover three things:

What the board is for
How anonymity works (and whether admins can see identities)
What happens after someone submits feedback

A direct message reads better than a vague announcement. Something like:

"We've set up a shared feedback board where anyone can post suggestions, flag problems, or share ideas. Submissions are anonymous. The team reviews new items every week and we'll update the status on each one so you know it was seen."

Add the board link to your Slack channel description, your Teams channel tab, and any internal wiki or handbook your organisation maintains.

If your organisation uses Microsoft Teams as a central hub, add the feedback board as a tab within a relevant Team using the "Website" tab type. This keeps the board one click away without requiring anyone to leave Teams.

Step 5: Build a Consistent Review Process

Collecting feedback without reviewing it damages trust faster than collecting nothing. If people submit ideas and never see a response, they stop submitting.

Set a weekly or bi-weekly review cadence:

Review new submissions: read each item, assign a status, and add a short public response if warranted
Surface top-voted items: anything reaching a vote threshold (e.g. 5 or 10 votes) moves into your planning discussion
Update statuses: move accepted items to "Planned" or "In Progress" so submitters see progress
Close completed items: mark resolved items as "Done" with a brief note on what changed

Share a summary in your Slack or Teams channel after each review. Even a two-line update ("We reviewed 8 new submissions this week. Three are moving to planning.") shows the team the board is active and their input matters.

This loop, from submission to review to update to communication, is what separates a functional feedback system from an ignored form.

How FlagUp Helps Teams Run This End to End

FlagUp, a client feedback and feature voting platform, brings all of these steps into one dashboard. Teams create a board, enable anonymous submissions, share the link in Slack or Teams, and route new submissions directly into a notification channel via webhook.

FlagUp handles voting, status tracking, and a public roadmap in one place. When a submission gains traction, the team sees it rise to the top of the board. When a decision is made, the status update publishes instantly and submitters see the outcome.

For teams managing client feedback alongside internal input, FlagUp separates boards by project or client, giving each audience its own space while the team manages everything from a single dashboard. FlagUp gives teams early visibility into client health, so dissatisfaction surfaces in the feedback board before it becomes a cancelled contract.

FlagUp starts at $19 per month, which makes it accessible for small businesses, agencies, and non-profits running on tight budgets.

Frequently Asked Questions

Can I make a feedback board completely anonymous, even from admins?

Yes. Some tools support full anonymity where even the platform admin cannot trace a submission back to its author. FlagUp allows teams to configure anonymity levels during setup. Check your chosen tool's privacy documentation before committing, especially if your use case involves ethics or compliance reporting where full anonymity is a requirement.

Will Slack or Microsoft Teams show who submitted feedback?

No. The Slack or Teams notification shows the content of the submission, not the submitter's identity. The notification message typically reads something like "New anonymous submission: [content]." The identity, if stored at all, stays within the feedback tool's admin panel, not in the chat notification.

How do I prevent the board from filling up with irrelevant or low-quality submissions?

Enable moderation for new submissions, set clear guidelines in the board description about what belongs there, and use category tags to help submitters self-sort their input. A brief sentence at the top of the board ("Share product ideas, flag blockers, or suggest process improvements") reduces off-topic submissions significantly.

Can I use one board for both employees and clients?

It depends on your tool. Some platforms support multiple boards per account, which is the cleaner approach. Running separate boards for internal team feedback and external client feedback keeps the signal distinct and prevents one audience from seeing the other's submissions.

What if nobody uses the board after launch?

This usually means one of three things: the board URL was not shared prominently enough, people do not trust the anonymity settings, or they do not believe anything will happen with their input. Fix the first by pinning the link everywhere. Fix the second by publishing a clear privacy statement. Fix the third by reviewing and updating at least two or three submissions publicly within the first week.

Conclusion

Anonymous feedback boards solve a real problem. They create a low-pressure channel for the honest input that never makes it into a Slack thread or a meeting. When connected to Slack or Microsoft Teams, they fit into existing workflows without asking anyone to change their habits.

The setup is straightforward: choose a tool that supports anonymous submissions and voting, configure the anonymity settings correctly, connect it to your workspace via webhook, and commit to a review process that closes the loop every week.

The teams that get the most from a feedback board are not the ones with the most sophisticated setup. They are the ones that review submissions consistently, update statuses publicly, and communicate what changed because of the feedback they received.

FlagUp helps teams collect feedback, predict churn, and build products users actually want — starting at $19/mo. Try it free →

How to Set Up an Anonymous Feedback Board for Slack and Microsoft Teams