Voice of the Customer Templates: 4 Free Copies, 40 Questions

Quick Summary

Voice of the customer templates give every team the same way to ask for feedback, record it and report it, so the answers can be compared across channels and quarters. This page holds four you can copy as a Google Doc or Sheet, with every field shown inline:

• A VoC survey template with five questions and the context fields that make segmentation possible later
• A 30-minute customer interview guide built around recent, specific stories
• A one-page VoC report template for readouts to leadership
• A VoC matrix that maps customer statements to testable requirements

Below the templates sits a bank of 40 voice of the customer questions, grouped by journey stage and channel, and a short note on the one thing templates cannot do: the analysis.

Why Feedback Needs a Shared Format Before It Needs Analysis

Customers are speaking up less. Qualtrics surveyed close to 24,000 consumers across 23 countries for its 2025 Consumer Trends Report and found that fewer than a third give feedback directly to a company, and that people are 8 points less likely to say anything after a bad experience than they were in 2021. They are not staying quiet because nothing is wrong: PwC found 52% of US consumers have stopped buying from a brand after a bad experience with its products or services.

So every response you do collect carries more weight, and the way you collect it decides whether it can be used. When product runs one survey, support sends a different CSAT form and every interview round uses a fresh script, the results never line up. A theme that shows up in all three gets counted as three small problems instead of one large one.

That is the collection problem, and templates solve it. If you need the background first, start with what voice of the customer means and how to build a voice of the customer program. This page skips the theory and gets you the documents.

Why Listen to Us?

Chattermill is the customer feedback analytics platform behind VoC programs at Uber, HelloFresh, H&M, Booking.com and Trainline. We unify feedback from 65+ channels in 100+ languages, which means we see what happens to survey responses, interview notes and support tickets after they are collected. 

Most of the problems we fix for customers start with a collection step that dropped the context: no customer ID, no segment, no journey stage. The fields in these templates are the ones our customers rely on when they need to split a theme by region, plan or stage, so we built them in from the start.

What a Voice of the Customer Template Should Include

A voice of the customer template is a reusable document that fixes four things in advance so nobody has to decide them each time:

• The questions and scales. The same NPS, CSAT or CES wording every time, so a 7 in March means the same as a 7 in September.
• Context fields. Customer ID, segment, channel and journey stage, passed through from your CRM or survey tool rather than asked.
• A place for the exact words. Verbatim quotes are the raw material for everything downstream, and paraphrasing them early loses the detail.
• An owner. Someone whose name is on the document and who acts on what comes back.

The four templates below each cover a different job in the feedback loop: collecting at scale, collecting in depth, reporting and turning statements into requirements.

1. Voice of the customer survey template

Copy the VoC survey template (Google Doc)

This template works for relationship surveys, which go out on a schedule, and transactional surveys, which fire after an event such as a delivery or a closed ticket. It is deliberately short. SurveyMonkey's analysis of roughly 100,000 surveys found abandonment climbs once a survey passes seven to eight minutes, and Qualtrics reports that completion starts to fall after the third open-text question. The template caps you at two. For distribution and timing advice, see the voice of the customer survey guide.

Setup fields

Questions

1. Score question (pick one). NPS: "How likely are you to recommend [brand] to a friend or colleague?" (0 to 10). CSAT: "How satisfied were you with [experience]?" (1 to 5). CES: "How easy was it to [task]?" (1 to 7).

2. Open "why" follow-up. "What's the main reason for your score?" This is the question that will do the most work in analysis.

3. Driver rating. "How would you rate [part of the experience, such as delivery speed]?" (1 to 5). Pick drivers you can change.

4. Second driver rating (optional). Same format, different part of the experience.

5. Optional open question. "What's one thing we could do better?"

6. Follow-up consent. "Can we contact you about your answers?" (Yes / No). Without this, you cannot close the loop.

Context fields

Customer ID, plan or product, region, language, channel, journey stage (onboarding, usage, support or renewal) and order or ticket ID. The template lists a source system next to each one. Pass them through automatically; never ask customers to type them.

2. Customer Interview Guide

Copy the customer interview guide (Google Doc)

‍

Surveys show you what is happening across thousands of customers. Interviews show you why it happens to one. This guide fits a 30-minute call and keeps the conversation on things that already happened, because people describe last week accurately and predict next year badly. Every block has a time budget so the interviewer gets to the friction section before the call runs out.

