6 Real Voice of Customer Program Examples (With Results)

Most "voice of customer program" advice tells you how to build one. This is the other thing teams actually want before they start: proof that it works, and a look at what a real program produced. The examples below are not hypotheticals or vendor case studies dressed up as thought leadership. They are six product and CX teams, the programs they run, and the measurable results those programs delivered. Every one of them runs on Enterpret, which is the through-line worth noticing: the results are different, but the underlying pattern that produced them is the same.

The six programs are at Canva, Descript, Apollo.io, Feeld, Notion, and Figma. What makes them worth copying is not the logo, it is the outcome each one moved: analysis time cut, feedback volume absorbed without new headcount, support load reduced, launches navigated in real time. Here is what each program did and what it produced.

What makes a voice of customer program worth copying

Before the examples, the filter. A program worth learning from clears three bars, and the numbers below are downstream of all three.

1. It unified the feedback first. Every one of these teams started by pulling scattered signal, support tickets, reviews, surveys, calls, community, into one place through feedback integrations, instead of analyzing each channel in isolation.
2. It categorized without manual tagging. The results below are only possible because an adaptive taxonomy does the classification that used to eat analyst weeks, and stays current as the product changes.
3. It tied feedback to the business. The programs that moved revenue and retention numbers did so by connecting each theme to the account and segment behind it through the customer context graph, so prioritization followed impact, not volume.

A program that clears those three bars produces results like the ones below. A program that stops at collecting survey scores does not.

6 real voice of customer program examples

1. Canva: 10x the feedback, the same size team

Canva supports a user base north of 220 million, and its feedback volume scaled with it. The insights team needed to understand the whole base, not a sample, without hiring in proportion to the growth. Running its program on Enterpret, Canva now processes roughly ten times more feedback with the same team and zero manual tagging. As Jesse Walker, Head of Insights and User Advocacy, put it, the program aligns everyone around the top issues and requests rather than leaving each team with its own slice. The result is coverage of the entire customer base instead of whatever a analyst could read by hand.

The result: 10x feedback processed, no proportional headcount increase.

2. Descript: 83% less time turning feedback into insight

Descript's user base grew into the millions, and feedback fragmented across tickets, calls, and surveys. Synthesizing it for a single research sprint could consume a full day of analyst time. After building its program on Enterpret, the research and support teams cut analysis time by 83%, turning a day of synthesis into a fraction of it. The program let Mike McNasby's research function and Jill McKinney's support team work from the same unified view instead of reconciling separate exports.

The result: 83% reduction in feedback analysis time.

3. Apollo.io: 40% fewer support tickets by acting on the signal

Apollo.io's product and support teams wanted feedback to drive fixes that removed ticket volume at the root, not just deflect it. Using Enterpret to consolidate every source and associate feedback with customer segments by buyer, title, and location, the team could target the issues generating the most load, segment by segment. Chief Product Officer Abishek Viswanathan framed the goal as freeing engineering to invest in the highest-impact work rather than an endless tail of small fixes. Mapping feedback to revenue is also how the program supported the company's broader growth.

The result: 40% reduction in support tickets.

4. Feeld: a 10x feedback spike absorbed during a launch

Feeld, a fast-growing dating app, hit a 10x spike in feedback during a product launch, the exact moment a manual, tag-by-hand process breaks. Because its program on Enterpret categorized incoming feedback automatically, the team stayed in close touch with community sentiment through the surge instead of falling behind it. Dina Mohammad-Laity, VP of Data, tied it back to the company's mission of staying close to what members are saying, which is only possible when the volume does not outrun the analysis.

The result: 10x launch-driven feedback spike handled without added headcount.

5. Notion: one holistic view across every channel

Notion's challenge was breadth: feedback arrived through social, support tickets, and every other interaction, and the team needed one view rather than a set of disconnected channel reports. Its program on Enterpret unifies those sources so the team can move past keyword counting to understand the broader sentiment behind what users say. Emma Auscher, Global Head of Customer Experience, described the value as a holistic read across everything from social coverage to support, in one place.

