# Shared or separate Slack channels for product feedback? > Use one shared Slack channel when a small team sees few items across all products. Use a channel per product when owners read different products or one product is busy. Escuta Produto sends alerts through one webhook per product, so you can mix both layouts, and every alert names its product. Source: https://escutaproduto.com/resources/shared-vs-separate-slack-channels Last updated: 2026-10-11 ## What is the real choice between shared and separate channels? The choice is about who reads the alerts and how many arrive. A shared channel puts every product's feedback in one place, so everyone sees everything. Separate channels split the alerts by product, so each owner reads only the product they run. Neither layout is wrong. The right one depends on team size and on how many items each product sends. The alert itself is the same in both layouts. Each item posts its type, product name, rating stars, sender, a 500-character excerpt and a dashboard link. The product name is part of the message, so a shared channel stays readable as long as your team reads the line. ## How does Escuta Produto send alerts to Slack? Each product has one notification webhook field. You paste a Slack incoming webhook URL there, and every new item for that product posts to the channel that webhook points to. Discord works the same way with a Discord webhook. Two consequences follow from that. First, a Slack incoming webhook is tied to one channel, so you create one webhook for each channel you want. Second, several products can point at the same webhook URL. That gives you the shared layout with no extra setup. Alerts only go to the one place each product points, and the product name in the message tells you which product sent it. The alerts do not filter by type or status. A channel that receives a product gets bug, idea, praise and other items alike. Plan for that before you choose a layout. ## When does one shared channel work? A shared channel fits when a small group reads everything and the volume is low. For example, suppose three products together send about 6 items in a typical week, and two people own all of them. A single shared channel means nobody misses an alert, nobody has to join three channels, and the team already watches the same place for other work. It stops working when the alerts become noise. If a busy product fills the channel, people mute it, and the quiet products get muted along with it. Then you lose the alerts you cared about most. ## When do separate channels earn their place? Separate channels are worth the setup when owners differ or one product is busy. Each owner watches the channel for their product and can mute or pin it without affecting anyone else. Slack's own per-channel notification settings then work for you rather than against you. For example, suppose product A sends 20 items a week, product B sends 4 and product C sends 2. Product A deserves its own channel because its owner needs to see its items quickly. Products B and C can share a channel without anyone losing track of them. ## What is a hybrid setup, and how do you build one? A hybrid gives busy products their own channel and puts quiet products into one shared channel. It is the layout most teams end up using once they have run both for a month. Build it in four steps: 1. List your products and count how many items each sent last month. 2. Give every product above the threshold you choose its own channel, for example a channel named after the product. 3. Create one shared channel for the rest and point their webhooks there. 4. Create a Slack incoming webhook for each channel, then paste each URL into the matching product's notification webhook field. Review the split every quarter. A product that grows moves to its own channel, and a product that goes quiet can join the shared one. Changing a webhook is a single field edit, so the change takes a minute. Before you move a product, tell the people who read the old channel. Otherwise the alerts simply stop, and nobody notices until a customer asks why nobody replied. A short message in both channels, naming the product and the new channel, prevents that gap. ## What do you lose with a shared layout? You lose the ability to separate concerns by product in Slack. Everyone sees every product's alerts, which is the point for a small team and a problem for a large one. You also lose per-product muting, so a person who only cares about one product cannot silence the others. You can recover some of that without changing channels. Filter the inbox by product and status to read the work, and treat the Slack channel as a signal that something arrived, not as the place where triage happens. The alert tells you that a bug came in. The decision belongs in your review slot. ## Setting up the webhooks in Escuta Produto Create the Slack or Discord incoming webhooks first, one for each channel in your layout. Then open each product's Settings and install page in Escuta Produto and paste the matching URL into the notification webhook field. Save, then send one test item from the product's real site or from the hosted feedback page, and confirm the alert lands in the right channel. The [notifications guide](/docs/notifications) lists the exact message format and the payload each service reads. For a longer comparison of channel designs, read [how to organize Slack channels for product feedback](/resources/slack-channels-for-feedback). If you are deciding how many products to add to one dashboard first, [one feedback inbox for many products](/resources/one-inbox-many-products) explains why the inbox stays the same no matter how the alerts are routed. ## Frequently asked questions ### Should every product have its own Slack channel? Not always. Give a product its own channel when its owner reads it closely or when it sends many items. Small or quiet products can share one channel, and every alert names its product, so the shared channel stays readable. ### Can one Slack webhook serve several products? Yes. Paste the same Slack incoming webhook URL into each product's notification webhook field, and each product's alerts will post to that channel. The product name in each message shows where an item came from. ### Can I send only bug alerts to Slack? Not directly. Escuta Produto posts every new item for a product, whatever its type, and the webhook setting has no type filter. Use the inbox filters for triage, and keep the channel as a signal that something new arrived.