A spa owner checks Google after a slow week and notices that the latest review is three months old. The usual response is a burst of activity: ask every therapist to bring in reviews, offer a small perk, and send a message to the clients most likely to say something nice. That approach creates avoidable problems and usually fades when reception gets busy again.
A better operating system makes an honest review easy to leave, gives someone responsibility for reading the feedback, and turns recurring complaints into changes clients can actually notice. The work starts with a clear request process rather than a target star rating.
Set the rules before choosing software
Google's Maps content policy permits requests for genuine reviews but prohibits incentives, selectively soliciting positive feedback, and pressure to review on the premises. It also prohibits asking staff to solicit a set number of reviews or requesting specified review content, including staff names.
For a spa, that rules out a discount for posting, a free add-on for changing a rating, and instructions to mention a therapist or treatment. Remove these practices from scripts and software settings before considering message timing.
Federal rules and platform rules are separate. The FTC's review-rule guidance explains that incentives conditioned on positive or negative sentiment are prohibited. It does not say every unconditional incentive is prohibited by that rule, but other disclosure and deception requirements can apply. Google's incentive ban is broader. An incentive-free Google review process avoids having to reconcile those different standards for each campaign.
Choose a neutral trigger that the team can maintain
Write down which completed visits enter the request process and why. A practical starting point is one invitation after a completed visit for clients who can appropriately be contacted through the chosen channel, with a cooldown to avoid repeatedly asking frequent visitors. This is an operating recommendation, not a promise that a particular interval produces more reviews.
Do not make eligibility depend on a satisfaction score, a generous tip, a rebooking decision, or whether someone complained. A private survey can be useful, but a workflow that sends happy respondents to Google while sending unhappy respondents only to reception filters the public invitation by sentiment.
Keep private feedback available to everyone, alongside the same public-review option. Clients should be able to raise a problem directly without being diverted away from expressing their own experience elsewhere.
Before enabling an automation, test it with internal test records rather than actual client data. Check completed appointments, cancellations, duplicate bookings, repeat visits and opt-outs. The trigger should not fire when a booking is created or when a canceled appointment is marked as completed by mistake. Use approved contact permissions and honor channel-specific opt-outs; booking a service is not a reason to assume permission for every type of follow-up.
Make the request short and optional
Google provides a review link or QR code that businesses can share. Customers need a Google Account to post. Use the link for the correct location and test it from a phone before putting it on receipts or into a message template.
A sample invitation for a nonmedical spa could read: “Thank you for visiting [Spa]. If you would like to share your experience, you can leave an honest Google review here: [review link]. Feedback is welcome, and reviewing is entirely optional. To contact our team directly, use [contact details].”
Replace every placeholder before use. Keep the private contact route available whether or not someone leaves a review. Do not add suggested praise, a requested rating or a prewritten account of the visit.
At the front desk, place a small review-link card where clients can take it away. Staff should not watch someone complete a review, ask to inspect the posted result, or make a review part of checkout. For medical settings, have the privacy lead approve both the message and the underlying contact workflow before using it.
Assign ownership without turning reviews into a sales contest
One person should own the system, with a backup for days off. That owner checks that links work, requests are not duplicated, opt-outs are respected, and replies that need management attention reach the right person. Therapists should know where to send feedback, but their pay or performance review should not depend on named mentions or stars.
Use a short weekly operations check rather than a leaderboard. Ask whether the process ran as designed, whether any messages failed, whether a location link was wrong, and whether a recurring complaint needs a decision. These questions identify fixable problems without asking staff to manufacture favorable comments.
Keep the public-review work separate from service recovery. If a client deserves a refund or another remedy under your policies, resolve that issue on its merits. Do not make the remedy conditional on removing or rewriting feedback.
Measure coverage and learning, not just the average rating
The following example is hypothetical and is not an industry benchmark. Suppose a spa has 200 completed visits in a month. Repeat visits within its chosen cooldown account for 40, leaving 160 distinct request opportunities. Of those, 140 have an appropriate contact channel and no applicable opt-out. The system sends 126 invitations, while 14 fail or are missed.
The process coverage is 126 divided by 140, or 90%. The first question is what happened to those 14 invitations. An incorrect contact field, integration failure or missing appointment status can explain the gap without any need to pressure clients.
Suppose the Google profile receives 18 new reviews during that month. Eighteen divided by 126 is 14.3%, but it is only a rough comparison of reviews received to invitations sent. Some reviews may come from older clients or people who used the reception card, and some invited clients may post next month. Do not label that ratio a precise campaign conversion rate unless you have a reliable, privacy-appropriate way to establish attribution.
Keep a small monthly record of completed visits, eligible request opportunities, invitations sent, delivery failures, new reviews received and recurring feedback themes. Use aggregate figures where possible. Pair this with your client-retention measures so you can distinguish public visibility from whether clients actually return.
Write replies that protect the client
A public response should show that someone is listening without turning the review into a debate. For a straightforward comment about the premises, a brief thank-you may be enough. For a complaint, give a direct route to a manager who can investigate privately. Do not publish booking notes, payment disputes, contact details or treatment history to prove your version of events.
Medical practices need particular care. HHS has settled an enforcement matter involving a dental practice's disclosure of protected health information in review responses. A reviewer's own post should not be treated as permission to disclose information from their record. Clinics should have their privacy lead determine applicable obligations and approve response templates.
A cautious starting response is: “We take feedback seriously. Please contact our practice manager through the contact details on our website so the concern can be addressed privately.” It does not confirm that the reviewer was a patient or describe what happened. Staff should escalate allegations involving safety, privacy or professional conduct rather than improvising a public answer.
Maintain a private issue log for operational follow-through. Record the broad theme, the responsible manager, the decision and the next check. Keep sensitive records in the appropriate restricted system, not in a shared marketing spreadsheet.
Turn the feedback into a change clients can see
Review requests are only one part of the job. If several independent comments mention unclear parking, revise the arrival instructions. If people repeatedly describe waiting without an update, give reception a clear escalation process. If pricing surprises recur, examine where the quoted service price, optional extras and final checkout total diverge.
Look for patterns before drawing conclusions about an employee from one public comment. Discuss the facts privately and check the relevant process. A single review can reveal a useful question without proving the cause.
Over the next 30 days, assign the owner, test one neutral request workflow, approve the response templates and review the first aggregate results. Keep the changes small enough to maintain during a busy week. A dependable process gives clients room to describe their experience honestly and gives the business a practical way to improve it.
Illustrative reception photograph: Meg von Haartman / Unsplash, used under the Unsplash License. The pictured venue is not an example of the review practices discussed.
