How to organize Slack channels for product feedback

One webhook per product is the building block

Each Escuta Produto product has one notification webhook, which is a Slack or Discord incoming webhook URL. Every new item posts an alert with its type, the product name, rating stars, the sender, a 500-character excerpt and a link to the dashboard. The webhook decides where alerts go, so a channel plan is really a plan for which webhook goes where.

Because the webhook is set per product, you can start with one channel and split later by changing a single product's webhook. The other products keep sending alerts to their channel untouched.

Option one: a channel per product

A channel per product works best when each product has an owner who watches it. The people in a product channel care about that app only, so the alerts carry clear meaning without any extra reading. Name the channel after the product, for example "feedback-scheduler", so nobody has to ask what it is for.

The downside is channel sprawl. Five products mean five channels to join, mute and archive. Keep the list short. If a product has no owner who would read its channel, do not create one for it. Send its alerts to the shared channel instead.

Option two: one shared channel with the product in every alert

A shared channel works when one person reads everything. Each alert names its product, so you can scan one feed and know where each item belongs. That product name in every message is what makes the shared option workable. Without it, a shared channel becomes a mess of unlabeled messages.

Use this option for a solo founder or a small studio where a single person triages. It keeps the number of channels low and gives you one place to check from your phone. The trade-off is that a busy product can bury a quiet one in the feed, so pair the shared channel with the weekly review described in the feedback routine for five products.

Discord works the same way. An incoming webhook on a Discord channel accepts the same alerts, so the two options apply to a Discord server as well as to Slack.

What you cannot split inside one product

Each product has one webhook, so every type goes to the same place. Bugs, ideas, praise and other messages all arrive in the same channel. You cannot send only bugs to a channel that pings you, and you cannot route praise to a separate channel for marketing. If you need that separation, read the channel for bugs during the day and treat everything else as your weekly list.

Be honest about spam too. The form has a hidden honeypot field and rate limits, and those catch most bots. Some spam still gets through, so expect a few low-value alerts and close them with a short note.

Control the noise without losing alerts

Slack and Discord both let members choose how they are notified for each channel. Use those settings rather than hiding the channel. Mute the shared channel during deep work, and set notifications so that only mentions of you interrupt you. The alerts stay in the channel, so nothing is lost. You can read the feed later in one sitting.

Keep the member list small too. A channel with five people who never read it is worse than a channel with one person who reads it every day. Add only the people who will act on an alert, and remove anyone who has left the team.

Agree on a rule for who acts on which alert. For example, a bug alert goes to the person who owns that product, and an idea alert waits for the weekly review. Writing the rule down prevents two people from fixing the same bug, or both assuming the other one will answer.

Keep the weekly review out of the channel

The alert channel is for awareness. The decisions happen during your weekly review in the dashboard, where you can change status, write internal notes and filter by type. Do not try to triage inside Slack or Discord, because a chat thread has no status field and no place for your reasoning.

When you change a webhook, update it in the product's settings. The old channel stops getting that product's alerts, so tell the people in it before you switch. A short message in the old channel that points to the new one saves a week of missed alerts.

Which option fits which team?

Use a channel per product when each product has a different owner, for example a designer who handles one app and a developer who handles another. Use one shared channel when you are the only person reading. A mixed setup is fine too: a shared channel for the small products and a dedicated channel for the one product that gets the most traffic.

Check each channel every few months. When a channel has been silent for a month, first confirm that its product still gets feedback at all. A quiet channel can mean the webhook broke rather than that customers stopped writing, so send one test message from that product's widget and watch for the alert.

How to set up Slack channels for feedback with Escuta Produto

Create the incoming webhook in Slack or Discord for each channel, then paste it into that product's notification settings. The notifications guide lists the steps for each platform. Send one test message from the product's widget and check that the alert names the right product. Then decide whether each product gets its own channel or sits in the shared feed.

For the reasoning behind one dashboard above many channels, read one feedback inbox for many products.