Asking for Reviews Script: Templates That Work

An effective asking for reviews script should be brief, personal and easy to act on. Ask every customer after a genuine service interaction, provide a direct link to your public Google review page, and make clear that honest feedback—positive or negative—is welcome. For multi-location businesses, standardise the wording while allowing each branch to personalise the message.

What makes a review request effective?

Customers are more likely to respond when a request is timely, specific and convenient. The goal is not to persuade someone to leave a positive review. The goal is to invite an honest account of their experience and make the public review process straightforward.

A practical script usually contains five parts:

1. A relevant opening: Refer to the visit, appointment, booking or completed job.
2. A clear request: Ask for an honest Google review.
3. A reason: Explain that feedback helps the local team and future customers.
4. A direct link: Take the customer to the correct location’s review page.
5. An open invitation: Let customers know they can also share concerns privately, while retaining the same open option to post publicly.

For example:

> Thank you for visiting [business/location] today. Would you be willing to share an honest review of your experience on Google? Your feedback helps our team and helps other customers make informed decisions: [review link]. If anything did not meet your expectations, please let us know as well at [contact route].

The final sentence must not replace the public review invitation. A customer who is unhappy must have the same direct and unobstructed opportunity to leave a public review as any other customer.

Asking for reviews scripts by channel

Different channels need different lengths and levels of formality. Keep the core request consistent across every location, then adjust the wording to suit the relationship and service.

In-person script for staff

Use this after the service has been completed and the customer is not dealing with an unresolved issue at the desk.

> Thank you for choosing [business name]. If you have a moment, would you leave an honest Google review about your visit? You can scan this QR code or use the link on your receipt. Feedback helps the whole team improve and helps future customers understand what to expect.

If the customer asks what to write, staff should not suggest particular words or ask for a five-star rating. A compliant response is:

> Please describe the experience in your own words. Honest feedback is most useful.

If a concern has just been raised, the employee can acknowledge it without blocking the review request:

> We are sorry that part of the experience was disappointing. You can share that publicly in a Google review, and we would also like to understand it directly so we can investigate it. Here is the review link, and here is the best contact route for our team.

SMS script

SMS works best when sent soon after the visit, appointment or completed job. Keep it short and identify the relevant branch.

> Hi [first name], thank you for visiting [location] today. Would you share an honest Google review of your experience? [review link] Your feedback helps our local team and future customers. If you would also like a direct response, contact [team/contact link].

For a service completed at the customer’s premises:

> Hi [first name], thanks for choosing [business name] for your [service] today. Please share an honest review of the work completed by our [town] team: [review link]. Your feedback is welcome, including anything we could have done better. For a direct follow-up, contact [contact route].

Do not send repeated reminders that feel persistent or intrusive. One initial request and a restrained follow-up are usually easier for customers to accept than a long sequence.

Email script

Email allows more context, but the request should still be visible near the top.

Subject: How was your experience at [location]?

> Hello [first name], > > Thank you for choosing [business name] for your [appointment/order/service] on [date]. We would appreciate an honest Google review of your experience. It takes only a few minutes and helps our local team understand what is working and where improvements are needed. > > Leave a Google review: [review link] > > Please share your experience in your own words. Positive, neutral and critical feedback is welcome. If you would also like the team to respond directly, contact [named team/contact route]. This private route is available in addition to, not instead of, the public review option. > > Kind regards,
> [name]
> [role]
> [location]

Receipt, invoice or booking-confirmation wording

Printed and transactional channels are useful when customers may not want to respond immediately.

> We value honest feedback about your experience at [location]. Leave a Google review: [short link or QR code]. If something could have been better, you are welcome to mention it publicly and contact our team directly at [contact route].

Check that QR codes and short links lead to the correct location’s Google review page. A multi-location brand should not send customers from one branch to another branch’s profile.

The right time to ask for a review

Timing should follow the customer journey, not an arbitrary campaign schedule. The best moment is generally after the customer has experienced the main value of the service and before the interaction becomes distant.

Useful timing examples include:

• Dental and healthcare practices: after an appointment has concluded and any immediate administrative issue is resolved. Avoid wording that implies the patient should review a clinical outcome before it is known.
• Salons: shortly after the appointment, once the customer has had an opportunity to see or experience the result.
• Restaurants: after the meal and payment, provided the customer has not raised an unresolved service issue.
• Law firms: after a meaningful milestone or completed service stage, using careful, non-confidential wording.
• Veterinary clinics: after the visit or follow-up point, with sensitivity to the owner’s circumstances.
• Automotive shops: after the vehicle has been collected and the customer has had reasonable opportunity to assess the work.

A simple operational rule is: send the first request on the same day or within 24 hours, unless the nature of the service calls for a later point. For longer engagements, define one or two legitimate milestones rather than sending a request after every interaction.