The result: a single cross-channel view replacing fragmented per-channel reporting.

6. Figma: feedback democratized across the whole company

Figma's aim was reach: making customer feedback accessible to everyone across product, customer success, and beyond, not locked with a single insights team. Its program on Enterpret uses AI to scale the feedback loop so any team can self-serve the signal relevant to them. That turns voice of customer from a reporting function into shared infrastructure the whole company draws on.

The result: feedback made self-serve across product, CX, and success teams.

What the best programs have in common

Read the six together and the pattern is unmistakable. None of these results came from running more surveys or buying more dashboards. They came from the same three moves: unify every channel into one place, categorize it automatically so analysis scales without headcount, and tie each theme to the customer and revenue behind it so the team acts on what matters most. The specific number each program moved, 10x volume, 83% time, 40% tickets, followed from that shared foundation.

The other commonality is that feedback stopped being a report and became an operating input. In each program, insight reaches the team that can act, product, support, or success, through the workflows they already use, closing the loop through close-the-loop workflows rather than landing in a monthly deck. That is the difference between a program that produces results and one that produces slides. For the profiles behind these numbers, see our companion piece on voice of customer programs at tech companies.

How to apply these lessons to your program

You do not need to be Canva's size to copy the pattern. Start by unifying the feedback you already have instead of adding new collection. Replace manual tagging with a taxonomy that maintains itself, so analysis scales as volume grows. Connect each theme to the account and revenue behind it so you can prioritize by impact. Then route insight into the tools your teams already work in, so acting on feedback is the default rather than a separate step. That sequence, not any single survey or score, is what produced every result above. For the foundational version, see what a voice of customer program is, and to see the layer these programs run on, Enterpret's voice of customer software.

The takeaway across all six: the best voice of customer programs are judged by what they change, not what they collect.

FAQ

What is a good example of a voice of customer program?

Canva's is a strong example: it processes roughly 10x more feedback than before with the same size team and no manual tagging, giving it a read on its entire 220-million-plus user base rather than a sample. Other strong examples include Descript, which cut feedback analysis time by 83%, and Apollo.io, which reduced support tickets by 40% by acting on the underlying issues. What they share is unifying every feedback channel, categorizing it automatically, and tying it to business context.

What results can a voice of customer program actually produce?

Real programs have produced measurable operational results: Canva absorbs 10x the feedback volume without adding headcount, Descript cut analysis time by 83%, Apollo.io reduced support tickets by 40%, and Feeld handled a 10x feedback spike during a launch without falling behind. The common driver is a program that unifies channels, automates categorization, and connects feedback to revenue, rather than one that only collects survey scores.

What do the best voice of customer programs have in common?

Three things. They unify feedback from every channel into one place instead of analyzing channels separately, they categorize it automatically with an adaptive taxonomy so analysis scales without more analysts, and they tie each theme to the account and revenue behind it so prioritization follows impact. They also route insight into the workflows teams already use, so feedback drives action rather than sitting in a report.

How do companies like Canva and Descript analyze feedback at scale?

They run their programs on a customer intelligence platform that ingests feedback from every channel, applies an adaptive taxonomy that learns their product language and categorizes automatically, and connects each signal to customer and revenue context. That removes the manual tagging bottleneck, which is what lets Canva process 10x the volume with the same team and Descript cut synthesis time by 83%.

How do I start a voice of customer program like these?

Begin by unifying the feedback you already collect across support, reviews, surveys, and calls into one place, rather than launching new surveys. Replace manual tagging with an adaptive taxonomy so analysis scales, connect themes to account and revenue context to prioritize by impact, and route insight into the tools your teams already use. That is the same sequence behind every program above, and it works at any size.

Want your program on this list? See how Enterpret powers these programs or book a demo.

‍