How to Collect Customer Feedback in Slack
Collect Slack customer feedback without losing the problem, source, or owner. Follow a review workflow for feature requests, support issues, and public-safe imports.
By Feedbackly · Updated
Product walkthrough
See how customer requests become visible for review and product communication.
Watch the product walkthroughExplore the feedback board workflow
Practical context for How to Collect Customer Feedback in Slack
Collect customer feedback in Slack by recording the task behind the comment, preserving its source, and assigning a review owner. A channel is convenient for conversation; a maintained request record makes the evidence easier to find during product planning.
Start with one channel or one recurring source of feedback. Define what belongs in the queue and what should go directly to support or incident response. The aim is to retain useful customer evidence without treating every message as a feature request or a commitment to build something.
Capture the need before rewriting the request
When someone forwards a customer comment, ask what the customer tried to accomplish, what prevented it, and what workaround they use. Keep the wording of the observation separate from the proposed feature. A request for a Slack notification might concern missed handoffs rather than the lack of a particular integration.
In a fictional reporting product, 'Please add scheduled emails' could mean an administrator must send the same report every Monday. Record the recurring task, recipient, timing, and manual effort. A scheduling feature is one possible response; it is not yet the validated solution.
- +Task: the outcome the customer needs and when they need it.
- +Obstacle: what actually happened and the current workaround.
- +Evidence: source reference, relevant role, and unresolved questions.
Review messages before they become public requests
Read the surrounding conversation where needed and decide whether the item is a product suggestion, an account-specific support problem, or a reproducible defect. Combine evidence about the same underlying need without erasing distinct customer contexts. Keep customer identifiers and sensitive source material in an appropriate internal record.
Feedbackly can preview up to 100 recent messages from a selected Slack channel during board creation. Edit the parsed titles and descriptions and select what to publish. Future source imports wait in a private review queue. The resulting board is public, even if the original channel was private; source access does not determine publication access.
- +Check that an imported title still describes the customer's problem.
- +Remove material that is unsuitable for the public board.
- +Treat a burst of messages from one account separately from independent reports.
Give each recurring need a decision and follow-up
At a regular review, compare the evidence with your product objective and available capacity. Choose a next action: clarify, investigate, prioritize, or defer. Name the owner and explain what would change a deferred decision. Votes can add a signal of interest, but they do not measure the consequence or delivery cost on their own.
Reply to the original conversation with a useful summary or a public request link when appropriate. After release, ask whether the original task is easier to complete. A status update closes the communication gap; checking the task closes the learning gap. Keep both in your review process.
- +Keep a reason with the decision, including decisions to make no change.
- +Avoid promising a date before scope and capacity support it.
- +Revisit recurring problems when new evidence arrives.
Keep exploring this topic
These next reads help you move from the concept on this page to a framework, tool, template, or deeper comparison you can apply right away.
Questions teams usually ask
Should every Slack message become a request?
No. Conversation includes questions, support needs, and repeated remarks. Review the message in context and publish only a useful, public-safe product summary.
How do we keep track without a public board?
An internal tracker or Slack list can hold the task, evidence reference, owner, and next action. Slack lists are available on paid plans. Choose the destination around who needs access and what your team maintains.
Are imported Slack requests already voted on?
No. Imported Feedbackly requests begin under review with zero votes. Slack reactions and historical conversation activity are not carried over as board votes.
Give reviewed customer requests a shared home
Preview Slack feedback in Feedbackly, choose what becomes public, and use requests, comments, votes, and statuses to keep the customer conversation connected to decisions.