Voice of customer (VoC): sort the feedback you already have before asking for more
A voice of customer program starts with tickets and notes you already collect, adds one or two scores, and uses interviews to explain what moved.
A voice of customer program should start with the feedback you already collect, sorted the same way every time, and use interviews to explain what the sorting shows. Voice of customer (VoC) means capturing what customers need, want and complain about, in their own words, and putting it in front of the people who make product, sales and service decisions.
The term comes from product development. Abbie Griffin and John Hauser's 1993 paper "The Voice of the Customer" describes it as the part of Quality Function Deployment (QFD) that identifies customer needs, structures them and sets priorities among them. Their raw material was one-on-one interviews and focus groups. Software teams now add tickets, surveys and call notes, but the job is the same: turn scattered comments into ranked needs.
The example: three teams, three different stories
Here is a made-up example. You run a payroll product for companies with 20 to 200 employees and have about 300 customers. Support gets a steady flow of tickets, customer success has quarterly check-ins, and sales hears objections every week. Nobody knows which problem matters most, because each team remembers different customers. (Each team is also sure its customers are the important ones.)
1. Use the feedback that already arrives
Before launching a new survey, list what already arrives:
- Support tickets and chats. Customers write these unprompted, about problems they hit in real work.
- Sales and customer success notes. Objections, feature asks and renewal concerns.
- Cancellation reasons and lost-deal notes. Short, often vague, but tied to money.
- Public reviews and community posts. The words customers use about you and competitors.
Start with support tickets. A team at the UK Government Digital Service described how it analyzes tickets for several products. They agree what they want to learn, then a product manager, designer and tech lead each categorize the same 50 tickets. They compare tags to build one shared list, tag tickets as they arrive, and report volumes every two to three months. Tickets, the team noted, aren't steered by its own roadmap or interview questions.
The payroll company's list might include "tax filing error," "off-cycle payment," "new hire setup" and "integration sync." After a quarter, you see which tags grow.
2. Track one or two scores, no more
Ask each at a sensible moment:
- Net Promoter Score. Bain defines NPS as the percentage of promoters (9 or 10 on "How likely are you to recommend us to a friend or colleague?") minus the percentage of detractors (0 to 6). If 120 payroll admins answer and 54 are promoters and 18 are detractors, NPS is 45% minus 15%, or 30 (hypothetical figures).
- The product-market fit question. "How would you feel if you could no longer use the product?" suits newer products; see the guide to the product-market fit survey.
- A one-question check after a key event, such as the first payroll run or a support ticket closing.
A score shows whether things are moving, never why. NN/g's overview of research methods says qualitative methods suit questions about why or how to fix a problem, and quantitative methods suit how many and how much.
3. Interview when a number moves and nobody knows why
Use interviews in three situations:
- A tag or score moves without explanation. If "off-cycle payment" tickets double in a quarter, talk to five or six admins who filed them. Ask them to walk through the last one and who else was involved.
- Before a roadmap decision. Tickets show where people get stuck. They rarely show what someone was trying to do or what it cost.
- When the people you need aren't in your feedback stream. Customers who left, deals you lost and people who never tried you don't file tickets. Churned customers and lost deals each need their own approach, and prospects sit outside your customer list entirely.
GOV.UK's guidance for live services draws the same line: review analytics and support tickets to find problems, run surveys for broader feedback, then use interviews, visits and usability testing to understand them.
| Source | What it tells you | What it misses | Typical rhythm |
|---|---|---|---|
| Support tickets | Where people get stuck, in their words | People who never contact support | Tag as they arrive, review monthly |
| NPS or other surveys | Direction of sentiment across many customers | Reasons behind a score | Quarterly or after key events |
| Sales and customer success notes | Objections and renewal risks | Detail; notes are secondhand | Weekly skim, monthly summary |
| Interviews | Why something happens and what it costs | How common it is | A few each month, triggered by the above |
4. Give the program one owner and a monthly summary
Decide:
- Who owns it. One person collects, tags and reports.
- One tag list shared by support, sales and customer success, reviewed each quarter.
- A monthly summary with the top tags, any score change and what interviews found. The research repository template is one simple place to store it.
- Where each finding goes: product backlog, help docs, onboarding or sales training. Then tell customers what changed because they spoke up.
5. Don't mistake the loudest feedback for the most important
- Who speaks up. NN/g describes customer feedback as a self-selected sample: you hear from people who choose to answer. Griffin and Hauser also found a self-selection bias in the satisfaction measures commonly used in QFD, so one group's answers are not the whole customer base.
- The loudest account. One large customer's requests can crowd out a pattern across fifty small ones. Count accounts as well as mentions.
- Mentions as importance. A need that comes up often may be mildly annoying; a rare one may be why people leave. Ask about impact before ranking.
Your next step
Tag 50 of last quarter's tickets with two colleagues, pick the tag that surprises you most, and book five conversations about it.
If the people you need are outside your customer list, such as payroll admins who use a competitor, search for people by describing their role. The operations professionals in payroll software directory page is a good place to start. Instant Expert finds people whose work matches your question. You review them, it sends the invitations, and you pay for each call that gets booked.
A lightweight voice of customer loop
- 1
Collect
Pull tickets, call notes, cancellation reasons and a small survey into one place.
- 2
Tag
Sort everything with one shared tag list so trends are countable.
- 3
Explain
Interview five or six people behind the tag or score that moved.
- 4
Route
Send each finding to product, docs, onboarding or sales, then tell customers what changed.