Why teams use it
Start where your team already talks
Slack is usually where raw feature demand first shows up. Feedbackly helps you capture that signal without making a product manager manually rewrite threads into a board.
Integration
Slack feedback integration
Connect Slack to Feedbackly, choose a channel, and turn recent customer feedback messages into starter requests ready for your review before publication.
Channel import
Slack
Connect Slack and turn channel chatter into product signal
Pick a Slack channel during board creation and Feedbackly converts recent messages into starter requests, so your team begins with real demand instead of a blank board.
What it gives you
A cleaner way to move from raw feedback to a usable board
1
Use the official Slack OAuth flow to connect a workspace
2
Choose a public or private channel after connecting
3
Review recent messages before publishing requests
4
Keep product, support, and customer-success feedback in one intake flow
Create a board with real context
Preview up to 100 recent messages, remove private details, and choose which requests to publish. New requests start under review with zero votes. Future imports wait in a private queue.
Better than leaving requests in chat history
Votes, statuses, and visibility happen in the board, while Slack stays the place where feedback naturally arrives. That split keeps intake lightweight and prioritization structured.
Set up a Slack feedback workflow
- Connect your Slack workspace from Feedbackly using Slack’s authorization flow. Workspace approval requirements still apply.
- During board creation, choose Slack and a channel you can access. Preview up to 100 recent messages.
- Edit titles and descriptions, remove private details, and select the requests you want to publish. Imported requests start under review with zero votes.
- Review future imports in the private queue before publication. Customers can then vote, comment, and follow a request’s status on the public board.
Channel access and importing are separate from publication. A private Slack source does not make the resulting Feedbackly board private; the board is publicly accessible. Review every selected request for its intended audience.
Use the Slack customer feedback guide to capture the task and evidence before importing, and the Slack bug reporting workflow when a message describes a product failure.
Capture enough detail when a bug arrives in Slack
A message such as “the export is broken” needs clarification before it becomes a useful record. Ask for the failed action, environment, steps, expected result, actual result, and impact. Use the free bug report template and Slack example to structure the report.
For a fictional export issue, a useful summary is “CSV export returns only a header when a date filter is active.” Keep the sanitized problem summary on a feedback board when it is relevant to other customers. Keep logs, credentials, personal information, and incident investigation in an appropriate internal issue system.
Understand what the import carries
The integration turns message text into requests for review. It does not reconstruct a full Slack conversation archive, historical votes, customer identities, attachments, or roadmap statuses. Keep source evidence where the reviewer can access it and add the context needed to understand the task.
If a channel is missing, check workspace access and whether the app can access that channel. If imports stop, check the connection and import settings in your dashboard, reconnect when needed, and confirm active account access. See CSV import for feedback already stored in a spreadsheet.
Next step
Start with SlackUse Slack as the starting point for a live board
Start with existing feedback instead of an empty setup flow, then let customers vote, let your team score requests, and keep status updates visible in one place.