Guide

How to analyse customer feedback from your calls.

Pull every problem and request out of your customer calls in the customer's own words. Note who said it and whether you asked. Group the sentences by the problem underneath, then count how many companies raised each one. Do it every week on the same sheet, so the themes add up over months.

Updated

Mentions or companies?

  • Exports cleaned up by hand
    23 mentions · 4 companies
  • Nobody hears back after reporting
    11 mentions · 8 companies

Why are calls different from tickets and surveys?

Most advice on feedback analysis is written for tickets, reviews and survey answers. Those arrive as short, separate pieces of text, so the usual method is to tag each one and score its sentiment.

Calls are different. One call holds a dozen pieces of feedback, mixed in with small talk and your own questions. The most useful sentences often sound calm, so a sentiment score misses them. And the same customer may say the same thing on four calls, which inflates anything you count by mention.

What calls give you that a survey cannot is the reason behind a request, and whether the customer brought it up themselves. The method below is built to keep both.

Step 1: Which calls do you include?

Every conversation with a customer or a prospect: sales, onboarding, success, renewals, research interviews and the calls where someone leaves. Leave out internal meetings, even when they are about customers. What your team thinks a customer meant is not feedback. For a one-off round of research interviews, see Customer interview analysis.

Keep them in one place, for example a folder in your notetaker, so nothing depends on someone remembering a call.

Step 2: What do you pull out of each call?

Read the transcript, not the summary. For every problem, workaround, request or reason someone gives for buying or leaving, keep one row:

Exact sentenceCompanyAsked?Call, date
"I reported it in March and I don't know if anyone read it."OstromNoSuccess, 4 Sep
"Our analysts export it every Friday and clean it up in Excel."Northvale SystemsYes, we asked about exportsRenewal, 11 Sep
"Adding someone new takes me half a morning."Caldera RetailNoOnboarding, 2 Oct

Keep the sentence word for word. A paraphrase loses how strongly it was said, and it drifts towards what you already believed. The rows above are made-up examples.

"Asked?" is the column most teams skip. If you asked "would you like better exports?", a yes tells you very little. If they brought it up before you asked, it is the strongest signal a call can give. Prompted and unprompted feedback covers the grey cases.

Step 3: How do you group what was said?

Group sentences by the problem underneath, not by the feature they ask for. "Can we get a status page?", "Do you have email updates?" and "Is there a way to see if it's been looked at?" are three requests and one problem: people report things and never hear back.

Name each theme from the customer's side, as a problem they have: "Nobody hears back after reporting something", not "Notifications". A name like that stops the team from jumping to the first fix.

Reuse the same theme names week after week, and merge two themes when they turn out to be the same problem. Themes are worth most once they have run for a few months.

Step 4: What do you count?

Count companies per theme, and separately the ones who raised it without being asked. Not mentions. Here is how much that changes the order, in a made-up quarter:

ThemeMentionsCompaniesWithout being asked
Exports have to be cleaned up by hand2341
Nobody hears back after reporting something1187
Adding a new colleague takes too long962

By mentions, exports win easily. By companies, they come last: one large customer raised it on call after call, mostly when asked. The theme that eight companies raised, seven without being asked, is the one most customers would notice if you fixed it.

We stopped reporting things. It goes into a hole.
Caldera Retail, renewal call (example)

Step 5: What do you do with the top themes?

Bring the top three themes, with one quote each, to whatever meeting decides what gets built. When the team picks one, write a one-page brief with the evidence first and the decision second. The product brief template has a copyable version.

When something ships, tell the companies that raised it. They are the people most likely to notice, and the most likely to tell you more next time.

What should you avoid?

  • Sentiment scores on calls. A calm sentence about a workaround can matter more than an angry one about a typo.
  • Counting mentions. It rewards the customers who talk most, not the problems most customers have.
  • Letting the last call decide. A vivid call this week feels bigger than ten quiet ones last quarter. The sheet is there to correct that.
  • Grouping by feature. It turns the analysis into a list of requests, and the reason behind them disappears. Feature requests: why they mislead shows how to keep the reason.

The full method, with what each rule costs you, is in How to hear your customers. If you record calls in Granola, Find patterns across your Granola customer calls shows how to do steps 1 and 2 from a folder.

Can a tool do the copying?

The thinking in steps 3 to 5 is yours. The copying in step 2 is what makes most teams give up after a few weeks.

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 count opens to the sentences behind it, shows who raised it without being asked, and you decide which calls it reads.

Get started

Works with Granola Business. Any other transcript can be pasted in.