Processed locally
Your input stays in this browser.
A customer-feedback QR code should lead to one clearly named route: a private survey for structured feedback, a public review page for a voluntary opinion, or a support form for a problem needing a reply. Do not make visitors guess which outcome follows the scan.
Pick the feedback route by what the operator will do next
A private survey is useful when a manager needs comparable answers; a public review is voluntary public opinion; a support form starts a case that somebody must own. A hotel should not put all three outcomes behind one ambiguous card. Put three routes on the card only if each has a visible label: ‘Tell us privately’, ‘Leave an honest Google review’, and ‘Get help now’. The visitor then chooses knowingly, and the team can route survey scores, public reviews, and service cases to different queues without pretending they are the same evidence.
Map the data before the code is printed
For the hotel case, a two-minute survey can have four scored questions and one optional comment; the help form needs room number only when the guest chooses to provide it; the review request should contain no prefilled rating. If 120 guests check out in a weekend and 18 scan the survey code, that is 18 inputs to review, not a statistically complete verdict about every guest. Record the response date and route, remove direct identifiers that are not needed, and set a named owner for unresolved support requests.
Run the checkout-card test
Print three 90 mm cards and ask two people to scan each one: a signed-in guest and a phone with no Google account. Confirm that the survey submits, the review link shows the correct property, and the support route displays a response expectation. Deliberately enter a complaint about a missing item. If it reaches a generic inbox with no owner, the QR artwork is not ready even though the camera decoded it. The finished card needs a desk or phone fallback for a guest who cannot use the form.
Avoid review gating and false promises
Do not use a smiley-face first question that sends only high ratings to Google. Google says reviews must reflect genuine experiences and prohibits incentives for reviews. A private complaint route is still valuable, but it must not be designed as a trapdoor that keeps dissatisfied guests away from the neutral public-review invitation. Equally, do not say ‘we will reply within an hour’ unless staff coverage makes that true. Feedback collection is a service workflow, not a decoration for a receipt.
Read the result as a routing signal
A low survey score may justify checking a shift, room, or process; it does not identify a guest unless the form collected a contact route. A public review deserves a response under the business’s review practice, while an urgent billing or safety report should move to a staffed escalation path. Compare counts by route: ten support requests about check-in are a clearer operational signal than a single undifferentiated ‘feedback’ total. Keep the printed source URLs with the artwork record so changed forms can be traced.
Know what the QR code cannot decide
A feedback code cannot replace a staffed escalation route for an urgent safety, billing, or accessibility issue. A camera scan cannot authenticate a complainant, guarantee anonymity, compel a public review, or provide immediate help when the desk is closed. The current behaviour of Google review requests is documented by Google Business Profile Help at https://support.google.com/business/answer/3474122?hl=en. Use the code for the route it names, and publish the non-digital escalation route where a person can see it before scanning.
Turn 18 responses into a usable service review
At the end of a weekend with 120 check-outs, the hotel has 18 private survey submissions, 6 public-review scans and 4 support cases. Keep those denominators separate. Four support cases about late room access need an owner and a due time; they should not be averaged with the 1-to-5 scores. If 11 of the 18 survey responses mention breakfast, read the comments beside the score and compare the dates and shifts before changing service. A review QR code is not a measurement instrument, and a survey score is not permission to publish a guest's comment. Export the three queues with their route and date, remove fields no longer needed for follow-up, then record the action taken. That turns the card into a feedback loop rather than a collection of unassigned messages.
Give each route a visible recovery path
A guest who has lost a key at 23:30 needs a desk number or emergency contact, not a survey confirmation page. A guest who wants to mention a clean room may choose the private form or a neutral public-review request. Put the support route first where the physical situation makes urgency likely, and put the review invitation after the stay rather than beside a complaint desk. The three URLs may share a domain, but their labels must still say what happens next. Test a failed form submission, a signed-out review attempt and a mobile call from the printed fallback. The result to retain is not merely three successful scans: it is proof that the person can reach help, give optional feedback, or leave an honest review without being silently pushed into another route.
Use a weekly ownership check
Once a week, reconcile the number of scanned support submissions with the number assigned, answered and still open. A report with 4 cases received, 4 assigned, 3 resolved and 1 awaiting a guest reply is operationally meaningful; a report saying 22 QR scans is not. Check whether the review link still names the correct property and whether the survey's privacy notice still matches its questions. Retire an old card when its form closes, property changes or support ownership moves. This small review also catches a dangerous drift: a team may keep promoting a review code while the assistance route has become an unattended inbox. The printed artwork record should name the three approved destinations and the person responsible for each one.
Publish an accountable feedback outcome
At month end, publish the operational result internally: 18 survey responses, 4 support cases, 3 cases answered within the promised period and one menu change made after repeated comments. Do not publish names, raw complaints or an invented satisfaction percentage from a small voluntary sample. Give the manager a list of unresolved issues, the owner of each route and the date for the next review. If a QR card produces feedback that nobody can act on, remove the promise from the card or repair the staffing process before printing another run. The value of separate survey, review and support routes is that each result has a different legitimate next action.
Keep the receipt wording honest
The receipt can invite a guest to choose private feedback, a neutral review or help, but it should not promise a response channel that the property does not staff. Recheck that wording after every ownership change.
Do not merge complaint records
Keep a missing-item report in the support system even when its author also submits a low survey score. The same guest experience can create two records with different response obligations. Google Business Profile Help is the named source for the current external rule or product behaviour.