Knowledge · B2B Marketing

VoC · Voice of the Customer

Voice of the Customer

📂B2B Marketing⏱2 min read📊Practical🔗7 related

What is VoC?

In one line
Voice of the Customer: the practice of systematically collecting and structuring the needs, complaints, and expectations customers express, then feeding them into product and service improvements.
⚡ Summary in 3 lines
  • Collect and structure what customers say, then turn it into improvements
  • Record the surface request separately from the need behind it
  • In B2B, record the speaker’s role too

Adopting VoC changes how meetings feel. 'My gut says customers want this' becomes 'Last quarter, the same sentence came up in 12 of 47 support conversations.' A fight over opinions becomes a fight over evidence, and that is the first change VoC brings to an organization. What sets the order is not the taste of the loudest executive but evidence with verbatim quotes attached, so the priorities of the development backlog and sales messaging actually change.

VoC is not the same as a satisfaction survey. NPS and CSAT are after-the-fact metrics that score “how good is it,” while VoC is the raw material that records “why” in the customer’s own words. A score falling from 8 to 6 tells you it happened, but not what to fix. In practice, VoC falls into three types: unsolicited VoC already sitting in support conversations, tickets, and churn reasons; solicited VoC gathered by asking directly, such as interviews and surveys; and indirect signals expressed through behavior rather than words, such as usage logs. Of these, unsolicited VoC is the most underrated, and you can pull it up today with no budget at all.

If you rank priorities by frequency alone, you get pulled toward a few accounts that complain often. It is more realistic to score by frequency × account revenue × churn risk and put only the top 5 on the quarterly roadmap. In B2B, also record the speaker’s role. End users talk about screen speed while approvers talk about audit readiness, and without a role label two different kinds of requests get mixed into one line, producing a feature nobody uses.

The most common mistake is translating a customer’s sentence straight into a requirements spec. If you build all ten requests for “open up Excel upload” exactly as written, the integration error that caused them remains, and six months later the same customer leaves for the same reason. The opposite failure is collecting feedback without answering it. A survey that never gets a reply sees response rates collapse from the second round, and sales reps stop writing down what they hear in the field because “nothing ever gets fixed anyway.” VoC dies not for lack of data but because the loop between acting and replying is broken.

Training that covers this term · Marketing
Recommended courses · Recommended instructors · Quick quote
🧮 Mini quote · Based on instructor fees
About KRW 1.2 million (≈ US$900)2-hour talk · up to 20 people · Korean
Get a quote for these requirements →
💡 In plain English
No doctor prescribes exactly what the patient asks for. You listen to the symptoms as described, but diagnose the cause separately.
Why it matters in practice
Products and messaging usually drift apart because what customers say gets scattered across the organization. Support records and churn reasons are the cheapest research material a company already has.
Origin and sources

Abbie Griffin and John Hauser laid the academic groundwork in their 1993 paper “The Voice of the Customer,” which set out a systematic way to collect and structure customer needs. The method later spread into quality function deployment (QFD) and customer experience management practice.

Source · Abbie Griffin & John R. Hauser, “The Voice of the Customer,” Marketing Science (1993)
An example

Company A is an HR management SaaS firm with 90 employees and KRW 6 billion (≈ US$4,489,000) in annual recurring revenue. Its second-year renewal rate had dropped from 88% the previous year to 71%, and no one inside could explain why. 1,400 CS tickets and sales call notes were scattered across different tools. (Hypothetical example)

  1. The CS team lead downloaded 1,400 tickets from the past six months and spent two days going through them. They pulled out 213 that said, in effect, 'lookups freeze on payroll closing day.'
  2. We met HR practitioners at 7 of the 12 clients that churned. One of them said, “It wasn’t that features were missing. Every month around the 25th, we just couldn’t trust it.”
  3. After the product owner split the verbatim quote and the interpretation into two columns, the real cause behind 31 requests to 'let us download it to Excel' turned out to be slow lookups on closing day.
  4. They added role tags to the sales call notes. End users talked about speed, but finance approvers asked, 'Can we pull the change history for an audit?' The requests turned out to be different.
  5. Three months later, the team shipped a fix that spreads load away from deadline days and emailed every client that had raised one of the 213 cases. By the next renewal season, the renewal rate rose from 71% to 86%, and related tickets fell from 47 to 9 a month.
Related terms
Training linked to this term
📚CX · Customer ExperienceNanum Consulting corporate training · On-site or onlineSee course →
Need in-house training on this topic?
Get a curriculum and quote tailored to your needs right away.
Ask About Training
Last updated 13 Sep 2026 · Reviewed by John Kim

FAQ

A survey is only one means of VoC. Existing unstructured data, such as support records, exit interviews, and objections heard in the field by sales, is often richer.
It’s risky. Customers speak in the language of the solutions they already know, so building their requests as stated misses the underlying need. Keep the original statement as is, and interpret the purpose behind it separately.
Even within a single client company, end users, the purchasing team, and decision-makers want different things. If you don't record who said what and in which role, contradictory requests get mixed together and you can't set priorities.
The words customers actually use become raw material for landing page headlines, search keywords, and sales scripts. Messages written in the customer’s language land far better than those in internal company jargon.