One feedback inbox for many products

Why one tool per product fragments your attention

When every app gets its own feedback tool, the routine breaks down. You log in to five dashboards, each with its own settings, notification rules and export format. A customer who writes about two of your products gets replies from two systems that know nothing about each other. Most small teams end up checking the tool they open most often, which is rarely the one with the most urgent bugs.

The real cost is not the subscription line. It is the minutes spent deciding where to look, and the items that never get read because they sit in a dashboard you forgot existed.

How per-product keys keep feedback apart

Escuta Produto treats each product as its own unit. Every product has its own widget key (the data-key value in the script tag), its own hosted page at /f/ followed by the product slug, its own accent color and its own notification webhook. Feedback from the widget or the REST API is filed under the product whose key sent it. A bug report from your scheduling app never lands in the invoicing app's inbox.

Inside the dashboard, each product has an inbox with filters for status and type, plus text search. Those filters apply to the product you are reading. That scoping is the point. You read one product at a time, with its own context, and then move on.

Set up each product the same way

Use the same steps for every product so nothing gets skipped:

1. Add the product with its name, website and accent color. Use the name your customers use, not an internal codename, because it appears in every alert.
2. Add its allowed origins. Only these sites can submit through the widget, so list every domain where the widget will run.
3. Copy the product's key into the widget snippet on that product's site, and only there.
4. Set the notification webhook to the Slack or Discord channel you want for that product.
5. Send one test message from each site and confirm it appears under the right product.

The last step is the one people skip. A key pasted into the wrong app sends feedback to the wrong inbox, and you may not notice for weeks.

Finish each product's setup in one sitting instead of across several weeks. A half-configured product, with a key on the site but no origins or webhook yet, is the state where feedback goes missing and nobody notices. Treat the five steps as a checklist you complete before you call the product live.

Keep the statuses and types the same everywhere

Every product uses the same five statuses (New, Planned, In progress, Done and Closed) and the same four types (bug, idea, praise and other). Because those lists are fixed, the discipline lives in what each status means. Agree on that before you start. If one product treats Planned as "maybe someday" and another treats it as a commitment, your counts stop meaning the same thing.

Write the rule down once and keep it near your routine. Two sentences are enough: "Planned means I will build it this quarter. Closed means I read it and decided no."

What stays separate and what you share

Setting	Per product	Shared across your work
Widget key	Yes	No
Allowed origins	Yes	No
Hosted page and accent color	Yes	No
Notification webhook	Yes	No
Statuses and types	No, same for all	Yes
Your review routine	You choose	Yes

What you give up by reading everything in one place

One place has real advantages. You build one habit, you export the same way every time, and you learn the status rules once. You also see the total volume of feedback, which shows where your attention actually goes.

The trade-offs are real too:

• A loud product can crowd out a quiet one. If you only open the inbox with the most new items, the quiet product's bug waits. Give every product a short slot each week.
• The same person can write to two products. Pass a stable id and a segment to identify. Those values are stored as metadata, so you can match one customer across products in your CSV export.
• Filters are not tags. Escuta Produto has no tag system, so a problem that crosses products, such as a shared login bug, lives in your internal notes or your spreadsheet.

A daily check that scales

Ten minutes a day keeps one inbox honest. Open the dashboard, look at the New count for each product, and read only the new bugs. Leave ideas and praise for the weekly pass. If a product's 30-day chart jumps after a release, open that product first.

Keep the daily check on the one dashboard page you already open each morning, not on a separate bookmark for each product. One page with the counts beats five tabs that you visit once a month and forget.

This works for three to ten products. The longer weekly version lives in the feedback routine for five products.

How to set up one inbox for your products with Escuta Produto

Start with the widget docs. For each product, create it in the dashboard, add its allowed origins, then paste its key into that product's site only. Route alerts with the notifications guide, one webhook per product, so a bug in one app pings the channel for that app. When you are ready to decide where your time goes, read how to choose which product to work on.