What is Voice of Customer?
Voice of Customer, often shortened to VoC, covers all the methods used to listen to customers, understand their experience and share their feedback across the organization.
It can draw on several sources:
- NPS, CSAT or CES surveys;
- open-ended comments;
- customer interviews;
- support tickets and conversations with customer service;
- online reviews;
- feedback collected during onboarding, after a purchase or at renewal time.
Collecting answers isn’t enough. You need to understand what happened, why it mattered to the customer and what they expected instead.
Why a questionnaire isn’t always enough
Closed questions are useful for tracking a metric over time. They make answers comparable and help you spot a trend. But they inevitably simplify the lived experience.
Take an answer like this one:
“7/10. Overall, it was fine.”
That answer can hide very different realities: a long wait, information that arrived too late, a feature that was hard to find or, on the contrary, a particularly helpful team.
A form usually moves on to the next question. A conversation can ask:
“What stopped you from giving a higher score?”
Then, if the answer calls for it:
“At what point did you feel you were missing information?”
The score remains the reference point. The conversation provides the context you need to act.
What a VoC program aims to surface
A well-framed Voice of Customer program helps bring out four types of signals.
Pain points
What makes the journey harder: delays, missing information, a gap between two channels, unnecessary effort or a misunderstood promise.
Expectations
What customers expected to find, receive or be able to do. An unmet expectation often explains dissatisfaction better than a score alone.
Moments that matter
The steps that strongly shape the overall perception: first contact, delivery, getting started, solving a problem or renewal.
The reasons behind a score
What explains an NPS, CSAT or CES result, without changing the metric already in place or breaking its history.
How to build a useful Voice of Customer program
1. Start from a decision you need to inform
Avoid overly broad campaigns such as “What do you think of our company?”. Start with a concrete topic: understanding onboarding difficulties, the reasons for dissatisfaction after an interaction or expectations ahead of a renewal.
2. Choose the right moment
Feedback is more precise when it is collected close to the experience: after a delivery, when a ticket is closed, after a visit, a stay or an important step in the journey.
3. Keep your existing metric
If your organization already tracks NPS, CSAT or CES, keep it. The conversation can come after the score, with a segment or a sample, to understand the reasons behind it.
These metrics don’t describe the same thing:
| Metric | What it observes | When to use it |
|---|---|---|
| CSAT | Satisfaction with a specific interaction | After a purchase, a visit or a contact with support |
| CES | The perceived effort needed to complete an action | After a journey, a resolution or a process |
| NPS | The overall likelihood to recommend | During a relationship review or a recurring measurement |
Choose the metric that matches the decision at stake. A single question shouldn’t mix satisfaction, effort and recommendation.
4. Ask few questions, but know when to dig deeper
An exhaustive list tires respondents out. An adaptive interview moves forward one question at a time and only explores the answers that still hold something worth understanding.
A good follow-up follows a simple pattern: acknowledge what was just said, pick up the point that deserves clarification, then ask an open question. If the person stays vague or says they have nothing to add, the conversation moves on to the next theme.
5. Link every insight to its source
An aggregated theme is only valuable if it can be traced back to the verbatims and context that revealed it. This traceability lets you check the interpretation and share a signal without distorting it.
Examples of Voice of Customer campaigns
After onboarding
Understand what helped or slowed down getting started, what information was missing and when the customer felt able to manage on their own.
After a purchase or a service
Explore the gap between the initial promise and the actual experience, from ordering through to follow-up.
After a ticket is resolved
Don’t stop at “issue resolved”. Understand the effort required, how clear the exchanges were and what would have made the resolution smoother.
Before a renewal
Bring out perceived value, key uses, hesitations and expectations that are not yet met.
After a customer leaves
Document the reasons the customer gives, without claiming that a single answer explains churn on its own.
What questions should you ask your customers?
A good VoC question focuses on a specific experience and invites the person to describe what happened.
- “Which moment of your journey required the most effort?”
- “What were you missing to move forward more easily?”
- “You mentioned a lack of clarity. At what point did you feel that?”
- “What did you expect instead?”
- “What contributed most to your satisfaction?”
- “If we could improve only one step, which one would you choose?”
A follow-up should stay tied to the previous answer. It isn’t there to drag the conversation out, but to clarify a signal that is still incomplete.
Avoid questions that combine two topics, such as “Are you satisfied with the price and the quality?”. A single answer wouldn’t tell you which of the two the person is rating. Prefer two separate objectives, and only cover the second one if it is useful to the campaign.
In what order should you ask the questions?
Order influences how customers reconstruct their experience. For a campaign designed to understand causes, start with the concrete steps of the journey, then finish with an overall assessment.
A sequence can follow this thread:
- state the purpose, the duration and how answers will be used;
- specify the experience concerned and its time frame;
- explore the key moments or attributes;
- ask about perceived effort if the topic lends itself to it;
- collect an overall assessment or a recommendation;
- leave room for an open comment;
- thank the person and explain what will happen with the answers.
If your priority is to compare an identical NPS every quarter, you can ask that question first. In that case, keep the same protocol from one wave to the next and treat this choice as a measurement rule, not a layout detail.
From the voice of the customer to actionable feedback
Sonar lets you describe the context and the themes to explore, then structures a conversational campaign. Each person joins the interview through a public link, with no account to create, and answers in writing or out loud depending on the chosen setup.
The conversation moves forward within the frame set by the team. It digs deeper into an answer when a point deserves clarification, then reports the themes, expectations and pain points along with their source verbatims.
Sonar separates running the conversation from the rules that control its progress. The agent phrases the follow-up, while guardrails track the themes covered, limit the number of questions and move on to the next topic when the conversation stops progressing. This separation keeps an interview from insisting for no reason or drifting outside the defined frame.
Sonar doesn’t replace your measurement platform, your Customer Success teams or your product analytics. It adds a qualitative layer to understand the “why” behind a signal you have already observed.
FAQ: Voice of Customer
What is the difference between Voice of Customer and customer satisfaction?
Customer satisfaction is something you measure. Voice of Customer is a broader approach that organizes how customer feedback is collected, analyzed and shared. It can include satisfaction scores, but also verbatims, interviews and signals from support or the journey.
Should interviews replace NPS or CSAT?
No. Scores let you track a metric over time. Interviews help you understand what explains those scores. The two approaches complement each other.
When should you launch a VoC campaign?
When a team needs to inform a decision about a specific step of the journey: onboarding, purchase, delivery, support, renewal or departure. An ongoing campaign can also follow the same topic over time.
How do you avoid answers that are too vague?
Ask questions tied to a recent experience, then ask for an example, a specific moment or the related expectation. A contextual follow-up usually produces a more useful answer than another generic question.
Does Sonar replace a product analytics tool?
No. Product analytics shows what users do in a product. Sonar captures what they experienced and the reasons they give. The two sources can be cross-referenced, but they don’t measure the same thing.