Voice of the customer, explained for small teams

Voice of the customer is what your customers say they need, in their own words, gathered on purpose and put to use. Some of it arrives without you asking, in support messages, reviews and sales calls. The rest you ask for, in interviews and surveys. It only counts once it changes something, such as the product, a page or a price.

A founder who answers support alone already hears most of it every day, and needs a routine more than software. Deacon is an AI customer support agent for founders like that. It replies to your customers in seconds from your own docs. It also keeps a running tally of what they ask, grouped by topic with a count of the people behind each, so you see what they’re stuck on and what they want next without sorting anything yourself. There’s a free plan, and it needs no card.

Where the term voice of the customer comes from

The term comes from quality management in manufacturing. The usual reference is The Voice of the Customer, a paper by Abbie Griffin and John Hauser in the journal Marketing Science in 1993. It studied the part of Quality Function Deployment that deals with customers’ needs. That’s a way of designing products that the paper traces to Mitsubishi’s Kobe shipyards in 1972 and to Toyota in the late 1970s. It came to the US in 1986, first at Ford and Xerox.

The paper’s definition of a customer need is still the useful one. A need is the benefit a customer wants, described in their words, and not a solution or a measurement. Its example is a computer user who wants lines on the screen to look straight, with no stair-step effect. A particular monitor is one way to meet that need, and a team that jumps straight to it can miss better ones. So when a customer asks for a feature, the need is whatever made them ask.

Two of the paper’s findings are worth knowing before you count anything.

How often a need comes up isn’t how much it matters

Griffin and Hauser had customers rate how important each need was, then checked whether the important ones came up more often in interviews. They didn’t. In a study of coolers, picnic baskets and other ways of carrying food, the needs rated most important were mentioned no more often than the rest. A count tells you how many people ran into something. How much it matters to them comes from reading what they wrote, and from asking.

Satisfaction scores lean towards the customers who chose you

A satisfaction survey asks people to rate the product they picked, so it mostly hears from people it already suits. In the paper’s data, a brand that had led its category for over 20 years had an average satisfaction score below many other brands’, and the highest score belonged to a small niche brand. A survey on your own site leans the same way, because the people who left aren’t there to answer it.

Seven ways to collect the voice of the customer

Each method hears from a different group of people and takes a different amount of your time. Feedback platforms such as Qualtrics split them into solicited feedback, which you asked for, and unsolicited feedback, which people offered. Usage data is neither, because it records what people did rather than what they said.

Which ways to use first

What you can use depends on how far along you are.

Before launch, interviews are all you have. Talk to the people you’re building for about their problem rather than your product, and write down the words they use.

After launch, support conversations and usage data carry most of it. Every early question is someone telling you where the product or a page fell short, and your website analytics shows where visitors leave without asking anything. What to do after you launch covers the first week.

Surveys earn their place once enough customers answer for the numbers to settle. With 30 replies, each one is more than 3% of the result, so one bad week can look like a trend.

Of the seven, support conversations give a founder the most for the least time. Customer insights from the questions customers ask goes through what each kind of question tells you and how to act on it.

What a voice of the customer programme is

A voice of the customer programme is the routine that turns what customers say into changes. It has four steps, repeated on a schedule.

1. Collect what customers say from the sources you chose, in their words, in one place.
2. Sort it into themes, each a need that one change would meet, with a count of the people behind each.
3. Act on a theme by changing the product, a page or a price, or by deciding plainly not to.
4. Tell the people who asked what changed.

At a large company the programme belongs to the customer experience team, and each step has its own owner. VoC platforms even have a name for the fourth step, closing the loop. Qualtrics splits it into an inner loop, which replies to the customer who raised something, and an outer loop, which sends a problem that keeps recurring to the team that can fix it.

A small team’s programme fits in an hour a week

At a company of one, you own every step, so the programme is one list and one hour a week. Keep the same hour each week and split it three ways.