A step-by-step review request process

A script performs well only when the surrounding process is reliable. Use this sequence across every branch.

1. Define the trigger. Choose the event that starts the request, such as completed appointment, paid invoice, collection or confirmed delivery.
2. Assign ownership. Decide whether reception, the branch manager, customer service or an automated system owns the request.
3. Map each location. Create and test a separate Google review link for every eligible branch or practitioner profile.
4. Select the channel. Use SMS, email, receipt wording or a staff conversation according to the customer’s existing communication preferences and consent requirements.
5. Personalise the message. Include the customer’s name, branch, service and date where appropriate. Avoid including sensitive health, legal or financial details.
6. Send the request. Invite an honest public review without asking for a particular rating or filtering who receives it.
7. Offer direct follow-up as well. Provide a named contact or support route for customers who want a response. Do not remove, hide or delay the public review option.
8. Monitor responses. Review new feedback regularly, acknowledge it professionally and escalate operational issues to the right owner.
9. Identify recurring causes. Group feedback by location, service, process and theme so managers can address root causes.
10. Review the process monthly. Check delivery, broken links, response times, branch coverage and whether staff are using the approved wording accurately.

What staff should and should not say

Consistency protects the customer experience and reduces accidental policy breaches. Give employees a short approved script, but allow natural conversation around it.

Staff checklist

• Ask every eligible customer through the same general process.
• Request an honest review rather than a positive or five-star review.
• Use the correct location link.
• Avoid offering discounts, gifts, refunds or other benefits in exchange for a review.
• Do not ask customers to remove or edit a critical review.
• Do not tell customers to submit feedback only privately.
• Do not describe a private complaint route as an alternative to public feedback.
• Avoid exposing confidential medical, legal, financial or personal information.
• Record operational issues separately from the customer’s public review.
• Escalate urgent complaints through the normal safeguarding or service-recovery process.

Avoid phrases such as “Leave us a five-star review”, “Only happy customers should scan this code” or “Tell us first before posting on Google”. These statements can pressure customers, selectively screen feedback or interfere with an open review process.

How to adapt one script across multiple locations

A central team can create the framework, while branch teams supply local details. Keep the following elements controlled centrally:

• The compliance-approved wording
• The review-request trigger
• Consent and communication preferences
• The escalation route
• Response standards and manager responsibilities

Allow each location to customise:

• Branch name and address
• Staff or practitioner name, where appropriate
• Local service terminology
• Correct Google review link
• Contact details for the local manager

A useful template structure is:

> Hi [name], thank you for [visit/service] at [location] on [date]. Would you share an honest Google review about your experience? [location review link]. Your feedback helps [local team/future customers]. You can also contact [named owner] at [contact route] if you would like a direct response.

For healthcare, legal and other sensitive services, use the minimum personal information necessary. A review request should never reveal why a person visited, what treatment they received or what legal matter they discussed.

Managing negative feedback responsibly

A review request is not complete when the message is sent. Managers need a response process for criticism that is visible, respectful and consistent.

A suitable public response is:

> Thank you for sharing your feedback. We are sorry that your experience did not meet expectations. We would like to look into this carefully. Please contact [team/contact route] so the appropriate manager can follow up. For privacy, please do not include personal details here.

Do not argue, reveal customer information or offer a benefit in exchange for changing a review. Record the issue internally, identify the process owner and agree a response deadline. Where the concern indicates a safety, clinical, legal or safeguarding risk, follow the organisation’s formal escalation procedure.

The purpose of private recovery is to investigate and improve the service. It must operate alongside the customer’s unrestricted ability to leave, keep or update a public review.

Measuring whether the process works

Avoid judging the programme only by the number of positive reviews. A healthy review workflow also measures execution and learning.

Track:

Measure	What it reveals
Request delivery rate	Whether messages are reaching customers
Link and branch accuracy	Whether customers reach the intended profile
Review response volume	Whether timing and wording are usable
Response time	Whether the business acknowledges feedback promptly
Recurring themes	Which operational problems need attention
Location coverage	Whether every branch follows the process

Compare themes over time and by location, but do not pressure staff to produce a particular rating or suppress critical feedback. A lower review volume can still reveal important service issues that deserve action.

How KundPulse supports the workflow

KundPulse can help multi-location service businesses operationalise this process without changing the core principle of open, honest feedback. Core Pulse (€99/month) provides a single-location SMS and email review request engine with basic analytics. Active Pulse (€199/month) adds multi-location workflows, Smart Reply AI drafts and sentiment categorisation. Elite Pulse (€399/month) adds root-cause trend analysis, autopilot auto-replies, high-volume automation, custom webhooks and dedicated support.

Annual billing is available at ten times the monthly price. Whichever workflow is used, every customer should receive a genuine public review option, while private follow-up remains an additional route for recovery and learning.