Customer Support
Go undercover in Customer Support for one or multiple days to discover customer's pains & needs.
What is Customer Support?
Customer Support undercover validation is a hands-on research technique where founders, product managers, or team members spend dedicated time working directly with customer support to uncover real user pain points and unmet needs. By immersing yourself in actual customer conversations, complaints, and requests, you gain unfiltered access to authentic user feedback that might never reach traditional feedback channels.
This approach provides invaluable qualitative insights into what customers actually struggle with versus what you think they need. Unlike surveys or interviews that can be influenced by social desirability bias, customer support interactions reveal genuine frustrations and desires when users are seeking help. The method is particularly powerful because customers contacting support are typically experiencing acute problems, making their feedback highly actionable for product development and validation decisions.
The technique works best when you can observe patterns across multiple customer interactions rather than isolated incidents. By spending full days embedded with support teams, you'll start recognizing recurring themes, common language customers use to describe problems, and gaps between your product's intended use and actual user behavior.
When to Use This Experiment
• Early-stage startups looking to validate initial problem assumptions before building complex solutions • Product teams preparing to prioritize feature development based on real user pain points • Companies experiencing high churn rates or customer dissatisfaction without clear understanding of root causes • Before major product pivots to ensure you understand current customer needs deeply • When traditional user research feels disconnected from actual customer experience • Scaling companies where leadership has lost direct contact with customer pain points • Prior to launching new features to understand how existing functionality creates friction • When customer satisfaction scores are declining but feedback is vague or inconsistent
How to Run This Experiment
-
Coordinate with Customer Support Team - Schedule 1-3 full days to work alongside support staff. Ensure they understand your goals and get permission to observe/participate in customer interactions while maintaining privacy standards.
-
Prepare Documentation Tools - Set up systems to capture insights in real-time: spreadsheets for categorizing issues, note-taking templates for common themes, and voice recording tools if permitted for later analysis.
-
Handle Real Customer Interactions - Don't just observe - actually respond to tickets, live chats, or phone calls under supervision. This hands-on approach reveals nuances you'd miss as a passive observer.
-
Track Patterns and Recurring Themes - Document frequency of different complaint types, common language customers use, workarounds they've created, and features they request repeatedly.
-
Conduct Mini-Interviews During Interactions - When appropriate, ask follow-up questions to understand the broader context behind customer issues: "How long has this been a problem?" or "What would ideal solution look like?"
-
Categorize Findings by Impact and Frequency - Group insights into themes like usability issues, missing features, pricing concerns, or onboarding problems. Rank by how often they occur and potential business impact.
-
Validate Insights with Support Team - Review your observations with experienced support staff to confirm patterns and get their perspective on long-term trends you might have missed.
-
Create Actionable Recommendations - Transform insights into specific, testable hypotheses about customer needs that can inform product decisions or trigger additional validation experiments.
Pros and Cons
Pros
• Authentic, unfiltered feedback from customers experiencing real problems in natural settings • Cost-effective validation requiring only time investment with no additional tools or research costs • Immediate pattern recognition across multiple customer touchpoints in concentrated timeframe • Builds empathy and deep customer understanding that influences better product decisions • Reveals language customers actually use to describe problems, improving marketing and communication
Cons
• Limited to existing customers who contact support, missing insights from silent churners or non-users • Potential bias toward negative experiences since most support interactions involve problems rather than positive feedback • Time-intensive requiring multiple full days to gather meaningful patterns and insights • May lack broader market context beyond your current customer base and their specific use cases • Requires existing customer support function making it unsuitable for pre-launch or very early-stage startups
Real-World Examples
Airbnb's founders famously spent extensive time handling customer support personally during their early years, which helped them discover that professional photography was a major factor in booking success. This insight, gained through direct customer interactions, led to their professional photography service that significantly improved host listings and platform growth.
HubSpot's product team regularly embeds with customer support to understand user struggles with their marketing automation platform. During one such session, they discovered customers were spending hours manually creating email sequences that could be automated. This insight led to the development of workflow templates that reduced customer setup time and improved satisfaction scores.
Buffer's leadership team maintains a practice of spending time in customer support quarterly, which helped them identify that customers were confused about optimal posting times across different social platforms. These support conversations revealed the need for their Smart Schedule feature, which automatically determines the best times to post content based on audience engagement patterns.