A useful invitation starts with the customer’s experience
Make it easy for a customer to find the right review page, invite them after the service is complete, and give someone responsibility for the response. A link alone does not create that routine. The missing piece is often deciding who asks, at what moment, and what happens when the customer raises a problem.
This walkthrough uses an imaginary bicycle repair shop. The messages are examples for the business to adapt, not reviews for customers to copy. You will finish with a checked link, two ways to share it, and a simple handoff for feedback.
Get the right link before printing anything
- Open the Google Business Profile you manage and check the location name and address.
- Open Read reviews, then Get more reviews. Copy the review request link. Interface labels may differ by language.
- On a computer browser, save the QR code from the same area. Google’s native review QR code is currently generated on desktop.
- Open the copied link on a customer-facing device and scan a test print. Confirm the intended location and that the page leads toward leaving a review. Do not submit a test review for your own business.
Use the request link, not the link for sharing one existing customer review. Those serve different purposes. Keep one approved copy per location so staff do not retrieve a different link each time. Google: review links and QR codes
For a printed card, leave clear space around the QR code and test it at the size and distance customers will actually use. These are practical layout suggestions, not a promise that every phone will scan the same way. If the destination is wrong, fix the source file before printing the full batch.
Choose a moment that fits the service
At a repair counter, finish explaining the work and returning the bicycle before mentioning a review. A customer holding a bike and a receipt may prefer to read a message later. For a remote handover, place the invitation in the existing completion or thank-you message rather than starting an unrelated conversation.
The choice is about convenience: a counter code is useful when someone wants to scan now; a direct link is easier when they are already reading on their phone. Choose one primary invitation for each completed visit. A second employee should not chase the same person simply because the first request produced no visible review.
Invite customers consistently, including those whose experience was mixed. Do not use a satisfaction questionnaire to direct only happy customers to Google. Reviews must reflect real experiences, and payment or discounts in exchange for reviews are prohibited. Google: prohibited content and fake engagement
A complete repair-shop example
At collection: a short spoken invitation
Example: the repair has been explained and the customer is ready to leave. Replace the shop name and use the verified location’s code.
Thanks for bringing your bike to [shop name]. If you’d like to share your experience, this code opens our Google review page. You can do it later, too.
Stop there. Do not suggest a rating, dictate phrases, or watch over the customer while they write. The request should still feel optional when the shop is busy or the customer is in a hurry.
After service: an email that stands on its own
Writing example. Replace both placeholders before sending; the bracketed link is not a working URL.
Subject: Thank you for visiting [shop name]
Hello [first name], thank you for trusting us with your bicycle repair. If you’d like to tell others about your experience, you can leave a Google review here: [your verified review request link]. Please share your own experience in your own words. There’s no obligation. If you still need help with the repair, reply to this message and our team will assist. Thank you, [shop team].
A support option belongs in the message because the service may need follow-up. It should remain available to everyone, not act as a barrier that diverts unhappy customers away from the public review link.
Respond to the experience, then take action
The business must be verified before it can reply. Review availability also varies by region and business category. Where available, open Read reviews and select Reply beside the relevant review. Approved replies are public, so leave order numbers, contact details and private service history out of the response. Google: managing customer reviews
Positive-feedback reply example:
Thank you for taking the time to share your experience. We’re glad the repair explanation was useful. If you have any follow-up questions about caring for the bicycle, our team will be happy to help.
Waiting-time complaint reply example:
Thank you for telling us about the wait. We’re sorry the collection process was frustrating. Please contact the shop through our usual contact channel so we can look into your visit privately and discuss the next step.
Use only statements that fit what happened. Before adding “we have changed our booking process,” actually agree and implement that change. Privately assign the collection issue to the shift lead; posting an apology does not resolve the operational problem by itself.
Make the next shift able to continue
Keep a short handoff note with the location, approved link, invitation touchpoint, reply owner and service-issue owner. For the example shop: the counter assistant offers the code after collection; the operations assistant checks new feedback; the workshop lead handles repair or waiting-time concerns. A named backup covers absence.
At a weekly check-in, ask whether the code still opens the right place, whether anyone received duplicate requests, and whether reported service issues have an owner and a next action. Use this to improve the process. Do not set a promised number of reviews or assume a ranking change follows from sending invitations.
Start with one completed-service touchpoint and one checked link. Once staff can use both consistently, add a second touchpoint only if it serves customers who are otherwise missed.