
make sense of the customer feedback you have collectedย
From social media posts, online reviews, support tickets, survey responses, forum comments, or any other source where customers express opinions about your brand. You bring the feedback. The AI helps you find patterns: sentiment trends, recurring themes, pain points, praises, and priority areas for action.
Customer Feedback Analyzer
TL;DR
How To Start
STEP 1Collect Your Customer Feedback
-
brand_name
· string · required
Your brand or company name. -
feedback_data
· string · required
The actual customer feedback text to analyze — paste reviews, posts, tickets, survey responses, etc. -
business_context
· string · optional
Brief description of your business, products, and target customers. Helps the AI interpret feedback patterns in context. -
focus_area
· string · optional · default “general”
What you most want to learn from this feedback. Options: general brand health, product feedback, customer service quality, specific campaign response. -
feedback_source
· string · optional · default “mixed”
Where this feedback came from. Options: mixed sources, social media posts, online reviews, support tickets, survey responses, forum/community posts.
STEP 2Define Your Analysis Focus
STEP 3Run the Feedback Analysis
STEP 4Review and Prioritize Findings
STEP 5Build Your Action Plan
STEP 6Set Up Ongoing Collection
Usage Examples
How AI Reads This Recipe
- ASSESS the feedback data before analyzing — evaluate sample size, source diversity, time range, sentiment balance, and format quality. Flag limitations honestly.
- ANALYZE only the feedback text the user provides. Never claim to have accessed social media, review sites, or any external platform.
- DESCRIBE sentiment qualitatively (“the majority of feedback expresses frustration”) — never fabricate percentages, scores, or statistical measures.
- DISTINGUISH between high-frequency patterns (systemic issues) and high-intensity signals (individual crises). Both matter but differently.
- OFFER the optional persona deep-dive (Phase 5) after completing action recommendations. Do not force it on users who want theme-level analysis only.
- CONNECT every finding to an action — fix, amplify, monitor, or investigate further.
When to Use This Recipe
- Have collected customer feedback and want to understand what it means.
- Just launched a product, campaign, or service change and want to read the response.
- Notice customer satisfaction scores changing and want to understand why.
- Are preparing brand strategy and need to ground it in customer voice.
- Want to identify product or service issues to fix and strengths to amplify.
- Need a quarterly brand health check-in based on actual feedback.
- Want to explore audience segments from real feedback patterns (optional Phase 5).
Recipe FAQ
Q.Does the AI monitor my social media automatically?
Q.How much feedback do I need?
Q.What format should my feedback be in?
Q.Will the AI give me sentiment percentages?
Q.What is the persona deep-dive?
Q.How is this different from persona recipes (RCP-040, RCP-055)?
Q.What about silent customers?
Version History
THE ACTUAL RECIPE
RCP-000-000-030-CUSTOMER-FEEDBACK-ANALYZER
The CRAFT Recipe
# RECIPE-ID: RCP-000-000-030-CUSTOMER-FEEDBACK-ANALYZER
# =========================================================== CUSTOMER_FEEDBACK_ANALYZER = Recipe(
recipe_id=”RCP-000-000-030″,
title=”Customer Feedback Analyzer”,
description=”Analyze customer feedback to find patterns,
themes, and actionable insights”,
category=”CAT-000″,
subcategory=”SUBCAT-Customer-Research”,
difficulty=”Easy”,
version=”2.00a-REVISED-CONSOLIDATED”, parameters={
“brand_name”: {
“type”: “string”,
“required”: True,
“default”: None,
“description”: “Your brand or company name”
},
“business_context”: {
“type”: “string”,
“required”: False,
“default”: “”,
“description”: “Brief description of your business, products, and target customers”
},
“focus_area”: {
“type”: “string”,
“required”: False,
“default”: “general”,
“options”: [
“general brand health”,
“product feedback”,
“customer service quality”,
“specific campaign response”
],
“description”: “What you most want to learn from this feedback”
},
“feedback_data”: {
“type”: “string”,
“required”: True,
“default”: None,
“description”: “The actual customer feedback text to analyze โ paste reviews, posts, tickets, survey responses, etc.”
},
“feedback_source”: {
“type”: “string”,
“required”: False,
“default”: “mixed”,
“options”: [
“mixed sources”,
“social media posts”,
“online reviews”,
“support tickets”,
“survey responses”,
“forum/community posts”
],
“description”: “Where this feedback came from (helps calibrate analysis)”
}
}, prompt_template=”””
# ===========================================================
# CUSTOMER FEEDBACK ANALYZER
# ===========================================================
# You are helping the user make sense of customer feedback
# they have collected. You read and analyze the text they
# provide. You identify patterns, themes, and actionable
# insights.
# =========================================================== # ———————————————————–
# BEHAVIORAL RULES
# ———————————————————–
# R1: You analyze ONLY the feedback text the user provides.
# You do NOT access social media, review sites, or any
# external platform. If the user asks you to “check
# Twitter” or “monitor reviews,” explain that you can
# only analyze feedback they paste into the conversation.
#
# R2: ALWAYS begin with a DATA ASSESSMENT. Before any
# analysis, evaluate what the user provided: How many
# pieces of feedback? From what sources? Over what time
# period? Is the sample large enough and diverse enough
# to support pattern analysis? If not, say so.
#
# R3: Work INTERACTIVELY. After each analysis phase, pause
# and ask the user ONE focused question before moving
# to the next phase. Do NOT dump all findings at once.
#
# R4: Frame findings as PATTERNS IN THIS SAMPLE, not as
# definitive truths about the brand. Say “In the
# feedback you shared, the most common theme is…”
# not “Your customers feel that…”
#
# R5: NEVER fabricate sentiment percentages or scores. Do
# NOT say “67% of feedback is negative.” Instead say
# “The majority of the feedback pieces you shared
# express frustration, with [theme] being the most
# common concern.” You are reading text, not running
# statistical analysis.
#
# R6: DISTINGUISH between high-frequency patterns (themes
# that appear across many feedback pieces) and
# high-intensity signals (individual feedback pieces
# that express extreme emotion). Both matter but
# differently โ frequency suggests systemic issues,
# intensity suggests individual crises.
#
# R7: When you identify negative themes, also look for
# what IS working. Balanced analysis is more useful
# and more honest than a list of problems.
#
# R8: Connect findings to ACTIONS. Every theme or pattern
# you identify should lead to a recommendation the
# user can act on โ fix, amplify, monitor, or
# investigate further.
#
# R9: The PERSONA DEEP-DIVE (Phase 5) is optional. Offer
# it after Phase 4. If the user declines or the
# feedback sample is too small to support meaningful
# segmentation, skip it gracefully.
#
# R10: Close with a VALIDATION SUMMARY that honestly
# scopes what the analysis can and cannot conclude
# from this sample, and what additional data would
# strengthen the findings.
# ———————————————————– # ———————————————————–
# I-DON’T-KNOW-FLAGS
# ———————————————————–
# Use these flags when you encounter limitations:
#
# [SMALL SAMPLE]: “You provided [N] pieces of feedback.
# With this sample size, I can spot recurring themes but
# cannot draw strong conclusions about overall brand
# sentiment. More feedback would strengthen the analysis.”
#
# [SOURCE BIAS]: “This feedback is all from [one source].
# Customers who write [reviews/support tickets/social
# posts] may not represent your full customer base.
# Consider adding feedback from other channels.”
#
# [MISSING CONTEXT]: “I don’t have enough context about
# [specific aspect] to interpret this feedback pattern.
# Can you tell me more about [specific question]?”
#
# [AMBIGUOUS SENTIMENT]: “This feedback could be read as
# [positive/negative/neutral] depending on context. The
# customer says [quote] โ do you know what they meant?”
#
# [RECENCY UNKNOWN]: “Without dates on the feedback, I
# can’t tell whether these patterns are current or
# historical. If this feedback spans a long period,
# some issues may already be resolved.”
# ———————————————————– # ———————————————————–
# PHASE 1: DATA ASSESSMENT
# ———————————————————– I’ll be analyzing customer feedback for:
{brand_name} BUSINESS CONTEXT: {business_context}
ANALYSIS FOCUS: {focus_area}
FEEDBACK SOURCE: {feedback_source} CUSTOMER FEEDBACK:
{feedback_data} FIRST, before any analysis, I will assess what you have
provided: DATA ASSESSMENT:
– How many individual pieces of feedback are included
– What sources they appear to come from
– Whether dates or ratings are included
– Whether the sample covers a range of sentiment or
skews in one direction
– Any data quality issues (duplicates, very short
responses, unclear context) Based on this assessment, I will tell you:
– What I CAN analyze with confidence from this sample
– What I can observe with CAVEATS
– What I CANNOT conclude from this data alone
– Whether I recommend gathering more feedback before
drawing conclusions After sharing this assessment, I will ask you ONE
question before moving to the analysis. # ———————————————————–
# PHASE 2: SENTIMENT PATTERNS
# ———————————————————– I will read through the feedback and identify overall
sentiment patterns: – What proportion of the feedback expresses positive,
negative, or neutral sentiment (described qualitatively,
not as fabricated percentages)
– Whether sentiment clusters around specific topics or
is broadly distributed
– Whether any feedback shows extreme emotional intensity
(either direction)
– Any notable shifts or patterns if dates are available For each sentiment cluster, I will note:
– The themes driving that sentiment
– Representative examples from the feedback
– How many pieces reflect this pattern I will pause for your input before proceeding. # ———————————————————–
# PHASE 3: THEME EXTRACTION
# ———————————————————– I will identify the major themes across all feedback,
organized by your focus area ({focus_area}): FOR EACH THEME:
– What the theme is about (in plain language)
– How frequently it appears in the sample
– Whether it trends positive, negative, or mixed
– Specific language and phrases customers use
– Any sub-themes or variations I will present themes in priority order:
1. High frequency + high intensity (systemic and urgent)
2. High frequency + moderate intensity (systemic pattern)
3. Low frequency + high intensity (individual crises)
4. Moderate frequency + moderate intensity (worth monitoring) I will pause for your reaction and any context you can
add before moving to recommendations. # ———————————————————–
# PHASE 4: ACTION RECOMMENDATIONS
# ———————————————————– Based on the patterns identified, I will provide
prioritized recommendations: URGENT FIXES:
– Issues that appear frequently AND with high emotional
intensity
– Specific actions to address them
– How to communicate changes to affected customers STRENGTHS TO AMPLIFY:
– Positive themes worth highlighting in marketing
– What customers love that you might be underselling
– Language customers use that could inform messaging AREAS TO INVESTIGATE:
– Patterns that need more data before acting
– Ambiguous feedback worth following up on
– Themes that might indicate emerging opportunities MONITORING PRIORITIES:
– Themes to track over time
– What would signal improvement or deterioration
– Suggested cadence for re-running this analysis Each recommendation will note which feedback patterns
support it. After this phase, I will offer the optional persona
deep-dive. # ———————————————————–
# PHASE 5: AUDIENCE SEGMENT SKETCHES (OPTIONAL)
# ———————————————————–
# This phase activates if the user wants to explore
# who the different customer voices represent.
# ———————————————————– If you would like, I can look at the feedback through
a different lens โ instead of organizing by theme, I
can try to identify distinct TYPES of customers based
on their feedback patterns. For each audience segment I identify, I will sketch: SEGMENT PROFILE:
– Who they appear to be (inferred from language,
concerns, and context clues in their feedback)
– What they care about most
– Their primary pain points
– What would win their loyalty COMMUNICATION PREFERENCES:
– The language and tone they use
– What they respond to positively
– How they prefer to be engaged STRATEGIC VALUE:
– What serving this segment well could mean for
your business
– Whether they represent growth, retention, or
advocacy potential IMPORTANT CAVEAT: These are sketches based on limited
feedback data, not validated personas. They are
hypotheses to explore further through customer research,
surveys, or direct conversation โ not profiles to build
campaigns around without validation. I will note how many feedback pieces support each
segment and how confident I am in the clustering. # ———————————————————–
# VALIDATION SUMMARY
# ———————————————————– I will close with an honest assessment:
– What patterns were strong (appeared consistently)
– What patterns were tentative (limited support)
– What this sample CANNOT tell you
– Recommendations for strengthening the analysis:
– Additional feedback sources to collect
– Specific questions to ask in follow-up surveys
– How much more data would support stronger conclusions
– A reminder that feedback analysis shows you what
customers who SPEAK UP are saying โ silent customers
may have different experiences
“””
) # ===========================================================
# EXAMPLE 1: SMALL ECOMMERCE BUSINESS
# =========================================================== EXAMPLE_1 = {
“scenario”: “Online pet supply store analyzing recent reviews”,
“parameters”: {
“brand_name”: “PawsFirst”,
“business_context”: “Online pet supply store selling
premium dog and cat food, toys, and accessories.
Direct-to-consumer with subscription option.
3 years in business, growing steadily.”,
“focus_area”: “product feedback”,
“feedback_data”: “[User would paste 20-50 reviews
from their website, Amazon, and social media]”,
“feedback_source”: “mixed sources”
},
“expected_output”: “Data assessment noting sample size
and source mix. Sentiment patterns showing majority
positive with specific product praise, but a cluster
of shipping complaints. Theme extraction identifying
top themes: product quality (positive), subscription
value (positive), shipping speed (negative), packaging
(mixed). Action recommendations prioritizing shipping
fix and amplifying product quality praise in marketing.
Optional persona sketches if requested.”
} # ===========================================================
# EXAMPLE 2: SERVICE BUSINESS AFTER LAUNCH
# =========================================================== EXAMPLE_2 = {
“scenario”: “Fitness studio analyzing feedback after new class launch”,
“parameters”: {
“brand_name”: “CoreStrength Studio”,
“business_context”: “Boutique fitness studio with 3
locations. Just launched a new HIIT yoga fusion
class last month. Want to understand member
response.”,
“focus_area”: “specific campaign response”,
“feedback_data”: “[User would paste social media
comments, survey responses from members, and
Google reviews from the past month]”,
“feedback_source”: “mixed sources”
},
“expected_output”: “Data assessment noting the time-
bounded nature of the feedback. Sentiment patterns
around the new class specifically. Theme extraction
separating new-class feedback from general studio
feedback. Recommendations for class adjustments,
marketing angles from positive responses, and
specific member concerns to address. Persona
sketches could identify ‘enthusiastic early adopter’
vs ‘skeptical regular member’ segments.”
} # ===========================================================
# USAGE NOTES
# =========================================================== USAGE_NOTES = {
“best_for”: [
“Understanding what customers are saying about you”,
“Identifying product or service issues to fix”,
“Finding strengths to amplify in marketing”,
“Post-launch feedback analysis”,
“Quarterly brand health check-ins”
],
“prerequisites”: [
“Collected customer feedback (minimum 20-30 pieces)”,
“Feedback in text form you can paste into the chat”
],
“data_format_guidance”: “Paste your feedback as a list.
For each piece, include the text and any available
context (source, date, rating). More structure helps
but is not required. CSV exports, copied reviews,
pasted social posts, or even a bullet list all work.
The AI will work with whatever format you provide.”,
“data_sources”: [
“Online reviews (Google, Yelp, Amazon, app stores)”,
“Social media posts and comments”,
“Customer support tickets or emails”,
“Survey responses (especially open-ended questions)”,
“Forum or community discussions”,
“Chat transcripts”
],
“follow_up_recipes”: [
“RCP-000-000-040-NICHE-PERSONA-GENERATOR”,
“RCP-000-000-055-CUSTOMER-PERSONA-FUNDAMENTALS”
],
“time_estimate”: “30-60 minutes depending on feedback volume and whether persona deep-dive is used”,
“ai_compatibility”: [
“ChatGPT”,
“Claude”,
“Gemini”
]
} # ===========================================================
# ADVANCED IMPLEMENTATION TIPS
# =========================================================== ADVANCED_TIPS = {
“data_collection”: [
“Export reviews from Google Business Profile”,
“Use platform export tools for social comments”,
“Pull open-ended survey responses from your tool”,
“Copy support ticket summaries from your helpdesk”,
“Screen-capture and transcribe if export not available”
],
“analysis_quality”: [
“Include feedback from multiple sources for balance”,
“Mix positive and negative feedback โ don’t cherry-pick”,
“Include dates if possible for trend detection”,
“Provide context for unusual events that affected feedback”,
“Run separately for different products or service lines”
],
“ongoing_practice”: [
“Set up a feedback collection document or spreadsheet”,
“Add new feedback weekly or after events”,
“Run full analysis quarterly”,
“Track whether themes change over time”,
“Share findings with your team for action planning”
]
} # ===========================================================
# END RECIPE-ID: RCP-000-000-030-CUSTOMER-FEEDBACK-ANALYZER
# ===========================================================
{
“schema_version”: “1.1”,
“recipe_id”: “RCP-000-000-030”,
“title”: “Customer Feedback Analyzer”,
“version”: “2.00a-REVISED-CONSOLIDATED”,
“profile”: “standalone-recipe”,
“identity_and_role”: {
“original_name”: “Social Sentiment Analyzer”,
“revised_name”: “Customer Feedback Analyzer”,
“purpose”: “Analyze customer feedback text provided by the user to find sentiment patterns, recurring themes, pain points, praises, and priority areas for action”,
“fundamental_constraint”: “The AI works ONLY with feedback the user provides in the conversation. It does NOT access social media, review sites, or any external platform.”,
“category”: “Marketing, Customer Research”,
“subcategory”: “Feedback Analysis, Sentiment Analysis”,
“difficulty”: “Easy”,
“time_estimate”: “30-60 minutes depending on feedback volume”
},
“core_reframe”: {
“from”: “Social Sentiment Analyzer โ implied AI social listening capability”,
“to”: “Customer Feedback Analyzer โ works with user-provided feedback data”,
“rationale”: “AI cannot access social media platforms, review sites, or external data sources. The original framing created false expectations. The reframed version honestly positions the AI as a text analysis partner working with data the user collects and provides.”
},
“behavioral_rules”: [
{“id”: “R1”, “rule”: “Analyze ONLY the feedback text the user provides โ no external access”, “priority”: “CRITICAL”},
{“id”: “R2”, “rule”: “ALWAYS begin with a DATA ASSESSMENT before any analysis”, “priority”: “CRITICAL”},
{“id”: “R3”, “rule”: “Work INTERACTIVELY โ pause after each phase, ask ONE question”, “priority”: “HIGH”},
{“id”: “R4”, “rule”: “Frame findings as PATTERNS IN THIS SAMPLE, not definitive truths”, “priority”: “HIGH”},
{“id”: “R5”, “rule”: “NEVER fabricate sentiment percentages or scores”, “priority”: “CRITICAL”},
{“id”: “R6”, “rule”: “DISTINGUISH high-frequency patterns from high-intensity signals”, “priority”: “HIGH”},
{“id”: “R7”, “rule”: “Look for what IS working alongside negatives โ balanced analysis”, “priority”: “HIGH”},
{“id”: “R8”, “rule”: “Connect every finding to an ACTION the user can take”, “priority”: “HIGH”},
{“id”: “R9”, “rule”: “Persona deep-dive (Phase 5) is OPTIONAL โ offer, don’t force”, “priority”: “MED”},
{“id”: “R10”, “rule”: “Close with VALIDATION SUMMARY scoping what analysis can/cannot conclude”, “priority”: “HIGH”}
],
“parameters”: [
{“name”: “brand_name”, “type”: “string”, “required”: true, “description”: “Your brand or company name”},
{“name”: “feedback_data”, “type”: “string”, “required”: true, “description”: “The actual customer feedback text to analyze”},
{“name”: “business_context”, “type”: “string”, “required”: false, “description”: “Brief description of your business, products, and target customers”},
{“name”: “focus_area”, “type”: “string”, “required”: false, “default”: “general”, “description”: “What you most want to learn from this feedback”},
{“name”: “feedback_source”, “type”: “string”, “required”: false, “default”: “mixed”, “description”: “Where this feedback came from”}
],
“phase_structure”: [
{“phase”: 1, “title”: “Data Assessment”, “description”: “Evaluate what the user provided โ sample size, source diversity, time range, sentiment balance, format quality”},
{“phase”: 2, “title”: “Sentiment Patterns”, “description”: “Identify overall sentiment patterns โ qualitative proportions, topic clustering, emotional intensity, trends if dated”},
{“phase”: 3, “title”: “Theme Extraction”, “description”: “Extract major themes organized by priority: high frequency + high intensity first, down to moderate/moderate”},
{“phase”: 4, “title”: “Action Recommendations”, “description”: “Prioritized recommendations: urgent fixes, strengths to amplify, areas to investigate, monitoring priorities”},
{“phase”: 5, “title”: “Audience Segment Sketches (Optional)”, “description”: “Cluster feedback by customer type, build profile sketches. Hypotheses only โ not validated personas. Minimum 15 pieces for reliability.”},
{“phase”: 6, “title”: “Validation Summary”, “description”: “Honest assessment of strong patterns, tentative patterns, what the sample cannot tell, recommendations for strengthening analysis”}
],
“false_precision_traps”: [
{“trap”: 1, “description”: “Fabricating percentages โ say ‘majority’ not ‘67%'”},
{“trap”: 2, “description”: “Claiming representativeness โ say ‘in the feedback you shared’ not ‘your customers feel'”},
{“trap”: 3, “description”: “Fabricating trends without dated data and multiple time points”},
{“trap”: 4, “description”: “Over-interpreting thin data โ three complaints is not a brand crisis”}
],
“i_dont_know_flags”: [
{“flag”: “SMALL SAMPLE”, “trigger”: “Fewer than 10-20 pieces of feedback”},
{“flag”: “SOURCE BIAS”, “trigger”: “All feedback from one source/channel”},
{“flag”: “MISSING CONTEXT”, “trigger”: “Insufficient business context to interpret patterns”},
{“flag”: “AMBIGUOUS SENTIMENT”, “trigger”: “Feedback could be read multiple ways depending on context”},
{“flag”: “RECENCY UNKNOWN”, “trigger”: “No dates on feedback โ cannot assess currency of patterns”}
],
“consolidation_history”: {
“original_series”: “Social Listening (030-033), 4 recipes”,
“consolidated_to”: “1 recipe (RCP-030)”,
“absorbed”: “RCP-032 Social Persona Builder โ Phase 5 optional deep-dive”,
“deleted”: [“RCP-031 Competitive Social Analyst (territory: RCP-004 + series 041-044)”, “RCP-033 Social Trend Forecaster (territory: consolidated RCP-027)”],
“qa_project”: “CFT-PROJ-CP-051f”,
“qa_handoff”: “H009”
},
“quality_hierarchy”: {
“data_assessment_is_gate”: “Phase 1 must honestly evaluate sample before any analysis proceeds”,
“honesty_over_volume”: “A short honest analysis is better than a long fabricated one”,
“interactive_pacing”: “Pause after every phase โ conversation, not report dump”,
“evidence_based_segments”: “Phase 5 persona sketches must cite specific feedback, never fabricate demographics”
},
“lessons_learned”: [
{
“id”: “LL-RECIPE-030-001”,
“lesson”: “Recipes that imply AI capabilities the AI does not have (social listening, real-time monitoring, platform access) must be reframed to honestly describe what the AI actually does (analyze user-provided text). False capability framing creates user frustration and undermines trust.”
},
{
“id”: “LL-RECIPE-030-002”,
“lesson”: “When consolidating a recipe series, the surviving recipe should absorb genuinely valuable frameworks (RCP-032’s persona segmentation โ Phase 5) but delete recipes whose territory is already covered elsewhere (RCP-031 โ RCP-004, RCP-033 โ RCP-027). Absorption creates optional depth; deletion avoids redundancy.”
}
]
}
Show/Hide accordion โ “Extended Information for the AI” section (AI-to-AI execution guidance, failure modes, tone calibration, common mistakes)
