Put the voice back in voice of customer
By Nic Chamberlain · Published · Updated
Short answer: to put the customer's voice back into voice of customer, interview customers at the moments that matter and ask your ratings inside the same conversation. You keep your CX metrics and hear the reasons behind them in customers' own words.
Voice of customer was meant to bring the customer's voice into the business. Too often it brings back a score. The score is useful, but somewhere between the survey and the slide, the voice went missing.
This post is about getting it back: running real conversations with customers at the moments that matter, while keeping the metrics your CX programme already tracks.
Where do voice of customer programmes lose the voice?
A typical programme is built on surveys. Surveys are good at counting, and a satisfaction score of 7.9 is easy to track and easy to report. What it can't do is tell you what sits behind it.
Take a customer who scores you a solid 8. In conversation they might say (an illustrative example): "I nearly left in March. The app lost a payment and no one called. I stayed because switching is a hassle, not because you fixed it." That customer looks loyal on the dashboard. They're one bad week from leaving.
Two places the voice usually gets lost:
-
Closed questions only confirm what you thought to ask. If the issue isn't on the list, it doesn't show up. The open comment box at the end collects a few words from a few people, and it's hard to find time to read them properly.
-
It arrives late. A quarterly or annual wave tells you about problems after they've already cost you customers.
None of this is a reason to stop measuring. It's a reason to add the conversation back.
What does a conversation add to voice of customer?
Juno runs AI-moderated interviews with real people. Each one adapts to the customer: it follows the thread of what they say and asks why it mattered to them. Customers take part in their browser by voice or text, with nothing to download.
The interviews aren't only open conversation. Rating scales and choice questions can sit inside the same interview, so you can collect ratings and the reasons behind them from the same person. Keep an established tracker while checking whether changes in format, timing or sampling affect comparability.
Because the interviews run at scale, you can hear from far more customers than a round of traditional interviews would allow. That makes it possible to run voice of customer as an ongoing programme, not a once-a-year project.
How do you run a voice of customer programme with AI interviews?
1. Brief Juno on what you need to understand
Describe the decision or the part of the journey you're worried about, the way you'd brief a researcher. For example:
"New customers are dropping off in their first month and our satisfaction scores haven't moved. We need to know what's getting in the way, and what nearly stopped the ones who stayed."
Juno turns that into research objectives rather than a fixed script, so each interview can follow what matters to that customer.
2. Reach customers where they already are
Send the interview link at the moment you want to hear about: partway through onboarding, or once a support case closes. It can go out through the tools you already use to reach customers, and carry your own brand.
3. Let the interview dig
When a customer says "the app was confusing", Juno asks what they were trying to do and where it went wrong. Any ratings you need sit inside the same conversation, so the number and the reason come from the same person at the same moment.
4. Get findings you can trace
Findings come back organised around your objectives, each linked to the customers and quotes behind it, and to the audio where it's available. You can debrief with Juno, challenge a finding, and drill into the evidence before you take it to the team.
When should you ask customers?
The best time to ask is while the experience is fresh. These are common moments to choose, and what each one tends to tell you.
| Moment | When to ask | What you hear |
|---|---|---|
| Onboarding | Just after someone signs up | Why they chose you, and the first friction they hit |
| First value | Once they start getting what they came for | What "working" looks like to them, and what nearly stopped them |
| Friction | After a complaint or support contact | What went wrong and how it felt, not just whether it was resolved |
| Renewal | Ahead of a renewal date | What keeps them, and what is quietly wobbling before it shows in the numbers |
| Cancellation | When they leave | The real reason they went, while it's still fresh |
| Win-back | Once they've lapsed | What it would honestly take to bring them back |
You don't need all six at once. A good place to start is the moment you understand least, such as cancellation or the first month.
How do findings turn into action?
A score moves and no one can prove why, so the meeting turns into a working group trading theories. The point of hearing customers directly is to skip that step. When a finding arrives with the quotes behind it, the person who owns that part of the experience can see the problem for themselves and act on it.
Juno tells you what customers said and why. What to do about it stays with your team, and it's a much easier call when the reasons are in front of you.
Always on, or in waves
You can run Juno as your voice of customer programme in its own right, by sending interview links at each moment you care about through your existing customer-contact tools. This requires your team to arrange the invitations; it is not a promise of built-in event triggers. Or you can run it in waves, as the depth beneath the CX and NPS measurement you already have. Starting with waves and moving to always on once you've seen what comes back is a sensible path.
A note on numbers
This runs on smaller samples than a large survey wave, by design. A survey tells you how many customers feel something. Interviews tell you why. Keep your survey for the counting, and use the conversations to understand what's behind each movement.
What doesn't this replace?
Your CX metrics stay the consistent, comparable measures they already are, and Juno doesn't replace your research or insight team. Your team still owns the questions and the decisions. What Juno adds is the customer's voice, in their own words, at the moments that matter.
Checklist: starting a voice of customer programme with interviews
-
Pick the one moment in the customer journey you understand least.
-
Write down the decision the findings should inform.
-
Keep the ratings you already report, and ask them inside the interview.
-
Send the interview while the experience is fresh, through the channels you already use.
-
Check each finding against the quotes behind it, and get it to the person who owns that part of the experience.
-
Once the first moment is working, add the next one.
Frequently asked questions
Do we have to give up our surveys? No. Juno can ask quant questions too. Rating scales, rankings, multiple choice, yes/no and number questions sit inside the same interview as the open conversation, so you can collect ratings and their reasons together. Check comparability before combining those ratings with a historical tracker. You can also run Juno alongside the surveys you already have.
Can we interview our own customers? Yes. You send them a link to the interview through whatever channel you already use to reach them. Nothing to download.
Can it carry our brand? Yes. You can set your organisation's brand for the interview and the reports.
How long does it take? Days, not months. Interviews run as customers complete them, so timing mostly depends on how quickly your customers respond.
How are findings presented? As claims linked to the evidence behind them, down to the quote and the moment in the transcript. You can debrief with Juno and challenge any finding.
Juno is built on 25+ years of experience in human behavioural research. See how it works or get in touch.