# How to write a monthly customer feedback report > A monthly customer feedback report fits on one page. Show volume by type, the top themes with distinct customer counts, what shipped because of feedback, what is planned next and what was declined, plus two or three short quotes. Reuse the same structure every month so trends stay comparable. Source: https://escutaproduto.com/resources/monthly-feedback-report Last updated: 2026-10-11 ## What belongs in a one-page feedback report? A monthly feedback report has one job: tell the reader what customers said, what the team did about it, and what happens next. Anything that does not serve those three points belongs in an appendix or in the spreadsheet. Readers skim, so the structure matters as much as the numbers. Use five sections, in this order: volume by type, top themes, what shipped, what is next, and quotes. Keep the whole thing to one page. If you cannot fit it, the report has too many themes, and the top three should win. ## How do you show volume by type? Start with a small table that counts feedback by type for this month and the previous one. The four types in Escuta Produto are bug, idea, praise and other, so the table can be short. The numbers below are an example, not real data. | Type | This month | Last month | | --- | --- | --- | | Bug | 34 | 41 | | Idea | 58 | 52 | | Praise | 19 | 14 | | Other | 7 | 5 | Add one sentence that explains the change, and note any release or incident that explains a spike. Counts without context invite the wrong conclusion. A rise in bugs the week after a release is a different story from a rise with no change in the product. Add the average rating if you collect ratings, and the number of distinct customers who wrote in. The distinct count is the number a reader trusts most, because it shows how broad the feedback is. ## How do you pick the top themes? Pick three themes at most. A theme is a group of feedback that describes one part of the product or one customer job, such as "setup is confusing" or "exports take too long." Use the groups you built during the month's triage rather than inventing new ones for the report. For each theme, show the number of distinct customers who raised it, the most common type, and one line on its status. Rank them by the number of distinct customers, then by severity for bugs. The [frequency and severity guide](/resources/prioritize-bugs-frequency-severity) explains how to weigh a severe bug above a noisy one. Do not present a theme that has only one customer behind it, unless it is a severe bug. Mention it in a footnote if it matters. ## What shipped, and what changed for customers? List the changes that shipped this month and that came from feedback. For each, write one line that names the change and the customers who asked, without naming private people. Then say what changed for them: a step that took fewer clicks, a bug that no longer happens. This section does double duty. It shows the team that feedback leads somewhere, and it gives you the list you need to tell customers their request shipped. The [guide to telling customers their request shipped](/resources/tell-customers-request-shipped) covers how to close the loop. ## What is next, and what did you decide not to build? Split the forward-looking part into two lists. The first is what you planned for next month, with the status of each item. The second is what you decided not to build, with a short reason for each. The second list matters as much as the first, because it shows that requests were weighed rather than ignored. Write the reasons in plain language, such as "only two customers asked, and both have a working alternative." The [guide to saying no to feature requests](/resources/say-no-to-feature-requests) gives wording you can reuse, and it helps keep the list respectful. ## Which quotes to include, and how to use them Choose two or three short quotes. Pick them because they show a theme in a customer's own words, not because they are dramatic. Trim them to a sentence or two, and keep the meaning intact. Do not invent quotes, and remove names and email addresses before you share the report beyond the team. If you want to name a customer, ask them first. Quotes make the report memorable. A reader who skims the tables will still remember one line from a customer who had a real problem. ## A copyable monthly report template Copy this structure into a document, and fill it in on the first working day of the next month: ```text Customer feedback, [Month Year], [Product name] 1. Volume by type: bug [n] (last month [n]), idea [n], praise [n], other [n] Distinct customers who wrote in: [n]. Average rating: [n] (if collected). One sentence on what explains the change: [release, incident or none]. 2. Top themes (three at most) - [Theme]: [n] distinct customers, mostly [type], status [status] - [Theme]: [n] distinct customers, mostly [type], status [status] - [Theme]: [n] distinct customers, mostly [type], status [status] 3. What shipped because of feedback - [Change]: asked for by [n] customers, effect for them: [effect] 4. What is next - [Item]: planned for [month], status [status] - Declined: [request], because [reason in plain words] 5. Quotes - "[short quote]" (type, page or flow, no names) ``` ## Generating the report from the Escuta Produto export Each month, export the product's feedback as CSV from the inbox and filter the created_at column to the month. Count the kind column with a pivot, count the distinct customers from the email column, and compute the average rating from the rating column. Compare with last month by exporting the earlier period too. The [spreadsheet analysis guide](/resources/analyze-feedback-spreadsheet) walks through the formulas. Use the statuses in Escuta Produto for the "what shipped" and "what is next" sections, since new, planned, in progress, done and closed map directly to the report. The [weekly feedback review template](/resources/weekly-feedback-review-template) feeds the month's notes into one place, so the monthly report is mostly assembly rather than new work. The [widget docs](/docs/widget) explain where the page URL and rating come from if you want to check a theme against a specific page. ## Frequently asked questions ### What should a monthly customer feedback report include? Volume by type compared with the previous month, the top three themes with distinct customer counts, what shipped because of feedback, what is planned next, what was declined with reasons, and two or three short customer quotes. ### How long should a monthly feedback report be? One page. Readers skim, so keep the tables short and the themes few. Put detailed counts in an appendix or the spreadsheet, and let the page carry the three things the reader needs: what customers said, what changed and what comes next. ### Should the report include every feature request? No. Include the themes with the most distinct customers and any severe bug. List declined requests with reasons, but keep the full backlog in the inbox where the team can see every item. ### How do you keep monthly feedback reports comparable? Use the same five sections and the same type categories every month, and count distinct customers the same way each time. A fixed structure lets a reader see a trend without re-learning the format.