What are some examples of voice of customer data?

Voice of customer data includes survey responses (NPS, CSAT, CES), in-app feedback, community forum submissions, social media mentions, online reviews, support ticket themes, and behavioral signals like session recordings, cart abandonment, and feature non-usage. Both solicited data (where you ask customers directly) and unsolicited data (where customers express views without being prompted) count as VoC. The distinction matters for program design: solicited feedback is easier to structure; unsolicited data often surfaces customer pain points you didn't know to ask about.

What is a real-world example of a successful VoC program?

Intuitive Health built a VoC program around emergency care patient feedback: surveys emailed within 24 hours of a visit, real-time detractor alerts to location leaders, and a resolution process targeting 36 to 48 hours. The outcome was an NPS of 81 in an industry where negative scores are typical. Just Eat closes 97% of detractor cases within 48 hours on their B2B restaurant partner side. In both cases, the score followed the process design, not the other way around.

Which industries benefit most from VoC programs?

Every industry benefits. The form changes, not the underlying value. Healthcare uses VoC to improve patient outcomes and meet compliance requirements simultaneously. Retail and e-commerce use it to develop products customers want and reduce returns. SaaS companies use it to prioritise roadmaps and reduce customer churn. Financial services brands compete on experience where product features are increasingly similar. Travel and hospitality brands use it to close the gap between guest expectations and operational reality. The mechanics are consistent across all of them: collect, analyse, act, close the loop.

Can small companies run VoC programs like the ones in these examples?

Yes. Intuitive Health started with six locations in Texas. Monzo built its community feedback engine when it had a few hundred beta users. The programs that work are not defined by company size. They are defined by designing the closed-loop workflow before launching the survey and starting with one touchpoint rather than trying to cover the entire customer journey at once.

What is the difference between a VoC program and a customer satisfaction survey?

A customer satisfaction survey measures how a customer felt about a single interaction at a specific moment. A VoC program is the broader system around that: which touchpoints to survey, how signals from multiple sources get unified, who receives the data, and what workflow closes the loop when a problem surfaces. The survey is one input into a VoC program. It is not the program itself.

14 Voice of Customer Examples: Real Programs by Industry

TL;DR

Running a VoC program and running a useful one are different things. The gap shows up in what happens after the responses arrive.
Every strong example here follows the same three-part pattern: a specific collection method, an insight that wasn't already obvious, and a change that followed.
Healthcare brands use department-level real-time feedback; retail brands like Starbucks and LEGO built product lines directly from customer ideas.
Netflix discovers 80% of watched content through behavioral signals, not user search. That's what unsolicited VoC looks like at scale.
USAA's NPS of 75 in a sector averaging 34 traces directly to reducing customer effort, not just measuring satisfaction.
Just Eat closes 97% of detractor cases within 48 hours. That's the gap between VoC as measurement and VoC as management.

Running a VoC program and running a useful one aren't the same thing. The first requires a survey tool and a distribution list. The second requires a decision about what changes when the feedback comes in. Design around that answer before a single survey goes out.

The 14 examples here span five industries: healthcare, retail, SaaS, banking, and travel. Each follows the same frame: what they collected, what it revealed, and what changed. A voice of customer example is only worth studying if something moved at the end.

What Makes a Voice of Customer Example Worth Studying

Not every program that collects customer data counts. Plenty of companies run annual NPS surveys, file away the results, and call it VoC. That's data collection. Not voice of customer.

Three things make an example worth learning from.

A specific method, not just "surveys." Exit intent on a pricing page tells you something different from a post-discharge form. In-app customer effort score immediately after a key task is different from quarterly email NPS. The channel, timing, and trigger are part of the program design, not afterthoughts.

An insight that wasn't already obvious. If your feedback confirmed what everyone suspected, you didn't need a program. The examples here uncovered something that changed a decision: a product feature that emerged from a community forum, a satisfaction gap between departments that aggregate scores were permanently hiding.

A change that followed. This is where most programs collapse. The examples below are notable because the loop closed. A product got built. A detractor case got resolved within 48 hours. A process got redesigned. That closure is the whole point. Everything before it is setup.

For a deeper look at structuring the surveys that feed each of these programs: voice of customer surveys

Voice of Customer Examples in Healthcare

Healthcare is where VoC carries the highest operational stakes. Since 2012, HCAHPS patient satisfaction scores directly influence hospital reimbursements under the Hospital Value-Based Purchasing Program. Around 30% of Value-Based Purchasing calculations are HCAHPS-based. That financial pressure has pushed healthcare organisations well past the annual survey.

