How to send user feedback to Slack
The gap between feedback arriving and feedback getting acted on is where most of it disappears.
A user submits a bug report at 2pm. It lands in a feedback dashboard. Nobody checks the dashboard until Friday. By that time, the user has moved on, the context is cold, and what could have been a five-minute fix becomes a three-week ticket.
Routing feedback to Slack doesn't solve every part of this problem, but it solves the most important part: visibility. When your team sees feedback in the channel where they already work, the probability that someone acts on it in the same day is dramatically higher than if it requires opening a separate tool.
This guide covers how the PushFeedback Slack integration works, how to set it up, and how to use it effectively without generating noise that your team starts ignoring.
Why routing feedback to Slack matters
Speed of response is one dimension. Team visibility is the other.
When a feedback submission lands in a Slack channel, every member of that channel sees it. The frontend developer who knows exactly which component owns that button. The documentation writer who can update the page the user found confusing. The support team member who can follow up if the issue is urgent. Nobody needs to be explicitly assigned: the right person sees the report and can act on it.
This is especially valuable for small teams where the person who needs to see a bug report and the person who checks the feedback dashboard are often different people. Routing to Slack removes the dependency on one person to triage and forward.
For documentation teams in particular, real-time feedback notifications let you catch problems with new content immediately. If you publish an update to an API reference page and three users leave negative feedback in the next hour, you'll know before the end of the day rather than a week later when you get around to checking the dashboard.
How the integration works
PushFeedback sends Slack notifications via incoming webhooks, Slack's standard mechanism for posting messages from external services to a channel.
When a user submits feedback on any page where the PushFeedback widget is installed, the integration sends a notification to the configured Slack channel. The notification includes:
- The user's message or rating
- The URL of the page the feedback was submitted from
- The screenshot if the user captured one
- Submission timestamp
The setup requires creating an incoming webhook in Slack and configuring it in your PushFeedback project. No additional software, no paid Slack tier required.
Prerequisites
Before you start, you need:
- A PushFeedback account with at least one project. If you haven't set one up yet, create an account at app.pushfeedback.com.
- A Slack workspace where you have permission to add apps and create incoming webhooks.
- The PushFeedback widget installed on your site.
Step 1: Create an incoming webhook in Slack
Slack incoming webhooks are created per channel. You'll get a unique URL for the channel you choose.
- Go to api.slack.com/apps and click Create New App.
- Choose From scratch, name the app (e.g., "PushFeedback"), and select your workspace.
- In the app settings, navigate to Incoming Webhooks and toggle it on.
- Click Add New Webhook to Workspace.
- Select the channel where you want feedback notifications to appear and click Allow.
- Copy the webhook URL. It will look like:
https://hooks.slack.com/services/T.../B.../...
Keep this URL handy. You'll use it in the next step.
Which channel to choose: A dedicated channel like #docs-feedback or #product-feedback works well. Mixing feedback notifications into a general #dev channel tends to create noise that eventually gets muted. A dedicated channel lets team members choose their notification settings: some may want every notification, others may prefer to check it periodically.
Step 2: Configure the integration in PushFeedback
- Open app.pushfeedback.com and go to Projects.
- Select the project you want to connect.
- Click Settings, then under Integrations, select Slack.
- Paste the incoming webhook URL you copied from Slack.
- Click Save.
To verify the integration is working, go to a page where your widget is installed and submit a test feedback entry. The notification should appear in your Slack channel within seconds.
For the full reference guide, see Integrations > Slack.
Step 3: Triage notifications effectively
Not all feedback requires the same response, and treating every Slack notification as an urgent task is the fastest way to burn out your team on the integration.
A simple triage approach that works:
Act immediately. Feedback that reports broken functionality, an error message the user couldn't recover from, or a blank page. These affect users right now. Route to the relevant developer in the Slack thread.
Tag for the docs backlog. Feedback about documentation gaps, outdated content, or unclear explanations. These are real and worth fixing, but not urgent. React with an emoji to acknowledge, add to the documentation backlog, and address in the next docs sprint.
Note and close. Positive feedback or feedback that doesn't require action. A thumbs-up emoji in the thread is enough. The analytics dashboard captures all ratings regardless.
Create a Jira issue. For confirmed bugs that need engineering attention, the Jira integration can handle this automatically. Set it up in parallel with Slack: bug reports go to both a Slack notification (for visibility) and a Jira issue (for tracking and assignment).
Tips for managing notification volume
The most common failure mode for Slack feedback integrations is too much noise. Teams initially want to see everything, then start ignoring the channel once the volume is high, then disconnect the integration entirely. Here's how to avoid that.
Use per-product channels for multi-product teams. If you're collecting feedback across multiple projects, route each project to its own Slack channel. A single channel receiving feedback from five different products is hard to triage.
Set channel notification preferences. Most team members don't need an audible alert for every feedback notification. Configure the channel to use the default notification setting and let individuals adjust. The people who need to monitor closely can set every message to notify; others can check periodically.
Create a weekly digest habit. For feedback that's interesting but not urgent, designate one person on the team to do a five-minute Slack channel review on Monday morning. This catches patterns that aren't visible in individual notifications but show up when you scan the previous week in sequence.
Don't use Slack as a permanent record. Slack notifications give you visibility. The analytics dashboard and feedback management tool give you the persistent record, filtering, and trend data. Use Slack for real-time awareness and the dashboard for analysis.
Connecting to the broader feedback workflow
Slack integration is one layer of the feedback loop. The channel handles real-time visibility. The dashboard handles trend analysis and reporting.
For documentation teams building a full feedback workflow — from collection through analysis to a systematic improvement process — the New in PushFeedback: analytics dashboard and integrations post covers how the dashboard and integrations work together.
For teams that receive high feedback volume and need to surface patterns across dozens of submissions rather than reading them one by one, AI Reports processes the full dataset and identifies the top themes automatically.
PushFeedback collects user feedback with screenshot capture on any web app or documentation site. The Slack integration routes every submission to the channel where your team already works. Get started with any major documentation platform or web framework.