Approved AppProductfeedbacksummaries

Customer feedback to themes and a one-pager

PL by Prompier Library ☆☆☆☆☆ New 0 adds Version 1 · updated Nov 10, 2026

About this app

Groups pasted customer feedback into themes with counts and quotes, stops so you can check the table, then writes a one-page summary for your team.

How it works. Paste customer feedback, one item per line, and say who the summary is for. Step 1 builds a table of themes and the run pauses so you can check it: fix a count, merge two themes or remove a quote you do not want to share. Step 2 writes a one-page summary from the table you approved. Remove names and email addresses before you paste.

What you enter

3 fields

Field	What to enter	Example
Product or area Short text	The product or area the feedback is about.	e.g. Mobile booking app
Customer feedback Long text	One item per line. Remove names and email addresses first.	e.g. Cannot change my appointment without calling the office.
Who reads the summary One of a list	Sets what the one-pager puts first. Choices: Product team, Leadership, Support team	—

What it does

2 steps

Group the feedback into themes Step 1Table

Show the instructions

You are a product researcher who turns raw customer comments into themes a team can act on. Product or area: {{product_area}} Customer feedback, one item per line: """ {{customer_feedback}} """ Follow these steps: 1. Read every item and note the need or problem behind it, not just the words used. 2. Group items that share the same need into one theme. Give each theme a short, plain name of two to six words. Aim for three to eight themes, and keep a one-item theme only if it is clearly different. 3. Count how many feedback items belong to each theme. An item that mentions two needs may count in both themes. Do not count anything twice within one theme. 4. For each theme pick one short quote copied word for word from the feedback. Leave out names and email addresses. 5. For each theme suggest one concrete next step the team could take, in one short sentence. 6. Sort the rows by count, highest first. Output format: a table where every row uses exactly these keys: theme, count, example_quote, suggested_step. The count is a whole number. Quality bar: use only what the feedback says. Do not invent quotes, counts, customer types or reasons. If a field cannot be filled from the feedback, write "Not stated". Do not add praise or criticism of your own.

System text
You are a careful product researcher. Use only the feedback you are given. Never invent a quote, a count or a customer detail.
Check the themes Review stepThe run stops here for you to read, edit or send the text back.
Write the one-page summary Step 2Document

Show the instructions

You are a product communicator writing a one-page summary of customer feedback for this reader: {{audience}}. Product or area: {{product_area}} Checked themes, as a table with a count, a quote and a suggested step for each theme: {{themes}} Write the summary with these headings, in this order: 1. Main point: two sentences. Put first what matters most to the reader named above. 2. Top themes: the three themes with the highest counts, each with its count and its quote. 3. What we do not know yet: two or three short bullets about the limits of this feedback, such as how many items there were and who they came from. 4. Suggested next step: one clear recommendation, with a short reason that points back to the counts. Quality bar: use only the table above. Quote customers word for word and never add a quote of your own. If the table does not say something, write "Not stated" rather than guessing. Use plain words and short sentences, avoid jargon and hype, and do not turn a count of a few items into a claim about all customers. Keep it under 350 words.

System text
You write short summaries for busy readers. Use plain words and short sentences. Separate what the feedback shows from what is only a guess. Never invent data, quotes or dates.

This is exactly what the app sends to the AI. It is public domain text: read it before you run it.

Sample run

Written for this page

What was entered

Who reads the summary: Product team
Customer feedback: Cannot change my appointment without calling the office. The reminder text arrives too late to be useful. I wanted to reschedule from my phone and had to phone in. Love the new look, but the calendar is slow to load. Reminders come the same morning, I need them the day before. Payment failed twice with no explanation. Calendar takes ages to open on my older phone. Please let me move my booking in the app. Paid twice for one visit and nobody told me why. Would like to book for my two kids in one go.
Product or area: Mobile booking app

Group the feedback into themes

theme	count	example_quote	suggested_step
Cannot reschedule in the app	3	Please let me move my booking in the app.	Add a reschedule option to the booking screen so customers do not need to phone the office.
Reminders arrive too late	2	Reminders come the same morning, I need them the day before.	Offer a reminder the day before the appointment as well as the same-day one.
Calendar loads slowly	2	Calendar takes ages to open on my older phone.	Measure how long the calendar takes to load on older phones and set a target.
Payment problems without explanation	2	Payment failed twice with no explanation.	Show the reason when a payment fails and check why one visit was charged twice.
Booking for several people at once	1	Would like to book for my two kids in one go.	Ask a few parents how they book today before deciding whether to build this.

Write the one-page summary

Mobile booking app: what customers told us

Main point

Customers most often want to change a booking from their phone instead of calling the office. Late reminders, a slow calendar and unexplained payment problems come next, with two items each.

Top themes

Cannot reschedule in the app (3 items). "Please let me move my booking in the app."
Reminders arrive too late (2 items). "Reminders come the same morning, I need them the day before."
Calendar loads slowly (2 items). "Calendar takes ages to open on my older phone."

Payment problems without explanation also have 2 items: "Payment failed twice with no explanation."

What we do not know yet

How many customers this affects overall: the sample is only ten items.
Which phones are slowest and how slow: not stated.
Whether the double charge was a one-off or a pattern: not stated.

Suggested next step

Decide whether rescheduling in the app comes first, since it has the most items (3 of 10). In the same planning session, look into the double charge, because paying twice is a trust problem even though only one customer reported it.

Sample answer written for this page; your answers will differ.