A review request is a small piece of customer communication, but it carries the character of the business. The strongest version sounds recognisable, explains why feedback matters and makes the next step easy without pretending to be a personal note when it is automated.
Start with the relationship you already have
Look at how the business normally communicates before, during and after the service. A family-run restaurant may be warm and informal; a care provider may be reassuring and precise; a trades business may favour direct practical language. The review request should feel like the same organisation.
Collect examples of emails, appointment messages and phrases colleagues use naturally. Identify two or three voice principles such as clear, friendly and unhurried. Avoid copying a competitor or using fashionable language that customers never hear from your team.
The message also needs to reflect the actual relationship. Use the customer’s name only when the data is reliable. Refer to the service accurately and avoid excessive familiarity after a single transaction.
Explain why honest feedback is useful
Give the customer a genuine reason to respond. Their experience can help another local customer make an informed decision and help the team understand what worked or needs attention. Keep the explanation short enough that the action remains clear.
Ask for an honest review, not a positive one. Do not imply that the team member needs five stars, suggest praise or tell customers the business only wants happy feedback. The words set the ethical standard as clearly as the underlying invitation rule.
If the request is for a public platform, name it and make clear that the review will be public. If feedback is private, explain who receives it. A customer should know what will happen before selecting the link.
Use a simple message structure
A useful request has four parts: recognition, purpose, action and a pressure-free close. Thank the customer for the specific service or visit. Explain why genuine feedback helps. Provide one clear link or a simple choice. Confirm that responding is optional.
| Part | Job it performs | Keep it human by |
|---|---|---|
| Recognition | Connects the message to a real experience | Naming the service accurately |
| Purpose | Explains why the business is asking | Using one honest customer-centred reason |
| Action | Shows exactly where to respond | Using a tested direct link |
| Close | Removes pressure | Thanking them whether or not they respond |
Keep the subject line and opening straightforward. Avoid false urgency, repeated exclamation marks and claims that the request takes a specific number of seconds unless you have checked the actual journey.
Adapt the same voice to each channel
An email can include a brief explanation and aftercare link. A text message needs a shorter form and a clear sender. A printed card or QR code needs enough context to explain the destination. A spoken request should sound conversational rather than like a line read from a policy.
Do not squeeze the email wording into SMS by removing all warmth. Preserve the purpose and optional nature, then shorten supporting detail. Equally, do not add marketing offers to a service follow-up without considering the relevant privacy and electronic-communications rules. The ICO distinguishes service messages from direct marketing and explains that promotional content can affect that classification.
Test every version on the device customers will use. Check link previews, accessibility, sender name and where a reply goes.
Personalise honestly and proportionately
Useful personalisation confirms that the request relates to a genuine experience. It might include the branch, service type or appointment date. Do not include sensitive service details in a subject line or reveal information on a shared device.
Automation should not claim a person wrote the message individually if they did not. A message can come from “The team at…” and still feel thoughtful. If a named colleague genuinely owns the follow-up, provide a monitored reply route so customers are not answering an unattended mailbox.
Use conditional text carefully. Missing fields, the wrong service name or a broken greeting damages confidence more than a clean general message. Build an exception list for records that need review.
Remove pressure and protect trust
Never offer a reward for a favourable review or send different public links according to private satisfaction scores. Google prohibits incentives in exchange for posting, changing or removing reviews. The CMA also provides guidance for businesses that publish review information and for fair commercial practices.
Keep service resolution separate. A customer who reports a problem should receive help whether or not they review the business. Do not ask them to change a review as a condition of a repair, refund or complaint outcome.
Make opt-out and contact preferences easy to respect where required. Keep only the personal information needed for the communication and follow your privacy arrangements.
Test the request with customers and colleagues
Ask several colleagues to read the message aloud. If it sounds unnatural, simplify it. Ask a recent customer what they think the message is requesting, where the link goes and whether anything feels pressuring. This reveals ambiguity that an internal approval process may miss.
Compare versions using process measures: successful delivery, completed clicks, customer questions and representative invitation coverage. Do not optimise solely for positive ratings. Read the feedback for signs that timing or wording creates confusion.
Review the copy when services, platforms or brand language change. A strong request remains short, recognisable and honest. It lets the business sound like itself while giving customers a clear, respectful way to share what really happened.