Voice of the customer template: the three documents that run a programme

People searching for a voice of the customer template usually want one thing: the survey. Fair enough, and a working VoC practice actually runs on three short documents: the survey itself, the plan behind each touchpoint, and the monthly brief that carries the findings to the people who act. All three fit on a page. Here they are, ready to copy.

Key takeaways:

• Three documents run a VoC practice: a thirty-second survey, a one-page touchpoint plan, a fixed-format monthly brief.
• The survey template is two questions; the plan template is six explicit choices; the brief template is findings, disagreements, movement and decisions.
• If the "decision this feeds" line of the plan is empty, the survey is not ready to launch.
• The closing promise ("we read every answer") is the highest-risk line in the survey. Template it only if you will keep it.
• Channel choice moves response rates by an order of magnitude, from roughly 3% on ecommerce email to over 80% at the point of sale; pick it in the plan, not by habit.

Template 1: the VoC survey

For a recurring touchpoint, the survey can remain very short:

For a delivery, that could read: "Your order arrived today. Two quick questions, about thirty seconds. How satisfied were you with your delivery? What is the main reason for your score? Thank you."

Resist decorating this. Every element that could be added, a rating for the courier, a product-quality matrix, a channel-preference question, has a department that wants it and a cost the department will not pay: the response rate. The template's brevity is not minimalism for its own sake; it is the feature that keeps the data representative.

A word about that closing line, because it is the most dangerous sentence in the template. It lands in a low-trust world: the 2025 Edelman Trust Barometer found 68% of people worry that business leaders deliberately mislead them. A promise to read and act is therefore either your strongest differentiator or one more confirmation of the cynicism, depending entirely on whether something visibly changes. Only template the promise if you keep it; the mechanics of keeping it are the subject of the feedback loops guide. The exact wording of the questions, and the ones to avoid, are covered in voice of the customer questions.

Template 2: the touchpoint plan

Before a survey goes live, use the four-leaf clover as the basis of a one-page plan that makes six choices explicit:

Plus one hygiene line: the contact policy check, how often can this customer already be surveyed elsewhere?

If the decision line is empty, do not launch the survey yet. The plan exists to make sure the organisation knows why it is asking and who will use the answers.

The channel row deserves more respect than it usually gets, because the differences are not marginal. Current benchmarks put e-commerce email survey response around 3.24%, in-app surveys around 27%, and a single question at the point of sale at roughly 84%. The same two questions, asked in a different place, can hear twenty-five times more customers. Choose the channel where your customers already are at the moment that matters, not the one your tooling makes easiest.

Template 3: the monthly VoC brief

Use the same one-page structure for the monthly findings:

• What the voice says: the top three findings, each as a chain: topic, impact on the score, affected segment, one raw customer quote.
• Where the sources disagree: surveys versus reviews versus support, and which customers sit in the gap.
• What moved: topics rising or falling since last month, and the fixes confirmed by a before-and-after.
• Decisions requested: what the owners are asked to schedule, in impact order.

Bring this page to the monthly cross-functional review of the voice of customer programme. The guide to voice of customer analysis explains the reasoning behind the format. Keeping the shape stable makes changes easier to see and turns an empty "what moved" section into a useful prompt.

A filled finding, for calibration: "Refund delays: 6.4% of feedback, up from 2.1%; strongest detractor driver this quarter; concentrated in web orders returned in-store; 'third week waiting for my money back.' Requested: finance operations restores the daily refund batch." One line of evidence, one line of ask. Twelve months of these briefs, stapled together, also happen to be the annual report and the budget case, already written.

A filled example: the delivery touchpoint

Templates convince fastest when filled in. Here is template 2 completed for a webshop's delivery moment:

• Decision this feeds: whether to switch carriers in two regions at the next contract renewal, and which delivery promises the site should make per region.
• What we ask: CSAT ("How satisfied were you with your delivery?") plus the open why.
• Whom we ask: every customer whose order was delivered, with order value, region, carrier and first-versus-repeat status attached as metadata.
• When we ask: triggered by the carrier's delivered scan, sent four hours later, no later than the same evening.
• Through which channel: email for desktop buyers, with the score question embedded in the mail itself; push notification for app buyers.
• Who owns the answers: the logistics manager receives detractor alerts daily; the monthly review compares carriers and regions.
• Contact policy check: suppressed if the customer received any survey in the past 21 days, and always suppressed while a complaint is open.

Fill the same seven lines for a support conversation or a claim and the differences do the thinking for you: the metric changes to CES, the trigger to case-closed, the owner to the support lead, and the alert window shrinks, because an unhappy customer after a support contact is further along the road to leaving than one with a late parcel.

Three ways the templates fail

1. Copying the survey without the plan. The visible questions are easy to reuse, but the value depends on the decision, owner and follow-up behind them.
2. Question creep. Departments add one item at a time until a short survey becomes a questionnaire. Protect the two-question core and require a decision for every addition.
3. A brief without a routine. The monthly page needs a consistent owner and a meeting in which decisions are taken.

Where the templates live

A template that lives in one analyst's drive is a personal habit, not an operating standard. Give the three documents a home and a little governance:

• One shared folder per journey, holding the touchpoint plans and the monthly briefs, named by date. When someone asks why the delivery survey asks what it asks, the plan answers without a meeting.
• One owner per document type. The programme manager owns the survey and plan templates; the CX lead owns the brief format. Changes to the shape of any template are announced, dated and rare, for the same reason survey wording stays stable: comparability across months is worth more than this month's clever improvement.
• Version the filled plans, not just the blanks. When a touchpoint plan changes (new channel, new trigger timing), the old version stays in the folder. Six months later, the response-rate step change in the chart has an explanation on file.

This is fifteen minutes of structure, and it is the difference between a programme that survives its founder's holiday and one that quietly improvises until the trend lines stop meaning anything.

Frequently asked questions

What should a voice of the customer template include?

Use three parts: a short survey, a touchpoint plan that states the decision and owner, and a monthly brief that shows findings, differences between sources, movement and decisions required.

How long should a VoC survey be?

Aim for roughly thirty seconds: one score question and one open question, with at most one temporary closed question tied to a live decision.

How do I adapt the template per touchpoint?

Change the score type (NPS for the relationship, CSAT for moments, CES for processes), name the moment in the question, and fill in a fresh touchpoint plan. The structure stays identical; the four-leaf choices change.

How often should the templates be reviewed?

The survey rarely; stability keeps trends readable. The touchpoint plan yearly, or when the journey changes. The brief monthly by design, with its shape held constant.

Can I use the same template for employees?

The structure carries over directly: score, why, plan, brief. Only the metric changes (eNPS for the relationship question) and the routing, since the owners sit in HR and team leads rather than CX. There is every reason to run it: Gallup's global tracking shows employee engagement falling for a second consecutive year, at its lowest since 2020, with productivity losses Gallup sizes at roughly 9% of global GDP. The people delivering your customer experience deserve the same thirty-second listening discipline as the people receiving it.

The templates only work if the routine does

The documents are deliberately simple. Their value comes from the discipline around them: asking only what will be used, reviewing the findings on a fixed rhythm, assigning decisions and telling customers when their feedback led to a change. Copy the pages, but copy the routine with them; the first is an afternoon's work, the second is the programme.