← All posts

Review request message: what to send after a studio visit

Write a review request message after a completed visit. Three neutral examples, a tested Google review link and a send log that prevents duplicate requests.

An ivory envelope passes between two paper hands beneath a blank green speech bubble

A review request message should name your business, invite an honest account of a completed visit and give the client a working review link. Send one request through the agreed channel, then record it so the next shift does not ask again. The client chooses whether to write and what to say.

In a salon or studio with several staff members, reception might send a thank-you email, the stylist a text, and a follow-up tool another request that evening. A small send log lets everyone check whether the request has already gone out.

Start with a completed visit and a neutral rule

Choose an objective starting point, such as completed visits from the previous working day. Check the visit status before preparing the list. A cancelled booking, a consultation that never took place or a future reservation should not trigger a message thanking someone for attending.

Apply the same invitation rule regardless of how pleased the client seemed. Google's review policy prohibits incentives and selectively soliciting positive reviews. It also prohibits pressuring people to review on the premises or requesting specific review content. Ask for an honest account without suggesting a rating, staff name or wording.

Keep any service problem with the person responsible for answering it. Give clients a monitored contact route alongside the optional public review link, available to everyone. A private satisfaction score should never decide who receives the public link.

Check permission for this purpose and channel through your existing communication process. Permission to receive essential booking details does not, by itself, establish permission for every later campaign. If the permission is unclear, stop the send for review by the responsible person. Record that operational reason without making assumptions about the client's opinion.

Open the business profile you manage and use Google's current option for sharing a review link. Google's instructions explain how to copy that link or download its QR code. Use the profile for the branch the client visited, especially when locations have similar names.

Test the link from the finished message on a phone. Check the business name, address and destination before approving it. A map pin, a link to an existing review and a link for writing a new review can lead to different screens. Record what your chosen link opens.

Google notes that customers need a Google Account to leave a review. A sign-in screen can therefore be an expected step. Test with a staff member's own account, without submitting a test review or asking anyone to lend you their login. Keep a separate sign-in-free contact route for clients who only want to speak to your team.

Store the approved link with its branch, test date and person who checked it. When the business moves or changes its public profile, repeat the check before the next send. Avoid a chain of unnecessary redirects that makes it harder for staff to see where the link goes.

Choose one of three review request messages

Replace every bracket before sending. These examples are alternative openings for the same request; they are not a sequence to send to one person.

A short message after the visit

Hi [name], thank you for visiting [business]. If you would like to share an honest review of your experience, you can write one here: [verified review link]. For help with your visit, contact [monitored contact]. To stop review requests, [working opt-out route].

Use this when the client recognises the business and a short message gives enough context. Leave detailed service notes out of the preview. A generic thank-you avoids exposing a private treatment or consultation on a locked phone screen.

If the sender can receive replies, name the person or team responsible for them in your internal instructions. If it cannot, replace any invitation to reply with a working phone or email route. Test the opt-out before using that wording.

A thank-you email with room for contact details

Subject: Thank you for visiting [business]

Hi [name],

Thank you for your visit to [business]. You are welcome to share an honest review of your experience on Google: [verified review link].

If you need help with your visit, reach us at [monitored contact and hours].

[Business name]

To stop review invitations, [working opt-out route].

Use one clear review link. Leave out a discount, a booking offer and a request to follow several social accounts. Those extra actions give the team more material to maintain and the client more decisions to make. Keep necessary aftercare instructions in the professional's approved service communication.

When the client asks where to leave a review

Thank you for asking, [name]. Here is the Google review link for [business and branch]: [verified review link]. Please share your experience in your own words.

Record this direct reply in the same log as planned requests. Otherwise, the client may receive another invitation hours after asking for the link. Send it to the person who asked; do not distribute a group's contact details through one review conversation.

Use a send log with one owner per request

Keep the log in a place the sending team can access, with access limited to the work they need to do. Use a client reference rather than copying full contact details into an open spreadsheet. The protected client record remains the place for private service information; the client notes guide covers that separate record.

Field What staff enter
Client and visit reference The completed visit being checked
Branch and destination Approved review link for the correct location
Permission check Purpose, channel and any stop request checked
Previous request Date and channel, or none found after checking
Owner One person who will send or close the request
State Ready, sent, withheld, failed or closed
Send evidence Time, channel and available delivery reference
Next action Investigate failure, apply opt-out or close

Before sending, the owner checks recent contact across reception, the professional and any active sending tool. Mark the request as assigned while it is being prepared, then sent after the provider accepts it. Keep a failed delivery separate from a client declining to write a review.

Choose a local rule for repeat visitors before starting. For example, a small studio might trial one invitation per client during its four-week review period, even if that person attends twice. That is an operating example, not an optimal frequency or a performance claim. Check older requests too, rather than treating the trial start as permission to ask everyone again.

Work through a six-client example

Suppose a fictional studio checks six completed visits. Four clients have clear permission for the chosen channel and no recent request. One client already received the link from their stylist, and one has asked to stop review invitations. The owner prepares four new requests and records the two withheld rows with their factual reasons.

Of the four sends, three are accepted and one fails. The log now contains three newly sent requests, one failure to investigate and two withheld entries. The stylist's earlier message remains a previous send. None of those states proves that a public review was posted.

If two new reviews appear on the profile, do not assign them to clients by guessing from display names. An accepted message is not proof of reading, and an increase in reviews does not establish which request caused it. Keep the operational check focused on correct destinations, permitted sends and duplicate prevention.

Close silence and handle replies

For a small first trial, one request with no automatic chase is a workable starting rule. Close the request at the review date you chose. Do not switch from email to a personal number because someone has not reviewed.

When a client raises a service concern, assign a reply owner and a realistic response time. Keep the public review route available under the same invitation rule. If replying publicly to a review, protect private visit details and move any detailed discussion to your monitored contact route. Google's reply guidance also advises protecting customer privacy.

Skedful's current pricing page lists Marketing on Pro. For a review-request process, ask the team to confirm the available destination links, channels and enabled settings for your account. Keep this worksheet staff-managed until you have checked the actual send and stop behavior.

Before the first client send, rehearse three internal cases: a completed visit with permission, a client already sent the link and a client who opted out. Only the first should reach the send step. Open that finished message on a phone, follow its link and test its contact and opt-out routes. Save the approved version beside the log with the sender's name and the review date.

About this article

Skedful is the publisher and corrections contact. Our editorial checklist covers product availability, source dates, worked examples and the limits of each claim.

About this article

Worked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.

Found an error? Send us the article link and the passage that needs a correction.

Report an error to Skedful

Reminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy