Cloud4Feed
Request a Demo
Customers Pricing
Request a Demo

Building a Voice of Customer programme

Who to ask, when to ask, and how to turn answers into action. A practical guide to designing a VoC programme that changes decisions, not just dashboards.

Cloud4Feed Research Team Updated 6 min read
Quick answer

A VoC programme is the system an organisation uses to collect customer feedback across channels, understand it and act on it, then tell customers what changed. Surveys are one part; the programme is the loop around them.

Listen → understand → act → tell customers what changedPlan your responses ↓

At a glance

Goal
Hear customers on purpose and act on it
Listening posts
Direct, indirect and inferred
Core metrics
NPS, CSAT, CES and open comments
Owner
A CX team with a senior sponsor
Start with
Two or three critical journeys

What is a Voice of Customer programme?

A Voice of Customer (VoC) programme is the system an organisation uses to hear its customers on purpose: it collects feedback across channels, turns it into insight and makes sure something happens as a result. A survey tool on its own is not a programme. The programme is the loop around it: listen, understand, act, and tell customers what changed.

Most organisations already collect plenty of feedback. What they often lack is a design: clear questions, the right moments, owners for each kind of signal and a rhythm for turning what they hear into decisions. This guide walks through those choices.

Where to listen

Customers speak in many places, and only some of them are surveys. A good programme combines three kinds of listening post.

KindExamplesStrength
DirectRelational NPS, transactional CSAT and CES, open questionsYou choose the question and the moment
IndirectContact-centre calls and chats, complaints, online reviews, social mediaUnprompted, in the customer’s own words
InferredBehaviour and operational data: repeat contacts, returns, churn, waiting timesShows what people do, not only what they say

Who to ask

For relational measurement, survey a representative sample of active customers, so the score reflects the whole base rather than whoever happened to call this week. For transactional measurement, invite customers who have just completed the interaction you want to improve. Do not forget the people who are easy to miss: customers who left, prospects who did not buy and customers with an open complaint, whose feedback you should collect through the case rather than a survey.

Decide in advance which segments you need to report separately, such as region, customer value or channel, because each segment needs enough responses of its own.

When to ask

Ask transactional questions as close to the moment as possible, ideally the same day. Run relational surveys on a fixed schedule, quarterly or twice a year, and keep the timing the same between waves. Then protect customers from over-surveying with a contact rule, for example no more than one survey to the same person within a set number of weeks, and no survey while a complaint is still open.

What to ask

Keep it short: one metric question, one open “why” question and, only if you will use them, a few driver questions. A survey that takes more than a couple of minutes on a phone loses people. Keep the wording identical over time so the trend means something.

A minimal transactional survey

How satisfied were you with [the experience]? What is the main reason for your score?

Use the NPS, CSAT and CES guides to choose the metric for each moment.

Response planner

How many responses do you need for a result you can trust, and how many invitations does that take?

Your response plan
385responses per segment
1,540responses in total
10,267invitations to send

From answers to action

Feedback only creates value when it changes something. Act on two levels.

Inner loop

Customer

The frontline follows up with individual customers, especially those who gave low scores; the closing-the-loop guide covers this.

Outer loop

Organisation

The organisation looks across all feedback for the issues that keep coming back and fixes their root causes.

For the outer loop, tag open comments by topic and sentiment, find which topics move the score with a driver model such as SEM, and use MaxDiff when you need customers to rank competing priorities. Then tell customers and employees what changed; it is the strongest reason for them to keep answering.

Who owns what

Give the programme a single owner, usually a CX team, and a senior sponsor who can unblock budget and decisions. Each listening post needs a named owner, and each recurring topic needs someone who is accountable for fixing it. A simple rhythm keeps it moving:

Weekly

Operational review of alerts and open cases.

Monthly

CX review of topics and actions.

Quarterly

Leadership review of trends and investments.

Track the health of the programme, not only the scores: response rate, the share of low scores followed up within target, the number of actions completed and the trend of the main metrics.

Your first 90 days

  1. Pick two or three critical journeys where you know customers struggle or where most revenue sits.
  2. Set a baseline from the data you already have: complaints, reviews, operational figures.
  3. Launch short surveys and alerts at those moments, with owners for every low score.
  4. Hold the first action review after a month and agree two or three fixes.
  5. Share the first wins with customers, employees and leadership, then add the next journey.

VoC programme FAQ

As few as possible: one metric question and one open question cover most needs. Add driver questions only if someone will analyse and act on them.

Cloud4Feed Research Team

Our research, analytics and CX team writes about what we learn running feedback programmes across 15+ industries.

About us →

New guides and research, once a month.

No sales emails. Unsubscribe anytime.

We use your details to respond to your request. See our Privacy Policy.

Ready to put this into practice?

A 45-minute walkthrough set up for your industry and your team.