What to do with feedback that has no email address

Why anonymous feedback still counts

A message with no email address is still a message about your product. The person who wrote it had a problem or an idea and took the time to tell you. You cannot reply to them directly, but you can still learn from what they said, and a bug report with no sender is just as real as one with a name attached.

The mistake many small teams make is to treat anonymous feedback as noise. They skim it, add nothing, and let the item sit in new forever. A better habit is to read every item once, decide whether it describes a real problem or a clear request, and record that decision. The item may not get a reply, but it still gets a status and a note.

What you can and cannot do without an address

Without an address you cannot send a reply, follow up, or tell the person when the change ships. Escuta Produto does not send automatic emails to customers, so there is no built-in path from an anonymous item to the sender. Your options are limited, and it helps to be honest about them.

You can still do four things:

1. Read the message and the page URL, which show where the problem happened.
2. Group it with similar items using text search on the message words.
3. Act on the pattern, for example by fixing a bug that many people report.
4. Record the outcome as an internal note and set the status, so the next person who opens the item knows what happened.

What you cannot do is close the loop with the person who wrote it. Accept that gap, and do not pretend you can reach them.

Should you ask for an email at all?

Ask for an email when a reply would change what you do. A bug report with a reproduction step often needs a follow-up question, so an address is worth asking for. A praise message rarely needs one. Forcing a sign-in before someone can say "the export button is slow" makes people leave, and fewer reports is a worse outcome than a few replies you cannot send.

If the widget is on a page where users are already signed in, the better move is to pass their details from your app instead of asking again. That removes the friction and gives you an address with every message.

Pass the signed-in user to the widget

The widget can take the user's details through the identify function. When you call it, the email and name fill the form, the email field is hidden because you already have the address, and any other keys you pass are stored as metadata on the item. This is the most reliable way to avoid anonymous feedback from logged-in users.

If the widget script may load after your own code runs, use the queue form so the call is not lost:

window.EscutaProduto = window.EscutaProduto || { q: [] };
(window.EscutaProduto.q ||= []).push(["identify", [{ email: user.email, name: user.name, id: user.id }]]);

Call this after your app knows who the user is, not on the public marketing pages. Send only what the form needs and what you would show in your own support tool. For the full option list, see the widget docs.

Capture contact details on the hosted page

Some customers arrive through the hosted feedback page instead of the widget. You can prefill the email field with a query parameter, so a link you send from your own app or support emails already carries the address. The page is not indexed by search engines, which makes it suitable for private links to specific customers.

For a product with its own sign-in, the API route is another option. The REST API accepts an optional email and name in the JSON body. Use it when your server already knows the user, and you want the address stored without a browser form. The API reference is at the API docs.

Acting on feedback you cannot answer

When you cannot reply, make the item useful for the rest of the team. Add an internal note that says what you think the problem is, what you checked and what you decided. Set the status to planned if you intend to act, or closed if you decided not to, following the status workflow.

Then look for repeats. A single anonymous message is weak evidence, but five similar messages, each with a page URL, point to a real issue. Search the inbox for two or three distinctive words, group the matches in your notes, and fix the pattern. Your next release note can say what changed without naming anyone. Customers who did not write in still benefit from the fix.

Putting anonymous feedback to work in Escuta Produto

In the product inbox, you can filter items by type and status, and search the message, name and email fields for text. An item with no email shows an empty email field, which tells you at a glance that a reply is not possible from the dashboard. Treat that as a signal to check the page URL and the metadata, not as a reason to skip the item.

Where you do have an email, write the reply from your own address and add a private note with the outcome. Where you do not, the note and the status are your record. If you are setting up identify for the first time, the steps in how to collect customer feedback cover where the widget belongs in your product, and the widget best practices explain how to keep the form short.