---
title: "Customer Feedback"
description: "6 posts about Customer Feedback, summarised, each linking to the original."
---

# Customer Feedback
> 6 posts about Customer Feedback, summarised, each linking to the original.

## Articles

### [How to launch with a validated idea - The Intercom Blog](https://yomu.fyi/post/how-to-launch-with-a-validated-idea-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 13, 2026
- Type: Tutorial

The post describes a three-step process for launching a validated idea, called the three I’s—Ideas, Input, and Iteration—mirroring the lean startup approach. The author explains how his team validated their idea by drafting mockups, creating a sign-up page, and running AdWords, and they got lucky when blogs shared their landing page, giving them a base of potential users for product preview sessions. They then launched a minimum viable product (MVP) and used Intercom to send surveys and automated in-app messages, creating a continuous feedback loop. To iterate, they formed a CoPilots program of users highly likely to purchase who provided weekly feedback via Google+ Hangouts in exchange for free use. The entire team was involved in reviewing interviews, and the cycle is presented as an ongoing process for SaaS startups.


### [6 Keys to Getting High-Quality &amp; Useful Customer Feedback](https://yomu.fyi/post/6-keys-to-getting-high-quality-amp-useful-customer-feedback.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post outlines six keys for collecting high-quality customer feedback: the type of customer, prompted vs. unprompted feedback, motivations, volume, repetition, and stakes. Loyal or heavy users provide more valuable feedback, and unprompted feedback often reveals unknown issues, while customers are motivated to give feedback when they have extreme experiences, leading to a J-curve distribution. Methods for collecting feedback include live chat, short surveys, and social media, and a seven-step analysis process categorizes feedback by type, theme, and code to prioritize insights. Volume protects against recency bias, repetition indicates unresolved basics, and high-stakes feedback like security loopholes requires immediate action. A case study of Albacross shows how using NPS surveys and automated follow-ups via Intercom doubled their NPS score from 12 to 30 and increased reviews on Capterra.


### [Make Sales &amp; Product meetings a win-win](https://yomu.fyi/post/make-sales-amp-product-meetings-a-win-win.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Fortnightly sales-product meetings at Intercom use a structured feedback loop to align product strategy with market needs. Sales teams first meet internally, using a shared Google Doc to categorize recent feedback and prioritize three to five items backed by concrete data such as the customer’s job title, revenue at risk, and competitor presence. The cross-functional sync includes representatives from each sales segment (SMB, Mid-Market, Enterprise) plus product owners, who ask context-gathering questions and share roadmap progress. This method replaces ad-hoc feature requests with evidence-based discussions, helping product understand customer impact and sales set realistic expectations with prospects. The process has resulted in popular features like automatic conversation routing to the right team and stronger cross-functional collaboration between sales and product teams.


### [Why you should have skin in the engineering game - The Intercom Blog](https://yomu.fyi/post/why-you-should-have-skin-in-the-engineering-game-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post compares the high-stakes feedback of professional cycling to engineering, noting that engineers in growing companies often become disconnected from customers through support teams and product managers. The author, a former cyclist, advocates for engineers to maintain ‘skin in the game’ by personally connecting with customers. Intercom enforces regular customer days for all employees to give first-hand exposure, uses GitHub integration to easily dig into real customer conversations, and encourages direct outreach for complex issues. Working through a subtle bug caused by a feature update, the author iterated directly with a customer for a week, restoring their broken workflow. This personal investment in outcomes motivates engineers and ensures their work has real impact, while the post encourages others to seek similar practices.


### [The right way to respond to feature requests - The Intercom Blog](https://yomu.fyi/post/the-right-way-to-respond-to-feature-requests-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Customer support teams frequently encounter feature requests that reveal gaps between a product and user goals, and responding effectively requires a rigorous framework. The post categorizes these requests into three types: unresolved problems with existing features, improvements to existing features, and brand new feature requests. For each type, it recommends a tailored response: educate customers on workarounds for problems without promising specific fix dates, suggest alternative existing functionality for improvements, and honestly decline new requests while acknowledging the gap and offering third-party solutions like Zapier or YouCanBookMe, sharing context about limited engineering resources. Prioritization should also consider customer lifecycle, high-value users, implementation difficulty, and feedback volume to balance satisfaction with engineering resources and long-term strategy. Closing the loop by tagging conversations in Intercom and sharing monthly customer voice reports with product managers ensures feedback drives roadmap decisions and builds long-term customer success.


### [Using Intercom to design Intercom - The Intercom Blog](https://yomu.fyi/post/using-intercom-to-design-intercom-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

A designer at Intercom explains how the team uses their own product to gather data-driven insights for design decisions, replacing intuition with evidence from real customer interactions. Support team members tag feature requests and confusing conversations, which the research team organizes by topic for easy access. In one example, the designer analyzed 120 conversations about multi-person messaging and found only 33% actually wanted that feature, while others needed handoff or transfer capabilities. In another, an automated message targeting users who sent one-to-one messages via the fully featured editor revealed within hours that the ability to duplicate messages was the missing feature. This approach ensures design solutions are based on real customer needs rather than surface-level requests.
