Skip to main content

ChatGPT Prompt to Analyze Customer Feedback Across Channels

Analyze customer feedback across channels to extract actionable insights, sentiment trends, and feature demand from one structured prompt.

Fill in the placeholders

Edit the values, then copy your finished prompt.

Your Prompt
prompt.txt
Build a customer feedback analysis framework for ProjectFlow that processes feedback from Intercom chats, G2 reviews, support tickets, NPS surveys, and Twitter mentions. We receive approximately 800 pieces of feedback monthly from enterprise, mid-market, startup, and free-tier users. Execute this analysis: 1) Design a feedback categorization taxonomy with 6 top-level categories (bug reports, feature requests, UX complaints, praise, questions, churn reasons) and subcategories within each — provide clear classification criteria and example phrases for each category to ensure consistent tagging. 2) Create a sentiment analysis prompt that scores each feedback item on a -5 to +5 scale, identifies the specific product area mentioned (onboarding, core workflow, billing, integrations, performance), and extracts verbatim quotes that best represent the sentiment. 3) Build a feature demand aggregation system that groups related feature requests even when expressed differently (e.g., "need dark mode," "too bright at night," and "eye strain" all map to the same feature), counts unique requesters rather than mentions, and weights by customer ARR, segment, and account health score. 4) Design a trend analysis prompt that compares this month sentiment distribution against the previous 3-month rolling average to identify emerging issues before they become widespread — flag any category that shifted more than 10 percentage points. 5) Create a competitive mention tracker that identifies when customers reference Asana, Monday.com, Jira, and Linear and extracts what specific capabilities they are comparing. 6) Generate an executive feedback summary template with: top 5 themes, NPS trend, most urgent issues, biggest opportunities, and recommended actions — formatted for a bi-weekly product review meeting. 7) Design an automated response suggestion system that proposes appropriate replies for each feedback category, routing urgent items to Customer Success and Product leads.

What this prompt does

This prompt builds a customer feedback analysis framework that turns scattered comments across channels into structured, de-duplicated signal. You provide [product_name], the [feedback_channels] you collect from, your monthly [feedback_volume], and your [customer_segments]. ChatGPT then designs a categorization taxonomy, a sentiment scorer, a feature-demand aggregator, a trend analyzer, a competitive-mention tracker, an executive summary template, and a response-suggestion system.

The variables tune the analysis to your reality. [category_count] sets how many top-level buckets feedback gets sorted into, [weighting_criteria] decides how feature requests are weighted (by ARR, segment, health score), and [threshold_shift] defines how big a sentiment swing must be before it gets flagged. [comparison_period] anchors trend detection, [competitor_names] tells the tracker who to watch for, and [report_frequency] and [escalation_team] shape the reporting and routing. The aggregation step is the core value: it groups requests worded differently into one real feature need and counts unique requesters rather than raw mentions.

When to use it

  • Feedback is pouring in from several channels and the signal is buried until something organizes it.
  • You want feature requests de-duplicated so "dark mode," "too bright," and "eye strain" collapse into one need.
  • You need a consistent categorization scheme so different people tag feedback the same way.
  • You want early warning when a category's sentiment shifts before the issue becomes widespread.
  • You need a recurring executive summary of themes, NPS trend, and urgent issues for product reviews.
  • You want competitive mentions surfaced so you know which rival capabilities customers compare you to.

Example output

You get a structured analysis framework. It includes a categorization taxonomy with [category_count] top-level categories plus subcategories and example phrases, a sentiment-scoring spec on a -5 to +5 scale that tags the product area and pulls verbatim quotes, a feature-demand aggregation method that groups synonyms and counts unique requesters weighted by [weighting_criteria], a trend-analysis approach comparing against [comparison_period] and flagging shifts beyond [threshold_shift] points, a competitive tracker for [competitor_names], a [report_frequency] executive summary template, and a response-suggestion system routing urgent items to [escalation_team].

Pro tips

  • List every real source in [feedback_channels] so the taxonomy and routing account for the formats each channel produces.
  • Keep [category_count] manageable — too many top-level buckets makes tagging inconsistent, which defeats the de-duplication goal.
  • Choose [weighting_criteria] you can actually pull; weighting by ARR is powerful only if you can join feedback to account data.
  • Set [threshold_shift] to a level that flags real emerging issues without drowning you in noise from normal monthly variance.
  • The framework defines how to analyze feedback, but running it at scale needs the model fed actual feedback batches, so plan that step.
  • Keep [competitor_names] current — an outdated competitor list means you miss mentions of whoever is actually pulling customers away.

Frequently Asked Questions

Does this prompt analyze my feedback automatically?
No, it designs the analysis framework, taxonomy, and scoring rules. To analyze real feedback you still feed batches of it into the model or wire the framework into a pipeline, because the prompt itself only produces the system, not the results.
How does it de-duplicate feature requests?
The aggregation step groups requests that express the same underlying need with different wording and counts unique requesters rather than raw mentions. This is where the real roadmap signal lives, since ten people describing one feature ten ways should register as one demand.
Can it weight feedback by customer value?
Yes, the `[weighting_criteria]` variable lets you weight requests by ARR, segment, or account health score. This only works in practice if you can connect each feedback item to the account that sent it, which the prompt assumes but cannot do for you.
Will it catch emerging issues early?
The trend-analysis step compares current sentiment against `[comparison_period]` and flags any category that shifts more than `[threshold_shift]` percentage points. Set the threshold carefully, because too low floods you with noise and too high lets real problems grow before they surface.
Engr Mejba Ahmed

Need this built for real?

Engr Mejba Ahmed

AI Developer · Software Engineer

I'm Mejba — I design and ship production AI systems, automations, and full-stack apps. If you want this turned into a working solution for your team, let's talk.

More in AI for Business & SaaS

Engr Mejba Ahmed

Engr Mejba Ahmed

AI assistant · trained on my work

👋

Hey there!

Quick Actions

WhatsApp Direct line to me

Chat on WhatsApp

+880 1723 741224 · Replies within the hour on working days

Popular Questions

Engr Mejba Ahmed is connected
Engr Mejba Ahmed is typing...
Engr Mejba Ahmed avatar

✉ Want me to follow up? Drop your email

Engr Mejba Ahmed avatar

📞 Connect Directly

Choose how you'd like to reach me

WhatsApp

+880 1723 741224

Email

mejba.13@gmail.com

✓ Details sent! I'll get back to you shortly.

Powered by OpenAI

335+

Blog Posts

25

AI Courses

63

Projects

Services & Expertise

Pricing & Process

Learning & Resources

Connect & Support