Voice of the customer: what it is, and what it is not
Voice of the customer is how a company hears, understands and acts on what customers say and do. Its sources, the feedback loop, who owns it, how to start.
Table of contents
Ask five people in one company what their voice of the customer program is and you may get five answers: the quarterly survey, the NPS slide, the review-monitoring tool, the support team’s ticket tags, the advisory board that meets twice a year. Each is a piece of it. None of them, alone, is the thing.
Voice of the customer (VoC) is the continuous practice of collecting what customers say and do, working out what it means, acting on it, and telling customers what changed. It counts only when something in the company changes as a result.
Hearing the voice of your customer is the easy half, and most companies already collect more feedback than they read. This is the practical version of the rest: where the customer’s voice comes from, how the feedback loop runs, who owns it, and how to start.
Key takeaways
- Voice of the customer is a continuous practice of collecting, understanding and acting on what customers say and do, then telling them what changed.
- An annual survey, an NPS number, a dashboard and a research project with an end date are parts of VoC that often get mistaken for the whole.
- The customer’s voice arrives solicited (surveys, interviews), unsolicited (tickets, reviews, cancellation reasons) and inferred (returns, churn, usage), and each source misses what another catches.
- A working feedback loop has an inner loop, where the frontline follows up with one customer, and an outer loop, where a process owner removes the cause.
- The VoC owner runs the listening system, but the fixes belong to the people who run the processes, so most of the job is connecting them to the evidence.
- Start small: one customer journey, two or three sources, one recurring review with someone who can change things, and one note telling customers what changed.
What is voice of the customer
The idea is older than most CX teams. Quality function deployment, a method developed in Japan beginning in 1966, was built to translate the voice of the customer into the engineering characteristics of a product.
Today the term covers the whole relationship, from the first website visit to the cancellation call, but the core has not changed: the customer’s words are meant to change what the company makes and does.
Two neighboring terms get mixed up with it. Customer experience is what customers go through: the purchase, the delivery, the bill, the support call. Voice of the customer is how you find out what that was like and what you do about it. Market research usually answers a defined question by a set date and then stops; VoC keeps running, because the experience keeps changing.
The test of a VoC program is uncomfortable: name the last three things that changed because of what customers said. If nobody can, the company has a collection habit.
What voice of the customer is not
Most VoC programs that fail mistook one part for the whole. Four of those mistakes come up again and again.
An annual survey. The yearly relationship survey is a useful pulse, but it asks customers to average a year into one rating and reports long after anyone could fix the delivery that went wrong in March. A survey once a year is a check-up; listening is what happens between check-ups.
An NPS number. A single score says something went up or down and nothing about why, and scores need the comments that explain them. When the number becomes the program, meetings argue about a two-point drop and nobody reads the three hundred comments behind it.
A dashboard nobody acts on. Dashboards are where a great deal of feedback goes to rest. A chart reviewed monthly by people who do not own the process it describes is decoration. It earns its place when it has a named owner and the review ends in a decision.
A research project with an end date. A six-month project can produce real insight. Then the team disbands, the deck goes into a shared drive, and customers keep talking to nobody.
Nor is VoC a software purchase. Customer experience management software can collect and route feedback very well, but it does not decide what to ask, whom to ask, or who acts on the answer.
Where the customer’s voice comes from
Customers tell you things in three ways: when you ask, when they choose to, and through what they do. A program built on only one of them hears a distorted customer.
Solicited feedback is what you ask for: surveys, interviews, customer advisory panels. You control the question and get a number you can track, but you hear only about what you thought to ask, from people willing to answer, and declining survey response rates make that limit harder to ignore. For depth, start by listening to your best customers in conversation.
Unsolicited feedback is what customers say without being asked: support tickets, calls and chats, reviews, social posts, sales notes after a lost deal, cancellation reasons. It comes in the customer’s own words and covers problems nobody put on a survey, but it leans toward the very unhappy and the very articulate. If you sell through marketplaces or resellers, much of it lands with them first, so listening to indirect customers needs arrangements of its own.
Inferred feedback is what behavior tells you: returns, repeat purchases, churn, product usage, abandoned checkouts. It covers every customer, including the silent ones, and shows what happened, never why.
| Source | Type | What it tells you | What it misses |
|---|---|---|---|
| Surveys | Solicited | A comparable score over time, at scale | Anything you did not ask; customers who do not respond |
| Interviews and advisory panels | Solicited | The reasoning and language behind a decision | Scale; how typical one customer’s view is |
| Support tickets, calls and chats | Unsolicited | Where processes break, in the customer’s words | Customers who gave up without contacting you |
| Reviews and social posts | Unsolicited | What customers tell other customers | The quiet majority; the context behind a post |
| Sales notes and cancellation reasons | Unsolicited | Why deals are lost and customers leave | Nuance, when reasons come from a short dropdown |
| Returns, churn and usage | Inferred | What customers actually do, across everyone | Why they did it |
Each row is incomplete on its own, and together they cover each other’s gaps. Behavior shows churn rising among new customers, tickets show they struggle with setup, and five interviews reveal that the setup guide assumes a step nobody takes.
The voice of the customer feedback loop
Collecting is the first of four steps, and a voice of the customer feedback loop is complete only when the customer can see the result.
- Collect what customers say and do.
- Understand it: read the comments, group them into themes, size each theme and link it to the customers behind it.
- Act on it, with the individual customer and on the cause.
- Tell customers what changed, both the person who raised the problem and everyone else.
The third step is where loops break, because “act” means two jobs on two clocks.
The inner loop: one customer, within days
The inner loop is the follow-up with one customer. Someone gives a low rating or cancels with a reason that points to a fixable problem, and a person on the frontline (an agent, a store manager, an account manager) contacts them, listens and resolves what can be resolved.
It needs two things: authority for the frontline to fix common problems without asking permission, and a short rule about which responses trigger a follow-up and how fast. Without both, follow-up becomes a script that apologizes and changes nothing.
The outer loop: the cause, over weeks
The outer loop fixes the reason the problem keeps happening. Themes from many customers go to the person who owns the process or product, such as the billing manager or the product lead, who decides what to change. Someone then checks whether it worked, ideally by measuring the change against a control group.
The two loops feed each other. Follow-up calls are the richest source of detail for the outer loop, so ask the people making them to record the cause. In return, an outer-loop fix stops the frontline from apologizing for the same broken thing every week.
| Inner loop | Outer loop | |
|---|---|---|
| Unit | One customer | A theme across many customers |
| Who acts | Frontline staff | Process and product owners |
| Speed | Days | Weeks to months |
| Typical failure | Scripts that change nothing | Themes reported, never assigned |
The last step closes the loop. Tell the customer who reported the problem that it was fixed, personally. Then tell everyone else: a dated page of what changed because of feedback, a line in the next survey invitation, an entry in the release notes. In my experience, nothing does more for the next survey than customers seeing that the last one did something.
Who owns voice of the customer
Someone has to own the program, and that person cannot own the fixes. Holding both truths at once is most of the job.
The VoC owner, whether a dedicated lead, a CX team or the founder of a small company, owns the listening system: the sources, the coding of themes, the follow-up rules, the review cadence, the evidence and the message to customers. The fixes belong to whoever runs the process: billing complaints to billing, delivery complaints to logistics, a confusing feature to product.
So the work is connection, and three habits do most of it:
- Name an owner for every major theme. A theme without an owner is a complaint with a chart.
- Hold a recurring review with people who can act. Monthly is enough, as long as the people in the room run the processes under discussion and every theme leaves with a decision and a date.
- Find an executive sponsor who asks. The sponsor asks process owners, in their own meetings, what they did with last month’s themes.
Report into someone with authority across departments, because most customer problems live in the handoffs between teams. Getting a department head to act on evidence they did not ask for is a sales job inside the company, and the internal marketing that builds buy-in for a pilot works the same way here.
How to start a VoC program, small or large
The right first move depends on how many people stand between the customer and the person who can fix things.
At a small company
The founder or head of support owns VoC, and the tools can be a shared inbox and a spreadsheet. For a month, read every support ticket and cancellation reason and code each into one of a handful of themes. Add five customer conversations a month: a recent buyer, a long-standing customer, someone who left.
Every two weeks, spend thirty minutes with whoever builds the product and whoever runs operations. Pick one theme, fix it, and tell the customers who raised it. Being small means the person who hears the complaint and the person who can fix it often share a room.
At a large company
The temptation is an enterprise-wide launch: a platform, a governance board and a survey for every touchpoint. Resist it. Start with one customer journey, such as onboarding, claims or returns, whose executive owner already feels the pain.
Begin with an inventory, because large companies hold more feedback than they realize: surveys run by different teams, ticket categories, call recordings, review sites, sales notes. Bring two or three of those sources together for that journey, set up the inner loop in one team, and hold a monthly outer-loop review with the journey’s owner.
After a quarter, measure the result against a comparison group, and only then expand. A program that has fixed two things is easier to fund than one that measures fifty.
Common mistakes that stall a VoC program
Collecting more than you can act on. Every new source creates an obligation to read it and respond. If the team cannot keep up with the comments it has, another channel adds only noise.
Reporting the score instead of the reasons. A slide saying satisfaction fell three points invites a debate about sampling. A slide saying the top reason for low scores is a confusing invoice, with five customer quotes, invites a fix.
Treating complainers as noise. The loudest customers are often the ones you failed, and they describe a broken process in more detail than any survey. That is the case for keeping the loud customer you must never fire.
Closing the inner loop but never the outer. The frontline apologizes to every unhappy customer, and next month the same problem produces the same calls. Recovery without a fix wears out staff and teaches customers that complaining is pointless.
Tying pay to the score. Once bonuses depend on a rating, people start asking customers for good ratings and skipping surveys after hard cases. The number rises and stops meaning anything.
Never telling customers what changed. Customers who see no result stop answering, and the ones who keep answering become less like the rest.
Where to start
- List every place customers already talk to you: surveys, inboxes, ticket queues, review sites, call recordings, sales notes and cancellation forms, with who owns each.
- Pick one customer journey and one owner who runs that process and wants it fixed.
- Read fifty raw comments or tickets from that journey and sort them into five or six themes.
- Write the inner-loop rule: which responses trigger a personal follow-up, who makes the call, and how fast.
- Hold a thirty-minute review with the journey’s owner, and leave with one theme assigned and a date to check the result.
- Tell the customers who raised it what changed, personally, once the fix is live.
FAQ
What is voice of the customer?
Voice of the customer (VoC) is the ongoing practice of collecting what customers say and do, understanding it, acting on it and telling customers what changed. It draws on surveys and interviews, unsolicited sources such as support tickets and reviews, and behavior such as returns and churn. It counts only when it changes something in the company.
What is the difference between voice of the customer and customer experience?
Customer experience is what customers go through when they deal with a company: buying, using, paying and getting help. Voice of the customer is how the company finds out what that experience was like and turns it into improvements. VoC is one of the main ways to manage customer experience, though not the only one.
What is a voice of the customer feedback loop?
A voice of the customer feedback loop is the cycle of collecting feedback, understanding it, acting on it and telling customers what changed. The inner loop is frontline follow-up with an individual customer; the outer loop is a process or product owner fixing the underlying cause. The loop is closed when the customer can see the result.
How do you collect voice of the customer data?
Combine three kinds of source: ask directly through surveys, interviews and advisory panels; gather what customers say unprompted in tickets, calls, reviews, sales notes and cancellation reasons; and study behavior such as returns, usage and churn. Each fills gaps in the others, so surveys alone hear a narrow slice.
Who should own a voice of the customer program?
A named person or team should own the listening system: the sources, the themes, the follow-up rules, the reviews and the messages to customers. In a small company that is often the founder or head of support, and in a large one a VoC or CX lead reporting to someone with authority across departments. The fixes belong to the owner of each process or product.
Is NPS the same as voice of the customer?
No. Net Promoter Score is a single survey metric, useful for tracking a relationship over time, and one input to a VoC program. It shows whether sentiment is rising or falling but not why, so it needs the comments behind it, other sources of feedback and a process for acting on them.
