# How agencies can collect feedback for client products

> Give each client their own product with a separate key, allowed origins, hosted page and webhook. Share weekly CSV summaries instead of logins, because Escuta Produto has no client accounts, team roles or client portal.

Source: https://escutaproduto.com/resources/agency-client-feedback
Last updated: 2026-10-09

## Use one product per client site

Give each client their own product in Escuta Produto, with its own widget key, allowed origins, hosted page, accent color and notification webhook. A client who runs two sites gets two products, because each site may have different users and different bugs. Keep the product name plain and recognizable, such as the client's brand and the app name.

One product per client keeps the separation clean. A bug from one client's app cannot land in another client's inbox, and you never have to explain which feedback belongs to whom. The hosted feedback page at /f/ followed by the product slug can also be shared with the client directly.

## Set allowed origins so each widget works only on its site

Each product has a list of allowed origins, and only those sites can submit through the widget. For a client's product, list the client's domains and any staging domain you use for testing. If a client launches a new domain, add it before you ship the snippet there. Until you do, submissions from that domain will be refused, and the API answers 403 for origins that are not allowed.

The key itself is safe to place in a client's HTML. A public key can only create feedback and can never read it, so the snippet you hand over does not expose their inbox.

## What clients can and cannot see

Escuta Produto has no client accounts, team roles or client portal. A client cannot log in to see their feedback, and you cannot give them a limited view of the dashboard. Plan around that before you promise anything. Escuta Produto also does not offer white-labeling, so do not promise a version of the tool with a client's name on it.

What you can do is share the hosted feedback page link, which uses the product's accent color, and send exports and summaries yourself. Those two pieces give the client a visible way to send feedback and a clear view of what came in.

## Send a weekly summary built from the export

Once a week, open each client's product and export its feedback as CSV. The file is UTF-8 and opens in Excel and Google Sheets, so you can count bugs, ideas and praise without cleaning the text first.

Then write a short summary in your own email: the number of new bugs, the top two ideas with the number of distinct people who asked, the average rating if it has enough ratings behind it, and the one item you plan to fix next. Keep it to a few lines. Use the same headings every week, so the client learns where to look and notices quickly when something changes. A short summary that arrives every week builds more trust than a long report that arrives once a quarter.

## Keep client data apart

A CSV holds the names and email addresses people typed into the form. Treat it as personal data. Send each export only to the client who owns that product, store it in a folder for that client, and check your contract for how long you keep it and where it can go. Do not paste one client's feedback into another client's summary, even as an anonymous example.

Keep internal notes internal too. The notes on each item are for your own reasoning, so do not copy them into a client summary without rewriting them.

## What do you do when a client leaves?

Export the product's CSV first and hand it over with a final summary, since that is the record the client will most likely want. Then delete the product from its settings and remove the snippet from the client's site, so the widget stops loading on their pages. Keep your own copy only as long as your contract allows.

## Onboard a client without a long handover

Give the client a short onboarding note with three items: where to paste the snippet, which domains are allowed, and who to contact when a message looks wrong. If the client's developer is busy, paste the snippet yourself, but tell them first. Then check the first submission from the live site, not from staging. A missing origin is an easy mistake when the live domain differs from the one you tested on, and the widget will refuse submissions from it until you add the domain.

## Should one agency share a single product across clients?

Avoid it. A shared product mixes feedback from different businesses into one inbox, and you lose the clean separation that makes each summary accurate. Even when two clients use similar apps, give each its own product, its own origins and its own webhook. The extra setup takes a few minutes, and it prevents the kind of mix-up that costs trust.

## How to set up client feedback with Escuta Produto

Create one product per client in the dashboard and fill in its name, website, accent color and allowed origins. Send the client the snippet with that product's key, and the link to the hosted feedback page. Point the notification webhook at your own channel, or at a shared channel with the client if they have one. The [widget docs](/docs/widget) cover the snippet options, and the [hosted page docs](/docs/hosted-page) explain the link. For a broader view of the weekly habit, read [a feedback routine for five products](/resources/feedback-routine-multiple-products). If you run several client products beside your own, [one feedback inbox for many products](/resources/one-inbox-many-products) explains how to keep them apart.

## Frequently asked questions

### Can an agency give each client their own feedback product?

Yes. Create one product per client site, each with its own widget key, allowed origins, hosted page, accent color and notification webhook. Feedback for each client stays in its own product inbox.

### Can clients log in to see their feedback?

No. Escuta Produto has no client accounts, team roles or client portal. Share a CSV export or a short written summary with each client instead.

### Does Escuta Produto offer white-labeling for agencies?

No. It does not offer white-labeling, so do not promise clients a branded version of the tool. The hosted page uses the product's accent color, which you can set to match the client's brand.