The review you get is the one somebody asked for. In a restaurant that means asking at the table, before the guest pays and walks out, on a code that's already in front of them. 83% of people who get asked to leave a review leave one. Everything below is about making that ask survive a busy Saturday: one tap to reach the review box, one sentence your floor staff can say without thinking, and three numbers you check every Monday. Two things to know before you start. Google's policy says you can't tell staff to ask for reviews that name them, and almost nobody follows that. And you can hand a guest a free coffee, you just can't hand it over in exchange for a review.

Asking is the mechanism. BrightLocal put the question to 1,002 US consumers in February 2026, and 83% of the people who'd been asked to leave a review had left one. Nothing else here comes close to that, so the rest of this article is about making the ask easy to run.

The moment does most of the work. Ask while the plates are going and the check is on the table, when the meal is still what they're thinking about. Wait until they've paid and you're stopping a stranger on their way to the door.

The ask itself is one sentence and a reason:

"How was the seabass? If you've got thirty seconds, that's the sort of thing that really helps us on Google. I'm Marco, by the way."

Three things are working in there. The dish gives them something to write about, which is the part most people get stuck on. The reason gives them a motive that isn't just doing you a favour. And the name turns a favour to a restaurant into a favour to a person, which is harder to say no to.

If a table was looked after by two or three people, split whatever you're paying between everyone the review names. Otherwise the first server to get their name in takes the lot, and everybody else stops asking by the second week. How much to pay, and whether to pay cash at all, are longer questions, so we've answered them separately in how to incentivize your team to collect more reviews and should you pay staff per review.

The ask converts when the review box is already in front of the guest. If it isn't, you're asking somebody to find your restaurant on Google Maps at the door, and most of them won't bother.

So you need a link that opens the review box directly, and a QR code on top of it. Building one takes a minute and it has its own guide: how to generate a google review link and QR code that works on iPhones. That article exists because Google's own share link fails on a lot of iPhones, which is worth knowing before you print anything. You can also build one now with the free google review link generator, which asks for no email.

Then you decide where the code goes, and that's the part that decides whether any of this works.

Two rules whatever you pick. The code has to open the normal Google review flow, not a page that pre-sets a star rating or writes the text for them. And print it somewhere you can change your mind about, because the destination behind a code isn't always going to be the one you started with.

Most of the tactics restaurants get told to run touch a rule somewhere. Here's what the rules say, and where we disagree with them.

Asking at the table is allowed. Google's policy is about pressure, not about asking. Merchants shouldn't "require or pressure users to leave ratings or write reviews while on the premises". So you can ask a happy guest on their way out. You just can't stand over them while they do it.

Asking them to mention their server is against the rules, and it's a gray area. Google lists "Merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member" under rating manipulation. Tripadvisor goes further and treats "a bonus for being mentioned in a review" as a violation on its own. Nobody enforces either of them. Reviews naming servers are all over Google and they stay there. And asking for them is the most effective thing you can do to get more reviews, because it changes what you're asking for. That's a gray area, and you should know which side of the line you're on before you build a programme on it.

Paying staff is allowed, with one word of care. Pay for reviews collected, not for positive ones. Paying for good reviews specifically is the part that's illegal, and it's also the part that gets a restaurant caught. After that, watch the pressure. Staff who chase reviews hard, or who push guests to include their name, are how a programme that works turns into one that gets noticed.

Keep a free dessert and a review apart. Offer the coffee, offer the dessert, and ask for the review. What you don't do is make the dessert conditional on the review. A guest who gets something and is then asked is fine. A guest who's told they'll get something if they post is a different transaction.

Emailing only the guests who haven't reviewed yet is allowed. That isn't filtering by who'll say something nice, it's filtering by who's already spoken. Is it legal to ask for reviews works through the rest of it, and the myths everyone repeats covers the ones that aren't true, including the idea that Google banned QR codes.

Consistency is what compounds, and nobody stays consistent about a number they don't look at. One restaurant needs three numbers and a day of the week.

Pick Monday morning and put them somewhere you'll see them again. A whiteboard in the office is enough.

Two things go wrong here. The first is chasing the rating instead of the flow. Your rating is the output, and the number you can move is how many reviews you collected. The second is working out how many five star reviews you need to reach 4.8, which is a worse question than it looks, and why free google review calculators are all wrong explains what to ask instead. If you want to see where your rating has been rather than where it is, that's google review history.

The manual version works and it has a ceiling. One dining room, one shift, one person who remembers. Past that you're relying on somebody's memory on a Saturday night, and Saturday night is exactly when it goes.

The first thing you lose is knowing whether it's working. You collected eleven reviews last month, and you don't know whether that came from the check presenter, the two servers who actually ask, or nothing you did.

The second thing is that you start asking people who already reviewed you. Doing that properly by hand means reading your own reviews and cross checking them against a customer list, which is why nobody does it.

The third is counting. If you're paying per review collected, somebody has to work out who collected what, and there's a review leaderboard version of that job.

If you run the floor on a POS, there are pages for Toast and Square. And if what you want is the whole thing running rather than a weekly habit, that's review management software for restaurants.

Start a free trial. Fourteen days, no credit card.