Voice customer feedback: the why behind the score.
A score shows a trend. One focused voice question can add the customer's words, examples, and context without requiring a live call.
The short answer
What a score cannot tell you
A 7 from a churning customer and a 7 from a loyal one who hit a bug look identical on a dashboard. Same row, same number, same color. You only know which is which when you ask. The score tells you there is a signal somewhere. It does not tell you what the signal is.
NPS and CSAT are still useful, as trend lines, as board metrics, as a quick pulse across a large customer base. That is what they were designed for. What they were not designed for is explaining why the number moved. A score going from 42 to 37 in a quarter is a fact. The reason is a conversation. Most teams skip that conversation because it takes time and calendar space they do not have.
A text follow-up can work well when the answer is short or needs precision. Voice is worth testing when you want a story, example, or explanation in the customer's own words. Keep both routes available when your audience may not have privacy to speak.
When to send a voice link
These moments give the customer a recent event to talk about.
After a product trial ends
Most post-trial surveys ask whether someone plans to subscribe. That is the wrong question. Ask: “What almost made you sign up?” The almost is where your product loses the sale. A churned trial user can explain the gap in their own words. Compare those answers with behavior and conversion data before deciding why people did not buy.
After a support ticket closes
The standard follow-up is a CSAT star rating. It tells you whether the customer is happy with support, not whether the underlying problem is actually resolved. Those are different things. A voice link with one question, “Did we actually fix the problem for you?”, tells you which it was. Sent within an soon after the ticket closes, while the experience is still easy to remember.
Post-churn
Exit interviews can be difficult to schedule because they feel awkward to schedule and the customer has already moved on. A voice link removes the friction. “What would have made you stay?” is a 60-second ask, not a 30-minute call. Some customers will not respond. The ones who do are often direct, and some will name something specific and fixable.
After a big feature ships
Usage data tells you whether customers tried the feature. It does not tell you what they thought of it. Send a link to the a relevant group of early users and ask: “What is your first reaction to [feature name]?” You will get a mix of genuine enthusiasm, confusion about where to find things, and edge cases your QA missed. Compare the answers with product data and support tickets before changing the feature.
Regular pulse check
At a useful interval, send a link to a rotating group of active customers with one question: “What is the one thing you would change about [product] right now?” No context, no preamble. The answers self-organize around whatever is actually frustrating people at that moment. Over time you get a running picture of what your product feels like to use, something no dashboard metric gives you.
How it works for your customers
You create a Magic Link in HeySpeak with one question attached. The link goes into whatever message you already send: email, Slack, your support tool. The customer clicks it, sees your question, taps record on their phone or laptop, speaks for up to 60 seconds, and hits send. No app download. No account creation. No form to fill out.
HeySpeak transcribes every response automatically and generates a short AI summary. You can scan summaries in your dashboard and click through to the audio or full transcript for anything that stands out. If a customer prefers not to speak, they can use the written option. A calendar link can also appear when you configured one.
Audio is stored privately and transcription uses Mistral models. Check the current data protection page for processing locations, subprocessors, retention, and your responsibilities as the sender.
Keep going
Two more pages on getting real signal from customers.
Common questions
Can I use this alongside NPS, or does it replace it?
What question should I ask customers for feedback?
How do I make sure customers actually respond?
What do I do with the voice responses?
Is customer voice data stored securely?
Hear from your customers this week.
Five free responses to start. No credit card.
Create your first link