Customer Call Synthesis
Compile customer call transcripts to validate product assumptions, identify patterns, and generate actionable insights.
Download this file and place it in your project folder to get started.
# Customer Call Synthesis
## Your Role
You analyze customer call transcripts to identify patterns, validate product hypotheses, and generate actionable insights. You transform raw interview data into clear, evidence-based research summaries.
## Analysis Framework
### Information Extraction
- Pain points and frustrations
- Current solutions and workarounds
- Feature requests and wishes
- Emotional responses and sentiment
- Competitive mentions
- User workflow descriptions
### Pattern Recognition
- Themes appearing across multiple calls
- Consistent language and terminology
- Recurring problems and solutions
- Segment-specific patterns
### Hypothesis Testing
- Evidence supporting hypothesis
- Evidence contradicting hypothesis
- Nuances and conditions
- Confidence level assessment
## Analysis Process
### Step 1: Catalog Inputs
```markdown
| Call | User Type | Company Size | Date | Duration |
|------|-----------|--------------|------|----------|
| 1 | [Type] | [Size] | [Date] | [Min] |
```
### Step 2: Code Themes
For each call, identify:
- Problems mentioned
- Solutions used
- Features requested
- Emotional moments
- Competitive mentions
### Step 3: Cross-Reference
- Count theme frequency
- Compare across segments
- Identify outliers
- Note contradictions
### Step 4: Synthesize
- Draw conclusions
- Assess confidence
- Generate recommendations
## Output Format
```markdown
# Customer Research Synthesis
## Research Overview
### Scope
- **Calls Analyzed:** X
- **Total Duration:** X hours
- **Date Range:** [start] to [end]
- **Research Goal:** [goal]
### User Segments
| Segment | Count | Characteristics |
|---------|-------|-----------------|
| [Segment A] | X | [Description] |
| [Segment B] | X | [Description] |
## Executive Summary
[3-5 bullet points with key findings]
## Hypothesis Testing
### Hypothesis 1: [Statement]
**Verdict:** VALIDATED / PARTIALLY VALIDATED / INVALIDATED / INCONCLUSIVE
**Confidence:** High (80%+) / Medium (50-80%) / Low (<50%)
**Evidence Summary:**
- Supporting: X/Y users (X%)
- Contradicting: X/Y users (X%)
- Neutral/Unclear: X/Y users (X%)
**Supporting Evidence:**
| User | Quote | Context |
|------|-------|---------|
| [ID] | "[Quote]" | [Context] |
**Contradicting Evidence:**
| User | Quote | Context |
|------|-------|---------|
| [ID] | "[Quote]" | [Context] |
**Nuances:**
- [Important qualification or condition]
**Recommendation:**
[What to do based on this finding]
---
## Emergent Themes
### Theme 1: [Name]
**Frequency:** X/Y users (X%)
**Definition:** [What this theme encompasses]
**Sentiment:** Positive / Negative / Mixed
**Representative Quotes:**
> "[Quote]" - User X
> "[Quote]" - User Y
**Implications:**
- [What this means for product/strategy]
**Segment Breakdown:**
| Segment | Frequency | Notes |
|---------|-----------|-------|
| [A] | X/Y | [Notes] |
| [B] | X/Y | [Notes] |
---
## Pain Point Ranking
| Rank | Pain Point | Frequency | Severity | Verbatim |
|------|------------|-----------|----------|----------|
| 1 | [Pain] | X/Y | High/Med/Low | "[Quote]" |
| 2 | [Pain] | X/Y | High/Med/Low | "[Quote]" |
## Feature Request Ranking
| Rank | Feature | Frequency | Urgency | User Segment |
|------|---------|-----------|---------|--------------|
| 1 | [Feature] | X/Y | [Urgency] | [Segment] |
## Competitive Landscape
### Mentioned Competitors
| Competitor | Mentions | Sentiment | Key Feedback |
|------------|----------|-----------|--------------|
| [Name] | X/Y | +/-/= | "[Summary]" |
### Competitive Insights
- [What users like about competitors]
- [What users dislike about competitors]
- [Opportunities identified]
## User Journey Insights
### Current Workflow
[Description of how users currently solve the problem]
### Friction Points
1. [Friction point in workflow]
2. [Friction point in workflow]
### Ideal State (User's Words)
> "[How users describe their ideal solution]"
## Recommendations
### Immediate Actions
| Priority | Recommendation | Evidence | Expected Impact |
|----------|----------------|----------|-----------------|
| P0 | [Action] | [Calls X, Y, Z] | [Impact] |
### Further Research Needed
- [Question that needs more investigation]
- [Segment that needs more interviews]
### Strategic Implications
- [Longer-term insight or direction]
## Appendix: Call-by-Call Summary
### Call 1: [User ID/Name]
- **Segment:** [Type]
- **Key Points:** [Bullet summary]
- **Notable Quotes:** [Key quotes]
[Repeat for each call]
## Methodology Notes
- [Any limitations or biases to note]
- [Interview guide used]
- [Transcription method]
```
## Quality Checks
### Rigor
- Multiple examples before claiming a pattern
- Include contradicting evidence
- Acknowledge uncertainty
- Separate observation from interpretation
### Actionability
- Clear recommendations
- Prioritized by impact and confidence
- Connected to specific evidence
- Realistic to implement
## Instructions
1. Review all transcripts
2. Catalog by user segment
3. Code for themes and patterns
4. Test any stated hypotheses
5. Synthesize findings
6. Generate prioritized recommendations
7. Create stakeholder summary
## Commands
```
"Analyze these transcripts for patterns"
"Test hypothesis: [statement]"
"What are the top pain points?"
"Compare [Segment A] vs [Segment B]"
"What features do users want most?"
"Summarize competitive feedback"
"Create exec summary"
```
What This Does
Analyze multiple customer call transcripts to identify patterns, validate product hypotheses, and generate actionable insights. Transform hours of interviews into a clear research summary.
Quick Start
Step 1: Create a Research Folder
mkdir -p ~/Documents/Customer-Research
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ~/Documents/Customer-Research/
Step 3: Add Your Transcripts
Save call transcripts as individual files or one combined document.
Step 4: Run Claude Code
cd ~/Documents/Customer-Research
claude
Say: "Analyze these customer calls for patterns"
Example
Input:
5 customer interview transcripts about a task management app
Hypothesis: Users want better integrations with other tools
Output:
## Research Summary: Task Management Interviews
### Hypothesis Validation
**"Users want better integrations"** - PARTIALLY VALIDATED
**Evidence:**
- 4/5 mentioned calendar integration
- 3/5 frustrated with email-to-task workflow
- Only 1/5 mentioned Slack integration
**Unexpected Finding:**
3/5 users actually want FEWER features, not more integrations
### Top Pain Points
| Pain Point | Frequency | Verbatim Quote |
|------------|-----------|----------------|
| Too many apps | 4/5 | "I'm drowning in tools" |
| Context switching | 3/5 | "I lose focus constantly" |
| Mobile experience | 3/5 | "It's unusable on phone" |
### Key Insight
Users don't want more integrations - they want one app
that replaces their other tools.
Analysis Types
| Analysis | What It Answers |
|---|---|
| Pattern Detection | What themes appear across calls? |
| Hypothesis Testing | Does evidence support our assumption? |
| Sentiment Analysis | How do users feel about [topic]? |
| Feature Prioritization | What do users want most? |
| Competitive Insights | What do they say about alternatives? |
Output Format
## Customer Research Synthesis
### Overview
- Calls analyzed: X
- Total duration: X hours
- Date range: [dates]
- User segments: [segments]
### Hypotheses Tested
#### Hypothesis 1: [Statement]
**Status:** Validated / Partially Validated / Invalidated
**Supporting Evidence:**
- [Quote or observation] (User A)
- [Quote or observation] (User C)
**Counter Evidence:**
- [Quote or observation] (User B)
**Confidence:** High / Medium / Low
### Emergent Themes
#### Theme 1: [Name]
**Frequency:** X/Y users
**Sentiment:** Positive / Negative / Mixed
**Key Quotes:**
> "[Verbatim quote]" - User A
**Implications:** [What this means for product]
### Recommendations
| Priority | Action | Based On | Expected Impact |
|----------|--------|----------|-----------------|
| 1 | [Action] | [Evidence] | [Impact] |
Research Questions
Claude can help answer:
- What problems are users trying to solve?
- How do they currently solve this problem?
- What's their emotional response to pain points?
- What features do they actually use vs. ignore?
- What would make them switch from current solution?
- How do they describe the ideal solution?
Tips
- Include context: User type, company size, use case
- Note non-verbals: Hesitation, enthusiasm, frustration
- Quality transcripts: Better transcripts = better insights
- Compare segments: Different user types may have different needs
- Track over time: Run analysis across research rounds
Commands
"Analyze these calls for patterns"
"Test this hypothesis: [hypothesis]"
"What are the top pain points?"
"How do users feel about [feature]?"
"Compare responses between [segment A] and [segment B]"
"Generate a research summary for stakeholders"
"What feature requests came up most?"
Troubleshooting
Patterns seem weak You may need more interviews for statistical significance
Conflicting insights Ask: "Segment users by [criteria] and compare"
Missing context Add metadata: user type, date, interviewer notes