A review request should enable voluntary feedback. It should not prescribe the desired outcome or pressure the customer during the service. Timing and wording therefore matter as much as the link to the review platform.
Choose a meaningful completion point in the customer journey. Delivery may provide a different moment from a long-running project. Ask when the person has an experience they can actually assess. A review requested before use or completion says little about the service promised.
Write a neutral invitation
Explain that feedback is possible and what it can concern. “If you would like to share your experience of the appointment, the review link is here” leaves the choice open. Asking specifically for five stars directs the outcome instead.
Google's guidance on getting reviews prohibits incentives such as free or discounted services in exchange for posting or changing reviews. Check the rules of other platforms as applicable. Calling something a general thank-you does not remove the issue if receiving it is actually tied to publication.
Avoid a process that asks about satisfaction first and sends only happy customers to a public review page. An internal complaint route can be useful, but it should not filter critical experiences out of public feedback. The invitation need not depend on a preferred assessment.
Consider the communication route separately
An emailed review request is additional communication. Check the legal and operational requirements for the particular sending method rather than assuming a completed purchase permits every later message. This article addresses process design, not the legal basis for a particular campaign.
If the invitation is offered in person or on a receipt, preserve voluntariness there too. A staff member should not stand beside the customer waiting for a review to be written. That can influence the response and create an uncomfortable situation.
Keep the route short and understandable. A QR code should lead to the correct profile and be tested on an ordinary smartphone. Give it enough context that it does not resemble an unexplained download. A brief written label can identify the destination.
Do not chase every missing review
Customers do not owe the business a public response. Avoid repeated personal follow-ups when someone does not participate. Decide internally how often requests may be made and through which permitted route, so their intensity does not depend on individual staff enthusiasm.
If a person gives criticism directly instead, handle the issue on its merits. Do not make a remedy conditional on deleting or improving a negative review. Resolving a problem and freely expressing an opinion are separate processes.
Review the workflow using real, anonymized examples. Do different customer groups receive the same opportunity? Do the link and QR code still work? Does any stage create pressure or an expectation about the star rating? A neutral request succeeds when it makes feedback easier without directing its substance. Keep the request wording separate from any incentive programme so later changes do not accidentally tie a benefit to the review.
