Side by side
| Aspect | Mystery shopping | Reviews |
|---|---|---|
| Who | Trained visitors on scripted scenarios | Real customers, with their own priorities |
| Measures | Compliance with standards | Impact: what customers noticed and felt |
| Frequency | A few visits per store per period | Continuous and plentiful |
| Strength | Controlled and comparable | Shows what customers actually care about |
| Biases | One visit can mislead; scripts miss things | Self-selected; many have no text |
| Cost | Costs money for each visit | Already there, no collection cost |
| Best use | Checking specific standards | Finding which stores and topics need attention |
- Mystery shopping: trained visitors, scripted scenarios, a checklist of standards; controlled and comparable; a few visits per store per period.
- Reviews: real customers, their own experiences and priorities; continuous and plentiful; self-selected, unstructured.
What each measures
Mystery shopping measures compliance: was the greeting given, was the product explained, was the store tidy at the time of the visit. Reviews measure impact: what customers noticed and how they felt. A store can pass a mystery shop and still draw complaints about the thing the script did not cover.
Biases
- Mystery shopping: a single visit can be unrepresentative; staff may spot shoppers; scripts miss what customers care about.
- Reviews: written by those motivated to write; many have no text; volume varies by store.
Using them together
- Use reviews to find which stores and topics need attention.
- Use mystery shopping to check the specific standards behind those topics.
- Update mystery shopping scripts with what customers actually complain about.
- Check after fixes with both.
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
An example
A retailer's mystery shops scored a store highly on greeting and product knowledge. Reviews from the same months complained about weekend billing queues, which the script did not test. Adding a peak-time visit to the programme confirmed the queues; a second counter fixed them.
Common mistakes
- Trusting one mystery shop over hundreds of reviews.
- Scripts that never change.
- Ignoring standards because reviews look fine.
- Comparing the two as if they measured the same thing.
Common questions
Which is cheaper?
Reviews are already there; mystery shopping costs per visit.
Should we stop mystery shopping?
Not necessarily; focus it where reviews point.
Can reviews replace audits?
They complement audits; audits check standards, reviews show impact.
How often should we mystery shop?
Where reviews show issues, and to check fixes.
Checklist
- Reviews used to target visits.
- Scripts updated from review topics.
- Both used to check fixes.
In short
Mystery shopping checks standards on a few visits; reviews show what real customers notice continuously. Let reviews decide where to look and mystery shopping check the standards behind the issues.
Redesigning a mystery shopping programme
Start from your top review topics and check whether the script tests them. If customers complain about weekend billing waits, schedule visits at weekend peaks and time the queue. If they praise staff explanations, add a scenario that tests them. A programme designed from what customers actually say gives far more useful results than a generic script.
Cost and coverage
Mystery shopping covers a few visits per store per period and costs money for each. Reviews cover many experiences continuously at no collection cost. Spending the mystery shopping budget where reviews point, rather than spreading it evenly, gets more insight for the same money.
Audits and reviews
The same logic applies to internal audits. Audits check whether standards and procedures are followed; reviews show whether customers notice. Use reviews to target audits at the stores and standards that matter most to customers.
Comparing the results
When mystery shops and reviews disagree about a store, look at timing first: mystery visits are a snapshot, reviews span many days. Then check whether the script covers the topic customers complain about.
Doing this with Falcon
Falcon shows negative share by topic, location and month on one heatmap, flags locations with too few reviews to compare, and lets you compare any period with the one before or the same weeks last year, so a location's problem can be told apart from a network-wide one. Every number opens the reviews behind it, in customers' own words, so a comparison can always be checked.