Google Review Request Templates
Adaptable Google review request templates for text, email, follow-up and in-person use.
SMS template
“Hi [First Name] — thanks for choosing [Business]. If you have a minute, we’d appreciate your honest feedback about your experience: [Review Link]. Thank you!” This works because the sender is clear, the request is neutral and the action is direct.
Post-service email template
Subject: How did we do? Body: “Thanks for choosing [Business], [First Name]. Your feedback helps us improve and helps other customers understand what to expect. If you’d like to share your experience on Google, you can do that here: [Review Link].”
Follow-up reminder template
“Just a quick follow-up in case you meant to share feedback and didn’t get a chance. Here’s the direct Google review link: [Review Link]. Thanks again for working with us.” Keep reminders limited and respectful.
In-person script
“Thanks again — we really appreciate your business. Feedback helps us a lot. If you’d like, I can send you a direct Google review link so it’s easy.” This creates permission for the follow-up instead of pressuring the customer to post on the spot.
How to personalize without rewriting everything
Use variables for name, service, technician, location or appointment type when the CRM data is reliable. Personalization should increase recognition, not create awkward messages with missing fields. Test templates from a real customer record before turning on automation.
Frequently asked questions
Should I ask for a five-star review?
It is better to request honest feedback without prescribing a rating.
Can I include an incentive in the template?
No. Google prohibits incentives offered in exchange for reviews.
How many reminder templates do I need?
For many local businesses, one polite reminder is enough. The right cadence depends on the customer relationship and communication norms.
Editorial note: Product features, pricing and platform policies change. We verify time-sensitive details against official Google Business Profile and HighLevel documentation before publishing or updating them.