Your staff talks to 50 guests a day. Fewer than one leaves a review. The problem is not willingness. Guests who had a great meal are happy to help. The problem is that “please leave us a Google review” is too vague, too awkward, and too easy to forget.
The restaurants that consistently collect 15-30 reviews per week are not running some special campaign. They trained their staff to say specific words at specific moments. That is the entire difference.
This guide gives you the exact scripts — word for word — for every touchpoint. Print it, laminate it, put it in the staff room.
Why “please leave us a review” fails
A 2025 BrightLocal survey found that 72% of consumers say they would leave a review if asked. Yet the average restaurant collects fewer than 2 reviews per week. The gap between willingness and action is enormous.
Three things kill the conversion:
- Vague asks get vague responses. “Leave us a review sometime” triggers a mental “sure, later” that never happens. Guests forget within 90 seconds of leaving.
- Wrong timing. Asking during a busy checkout moment creates pressure, not goodwill. The guest is reaching for their card, not their phone.
- Too many steps. “Find us on Google Maps, then click reviews, then…” — every instruction halves the conversion rate.
The fix is specific language at the right moment with friction removed.
The 3-second rule: when to ask
The moment a guest expresses genuine satisfaction is your 3-second window. Not before, not five minutes after.
The peak-end rule (Kahneman, 1999) shows that people judge an experience almost entirely by its emotional peak and its ending. Your review ask needs to land at or near the peak — which in a restaurant context is usually:
- Table service: right after the guest compliments the food, says “that was amazing,” or tells the server they enjoyed their meal
- Counter/takeaway: the moment the guest says “thanks, this looks great” or compliments the order
- Checkout: after they have paid, not during payment
If the guest says nothing positive, do not ask. Forcing a review request on a neutral or unhappy guest backfires. Let it go — that guest was not going to leave a 5-star review anyway.
Word-for-word scripts by touchpoint
Table service (waiter or waitress)
Trigger: Guest says something positive about the meal.
“I’m really glad you enjoyed it. If you have 30 seconds, it would mean a lot if you could share that on Google. There’s a QR code on the table — just scan it and it opens the review page directly.”
Why it works:
- “30 seconds” reframes the task as tiny. The actual median time to write a Google review is 42 seconds (Podium, 2024), so 30 seconds is honest.
- “It would mean a lot” uses reciprocity. The guest just received great service. A small favor feels natural.
- “Just scan it” removes every friction point. No searching, no typing the restaurant name, no navigating Google Maps.
Common mistake: Saying “if you get a chance” or “when you have time.” These phrases give the guest permission to never do it.
Counter or takeaway
Trigger: Guest picks up their order and reacts positively, or completes a counter-service transaction.
“Thanks for coming in! Quick favor — if you enjoyed it, a Google review really helps us. You can scan this [point to QR code] right from your phone.”
Why it works:
- “Quick favor” signals low effort and positions it as a personal request, not a corporate demand.
- Pointing to the QR code creates a physical anchor. Guests are much more likely to scan something their eyes are already on.
Common mistake: Asking while the guest is still in line or while others are waiting. It creates social pressure and makes the ask feel transactional.
Post-visit text or WhatsApp message
Trigger: 2-4 hours after the visit (enough time to finish the meal experience, not enough to forget).
“Hi [Name], thanks for visiting [Restaurant] today! If you enjoyed your meal, we’d love a quick Google review — it helps other food lovers find us. Here’s the direct link: [link]”
Why it works:
- Uses the guest’s name (personalization increases response rates by 26% — Experian).
- Sent at the right delay: same-day but after digestion, not immediately.
- Direct link removes all navigation friction.
Common mistake: Sending a review request the next morning. By then the emotional peak has faded. Same-day, 2-4 hours later is the sweet spot.
Handling objections
Guests rarely say “no” directly. They deflect. Here are the four most common deflections and how to handle each:
| Objection | Response |
|---|---|
| ”I don’t have time right now" | "No problem at all. If you scan the QR code it saves the link — you can do it whenever it’s convenient. It takes about 30 seconds." |
| "I don’t have a Google account" | "That’s fine! If you have Gmail or an Android phone, you already have one. But no worries at all if not." |
| "I’ll do it later" | "Of course! The QR code saves the link to your phone so you don’t have to search for us." |
| "I already left one before" | "Thank you so much! That really means a lot to us. We appreciate you coming back.” |
The goal is zero pressure. If a guest declines, smile and move on. Pushing turns a happy customer into an annoyed one.
QR shortcut: 3 words instead of 30
The biggest staff training challenge is consistency. Scripts only work if every server uses them every shift. The more words they have to remember, the faster compliance drops.
A QR code on the table or counter changes the conversation from a 30-word pitch to three words: “Scan for review.” The QR code opens the Google review page directly. No searching, no navigating, no “how do I find you on Google.”
QR-based review flows convert at 20-30% compared to 2-5% for verbal asks alone. The QR code does not replace the ask — it removes the friction that kills conversion after the ask.
SpiniX takes this further: the QR code opens a prize wheel first, the guest wins a reward, and then gets a soft review prompt. The emotional peak of winning makes the review feel natural rather than transactional. Restaurants using this approach see 31.5% scan-to-review conversion.
Printable staff cheat sheet
| Situation | When to ask | What to say | What NOT to say |
|---|---|---|---|
| Table service | After guest compliments food | ”If you have 30 seconds, it would mean a lot if you could share that on Google. QR code is right there." | "Could you leave us a 5-star review?” |
| Counter pickup | After positive reaction to order | ”Quick favor — a Google review really helps us. Scan this right from your phone." | "We need more reviews, can you help?” |
| Checkout | After payment is complete | ”Thanks so much! If you enjoyed it, the QR code right there opens our Google page." | "Before you go, can you review us?” |
| Post-visit text | 2-4 hours after visit | ”If you enjoyed your meal, we’d love a quick Google review — here’s the direct link.” | Next-day generic blast to all guests |
| Guest declines | Immediately | ”No worries at all!” + smile | Repeat the ask or look disappointed |
What NOT to say
Some phrases violate Google’s policies. Others just make guests uncomfortable. Avoid all of these:
Policy violations:
- “Leave a review and get 10% off your next visit” — direct incentive exchange, banned by Google
- “Leave us a 5-star review” — soliciting a specific rating violates Google’s guidelines
- “We’ll enter you in a raffle for leaving a review” — contest entry for review = incentive
Awkward or pushy:
- “We really need reviews to survive” — guilt-tripping makes guests uncomfortable
- “Our competitors have more reviews than us” — signals desperation
- “Can you do it right now while I watch?” — pressure kills goodwill
- “I’ll show you how to do it” — patronizing; the QR code handles this
The line is simple: ask once, make it easy, accept any answer. Google encourages businesses to ask for reviews — just without incentives, without gating, and without pressure.
Measuring staff review performance
Track reviews by shift, not by individual server. Singling out servers creates anxiety and gaming behavior. Shift-level tracking reveals patterns without blame:
- Morning shift averaging 2 reviews/week, evening shift averaging 8? The morning team may not be asking, or the breakfast crowd may not be the right audience.
- Weekend reviews 3x weekday? Higher guest volume, happier diners, or more experienced staff on weekends.
- Reviews spike after training, then fade? Schedule monthly refreshers, not one-time training sessions.
SpiniX dashboards show review volume by day and time, making shift-level patterns visible without manual tracking.
The goal is not to turn every server into a review-collecting machine. It is to make the ask so natural and so easy that it becomes automatic — like saying “enjoy your meal.”