Generate Customer Feedback System

Most businesses collect customer feedback. Far fewer have a feedback system. The difference is what happens after the response comes in. A survey that nobody analyzes, comments that sit in an inbox, a satisfaction score reported in a meeting and then forgotten — these are feedback activities, not a feedback system. A real system has a loop: it captures input at the right moments, routes it to the people who can act, turns it into prioritized decisions, and closes the loop with the customer who raised it.

This prompt designs that end-to-end system for your specific business. It identifies the right moments to ask, the right questions to ask, how to route and prioritize what comes back, and how to ensure feedback actually changes something — so the customer's effort in giving it is not wasted, and yours in collecting it is not either.

What It Does

Designs an end-to-end customer feedback system — capture, routing, analysis, action, and loop-closing — not just a survey.
Identifies the right moments and methods to collect feedback so it is timely, honest, and low-friction for the customer.
Builds in the mechanism that turns feedback into prioritized decisions and visible change.

The Prompt

#CONTEXT:
I want to build a customer feedback system for my business — not just a survey, but a complete loop that captures customer input, routes it to the right people, turns it into prioritized decisions, and closes the loop with customers so they see their feedback led to change. Your job is to design that system specifically for my business: the touchpoints where feedback should be collected, the questions worth asking, how responses are analyzed and prioritized, and how action is taken and communicated back. The goal is a system that improves the business and that customers trust enough to keep engaging with.

#ROLE:
You are a customer experience strategist who has built voice-of-customer programs for product and service businesses. You know that feedback only creates value when it changes a decision, and that customers stop giving honest feedback when they sense it goes nowhere. You design lightweight systems that fit small teams, not bureaucratic ones.

#RESPONSE GUIDELINES:
1. Begin by mapping the key moments in my customer journey where feedback is most valuable and most honestly given.
2. For each moment, recommend a feedback method (short survey, single-question prompt, interview, review request) and the specific questions to ask.
3. Design how responses are captured, tagged, and routed to the person who can act on each type of feedback.
4. Define a prioritization method so the team acts on what matters most rather than the loudest or most recent input.
5. Specify how the loop is closed — how customers learn their feedback led to a change.
6. Recommend a simple cadence and a small set of metrics to track the system's health over time.

#FEEDBACK SYSTEM QUALITY CRITERIA:
1. Timely: Feedback is requested close to the experience it concerns, while memory is fresh.
2. Low-friction: Asking is short and easy; the system favors response rate over question quantity.
3. Actionable: Questions are designed to produce input a team can actually act on.
4. Routed: Every type of feedback has a clear owner who can do something about it.
5. Closed-loop: The system includes a deliberate step that tells customers what changed because of them.

#INFORMATION ABOUT ME:
- My business and what I sell: [BUSINESS_AND_OFFERING]
- My customer journey, briefly — from first contact to ongoing use: [CUSTOMER_JOURNEY]
- How I collect feedback today, if at all: [CURRENT_FEEDBACK_PRACTICE]
- My team size and tools available: [TEAM_AND_TOOLS]
- The decisions I most want feedback to inform: [DECISIONS_TO_INFORM]

#RESPONSE FORMAT:

Feedback Touchpoint Map:
- [Journey moment]: [Why feedback here is valuable] — [Method] — [Questions to ask]
- [Journey moment]: [...]

Capture & Routing:
[How responses are recorded, tagged, and sent to the right owner]

Prioritization Method:
[How the team decides what to act on first]

Action & Loop-Closing:
[How feedback becomes change, and how customers are told]

Cadence & Health Metrics:
- Cadence: [How often each part of the system runs]
- Metrics: [Small set of numbers that show the system is working]

Quick-Start Plan:
[The first 3 steps to launch a lightweight version this month]

How to Use

Describe your customer journey honestly, including the unglamorous moments — onboarding friction and churn are where the most useful feedback lives.
Be clear about your team size and tools so the system designed is one you can actually run.
Copy the completed prompt into your preferred AI tool.
Start with the Quick-Start Plan rather than building the whole system at once; a small loop that runs beats a complete system that does not.

Example Input

## Information about me

- My business and what I sell: A B2B project management SaaS tool sold on monthly subscriptions
- My customer journey, briefly: Free trial → onboarding → first project created → ongoing use → renewal or churn
- How I collect feedback today, if at all: An annual survey that gets a low response rate, plus support tickets nobody analyzes systematically
- My team size and tools available: 8 people; we use Intercom, a help desk, and a basic analytics tool
- The decisions I most want feedback to inform: What to build next, why trial users don't convert, and why customers churn at month 4

Tips

Ask close to the moment. Feedback requested days after an experience is feedback filtered through forgetting. Trigger requests at or right after the relevant touchpoint.
Fewer questions, higher response. A one-question prompt that 40% of customers answer beats a 20-question survey that 3% finish. Optimize for response rate.
Talk to the customers who left. Churn and cancellation are the most honest feedback moments you have. Build a specific exit-feedback step into the system.
Close the loop visibly. When you ship a change driven by feedback, tell the customers who asked for it. Nothing increases future response rates more.
Separate signal from volume. One thoughtful interview can outweigh a hundred survey checkboxes. Build qualitative depth into the system, not just quantitative scores.