Header fields

Interviewee name and role, customer ID, segment, date, interviewer, note-taker and consent to record (Yes / No). The customer ID is there so the interview can be matched to the same person's survey scores and tickets later.

Script

Notes fields

Verbatim quotes with timestamps, pains, workarounds, surprises and a one-line summary. The summary gets written within an hour of the call. Interviewers who leave it until the end of the day tend to remember the conclusion they expected rather than the one they heard.

3. VoC Report Template

Copy the VoC report template (Google Doc)

A VoC report, or readout, is where feedback becomes a decision. The template is one page, in the order a leadership team will read it: what changed, why it changed, what you want done about it and what happened to last period's asks. If your executives only read the first table, they should still leave with the headline.

Report fields

The business impact section is the one most teams skip and the one leadership reads first. A theme that accounts for 12% of feedback but drags NPS down by six points matters more than a theme at 20% that moves nothing. Our framework for connecting NPS to revenue and retention shows how to put a number on it.

4. Voice of the Customer Matrix

Copy the VoC matrix (Google Sheet)

The matrix is the oldest template on this page. Lean Six Sigma teams call it a VOC translation matrix and use it in the Define phase of DMAIC to turn vague customer comments into critical-to-quality requirements that a process can be measured against. The logic holds just as well for a product team working through app reviews: one statement per row, the need underneath it, a requirement someone can test, and a target that says when it is done.

Matrix columns

• Customer statement (verbatim). The comment in the customer's own words.
• Source. Channel, date and customer ID.
• Underlying issue. The need behind the comment, written by you.
• Requirement. A specific, testable change. "Improve delivery communication" is not one. "Customers can reschedule in the app up to 24 hours before dispatch" is.
• Measure and target. How you will know it worked, with a number and a deadline.
• Priority and owner. High, Medium or Low, plus the team on the hook.

The sheet ships with one worked row:

Two habits make the matrix work. Keep the first column verbatim, because the moment you paraphrase you start recording your interpretation instead of the customer's problem. And resist merging rows too early. Ten statements that look alike often split into two or three distinct issues once you write the requirement for each.

40 Voice of the Customer Questions by Journey Stage and Channel

These voice of the customer questions are grouped by the stage of the customer journey, then by the channel each one suits. Survey questions should be answerable in seconds, interview questions should prompt a story and in-app questions should take one tap. Swap [brand], [product] and [task] for your own, and pair every score with a "why" follow-up. Our guides to open-ended survey questions and avoiding bad survey questions cover wording in more depth.

Onboarding questions

Survey

1. How easy was it to complete your first [order or setup]? (1 = very difficult, 7 = very easy)

2. What nearly stopped you from finishing sign-up?

3. Did your first [week or order] match what you expected when you bought? (Yes / Partly / No)

4. Which part of getting started took longer than it should have?

Interview

5. Take me back to the week you signed up. What were you trying to solve?

6. What were you using before, and what made it stop working for you?

7. When was the first moment you felt [product] was, or wasn't, going to work out?

In-app

8. Was this step clear? (thumbs up / thumbs down)

9. What were you expecting to happen here?

10. Would a two-minute walkthrough of this feature help? (Yes / Not now)

Usage questions

Survey

11. How likely are you to recommend [brand] to a friend or colleague? (0 to 10)

12. What's the main reason for your score?

13. Which part of [product] do you rely on most, and why?

14. What do you still go elsewhere to do?

Interview

15. Describe the last time you used [product]. What were you trying to get done?

16. When did it last get in your way, and what did you do instead?

17. If [product] disappeared tomorrow, what would change about your week?

In-app

18. How well did this feature do what you needed? (1 to 5)

19. What's missing from this screen?

20. Did this take longer than you expected? (Yes / No)

Support questions

Survey

21. How satisfied are you with the help you received today? (1 to 5)

22. How much effort did it take to get your issue sorted? (1 = very little, 7 = a great deal)

23. Is your issue fully resolved? (Yes / Partly / No)

24. What could we have done so you didn't need to contact us?

Interview

25. Walk me through what happened before you reached out.

26. Where did you look for an answer first, and what did you find?

27. What did the person who helped you do that made the biggest difference, good or bad?

