How to add a new product to your feedback routine

What does a new product need before its first feedback arrives?

A new product needs five things before it can receive useful feedback: a product entry with a clear name, allowed origins for the sites that will show the widget, an install method, a place for alerts, and a slot in your review routine. Missing any one of them leaves a gap. The most common gap is the review slot. A product that nobody is assigned to collects items that nobody reads.

This checklist follows that order. Work through it once per product, and keep it in the same place as your other routine notes so the next product is a repeat rather than a fresh start.

Step 1: Create the product with a clear name

Add the product in the dashboard and enter the name customers use. The name is set once from this value when the product is created, and it becomes the slug in the hosted feedback page address. The naming guide covers how to avoid slug clashes with products you already run.

Add the website address and choose an accent color. The website is for your reference, and the accent color styles the hosted feedback page, so pick a value that matches the product's own design.

Step 2: Set the allowed origins with a scheme

Allowed origins decide which sites can submit through the widget. List every site that will show it, one per line or separated by commas. Each entry needs its scheme, so write https://app.example.com and not app.example.com. Entries without a scheme are ignored when the list is saved, and a missing entry means a real user on that site gets a 403 error when they try to send feedback.

Include both the www and the bare domain if your site answers on both, because they are different origins. Add localhost with its port only for development, for example http://localhost:3000, and remove it before launch if the list should be strict.

There is one behavior to know. When the allowed origins list is empty, the origin check is skipped entirely. Add the origins before the widget goes live, not after.

Step 3: Install the widget or the hosted link

Pick one install method per surface. A marketing site or web app gets the widget with its data-key snippet. A place where you cannot run a script, such as an email or an app store listing, gets the hosted feedback page. A mobile app or server-side flow posts to the REST API with the same key.

For the widget, add the snippet once to the layout that wraps every page. The widget guide lists the options such as data-position, data-locale and data-trigger. For apps, the API reference shows the request body and the error codes to handle.

Step 4: Connect the notification webhook

Create a Slack or Discord incoming webhook for the channel that will read this product, then paste its URL into the product's notification webhook field. Choose a channel layout deliberately. The shared versus separate channels guide helps you decide whether the new product needs its own channel or can share one.

Step 5: Send one test item from the real site

Open the live site, use the widget to send a test item, and check three things in the dashboard. The item should appear in the new product's inbox, the alert should arrive in the channel you chose, and the page URL on the item should be the page you tested from. If the item is missing, the most likely cause is an origin that is not on the list.

Mark the test item closed with a note such as "test submission", so the first week's counts start clean.

Step 6: Add the product to the review routine

Give the product a fixed slot in your weekly review, the same length as the others or longer if it is new. Add it to the calendar with the product name in the title. Then add it to the daily count check, so its New count appears alongside the rest.

For the first two weeks, read every item in the slot, even the praise. You are learning what the product's customers write about, and that baseline makes later weeks easier to judge.

What should you check in the first week?

Keep a short list for the first seven days. Confirm that the item count matches what you expect, that origins are not rejecting real users, and that the alert channel is quiet enough to read. If the product has a hosted link in emails, send a test to yourself and open it from a mobile device to confirm the form loads and the language matches the browser.

Write down anything that surprised you. A product that generates more praise than bugs in week one tells you something about its early users, and that note is worth keeping next to the routine.

Adding the new product in Escuta Produto

The dashboard stays the same no matter how many products you add. The new product appears in the list, gets its own inbox with the same status and type filters, and its own CSV export that joins the weekly digest. Once the six steps above are done, the product is part of the routine and no longer a special case.

For the reasoning behind keeping every product in one dashboard, read one feedback inbox for many products. When you are deciding which product should get a widget first, which product gets feedback first gives a simple scoring approach you can run before you start this checklist.