Voice of the customer (VoC)

VoC is the discipline of systematically hearing what customers say and do, then acting on it. CS teams sit on the richest source of that feedback.

Quick answer — What is voice of the customer? A program to systematically collect, analyze, and act on customer feedback from surveys, conversations, and behavior.

Sources of feedback

SourceExamples
DirectSurveys (NPS, CSAT, CES), interviews, advisory boards
ConversationalCalls, emails, chats, support tickets, QBRs
BehavioralProduct usage, feature requests, drop-off points
PublicReviews, social posts, community forums
CommercialChurn reasons, lost deals, competitor mentions

Analyzing it

  • Tag feedback by theme, segment, and severity.
  • Quantify how many customers and how much ARR are affected.
  • Separate loud requests from widespread ones.
  • Look for patterns over time.
  • Use AI to cluster themes across thousands of comments. See sentiment analysis.

Acting on it

  1. Share themes with product, engineering, sales, and support on a regular rhythm. See the product feedback loop.
  2. Prioritize with data on revenue impact.
  3. Fix quick wins and publicize them.
  4. Update the roadmap communication for customers.
  5. Review impact next quarter.

Closing the loop

Customers who give feedback and hear nothing stop giving it. Tell them what you heard and what changed, even if the answer is no. That builds trust and supports advocacy.

Setting up a simple VoC program

  1. Pick three sources you will review regularly, such as support tickets, call notes, and surveys.
  2. Create a shared tag list.
  3. Review monthly in a cross-functional meeting.
  4. Publish a short summary of themes and actions.
  5. Close the loop with customers.

Mistakes to avoid

  • Collecting more feedback than you can act on.
  • Treating anecdotes as trends.
  • Only listening to the loudest customers.
  • Skipping the summary, so no one reads the data.

Why most VoC programs stall

Voice-of-the-customer efforts often begin with enthusiasm and end as an unread spreadsheet. The usual cause is a mismatch between collection and action: teams gather feedback from many places but have no agreed owner, no regular meeting where it is reviewed, and no way to show customers what changed. The fix is rarely more data. It is a small, reliable rhythm: a handful of sources, a shared tag list, a monthly review with product, support, and sales, and a short written summary that goes to leadership.

Quantification is what turns stories into decisions. A single customer asking for a feature is an anecdote; fifteen accounts representing a meaningful share of ARR describing the same problem is a business case. Capture the account, segment, ARR, and whether the issue influenced a renewal or a loss. That discipline makes it far easier to win prioritization arguments and to show the CS team that its insight leads somewhere.

Key takeaways

  • Pick a few sources and review them on a fixed rhythm.
  • Always capture account, segment, and revenue with each piece of feedback.
  • Publish a short monthly summary of themes and actions.
  • Tell customers what changed because of their input.

Frequently asked questions

What is voice of the customer?
A program to systematically collect, analyze, and act on customer feedback from surveys, conversations, and behavior.
What are VoC sources?
Surveys, interviews, calls and emails, support tickets, product usage, reviews, and churn reasons.
How does AI help with VoC?
It can analyze large volumes of comments and transcripts to find themes and sentiment.
Why close the loop?
Customers give more feedback and trust you more when they see action.
Who should own voice of the customer?
Often CS, support, or a CX team, with product and marketing as consumers. Ownership matters less than a consistent rhythm of review and action.

See what CSMs really earn

Compare your pay against real CSM submissions — free, anonymous, takes 2 minutes.

B
Ben Hancock
Customer Success Manager · built this database to bring transparency to CS compensation