Cleveland Clinic: Department-Level Scores, Not Rollups

Cleveland Clinic runs a real-time patient feedback program where survey results, complete with benchmark comparisons and performance indicators, sit on an internal dashboard accessible to every leader and manager in the system.

The design decision that matters: results are broken down by department, not just overall. Nurses track "communication with nurses" as a distinct HCAHPS category. Before this structure was in place, according to a Brandeis University case study on the Clinic's patient experience transformation, HCAHPS scores weren't posted or discussed at floor level. Some nurses didn't know the hospital measured patient satisfaction at all.

Surfacing department-level scores changed behavior. When a unit could see its own number against a benchmark, ownership shifted from the executive team to the care team. That's the insight rollup scores permanently hide: which unit needs attention, not just whether the overall number is up.

Aggregate scores are useful for board reporting. They're almost useless for driving change at the point of service.

Intuitive Health: Closing the Detractor Loop in 36–48 Hours

Intuitive Health, a network of freestanding emergency rooms in Texas, set one specific goal for their VoC program: reduce the time between a bad patient experience and the moment someone follows up on it.

Their setup: surveys go out within 24 hours of a visit. Non-responders get a reminder at 36 hours. When a detractor or passive score comes in, real-time notifications fire to location leaders. The case stays open until resolved, typically in 36 to 48 hours.

The outcome: an NPS of 81, comparable to top consumer retail brands, in an emergency care environment where negative scores are the norm. Response rates hit 24%, well above industry benchmarks.

The takeaway isn't the NPS number. It's the sequence. Intuitive Health designed the closed-loop workflow before the survey launched: notification triggers, accountability structure, resolution process. The survey was inserted into that system. Most teams do this in the wrong order, launching the survey and hoping someone acts on the results.

For how healthcare organisations build programs that meet both compliance and experience goals: voice of customer best practices in healthcare

Voice of Customer Examples in Retail and E-Commerce

Retail interactions are high-volume, often anonymous, and brief. Getting useful customer feedback from a transaction that lasts three minutes takes a different approach from healthcare or B2B.

Starbucks: Customers Who Built the Menu

My Starbucks Idea launched in 2008. Customers could submit, vote on, and comment on ideas for new products, store improvements, and company initiatives. Over 70,000 ideas came in the first year. By 2013, more than 150,000 had been submitted and approximately 277 implemented.

Free in-store Wi-Fi came from it. So did the birthday reward program and cake pops, which Starbucks now sells millions of annually.

What's worth studying isn't the headline products. It's the mechanism. Starbucks published the status of every idea: under review, in development, implemented, or declined. Customers could track their submission in real time. That transparency closed the feedback loop publicly and made the program worth participating in.

Most community-based VoC programs fail because submissions go into a void and customers stop sending them. Starbucks built a structure where the void was visibly absent. Customer loyalty metrics improved alongside participation, with higher retention rates among customers who engaged with the platform.

LEGO: Fan-Submitted Ideas That Become Real Products

LEGO Ideas lets fans submit and vote on concepts for new sets. When a design reaches 10,000 votes, the LEGO team reviews it for commercial viability. Successful ones go into production, credited to the original creator.

The Ghostbusters Ecto-1 set came from this program. So did the Big Bang Theory set and the NASA Women of NASA set. Several became commercial hits.

What LEGO does differently from most feedback programs: they built a public commitment mechanism. A submission that hits 10,000 votes isn't just a suggestion. It's a trackable milestone that triggers a formal review. Customers know the threshold. They know what happens when it's hit. And they trust the process because it's produced products they can buy on shelves.

That trust is what drives sustained participation. And sustained participation is what makes the VoC data rich enough to actually use.

For how retail brands structure their VoC approach: voice of customer best practices in retail

Voice of Customer Examples in SaaS and Technology

SaaS companies have an advantage most industries don't: direct access to users inside the product, during the exact workflows they're trying to understand. That proximity raises the bar for what a useful VoC program looks like.

Figma: Co-Creation as Product Strategy

Figma's "Suggest a Feature" forum has over 4,500 topics and 26,000+ replies. Product teams actively monitor it. When features from the forum ship, Figma credits the community explicitly. Their 2024 product releases used the phrase "We shipped it, you shaped it."