• Spend the first 20 minutes adding the week’s questions and requests to the list in customers’ words, and adding one to a theme’s count for each new person who raised it.
• Spend the next 20 choosing one theme and deciding what changes.
• Spend the last 20 telling the people behind last week’s theme what you changed, in a two-line email each.

Choose the theme by weighing its count against who is asking and what the problem costs them, since the count only tells you how common a need is. A how-to question that keeps coming back is usually fixed on the page it was asked from, and how to reduce support tickets shows how to find those.

The last 20 minutes are the ones small teams skip, and the ones customers notice. A customer who hears that their request shipped learns that writing in works, so they write in again, and your list gets better for it.

Voice of the customer software and who it’s built for

Voice of the customer software, or VoC software, gathers feedback from many channels into one place, sorts the text into themes and sentiment, and sends what it finds to the teams that act on it. It’s built for companies with a customer experience or research team, and more comments than those people can read. These four, prices included, were read on their own sites on 27 September 2026, and they’re listed in no order.

For a small team, the deciding question is volume. Thematic’s Foundation plan takes up to 25,000 comments, and Thematic says it works best with at least 2,000. If you can read everything customers sent this week in an hour, a list and a count do this job, and the platforms can wait until you can’t.

How Deacon collects the voice of the customer from your chat

Most founders hear the voice of the customer from the few people who email. Deacon hears from everyone who asks on your site. It answers them in seconds, at any hour, from your website, your files and the answers you write, in whatever language the visitor writes in. When your docs don’t cover a question, it says it doesn’t know instead of guessing and asks for the visitor’s email, and you get an email when they leave one.

Every conversation is saved word for word and searchable by what visitors asked, so you can pull up every conversation in which someone asked about invoices, in their own words. That’s the first step of the programme, done for you.

Topics does the sorting and the counting. It groups similar questions across conversations and counts the people behind each group. A topic is listed once two people have asked, and most get a type, such as a feature ask, a bug report or a how-to, so the requests and the problems don’t sit in one pile.

Analytics › Widget shows the languages people wrote in, so you can see who’s finding you. Once one page’s questions go unanswered more often than anywhere else on your site, it names that page, and that’s where people are getting stuck.

Deacon doesn’t run surveys or score sentiment. What it collects is the voice of the customer nobody had to ask for, from the moment each person needed something.

Every answer you write makes Deacon better. A question your docs didn’t cover gets an Answer this button, and Save & check shows you the reply Deacon now gives and how many other open questions your answer covers. So acting on a theme can be as quick as writing the answer once.

The same script runs your website analytics, so the usage data from the table sits beside what people asked, with no second script to add.

Every feature is on every plan, the free one included. Free gives you 50 answers a month, needs no card and has no end date, and nothing is billed past a plan’s answers.

Questions about voice of the customer

How many customers should I interview?

Aim for 20 to 30 for each kind of customer you serve. Griffin and Hauser interviewed 30 people about carrying food, and a random 20 of them raised, on average, over 90% of the needs that all 30 did. In their office-equipment study, two one-hour interviews turned up about as many needs as one two-hour focus group, so you don’t need a room full of people. Have more than one person read your notes, too. In the food study, a single analyst reading the transcripts found 54% of the needs on average.

What’s an example of voice of the customer?

Say three customers ask in one week whether you connect to Xero. The need behind it is getting their invoices into their accounts without typing them twice. The change might be the integration, a download their accountant can import, or a line on your pricing page saying what’s coming, followed by an email to the three who asked. A review saying set-up took an afternoon, or a prospect who chose a rival because it offered single sign-on, would go on the same list.

Is Deacon voice of the customer software?

No. VoC platforms such as Qualtrics and Medallia gather feedback from surveys, calls, reviews and social posts across a whole company. Deacon is an AI support agent. It answers customers on your website and shows you what they asked, which is the voice of the customer from one channel, your chat, already sorted. It doesn’t read your email, your reviews or your sales calls.

Can I send Deacon’s conversations to a VoC tool?

Not automatically. Deacon has no CSV export, no outgoing webhooks and no public API for conversations, so they stay in its dashboard. You can search and read every one of them there.