Guide
Voice of customer examples from B2B customer calls.
Voice of customer is what customers say about their work and your product, in their own words. On B2B calls it comes in six kinds: a struggle, a workaround, a request, a reason they bought, a reason they might leave and a misunderstanding. Each one below is an example with what it tells you and what to do with it.
Updated . Every company and quote on this page is made up.

A struggle, said calmly
“We find out the sync broke when a customer emails us.”
Northvale Systems · success call (example)
What counts as voice of customer?
A sentence a customer actually said, kept as they said it, with who said it and when. A survey score is not voice of customer, and neither is a summary of a call. Both are useful, but they are your words about the customer, not theirs.
The exact words matter because they carry how strongly something was meant, and because they survive being passed around. "Customers want better reporting" turns into whatever the next reader wants it to mean. "I go through every report by hand on Monday mornings" does not.
Six examples from customer calls
1A struggle
Monday mornings I go through every report by hand to see what moved before the leadership meeting.
What it tells you: A problem in the customer's own time and words. This is the most useful kind, and the easiest to miss, because it sounds like small talk.
What to do: File it under a problem named from their side, and count the company.
2A workaround
We built a spreadsheet that pulls the export every Friday and fixes the columns. Mia maintains it.
What it tells you: Proof the need is real: someone is paying for it with their own time. A workaround also shows you what "good enough" looks like to them.
What to do: Ask how often and how long. Note it next to the problem it works around.
3A request
Could you add a Slack alert when a report changes?
What it tells you: A guess at a fix. The problem behind it is usually right, and the fix often is not.
What to do: Ask "what were you trying to do when you noticed?" and keep the answer, not just the request.
4A reason they bought
Honestly, we picked you because the briefs are the only thing our engineers actually read.
What it tells you: What the product is worth to them, in words you did not write. These are the strengths you must not break.
What to do: Keep them in their own list. Read them before any redesign and any pricing change.
5A reason they might leave
If we can't get the old calls in before budget season, we'll probably go back to doing it by hand.
What it tells you: A deadline and a consequence. It is often said quietly, at the end of a call, in a conditional.
What to do: Flag it to whoever owns the account the same day, then file the problem underneath like any other.
6A misunderstanding
Wait, it can merge two themes? I've been doing that in a doc.
What it tells you: Not a missing feature: a feature nobody found. The fix is in onboarding, naming or the screen itself.
What to do: Count these separately. Three of them in a month say more about your product than a new request does.
What does a weak example look like?
| Weak | Why | Stronger |
|---|---|---|
| "Users want better reporting." | A summary, in your words. Nobody said it. | "I go through every report by hand on Monday mornings." |
| "Would love Slack alerts!" | A request with no reason attached. | The same request, plus what they were trying to do. |
| "Yes, that would be useful." | An answer to your own suggestion. | Something they raised before you asked. |
| A score of 7 with the comment "good" | A number with nothing to act on. | The one sentence on the call that explains the 7. |
How do you present voice of customer?
One quote and one count. The quote makes the problem real, and the count stops one vivid quote from deciding on its own:
We stopped reporting things. It goes into a hole.
One of 8 companies that raised the same problem this quarter, 7 of them without being asked.
Count companies, not mentions: one customer saying it on five calls is still one customer. And count separately the companies who raised it without being asked, because a problem people raise on their own is worth more than one they agreed with when asked. The guide How to analyse customer feedback from your calls goes through the counting.
When a theme is ready to act on, the quotes go straight into the first half of a product brief.
Where do the best examples come from?
From the calls your team already has: sales, onboarding, success, renewals, and the call where someone leaves. Calls give you something tickets and surveys cannot: the reason behind a request, and whether the customer brought it up themselves.
The best ones are often off-script, at the start or the end of the call, when the customer is talking about their week rather than answering your questions. That is why the transcript is worth more than anyone's notes: notes keep what the note-taker thought was important.
If your calls are in Granola, Find patterns across your Granola customer calls shows how to pull these sentences out of a folder.
Can you collect them without the copying?
Finding the sentences is slow: reading transcripts, copying the exact words, noting who said them and whether they were asked.
Ordagrann reads the customer calls you record in Granola, groups every problem and request into themes, counts how many companies raised each one, and turns a theme into a one-page brief your team can build from. Every sentence is kept word for word, with who said it, in which call, and whether they raised it without being asked.
Works with Granola Business. Any other transcript can be pasted in.