That attribution isn't just messaging. It closes the loop in a public, visible way that increases future participation. When users see a request they posted six months ago become a shipped feature, the quality of subsequent submissions improves. They know it goes somewhere.

The subtler point: the forum gives Figma's product team access to the emotional texture of requests. Not just what users want, but how urgently they want it and how they describe the problem. A satisfaction score doesn't carry that. Qualitative feedback, specifically actual customer language grouped by theme and tracked over time, does.

Typeform: Tying NPS Directly to the Product Roadmap

At the Customer Success Summit in 2016, Typeform's Director of Customer Success David Apple described how the company built a system around their NPS data called "Customer Voice."

NPS responses were tagged and categorised, then tied to internal data sources. The dashboard showed the top feature requests and major customer pain points. Critically, it also tracked whether shipping a new feature actually reduced support ticket creation afterward.

That last piece is underrated. Most product teams ship a feature and move on. Typeform built a feedback loop that measured whether the fix worked by tracking what happened to support volume next. If a feature went live and tickets went up, the customer problem hadn't been solved. That's VoC being used as a measurement tool for product decisions, not just an input to them.

For how to structure and act on VoC data across your program: voice of customer analytics

Netflix: 80% of Content Discovered Through Behavioral Signals

Netflix doesn't rely on customers telling it what to watch. It watches what they do.

Viewing history, thumbnail interactions, search queries, episode abandonment points, time of day, device type. All of it feeds the recommendation algorithm. Netflix has stated that over 80% of content watched on the platform is discovered through those recommendations, not through user-initiated search. Personalised thumbnail A/B testing, which serves images tailored to individual viewing behavior, increases click-through rates by around 30%.

No survey. No focus group. Continuous, observed customer behavior feeding directly into product decisions: which content to acquire, how to present it, when to surface it.

The lesson: behavioral signals are customer feedback. Session duration, feature non-usage, search queries that don't convert, abandonment points. These are customer voices that don't require anyone to fill out a form. Most organisations collect them. Few treat them as VoC data.

More on the tools that support multi-channel VoC collection: voice of customer tools

Voice of Customer Examples in Banking and Fintech

NPS benchmarks for traditional banks have historically sat in negative or near-zero territory. The brands pulling away from that average share one thing: they treat customer feedback as a product input, not a compliance output.

USAA: Effort Reduction as the Core VoC Insight

USAA holds an NPS of 75 in banking and 76 in insurance. The sector average is 34. That gap doesn't come from better marketing. It comes from a deliberate, sustained strategy of reducing customer effort at high-frequency touchpoints.

Customers can check their balance via text message. After a car accident, they can file a claim remotely by attaching photos and voice recordings through the app. Each of these started as a customer pain point surfaced through VoC data. The insight wasn't "customers want a text balance feature." It was "customers experience friction at moments that matter most, and removing that friction directly affects loyalty scores."

MIT Sloan research on USAA's transformation documented how the bank's IT organisation built its roadmap directly around reducing customer effort at key touchpoints. The NPS of 75 is an outcome. The VoC program is the friction-detection engine that produced it.

Monzo: Community-Driven Product Decisions at Scale

Monzo's community forum started as a feedback channel for its first few hundred beta users. It became a public product co-creation engine with tens of thousands of participants.

"Pots" is one of Monzo's most-used tools, letting users set aside money in labelled sub-accounts. It started as a community suggestion for "folders" or "buckets." Monzo took the idea, developed it, and shipped it. Monzo Labs, the bank's early access program, runs each new feature through a dedicated community thread before general release. Existing customers give direct input before the product decision is final.

80% of Monzo's new customer acquisition comes through referrals from existing customers. That figure doesn't come from good advertising. It comes from customers who consistently feel their feedback shapes the product.

Monzo also uses social listening through Brandwatch, tracking customer conversations across 14 million customers to separate genuinely high-demand requests from vocal-but-niche ones. "We can say this is noisy or trending upwards and we can tell the wider story," their team described when evaluating a specific feature request. Volume and importance are different signals. Treating them as the same is how teams end up building features nobody needed.

For VoC programs in financial services and insurance: voice of customer best practices in insurance

Voice of Customer Examples in Travel and Hospitality

Travel is a high-emotion category. The gap between what guests expect and what they experience is felt more acutely here than almost anywhere else. The window for service recovery is narrow.

Marriott: Real-Time Loop Closure Through GuestVoice

