Customer feedback resources
Guides for founders and product teams on hearing customers: how to collect feedback, how to triage it and how to turn it into product decisions.
Feedback glossary
Short, precise definitions of the terms product teams use for customer feedback.
What is in-app feedback?
In-app feedback is a form inside your product that sends bugs, ideas and praise to your team with the page and user context attached. Here is how it works.
What is a feedback widget?
A feedback widget is a small script that adds a feedback button and form to your site or app. Learn its three parts, the main widget types and setup basics.
What is feedback triage?
Feedback triage is the regular step where each customer message gets one decision: act, plan, close or ask. Learn the statuses and a sensible cadence.
Bug report vs feature request: what's the difference?
A bug report says the product fails its promise. A feature request asks for something new. Clear tests for each, the gray areas, and why the label matters.
Qualitative vs quantitative customer feedback
Quantitative feedback counts answers, like ratings and votes. Qualitative feedback is the words customers use. What each is good for and how to combine them.
NPS vs open-ended feedback: which tells you more?
NPS gives one loyalty score from minus 100 to 100. Open-ended feedback explains the score. What each measures, what each misses, and when to use each.
What is a product feedback loop?
A product feedback loop is the cycle of collecting feedback, deciding, building and telling customers. Learn the four steps and where loops usually break.
What is voice of the customer (VoC)?
Voice of the customer (VoC) is the practice of gathering what customers say about a product from many sources and sharing it. A light setup for small teams.
What is a feedback inbox?
A feedback inbox is one place where every customer message lands, with statuses, search, context and notes. Why one inbox beats scattered channels.
What is feedback metadata and why does it matter?
Feedback metadata is the context attached to a message: page URL, browser, country, user and plan. How it makes feedback actionable and what to leave out.
Feedback by product type
How to collect feedback for SaaS, mobile apps, extensions, plugins and more.
How to collect feedback in a SaaS product
Collect in-app feedback from SaaS customers: load the widget once, identify users after login, add plan metadata and place entry points where work happens.
How to collect feedback in a mobile app
Collect feedback from iOS, Android or React Native with one REST API request, app version metadata and a hosted form link in your store listing.
How to collect feedback for a Chrome extension
Collect Chrome extension feedback with a REST API call from the popup, a hosted form as the uninstall URL and the extension version on every report.
How to collect feedback for a WordPress plugin
Collect feedback for a WordPress plugin with a settings page link to a hosted form, server-side API posts with site details, and no remote script in wp-admin.
How to collect feedback for a Shopify app
Collect Shopify app feedback from your backend with the REST API, store the shop domain as metadata and link a hosted form in onboarding emails.
How to collect feedback on internal tools
Collect feedback on internal tools by treating employees as customers: one product per tool, people identified by work email and alerts sent to the owning team.
How to collect feedback for an open-source project
Collect open-source feedback beyond GitHub issues: a docs-site widget, a hosted form linked from the README and private messages from quiet users.
How to collect feedback for API and developer tools
Collect API and developer tool feedback from docs pages, errors and CLI commands, with request ids as metadata and the per-IP rate limit planned for.
How to collect feedback in a two-sided marketplace
Keep buyer and seller feedback apart in a two-sided marketplace, with one product per side or a side value in metadata, and ask each side at its own moment.
How to collect feedback before you launch
Collect feedback before launch with a hosted form for invited testers, a landing page widget and specific questions that turn early opinions into decisions.
Collecting at the right moment
When to ask customers for feedback, from onboarding to cancellation.
How to collect customer feedback for a software product
A practical guide to collecting customer feedback for SaaS and apps: where to ask, what to ask, which context to capture and how to keep it in one place.
How to ask for feedback during onboarding
Which onboarding steps to ask about, where to place a prompt, how to avoid blocking activation and how to tag each answer with the step it came from.
Asking for feedback after a user's first success
How to define a first-value moment, wait one session before asking and collect praise and friction with one light prompt that does not feel like a survey.
How to collect feedback on a new feature launch
Place entry points inside a new feature, preselect the type you need, tag each item with the feature name and separate launch noise from real problems.
How to collect cancellation and churn feedback
Add one optional cancellation question, send the reason to your inbox from your backend with the REST API, and read churn feedback by reason each month.
What to ask customers after a failed payment
After a failed payment, send the card update link first, then ask one feedback question only if the card is not the problem. Keeps billing and churn apart.
Collecting feedback after a support ticket closes
Ask for product feedback after a support ticket closes, keep it apart from support satisfaction and link each answer to its ticket id in metadata.
How to collect feedback in a beta program
Keep beta feedback apart from everyday feedback with a separate product or a metadata flag, set tester expectations early and run a short weekly review.
How to collect feedback on your pricing page
A quiet feedback link on your pricing page catches visitor questions and objections. Read them by theme, count distinct visitors and keep visitor data out.
Using empty states to collect product feedback
Use empty states to ask what users expected to see, connect the button to the widget, tag the screen in metadata and avoid nagging people who are starting.
How to collect feedback from release notes
Add a feedback button to each release note entry, tag each item with its release in metadata and read the answers against the change that prompted them.
Install by framework
Step-by-step feedback widget setup for popular web frameworks.
Add a feedback widget to a React app
Install the Escuta Produto feedback widget in a Vite React app: the script in index.html, identify from your auth context, and how routes behave.
Add a feedback widget to a Vue app
Add the Escuta Produto feedback widget to a Vue 3 app with Vite: script in index.html, identify in a composable after login, and Vue Router notes.
Add a feedback widget to a Nuxt app
Add the Escuta Produto feedback widget to a Nuxt app: app.head script config, a client-only plugin for identify, and server rendering caveats.
Add a feedback widget to a SvelteKit app
Add the Escuta Produto feedback widget to a SvelteKit app: the app.html script, identify from layout data, and Content Security Policy in svelte.config.js.
Add a feedback widget to an Astro site
Add the Escuta Produto feedback widget to an Astro site: a base layout script with is:inline, view transitions, and static pages without login.
Add a feedback widget to a React Router or Remix app
Add the Escuta Produto feedback widget to a React Router or Remix app: the root Layout script, identify from loader data, and client-side navigation.
Add a feedback widget to an Angular app
Add the Escuta Produto feedback widget to an Angular app: the index.html script, identify from an auth signal, and notes for routing and server rendering.
Add a feedback widget to a Ruby on Rails app
Add the Escuta Produto feedback widget to a Ruby on Rails app: layout script, identify with safe JSON in a meta tag, Turbo notes and a CSP initializer.
Add a feedback widget to a Django app
Add the Escuta Produto feedback widget to a Django app: the base.html script, user data with json_script, and django-csp settings for the widget host.
Add a feedback widget to a Laravel app
Add the Escuta Produto feedback widget to a Laravel app: the Blade layout script, a safely encoded user meta tag, a Vite identify module and CSP middleware.
No-code and website builders
Adding a feedback widget to WordPress, Webflow, Shopify and other builders.
Add a feedback widget to a WordPress site
Add the Escuta Produto feedback widget to WordPress with a header and footer plugin or a child theme, pass logged-in users and allow your domain.
Add a feedback widget to a Webflow site
Add the Escuta Produto feedback widget to Webflow through site-wide footer custom code, a page-only button, and a publish and allowed-origins check.
Add a feedback widget to a Framer site
Add the Escuta Produto feedback widget to a Framer site through the end-of-body custom code, an Embed button and a publish check on the live domain.
Add a feedback widget to a Shopify store
Add the Escuta Produto widget to a Shopify store through theme.liquid, identify signed-in customers with Liquid and allow both your domains.
Add a feedback widget to a Wix site
Add the Escuta Produto feedback widget to a Wix site through custom code at the end of the body, with placement, page scope and an allowed-origins check.
Add a feedback widget to a Squarespace site
Add the Escuta Produto feedback widget to Squarespace through the footer code injection, limit it to chosen pages and confirm your domain is allowed.
Add a feedback widget to a Ghost blog
Add the Escuta Produto feedback widget to a Ghost blog through the site footer code injection, add a per-post prompt and identify members from the theme.
Add a feedback widget to a Carrd landing page
Add the Escuta Produto feedback widget to a Carrd landing page with an embed element, collect pre-launch feedback and use a hosted link as the fallback.
Add a feedback widget to a Bubble app
Add the Escuta Produto feedback widget to a Bubble app through the SEO and metatags header, identify the Current User in a workflow and test the live version.
Install a feedback widget with Google Tag Manager
Install the Escuta Produto feedback widget with a Google Tag Manager Custom HTML tag on all pages, keep the data attributes intact and test in preview mode.
Analyzing and prioritizing
Turning raw feedback into decisions and a roadmap.
How to triage customer feedback
A weekly routine for turning raw customer feedback into decisions: statuses, tagging by type, spotting patterns and closing the loop with customers.
How to use RICE to prioritize customer feedback
Score feedback with RICE: count distinct customers for reach, rate impact and confidence, then divide by effort. Includes a worked example.
How to apply the Kano model to feature requests
Use the Kano model to sort feature requests into basic, performance, delighter and other groups, and learn when the model stops being useful.
Prioritize bugs by frequency and severity
Rank bugs by how often customers hit them and how much damage they cause. A 2x2 grid, a frequency count from feedback and clear rules for what goes first.
How to build a tagging system for customer feedback
Escuta Produto has no tags, so build a small, stable set of areas in metadata and notes. Define each label, review the list quarterly and keep it short.
Find the problem behind a feature request
Customers describe solutions, not problems. Ask why, frame the job to be done, record the underlying problem and group requests by it.
How to weigh feedback from paying vs free users
Weigh feedback by fit, not only by payment. Send a segment field with identify, compare requests by segment and know when free users matter more.
How to deduplicate feature requests
Find duplicate feature requests with search and careful reading, name one canonical request, and count distinct customers instead of repeated messages.
How to analyze customer feedback in a spreadsheet
Export feedback as CSV, open it in Excel or Google Sheets, then count by type, status and month with a pivot table and a few simple formulas.
How to group customer feedback with an LLM
Group customer feedback with a language model safely: remove personal details, ask for themes with quotes, check a sample by hand and count in a sheet.
A weekly feedback review template
A 30-minute weekly feedback review template with a fixed agenda, roles for a small team, expected outputs and a checklist you can copy.
Closing the loop
Replying to customers, saying no well and announcing what shipped.
How to reply to customer feedback (with templates)
Copy-ready replies for bug reports, feature ideas, praise and unclear messages, plus tone and timing rules for answering customer feedback from your own email.
How to say no to a feature request
How to decline a feature request honestly: give the real reason, offer a workaround you would support, record the decision and keep the customer who asked.
How to write a changelog customers read
Write a changelog people read: customer language, entries grouped by what changed for users, credit for requests and links back to the feedback behind them.
How to tell customers their request shipped
Find everyone who asked for a feature, write a short shipped message, send it from your own email at the right time and record who you told so nobody is missed.
Should you have a public roadmap?
The benefits and costs of a public product roadmap, the alternatives that keep customers informed, and why Escuta Produto has no public roadmap board.
How to follow up on a bug report
Follow up on a bug report in four steps: acknowledge it, ask for the one missing detail, report the fix and confirm it works for the customer who found it.
How to turn customer praise into testimonials
Sort praise from usable testimonials, ask permission before you publish, edit lightly without changing the meaning and keep a log so good quotes are never lost.
How to design a feedback status workflow
Design a feedback status workflow with five statuses: what each promises, who moves an item, which moves to allow, which to avoid and how to review stale items.
How to thank customers for feedback
Thank customers for feedback in a way they notice: name the specific thing, keep it short, thank bug reporters too and avoid promises you cannot keep.
How to turn customer feedback into a roadmap
Turn customer feedback into a roadmap: group requests into themes, turn themes into bets, sort them into now, next and later, and link items to their feedback.
Running multiple products
Feedback routines for founders, studios and agencies with several products.
One feedback inbox for many products
Why one feedback inbox beats a separate tool for each app, how per-product keys keep feedback apart, and what you give up by reading it all in one place.
A feedback routine for running five products
A weekly feedback routine for five products: a daily count check, one fixed review slot per product, a bugs-first triage order and a list of what to skip.
Using feedback to choose which product to work on
How to use unique customers, rating direction and revenue fit to pick the product that gets your next week of work, and avoid the loudest-product trap.
How to organize Slack channels for product feedback
How to set up Slack or Discord channels for product feedback: one webhook per product, a channel per product or a shared one, and ways to keep alerts quiet.
How agencies can collect feedback for client products
How agencies can run feedback for client sites with one product per client, separate keys and origins, CSV summaries instead of logins and honest limits.
Feedback metrics for a portfolio of products
Four feedback metrics for a portfolio of products: unique people, open items, rating average with its count and the 30-day trend, plus the numbers that mislead.
Customer feedback for indie hackers and solo founders
A minimum feedback setup for indie hackers and solo founders: one widget, one webhook, a 30-minute weekly triage and personal replies to users.
Using feedback to decide when to sunset a product
How to read feedback signals before you sunset a product, tell customers early, collect exit feedback with the widget and export data before deleting.
Spotting feedback patterns across products
How to spot the same complaint across several products, label themes without tags, and fix a shared login or billing problem once instead of many times.
Keeping the feedback experience consistent across apps
How to keep feedback forms consistent across several apps with the same placement, copy and statuses, a color per product and one shared configuration template.
Widget design, privacy and performance
Designing fast, accessible, private and spam-resistant feedback widgets.
Feedback widget best practices
Where to place a feedback button, how to keep it fast and accessible, and how to protect it from spam. Practical rules for in-app feedback widgets.
What should a feedback button say?
How to word a feedback button: verbs or nouns, labels that match each page and feedback type, localized copy, and how to replace the default Feedback button.
Designing a feedback widget for mobile screens
Designing a feedback widget for phones: thumb reach, keyboard overlap, bottom navigation conflicts and the checks to run on a real device before you ship.
How to make a feedback widget accessible
Make a feedback widget usable with a keyboard and screen reader: real buttons, dialog semantics, focus return, labels, contrast and known gaps.
Why embeddable widgets use Shadow DOM
What Shadow DOM isolates in an embeddable feedback widget, what it leaves open to the host page, how to theme across the boundary, and how to test it.
Content Security Policy for third-party widgets
Which Content Security Policy entries a third-party feedback widget needs: script-src, connect-src and style-src, nonces, and how to debug blocked requests.
Feedback widgets, GDPR and LGPD
What a feedback widget collects, field by field, what it stores on the visitor's device, and how to write a privacy notice for GDPR and LGPD. Not legal advice.
How to protect a feedback form from spam
Stop spam in a feedback form with a honeypot field, allowed origins, rate limits and size limits, and why a CAPTCHA usually costs more than it stops.
How to keep a feedback widget from slowing your site
Keep a feedback widget from slowing your pages: load it with defer, keep the payload small, avoid extra requests and measure the impact before and after.
How to collect feedback in multiple languages
Collect feedback in several languages: how the widget picks its language, when to override it with data-locale, and how to read messages in other languages.
Matching a feedback widget to your brand and dark mode
Match a feedback widget to your brand: set the accent color, check button contrast, understand why the panel stays light on dark sites, and position it well.
Comparisons and alternatives
How Escuta Produto compares with other ways to collect product feedback.
Escuta Produto vs Canny
Canny is a public voting board and roadmap. Escuta Produto is a private inbox for feedback across many products. See which one fits your team.
Escuta Produto vs Featurebase
Featurebase is an all-in-one feedback and roadmap suite. Escuta Produto is a lightweight widget with one private inbox for all products. Compare the two.
Escuta Produto vs Usersnap
Usersnap focuses on visual bug reporting for QA and website teams. Escuta Produto is a feedback inbox for customer bugs, ideas and praise. Compare them.
Escuta Produto vs Userback
Userback is a visual feedback platform built around annotated reports. Escuta Produto is a minimal widget and REST API feeding one inbox. Compare them.
Escuta Produto vs Marker.io
Marker.io is visual bug reporting for teams and QA. Escuta Produto collects customer feedback in a private inbox. Here is how to choose.
Escuta Produto vs Hotjar Feedback
Hotjar bundles heatmaps, recordings and feedback. Escuta Produto is a dedicated feedback inbox for many products. See which approach fits your team.
Escuta Produto vs Google Forms and Typeform
Google Forms and Typeform are form builders for surveys. Escuta Produto is an in-app feedback widget that adds page context. Compare them.
Escuta Produto vs Intercom for product feedback
Intercom is a customer messaging platform for chat, help and outreach. Escuta Produto is a focused inbox for product feedback. See which one fits.
Should you build your own feedback widget?
A feedback widget looks simple until spam, rate limits, storage and alerts arrive. Learn what building involves and when Escuta Produto makes sense.
Feedback widget vs a mailto link
A mailto link is quick, but replies lose context and fill a personal inbox. A feedback widget sends structured feedback with the page attached.