How to send user feedback to Slack

Sending documentation feedback to Slack can help the right team see new reports without checking another dashboard throughout the day.

The important choice is the channel. Feedback about an unclear guide or API example is more useful in a documentation or developer-experience channel than in a general engineering channel where nobody owns the review.

PushFeedback sends feedback notifications to Slack through an incoming webhook.

Choose the Slack channel

Start with the team that will actually review the feedback.

Depending on your documentation workflow, that might be:

• a documentation channel
• a DevRel or developer-experience channel
• a support-content channel
• a project-specific documentation channel

Avoid routing every report into a broad company or engineering channel simply because it has the most people.

The people receiving the notification should know what to do when a report needs investigation.

Connect PushFeedback to Slack

The Slack integration is available on PushFeedback Professional and Unlimited plans.

You need:

• a PushFeedback project
• a Slack workspace
• an incoming webhook for the Slack channel you want to use

To connect them:

1. Create an incoming webhook for the intended Slack channel.
2. In PushFeedback, open the project that receives your documentation feedback.
3. Go to Settings → Integrations → Slack.
4. Add the Slack incoming webhook URL.
5. Save the integration.

See the Slack integration guide for the current setup steps.

Keep the webhook URL private rather than copying it into shared documentation or tickets.

Submit a test report

After saving the integration, submit feedback from a page where the PushFeedback widget is installed.

Use a simple test report, for example:

Page: /api/authentication
 
Feedback:
I cannot find where the required scope is configured.

Then check the Slack channel connected to the webhook.

Confirm that the notification arrives in the channel your team expects to monitor.

If it does not arrive, check the webhook configuration and PushFeedback Slack settings before enabling the workflow more broadly.

Use Slack for notification and discussion

Slack works well for making new feedback visible quickly.

A report can trigger a short discussion such as:

• Is the page actually unclear?
• Does the documentation match current product behavior?
• Has someone reported the same problem before?
• Does this belong to docs, product, or support?
• Does someone need to create a tracked work item?

Not every report needs to become a long Slack thread.

Keep feedback available in PushFeedback for review, filtering, archiving, and export. If a report turns into work that needs to be tracked through completion, move that work into the system your team normally uses for tasks or issues.

PushFeedback feedback management covers the workflow for reviewing collected reports.

If your team uses Jira for actionable documentation work, see how to turn documentation feedback into Jira issues.

Send useful feedback to the right channel

Slack notifications are most useful when the original feedback contains enough context for the receiving team to understand the problem.

A report such as:

This page is bad.

may create a Slack notification without giving the team much to investigate.

A report such as:

I cannot find where the required OAuth scope is configured.

gives the team a clearer starting point, especially when it remains connected to the documentation page where it was submitted.

For the broader feedback workflow, see how to collect and use documentation feedback.

Frequently asked questions

Is Slack available on every PushFeedback plan?

No. Slack integration is available on Professional and Unlimited plans. See PushFeedback pricing for current plan details.

How does PushFeedback send feedback to Slack?

PushFeedback uses a Slack incoming webhook associated with the channel where you want notifications to appear.

How should we test the Slack integration?

After saving the webhook in PushFeedback, submit feedback from a page where the widget is installed and confirm that the notification reaches the intended Slack channel.

Should every feedback report go to Slack?

Not necessarily. Use Slack when immediate visibility or team discussion helps. PushFeedback can remain the feedback record, while actionable work can move into Jira or another task-management workflow when needed.

What should we do if feedback does not reach Slack?

Check that the incoming webhook is valid and connected to the intended channel, then review the Slack integration settings in PushFeedback. See the Slack integration guide for the current setup.

Send your first feedback notification to Slack

Create a PushFeedback project, connect the project to the Slack channel your team actually reviews, and submit one test report from your documentation site.

Once the notification arrives where you expect it, use Slack for visibility and discussion while keeping the underlying feedback available in PushFeedback.