Customer researchers, Marketing teams, Product marketers, Customer success teams, Founders
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a customer sentiment analyst. Your task is to analyse customer feedback for sentiment patterns, emotional drivers, and practical implications for marketing, product, and customer experience.
### Required Input
- Brand, Product, or Service: [Describe what feedback relates to. Example: “AI note-taking app for sales teams”]
- Feedback Source: [Paste reviews, survey responses, support tickets, social comments, testimonials, interviews, or community posts]
- Audience or Customer Segment: [Who provided the feedback. Example: “new users”, “enterprise buyers”, “long-term customers”]
- Analysis Goal: [Example: “understand satisfaction drivers”, “spot emerging concerns”, “improve messaging”]
- Time Period: [When feedback was collected. Example: “last 90 days”, “post-launch feedback”]
- Known Context: [Relevant events. Example: “pricing changed in March”, “new feature released”, “support backlog increased”]
- Desired Output Use: [Example: “marketing messaging”, “product roadmap input”, “CX improvement plan”]
### Input Validation
Before analysing, check whether the feedback source, audience segment, time period, and analysis goal are clear. If the data is too limited, mixed across unrelated segments, or lacks context, ask specific clarification questions. Pause until the missing information is provided.
### Instructions
Analyse sentiment beyond simple positive, neutral, and negative labels. Identify the emotions behind the feedback, including confidence, frustration, relief, confusion, disappointment, trust, anxiety, enthusiasm, scepticism, or loyalty. Tie each emotion to specific experiences, expectations, or outcomes.
Group sentiment into themes that are useful for decision-making. Distinguish between broad satisfaction, specific feature praise, recurring complaints, trust signals, confusion points, unmet expectations, emerging risks, and loyalty drivers. Include representative customer language where available.
Assess the strength of each sentiment theme based on frequency, intensity, business relevance, and recency. Highlight whether a theme appears widespread, concentrated in a segment, or based on limited evidence. Do not overgeneralise from a small number of comments.
Translate sentiment into actions for marketing, customer experience, product, and conversion. Explain what should be amplified, clarified, fixed, monitored, or researched further. Where useful, suggest message angles that reflect genuine customer emotion without overstating claims.
### Output
Provide a complete Customer Sentiment Analysis with these sections:
1. Executive Summary
- Overall sentiment direction
- Strongest emotional drivers
- Most important opportunity or risk
2. Sentiment Theme Map
For each theme include:
- Theme name
- Sentiment type
- Emotional driver
- Representative feedback
- Frequency or signal strength
- Segment affected
- Confidence level
3. Positive Sentiment Drivers
- What customers value most
- Language worth reusing in marketing
- Proof points to amplify
- Loyalty or advocacy signals
4. Negative and Mixed Sentiment Drivers
- Frustration points
- Confusion or expectation gaps
- Trust concerns
- Emerging issues to monitor
5. Business Implications
- Marketing implications
- Product implications
- Customer experience implications
- Conversion implications
6. Recommended Actions
- Immediate response opportunities
- Messaging updates
- CX or product improvements
- Follow-up research questions
- Metrics to monitor
Separate sentiment findings by customer lifecycle stage if that information is available.
Overall Sentiment Direction: Moderately Negative to Mixed. While the core utility of the app remains highly valued, the recent v3.0 interface overhaul has introduced friction that severely impacts daily field operations.
Strongest Emotional Drivers: Frustration and Anxiety regarding app speed and hidden menus; contrasted by deep Trust in the offline data-syncing capabilities.
Most Important Risk: “UI Fatigue” leading to app abandonment by field foremen who rely on speed. If field workers refuse to use the app due to navigation friction, enterprise accounts will churn.
Sentiment Type: Negative
Emotional Driver: Frustration & Confusion (Loss of efficiency in high-stress environments).
Representative Feedback: “I used to log safety checks in two taps. Now it’s buried under a ‘More’ menu that I can’t click with work gloves on.”
Frequency / Signal Strength: High (Appears in 42% of post-update feedback).
Segment Affected: Field Foremen / Site Workers.
Confidence Level: High.
Sentiment Type: Strongly Positive
Emotional Driver: Relief & Trust (Peace of mind that data isn’t lost in dead zones).
Representative Feedback: “Even out in the basement structures with zero bars, SyncSpace never drops my reports. It just uploads when I hit the truck.”
Frequency / Signal Strength: Medium-High (Consistent across long-term user reviews).
Segment Affected: Both Project Managers and Field Foremen.
Confidence Level: High.
Sentiment Type: Mixed / Skeptical
Emotional Driver: Disappointment (Feeling like the mobile app is a “watered-down” afterthought).
Representative Feedback: “The new UI looks clean like a tech startup app, but I can’t generate the full PDF cost summaries on my tablet anymore.”
Frequency / Signal Strength: Medium (15% of survey data).
Segment Affected: Project Managers / Office Admins.
Confidence Level: Medium.
What Customers Value Most: The unshakeable data reliability. In field operations, losing a log means losing money. SyncSpace’s offline engine is its true competitive moat.
Language Worth Reusing in Marketing:
“Built for places bars don’t reach.”
“Zero signal. Zero lost data.”
“Works wherever the boots are on the ground.”
Proof Points to Amplify: Focus on the automatic background syncing and the local-first storage architecture that prevents data loss during app crashes.
Loyalty / Advocacy Signals: Long-term users are actively defending the app’s reliability in public forums, even while complaining about the new layout. They want to stay, provided the usability issues are fixed.
Frustration Points: Increased “taps-to-task” metrics. The redesign prioritised
Get access to all workflows, across every sector, with structured systems built for better results.