Review themes can show recurring service issues without turning individual customers into a public data set. Count themes from authentic reviews, preserve context and use a minimum sample before announcing a trend. The purpose is a service decision, not a sentiment score for its own sake.
Decision framework
| Step | Practical check |
|---|---|
| Define themes | Use a small set of mutually understandable categories such as wait time, fit, staff help and delivery. |
| Remove identifiers | Keep names, phone numbers, order IDs and sensitive details out of the analysis sheet. |
| Code consistently | Have a second reviewer check ambiguous examples and record multi-theme reviews. |
| Link action | Assign an owner to any repeated operational issue. |
How to make the decision
Build a monthly table with review date, source, rating, theme, whether the experience is verified where appropriate, and an anonymized summary. Compare counts against the number of reviews in the period rather than quoting a percentage from a handful of comments. Keep the original platform review accessible to authorized staff for context, but report themes only in aggregate. If the sample is too small, label an observation as a signal to investigate.
Worked example
Synthetic 12-review month: five mention slow collection, three mention unclear parking, two praise staff knowledge and two discuss price. One review contains both collection and parking, so the theme counts exceed the number of reviews. The owner checks queue records and signage before changing hours or promising a ranking benefit. No reviewer names appear in the shared report.
What can change the answer
Automated sentiment labels can miss sarcasm, language nuance and mixed experiences. Human review matters most when a theme could lead to a consequential service change.
Review checklist
- Are personal details removed from the shared view?
- Are theme counts tied to the total sample?
- Does a repeated issue have an owner and a verification step?
Common question
Can one review count in two themes?
Yes, if the coding rule says so. Disclose that theme totals may exceed the number of reviews.
Next useful step
Document a potentially policy-violating review separately from normal feedback: How to Document a Suspected Fake Review. For help applying this to a UAE business, see Megvi’s local SEO service. Bring the source records and the decision you need to make.
Source checked 26 October 2026: Google Business Profile Help: tips to get more reviews. Check the current platform interface and rules before acting.
Worked examples are illustrative unless a public source is explicitly named; they are not claimed Megvi client outcomes.