Google reviews for restaurants: a service-night playbook
The busy-night 1-star, the rave with a wrong detail, and the ask that works at the table.
No industry gets reviewed like restaurants: more volume, more emotion, and reviews written from the parking lot before the card machine cools down. That volume is an asset if you run a system for it, and a slow leak if you don't. This is the playbook for both directions: earning the reviews and answering the hard ones.
What diners read before they book a table
Diners check three things in order: the rating (with 31% filtering below 4.5 stars), the newest reviews for what the kitchen is like this month, and photos. Recency hits restaurants hardest of any industry because menus and staff turn over; 73% of customers only trust reviews from the last 30 days (both figures in our statistics rundown, pending verification). A quiet review month reads as a quiet dining room.
The busy-night 1-star
Every restaurant knows this review: Saturday rush, 40-minute ticket times, and Sunday morning brings the one-star naming the wait. Reply the same day, own the specific failure, and give the reader the fix:
The structure is the standard five-part pattern from our negative review templates: thank, acknowledge specifically, own it, name the change, move it offline. On a busy-night review, the named fix ("how we staff weekend shifts") is what future readers remember.
The rave with a wrong detail
Five stars, glowing, and it credits a dish you don't serve or a "he" who is a she. Correct warmly without correcting the customer: "Thrilled you loved the al pastor night! Small note for anyone reading: it runs Thursdays." The reply thanks the reviewer, quietly fixes the record for the 97% of readers who read replies, and keeps the star. Never argue with a compliment.
The ask that works at the table
Restaurants have the natural ask moment most industries envy: the goodbye after a good meal. Keep it one sentence at the check drop or the door, then make the review one tap: