Restaurant QR Feedback: Getting Honest Reviews Before Customers Leave
How to set up restaurant QR feedback at the table that catches problems in real time, and invite public reviews without breaking Google's rules.
A table tent with a QR code has become about as normal in restaurants as a menu card by now, but most of them exist for one thing: pushing people to Google or Zomato. Restaurant QR feedback done right works the other way around. You catch the complaint about slow service or a cold dish while that table is still sitting there, not 3 days later in a 1-star public review you can't take back.
In this piece I'll cover how to set up restaurant QR feedback that actually gets read, why timing it at the table beats emailing a receipt link, and how to invite public reviews without faking or filtering anything.
Why table-side feedback beats the post-visit email
You've probably tried the slow way already: a receipt with a survey link, or an SMS that arrives the next morning. By then, the memory of the meal's faded, and only the most annoyed or most delighted customers bother to respond. That's a skewed sample, and it's too late for you to fix anything for that specific table.
Put a QR code on the table while the meal's still happening and you change both problems at once. A guest rating the biryani as they finish it gives you a sharper answer than one they'd type from memory 2 hours later at home. If a table flags cold food or a slow server, you or your manager can walk over and fix it before that guest ever opens Google Maps. And your response rates will actually go up: scanning a code at the table takes about 15 seconds, while an email buried in a promotions folder takes none, because nobody's opening it.
Setting up a QR feedback form your guests will actually use
Keep your form short, 3 to 5 questions at most, because nobody wants a research survey between courses. You'll get what you need from a rating question for food quality, one for service, an open-text box for anything specific, and maybe a single NPS-style "would you recommend us" question. That's enough to act on without it feeling like homework.
Use the right question type for the moment, too. You want a star rating or a numeric scale, since those take one tap, and you should save the free-text box for "anything you'd like to add" so your guests aren't forced to type unless they've actually got something to say.
Then branch based on the answer you get back. A low rating should lead somewhere different than a high one: if a guest rates their meal poorly, show them a simple "we're sorry, tell us what happened" prompt that your manager sees right away. If you invite public reviews, put that invitation on the thank-you screen for every guest, not just the ones who rated you highly. Don't ever autogenerate or pre-write that review text; it should stay a genuine invitation, nothing more.
Where you print the code matters more than you'd think. A table tent next to the condiments gets noticed. A code buried on the back of a receipt, after the bill's paid and your guest is already halfway out the door, mostly doesn't get scanned at all.
Finally, set up an alert for low scores, because the whole value of table-side feedback is speed. If a 1-star response doesn't reach you until the next morning, you've already lost your window to fix anything in the moment.
From feedback to reputation, without faking it
Table-side feedback and public review growth work best as 2 connected steps, not 1. The form's job is to catch problems while you can still fix them; the review invitation's job is to give every guest an easy way to post publicly. What you can't do is merge the two into a filter, where only 4 and 5-star guests ever see the review link. Google's policy calls that review gating and prohibits it, even when the guest picked the rating themselves.
The good news is that a recovered guest is a likely reviewer. When a manager fixes a cold dish at the table, that guest often leaves a better review than one who had an uneventful meal, so the real lever for your rating is the speed of recovery, not who gets asked.
A worked example
Say a guest finishes their meal, scans the table tent, and rates food quality 4 out of 5 and service 5 out of 5, with no complaint in the text box. That guest sees a short, specific thank-you with a link to the restaurant's Google review page, and can get the same link later on WhatsApp from the restaurant's own business number, so the ask feels like it's coming from the restaurant itself, not a third-party survey platform.
Now say a different table rates food quality 2 out of 5 and writes "the pasta was cold." That response triggers a manager alert right away, and the guest sees the same thank-you and review link as everyone else. The manager can comp a dessert, apologize at the table, or follow up directly, and that's the kind of recovery that actually changes how a guest remembers the visit, which a generic apology email sent 2 days later almost never does.
Try it yourself
If your restaurant's feedback currently lives on a receipt nobody reads, set up 1 table-side QR form this week and compare how many responses come in against your old post-visit method. Start on the restaurants industry page to see how feedback, bookings, and reviews connect for restaurant businesses, then build the form itself with Surveys & Feedback and add your Google review link to the thank-you screen for every guest. Sign up free and get your first table tent printed before dinner service tonight.
Frequently asked questions
Not really. It's optional and takes under 60 seconds.
Be careful here. An incentive tied to leaving a specific star rating or a public review crosses into manipulating reviews, which platforms like Google actively penalize. An incentive for simply completing the form, with no rating condition attached, is safer and still works.
It's still useful. A low numeric score with no text tells you something went wrong even without the detail, and having a manager ask at the table, if the guest is still around, usually surfaces more than the form alone would on its own.
You can, but it's worth thinking about whether you need 2 separate forms instead, since a takeout order has no "service" to rate the way a dine-in table does, and a shared form ends up asking a question that doesn't apply to half your respondents, which looks sloppier than having none at all.
Timing. A receipt link only reaches guests who already paid and are steps from the door, while a table-side form reaches everyone while they're still seated.
Try it
Keep reading
All articlesB2B CSAT Survey Questions for Service Businesses
B2B CSAT survey questions for consultants, agencies, and SaaS vendors: delivery, support, account, and renewal survey questions to use.
Course Feedback Survey Questions: A Complete Question Bank for Students
24 course feedback survey questions for students, split into session-level and end-of-program sections, built from SurveyKar's live templates.
Event Feedback Survey Questions: A Complete Question Bank
24 event feedback survey questions covering logistics, speakers, networking and would-attend-again, built from SurveyKar's live event feedback template.