# Asking for feedback after a user's first success

> Ask for feedback right after a user's first real result, such as their first report or first sent invoice, and only once they have finished the action. Use one light prompt with the praise type preselected, then read the praise and the friction together.

Source: https://escutaproduto.com/resources/feedback-after-first-success
Last updated: 2026-10-09

## Define the first success before you ask

A first success is the first moment a user gets the result your product promises. For a reporting tool it might be the first report they export. For an invoicing tool it might be the first invoice that reaches a client. For a booking app it might be the first confirmed appointment. The exact event depends on your product, but it should be something a user did on purpose, not something that happened to them.

Write the event down as a sentence before you touch any code: "A user has succeeded when they have ___." If you cannot finish the sentence in one line, the first success is not clear yet, and asking for feedback too early will produce vague answers. Check the sentence against your own data. The users who keep coming back usually reached this moment in their first few sessions.

Once you have the sentence, you have a trigger. The prompt fires after this event, not after a fixed number of days, because a fixed timer ignores what the person actually did.

## Wait one session before asking

Asking the moment the success happens is tempting, but people are often still reading the result. A better rule is to wait until the next session. The user has come back, which means the product mattered enough to return to, and they now have a view of the whole result rather than a fragment of it.

Implementation is simple. When the success event fires, store a flag in your own database or in the user's profile. On the next page load where the flag is set, show the prompt once and clear the flag when the user answers or dismisses it. Do not rely on browser storage for this, because a user who switches devices would see the prompt twice or never.

## Ask with one light prompt

The prompt should be one line and one optional text box. A question such as "How did the first report go?" gives people a reason to answer. A question such as "Please rate your experience on a scale of 1 to 10 and tell us about any improvements" gives them a reason to close the tab.

Use a link or a small card, not a modal. A modal says the product wants something from the user right now. A small card says the user can answer when they have a moment. In the widget, the easiest pattern is a button with `data-escuta-open` set to `praise`, so the form opens with the praise type already selected.

```html
<script src="https://escutaproduto.com/widget.js" data-key="pk_your_product_key" defer></script>

<p>Your first report is ready. How did it go?</p>
<button type="button" data-escuta-open="praise">Tell us what you think</button>
```

The form still offers the other types, so a user who wants to report a problem can change the type before sending. Preselecting praise changes the starting point, not the outcome.

## Collect praise and friction in the same prompt

People who reached a first success usually have two things to say. They liked a part of the result, and they hit a snag somewhere on the way. A praise-only prompt misses the snag. A bug-only prompt misses what worked. The open message box handles both, because people write what stands out to them.

When you read the answers, sort each one into what to protect and what to fix. Praise tells you which part of the flow must not break in the next release. Friction tells you where the first success almost did not happen. Both are useful, and the same message often contains both.

Keep the optional star rating in mind too. The product shows an average rating, and the words explain the number. Use the rating to find unusually low or high answers, then read those messages first.

## Keep the prompt from becoming a survey

Escuta Produto does not run surveys, NPS campaigns or multi-question forms. That is deliberate for this moment. A survey after a first success asks the user to switch from doing the task to evaluating it, and the answers become generic. One open message with a type gives people a small, specific thing to say.

If you need a structured score for reporting, collect it separately and on a different schedule. Mixing it into the first success prompt makes the praise look like a grade.

## Turning answers into a praise library

Praise from the first success moment is some of the most honest copy you will get. People describe the result in their own words, and those words are often better than your landing page. Before you use any of it publicly, ask for permission and keep the wording as close to the original as you can. The [guide to turning praise into testimonials](/resources/turn-praise-into-testimonials) covers the permission step and light editing.

For internal use, keep a short list of the phrases customers repeat. When you write release notes or onboarding copy, check that the words match how customers describe the benefit rather than how your team names the feature.

## How to run first success prompts in Escuta Produto

Set up the trigger in your own code, then send the prompt through the widget. Use the praise button described above, and set the first success event as metadata before the form opens, so every answer records which milestone produced it.

```js
EscutaProduto.setMetadata({ milestone: "first-report-exported" });
EscutaProduto.open({ kind: "praise" });
```

Review the inbox weekly and filter by type. Praise items tell you what to protect in the next release, and bug items from this group are often the first sign of a problem in the flow. The [widget docs](/docs/widget) list every option for the button, locale and position, and the [API docs](/docs/api) describe the JSON body if you want to send the praise from your server instead.

If you want the full picture of a feedback program, read [what is in-app feedback](/resources/what-is-in-app-feedback) for the broader case for asking inside the product.

## Frequently asked questions

### What counts as a first success for a product?

It is the first time a user gets the result the product promises, reached through an action they chose to take. Write it as one sentence, such as a user has succeeded when they have exported their first report, then check that your data shows returning users reached it early.

### Should the feedback prompt appear right after the success event?

Usually not. Wait until the user comes back in a later session. That gives them time to see the whole result, and it avoids interrupting the moment they are still reading what the product produced.

### Why use a praise type for a first success prompt?

Praise preselects the form with a positive starting point, and the message box still lets people report problems. Most people at this moment have something to say about what worked and something that slowed them down, so the same prompt collects both.