In-app

28. Did this article answer your question? (Yes / No)

29. What were you looking for that you didn't find here?

30. How was your chat with us today? (thumbs up / thumbs down)

Renewal questions

Survey

31. How likely are you to renew or order again in the next [period]? (1 to 5)

32. What has [product] helped you achieve this year?

33. What would make you consider switching to another provider?

34. Which single change would make renewing an obvious decision?

Interview

35. What goes into the renewal decision on your side, and who else is involved?

36. What have you seen elsewhere that you wish we offered?

37. If your budget were cut tomorrow, where would we sit on the list of things to keep?

In-app

38. What's the main reason you're cancelling? (multiple choice, plus "other")

39. Is there one thing we could fix that would change your mind?

40. Would you be open to a short call before you go? (Yes / No)

What These Templates Don't Solve

Every template on this page improves the collection side. None of them helps once the responses pile up, and for a brand with any volume that happens in the first month.

Take the survey template at face value: one score and one open "why" per response. Send it after 15,000 deliveries a month and you have 15,000 comments to read, before you count the support tickets, app reviews and call transcripts that arrive without any template at all. Tagging them in a spreadsheet works for the first few hundred. 

After that, the tags drift as different people apply them, and the themes stop matching the ones in the matrix. Pasting batches into ChatGPT runs into the same problem from the other direction: each prompt invents its own categories.

This is the gap Chattermill fills. The platform pulls feedback from 65+ channels into one place and tags every comment against a single set of themes, using Lyra, our AI engine, to find the specific issue inside each one rather than a sentiment score. 

Impact analysis then shows which themes are moving NPS, CSAT or CES, and by how much, which is the business impact row of the report template filled in for you. Because the context fields in these templates carry straight through, any theme can be split by segment, region or journey stage.

Limehome, which collects thousands of online reviews a month, runs feedback through Chattermill across its executive, product, support, operations and marketing teams and grew NPS by 20% in a year. 

Julia Zuber, its Senior Customer Insights Manager, describes the platform as doing "what no human could": reading thousands of reviews in real time, categorising them and assigning sentiment and themes so the team can prioritise.

If you are weighing up options, our roundup of the best voice of customer tools covers the wider market. Or book a demo and we will run your own feedback through the platform.

Start With One Template and Plan for the Volume

You don't need all four templates on day one. Copy the survey, send it to one segment this month and keep the context fields intact. When the first themes repeat, open the matrix and give each one a requirement, an owner and a target. The report template earns its place the first time leadership asks what changed and why.

What you will hit next is volume, and no template fixes that. When the open-text answers outgrow a spreadsheet, book a demo and we will show you what your customers are already telling you, with the reasons behind every number.

FAQs

What is a voice of the customer template?

A voice of the customer template is a reusable document or spreadsheet that standardises how a company collects, records and reports customer feedback. It fixes the questions, scales, context fields and ownership in advance so responses from different teams, channels and time periods can be compared. The four on this page cover surveys, interviews, reporting and requirements mapping.

What questions should a voice of the customer survey include?

A VoC survey needs one score question (NPS, CSAT or CES), one open question asking why, and at most one or two short driver ratings on parts of the experience you control. Add a consent question so you can follow up. Everything else, such as customer ID, segment and journey stage, should be passed through from your systems rather than asked.

How many questions should a VoC survey have?

Five or fewer for most transactional surveys. SurveyMonkey's data shows abandonment rising once a survey passes seven to eight minutes, and Qualtrics finds completion falls after the third open-text question. A relationship survey sent quarterly can run slightly longer, but every extra question costs responses from the customers you most want to hear from.

What is a VoC matrix?

A VoC matrix, also called a VOC translation matrix, is a table that turns individual customer statements into measurable requirements. Each row holds the verbatim comment, the issue underneath it, a testable requirement, a measure and target, a priority and an owner. It comes from Lean Six Sigma, where it is used in the Define phase of DMAIC, but any product or CX team can use it.

How often should you run a voice of the customer survey?

Run transactional surveys continuously, triggered by events such as a delivery, a closed ticket or a cancellation. Run relationship surveys on a fixed schedule, usually quarterly. Set an exclusion rule, such as no customer surveyed more than once every 30 days, so the two don't overlap and wear out your response rate.