Sample result
Review Request System Builder for Restaurants
The owner asked this:"I have 3.9 on Google with 61 reviews and the place across the street has 4.6 with over 400. My servers ask for reviews when they remember. I want a system for the Laureles location."
① The system in one table
| Moment | Signal that triggers it | Who asks | Destination listing | Physical bridge |
|---|---|---|---|---|
| Weekday lunch | The plate came back empty and the table said so | Whoever served | Card on the coaster | |
| Friday dinner | They asked for a second dessert | Whoever served | Card in the check folder | |
| Delivery order | The order arrived hot and complete | Nobody at that moment | Channel listing | Sticker on the bag |
The window: 15 min from the signal, a cap of 2 tables per shift. Past 24 hours it waits for the next visit — asking late sounds like a charge.
SUPUESTO: no «industry normal» rate of reviews per 100 covers is hard-coded. The target starts against Sazón de Origen's own count over the first 4 weeks; if the platform changes pace, that is said and the target recalculated.
② Who yes, who no
The list does not filter opinions, it filters FACTS. That difference decides whether the listing survives: choosing by what happened at the table is judgement; asking "how was everything?" first and showing the link only to whoever answers well is filtering the opinion, and platforms hunt that down.
| Observable signal | Ask or not | What happens to that table |
|---|---|---|
| Plate finished and something else ordered after the main course | Yes | Ask within the next 15 minutes, folder already on the table |
| Third visit or more, recognised by the server | Yes | Ask, and log the server's name in the shift notebook, not the guest's |
| Asked about the recipe, about the chef or about the Trucha al ajillo | Yes | Ask using the chef variant |
| The plate came out after 25 minutes | No ask | The floor manager apologises at the table and the dessert is on the house; the QR stays in the folder, as at every table |
| Something sent back to the kitchen or swapped | No ask | Ask what went wrong and log the dish, which is what the kitchen can fix |
| First visit at the 1:00 p.m. peak with rushed service | No ask | Invite them back on a Tuesday, when the house can serve them properly |
| Already left a review in the last 90 days | No ask | Thank them by name and nothing more |
The hard rule, written so nobody interprets it. Reviews are not bought. Nothing is given in exchange for a review: no dessert, no discount, no monthly prize draw, no "coffee is on me if you leave it right now". And the link is hidden from nobody over what you suspect they will write. What you may do is a gesture for whoever COMES BACK: the third-visit guest gets the house coffee, with no condition, with no mention of reviews and with nobody checking whether they left one. The difference matters because an incentive per review buys the opinion and makes it useless as a signal —for the guest reading it and for you, who no longer know whether the 4.8 is true— while a gesture for coming back rewards behaviour counted in visits and touches not one word of what the guest writes.
③ The twelve-word sentence
The sentence is said by whoever served the table, folder already down and looking at the person. Whoever takes payment does not ask: at the paying moment any request sounds like a surcharge.
The sentence, twelve words counted:
Would you help us with a review? The code's on your check.
Variant for the Sunday table, twelve words:
Would you leave us a review? The code sits in that folder.
Variant for whoever asked about the chef, twelve words:
The chef reads these himself. Would you leave us a review, please?
When they say not now:
Of course, no problem at all. Thank you for coming today.
And it ends there. No pushing, no asking again during that visit, and nothing logged about that guest. A "no" that gets asked twice costs more than the review you did not get.
Three things the sentence does not say, on purpose. It does not say why it is needed: telling a guest the house is short of reviews to reach 4.5 turns them into staff, and that favour gets paid with a lukewarm review. It promises nothing in return. And it never says "five stars": asking for the score is asking for the opinion, and that is exactly the line nobody crosses.
How it gets trained in five minutes, at the Tuesday pre-shift. The floor manager says the sentence out loud twice, each server repeats it once in their own words —it is a twelve-word sentence, not twelve words memorised— and the shift notebook gets an owner. With 18 people in operations split across two locations, the Laureles lunch runs on 6 servers: six sentences, not one corporate script.
The full example has 2 more part(s): you see them inside the library, with your account.