Marriott uses guestVoice, a feedback platform built with Medallia, to collect and act on guest feedback across its global portfolio. Post-stay surveys go out after every visit, covering room comfort, service quality, and overall experience. The platform also syncs social media comments alongside survey results, giving property managers a unified view of guest sentiment across channels.

What's documented in Medallia's case study: hundreds of thousands of Marriott guests have received a direct response through the guestVoice platform as a result of their feedback. Not just a data point logged to a dashboard. A direct reply from the property.

Property managers can also message guests via SMS during a stay to resolve issues before check-out. A complaint addressed during the stay is recoverable. The same complaint filed in a post-stay survey usually isn't. Four Marriott brands consistently rank in the top 10 for hotel guest satisfaction scores. GuestVoice is a significant part of why.

Airbnb: Honest Feedback by Design

Airbnb's review system is a VoC mechanism by structure. Both guests and hosts review each other, but neither review is visible until both parties have submitted, or the 14-day window closes.

That simultaneous-reveal design removes retaliation bias. A guest is more honest about a difficult stay when they know the host can't read the review before submitting their own. The result is a review corpus that's structurally more honest than programs that rely on customers being candid voluntarily.

Airbnb uses that data to identify quality patterns by geography, flag hosts trending toward poor outcomes, and adjust search rankings based on sustained experience signals.

Most VoC programs assume honesty. Airbnb engineered it into the mechanism itself.

What Separates a Functional VoC Program from a Transformational One

Across 14 examples and five industries, the same patterns keep showing up.

The signal reaches the right person.

Cleveland Clinic's dashboards meant nurses saw their own scores. Intuitive Health's alerts went to location leaders, not headquarters. Monzo's social listening data fed directly into product team decisions. A VoC program that reports upward to a VP of CX but doesn't reach the team member who can actually fix the problem isn't a feedback loop. It's a reporting mechanism.

Feedback is tied to a specific question, not just a score.

USAA wasn't asking "how satisfied are you?" They were asking "where do customers experience unnecessary friction, and what does removing it do to loyalty?" Typeform wasn't just collecting NPS. They were asking "did the feature we shipped actually reduce the customer complaints it was meant to address?" That specificity is what makes VoC drive decisions rather than just describe them.

Channel choice is deliberate.

Starbucks used a public platform because community visibility was the point. Netflix uses behavioral data because observed actions are more accurate than stated preferences. Marriott uses SMS mid-stay because the timing determines whether recovery is still possible. The channel isn't a preference. It's a decision about what kind of feedback you need.

The loop closes.

Just Eat closes 97% of detractor cases within 48 hours of receipt on their B2B restaurant partner side. Figma attributes shipped features back to community requests publicly. Intuitive Health resolves detractor cases in 36 to 48 hours. Every program here has a mechanism for completing the cycle. That's the piece most programs skip. It's also the piece customers actually notice.

VoC feeds a process, not a report.

These companies didn't build VoC programs to produce quarterly CX dashboards. They built them to change how specific decisions get made: which features to prioritise, which frictions to remove, which accounts to recover before churn. The output should be action. Not documentation of inaction.

How to Apply These Examples to Your VoC Program

The patterns above hold regardless of industry or company size.

Start with one touchpoint.

Not a full customer journey map. One moment where you genuinely don't know why something happens: post-onboarding dropout, post-support satisfaction, exit behavior on a pricing page. One specific signal with depth beats a broad program with none.

Design the closed-loop workflow before the survey launches.

Who receives the alert? What do they do with it? How fast? Answering these questions first determines what collection method you need, not the other way around. Most teams answer them after launch. That's why most programs don't close the loop.

Match the channel to the question.

Exit intent for drop-off analysis. In-app CES immediately after a key task. WhatsApp surveys where email open rates are low. Post-discharge forms where customers are most reflective. The channel shapes the feedback. Choosing it deliberately shapes what you learn.

Platforms built for the full cycle, covering collection across email, SMS, WhatsApp, in-app, kiosks, and web through to analysis and closed-loop workflows, let you run programs like the ones above without stitching together separate tools. That's not a minor convenience. It's what makes matching the collection method to the customer moment operationally practical.

Build your full program with the framework: VoC strategy and best practices

Closing

The companies in this piece aren't running better VoC programs because they spent more. They're running better ones because they got specific: one touchpoint, one question worth answering, one workflow that closes the loop.

That specificity is the starting point. Not the survey format. Not the channel mix. The answer to: what changes when the feedback comes in?