Case Study 01 — When a 3.55 / 5 Average Hides an Entirely Different Story
A hospitality property in the Saudi market. On the surface, a reasonable average rating. Beneath the surface: a 98% reputation-management gap, and close to a third of the base (29.1% of reviews: 23.0% one-star + 6.1% two-star) giving one or two stars.
Client Profile (Identity Concealed)
- Market:
- Saudi Arabia
- Review count:
- 148 reviews
- Analysis window:
- 24 months ending Q1 2026
- Sources:
- Google Maps + Booking.com
- Languages:
- Arabic + English
The Shocking Result in One Line
The average looks "acceptable" viewed alone. But once you decompose the distribution, the hotel is living in two parallel worlds: half the guests are thrilled, close to a third (29.1% by star distribution) are furious. And management hasn't spoken to the furious ones on 145 out of 148 occasions.
* Percentages are computed under different analytical definitions (e.g. share of reviews flagged as critical vs. the star distribution); figures are from an anonymized case study shown to illustrate the methodology.
1. Star Distribution — A Bimodal Shape, Not a Normal One
2. Sentiment Pulse — Negative and Mixed Beat Positive
Guests expressing negative or mixed sentiment account for 33.8% — a third of the base. Genuinely positive tone (29.1%) — a numerical coincidence with the one-and-two-star share in the previous section, and unrelated to it — is below neutral (37.2%), an early-warning signal that the hotel is at risk of being coded "average" rather than "distinctive" in searcher memory.
3. Source Distribution — 93% of the Verdict Lives Outside Your Direct Channel
| Source | Review count | Share |
|---|---|---|
| Google Maps | 137 | 92.6% |
| Booking.com | 11 | 7.4% |
Google Maps is this hotel's primary digital storefront. Any local searcher (especially Saudi residents) sees Google first. Treating Booking.com as "the critical channel" because it's an OTA is a common error — in this market, Google is the gateway.
4. The Decisive Finding — 98% of Reviews Have No Management Response
This is the analysis's lightbulb moment. Not because replies create a new rating on their own — but because answering a negative review before 100 more searchers see it could save 30–40 bookings a month at a hotel this size — a modelled estimate for a property of this size, not a measured result. Its absence signals to every searcher: "Nobody here is listening."
5. Most-Mentioned Departments (Negative)
After classifying every review by the department implicated, the concentration emerged:
| Department | Complaint share | Dominant pattern |
|---|---|---|
| Housekeeping | Highest | Room cleanliness, odors, linen quality |
| Transport | High | Parking issues above all |
| Front Desk | Medium | Staff behavior and procedure speed |
Most-Mentioned Tags
6. Operational Risk — 6 Red Flags
The analysis flagged 6 reviews as "high operational risk" — complaints beyond dissatisfaction that could escalate into:
- Formal complaints to municipal or tourism authorities
- Social-media coverage with viral potential
- Direct legal exposure (safety, conduct)
In a hotel that doesn't reply to 98% of reviews, these signals were never handled. Each one was a missed containment opportunity before escalation.
7. Methodology — How I Arrived at the Numbers
- Collected every public review available on Google Maps and Booking.com over a 24-month window
- Classified reviewer type (solo, couple, family, business) where available
- Tone of every review classified as Positive / Negative / Neutral / Mixed, using a terminology dictionary built for the Saudi market
- Theme tagging mapped to operational departments (Front Desk, Housekeeping, F&B, Transport, Maintenance, Technology)
- Computed management response rate per source
- Flagged operational-risk signals: claims relating to safety, health, conduct, or discrimination
- Every negative entry reviewed line by line to confirm its classification before it is accepted
See definitions in the SIA glossary, or read the guide on responding to negative reviews.
8. Study Limitations
- The study used public reviews only — no internal hotel data was used
- No booking or PMS data was shared for this analysis
- Percentages are drawn from the public review base, not from every guest who stayed
- Identifying terms (hotel name, neighborhood, phone, staff names) are stripped from every output
9. What's Different About the SIA Approach?
Many reputation monitoring platforms stop at "3.55/5 average, thank you." My approach differs in three points:
Read the Other Case
Silence is not the only possible failure. Case Study 02 — Economy Serviced Apartments shows the mirror image: management replies to 35% of reviews, but only 4% of those replies are actually personalized. For the terms used here see the SIA glossary, and for the practical application see the guide on responding to negative reviews.
Need a similar study for your hotel?
I personally conduct reputation analyses for a limited number of Saudi hotels each quarter. Same methodology — and a detailed report your hotel alone owns.
Request your analysis