The loop
The voice of customer process turns what customers say into changes they notice. It is a loop, not a project.
- Collect feedback from every source.
- Classify it into topics with sentiment.
- Prioritise what matters most.
- Assign owners and act.
- Check whether the fix worked.
- Tell customers and staff what changed.
1. Collect
Start with what you already have: Google reviews of every store, app reviews, complaint logs, form comments, call notes. Add new collection only where gaps remain. Keep the source, date, location and channel of every piece of feedback.
What is voice of customer?
What is voice of customer2. Classify
Use one topic list for all sources, built from your own feedback, with sentiment for each mention. Keep the customer's words attached to every label so anyone can check it.
3. Prioritise
Rank topics by negative volume, negative share and trend, then weigh cost and control. Pick a few priorities per period.
Prioritising CX fixes by volume, negativity and trend.
Prioritising cx fixes volume negativity and trend4. Assign and act
Each priority gets an owner in the team that can fix it, such as operations, product, merchandising or policy, with an agreed action and date. The CX team supports; it does not own every fix.
Assigning owners to CX themes.
Assigning owners to cx themes5. Check
After the fix, watch the topic's negative share in the stores or segments affected, compared with the period before and with places not yet changed. If it did not fall, find out why.
Free review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
6. Communicate
Tell staff what changed because of customer feedback, and tell customers where you can, for example in replies to reviews that raised the issue. It shows feedback is used, and encourages more of it.
Rhythm
- Weekly: new spikes and urgent issues.
- Monthly: action review with owners.
- Quarterly: priorities refreshed.
- Yearly: strategy and topic list reviewed.
Governance: a monthly CX action review.
Governance a monthly cx action reviewAn example
A restaurant chain collected reviews from all outlets, classified them and found waiting times at weekend lunch rising fastest. Operations owned it, added a second cashier at the busiest outlets, and checked weekend-lunch complaints for six weeks. They fell at those outlets and not elsewhere; the change was rolled out.
Common mistakes
- Collecting more before using what you have.
- Different topic lists per source.
- CX owns every fix.
- No check after the fix.
- Never telling anyone what changed.
Common questions
Who runs the process?
A CX lead or analyst, with owners across the business.
How long to set up?
A first loop can run within weeks using existing feedback.
Do we need new software?
Not to start; you need consistent classification and a routine.
How do we show value?
Count fixes made and checked, and the change in their topics.
Checklist
- Existing sources collected.
- One topic list.
- Few priorities with owners.
- Fixes checked.
- Changes communicated.
In short
Collect existing feedback, classify it with one topic list, prioritise, give each priority an owner, check the fix and tell people what changed, in a monthly loop.
Doing this with Falcon
Falcon does not run surveys or feedback forms. It analyses the feedback customers volunteer in Google Maps and Google Play reviews, sorted into themes from your own reviews, which you can set beside survey scores to see the reasons behind them. Negative share by topic, location and month shows which reasons are growing, and every number opens the reviews it was built from.