NPS vs open-ended feedback: which tells you more?

What does NPS actually measure?

Net Promoter Score asks one question: how likely is the customer to recommend the product to a friend or colleague, on a scale from 0 to 10? Customers who answer 9 or 10 are promoters, those who answer 7 or 8 are passives, and those who answer 0 to 6 are detractors.

The score is the share of promoters minus the share of detractors. It ranges from minus 100, when every customer is a detractor, to 100, when every customer is a promoter. Passives count in the total but not in the result, so a product with many passives scores lower than the raw ratings suggest.

NPS measures willingness to recommend. That is a useful signal of loyalty, and it is easy to track over time because the question never changes.

What does NPS miss?

A single score cannot say why a customer answered the way they did. A 7 from a customer who loves the product but found one bug looks the same as a 7 from a customer who tolerates it and is looking for a replacement. Both land in the passive group, and the number gives you no way to tell them apart.

NPS also reflects the customers who answer. If the people who never reply are the unhappy ones, the score can look healthier than the product really is. Timing matters too. A score taken right after a support problem is not the same measurement as one taken during a quiet month.

Finally, NPS does not tell you what to build next. It is a headline, not a plan.

Why does open text explain the score?

Open-ended feedback fills the gap. A customer who writes "the reports take a minute to load on my phone" tells you what is wrong, where it happens and how much it matters to them. That sentence is much harder to get from a number.

Open text also surfaces problems you did not ask about. A fixed question can only ask what you already suspect. An open message can say "the invoice is confusing for my accountant", which may point to a feature you never considered.

The cost is effort. Open text has to be read, grouped and counted by a person, which is why teams often skip it in favor of the score.

When should you use NPS?

NPS works best as a periodic check on loyalty across the same group of customers. It answers a question that open text answers poorly: is the overall trend moving up or down? Use it when you want one number to compare over quarters, and when you have enough customers that a single unhappy message will not swing it.

Avoid using NPS as a verdict on a single release or a single customer. A low score after one bad week is noise until the open comments confirm a pattern.

When is open-ended feedback the better tool?

Open-ended feedback is better when you need to act. Use it when you are deciding what to fix, when you are checking whether a new feature landed, or when you want to learn the vocabulary customers use for their problems. It is also the right tool for small products, where a handful of messages can be read in a sitting.

Open text is also the right channel for bugs. A score cannot reproduce a broken export. A message with the page URL and browser can.

How do you read NPS and open text together?

Treat the two as a pair. Use the score to decide when to look, and use the comments to decide what the score means. If the score falls, read the detractor comments first, then group them by theme. If the score rises, read the promoter comments to learn what to protect.

Keep the two in separate places but record the link. A simple way is to store the score as metadata on the feedback item, so each message carries the score the customer gave.

How do you collect open feedback with Escuta Produto?

Escuta Produto does not run NPS surveys, scheduled questions or score dashboards. Its feedback form is open by default: customers choose a type, write a message and can add an optional 1 to 5 star rating. That rating is not NPS, so do not treat the two as the same measure.

If you run NPS with another tool, you can still bring the two together. Send the result to the REST API at /api/v1/feedback with your public key, the customer's comment as the message and the score in metadata, for example { "nps": 9 }. The item then appears in the inbox next to the open text. Read the API documentation for the request format and error codes, and the widget documentation for the in-app form. For the difference between a rating and free text, see qualitative vs quantitative feedback. To decide what the comments mean for your roadmap, read what feedback triage is.