Choose the right moment for an appointment review request

Key takeaways

• An appointment on the calendar is not evidence that the service took place.
• Choose an observable customer moment and apply the same invitation rule regardless of expected sentiment.
• A cancellation or booking interaction can still be a genuine experience. Do not describe unperformed work as complete or suppress criticism.
• Keep support available independently, check the correct location link and measure invitations separately from published reviews.

Choose the event before choosing the delay

An appointment ends at four on the calendar. At four, one customer may be leaving after a completed service, another may have rescheduled and a third may still be waiting. A message that thanks all three for a finished visit describes three different situations as one.

Start with a better question than how many hours to wait: what actually happened, and what can this person reasonably describe? For a single visit, that might be the completed handoff. For work spread across visits, it might be an agreed milestone rather than the date of the original booking.

Google requires reviews to reflect genuine experiences. It does not establish one universal appointment-to-invitation delay. The timing method in this article is an editorial operating plan: use a reliable event, truthful wording and a customer-controlled choice, rather than treating a calendar time as proof of completion.

Sources: Google Maps: genuine experiences and rating manipulation policy

Keep booking, payment and service completion separate

Write down what each record establishes before using it to prepare a message. A reservation tells you that time was booked. A payment record may show money collected, including a deposit. Neither alone shows that the promised work was performed or establishes a destination platform’s verification badge.

The distinction is about the experience named in the request. Someone can have a real experience with booking or cancellation without receiving the service. Do not say they are ineligible to review the business simply because the visit did not happen. Instead, avoid a completed-service message when the evidence only supports a different interaction.

Define a coverage rule your team can apply consistently

Use observable service facts to define this campaign’s invitation point: the recorded handoff for the selected service and location, for example. Assign someone to reconcile missing or contradictory records. Do not let each colleague decide who seems pleased enough to invite.

Google prohibits selectively soliciting positive reviews, discouraging negative reviews and offering incentives for reviews. A complaint, refund request or low internal score must not become a reason to hide the public review option. Keep the invitation decision separate from a prediction about the rating.

Document legitimate contact constraints through your existing communication process, including an opt-out, a wrong address or a previous request that should not be repeated. Track an unresolved status as unresolved. Do not quietly relabel a difficult visit as cancelled to remove it from the invitation group.

For a multi-stage service, decide which interaction this invitation concerns and how the team avoids overlapping requests. This is a planning choice to review with the service owner, not a requirement to send a message after every visit or enroll customers in a new sequence.

Sources: Google Maps: genuine experiences and rating manipulation policy

Rehearse the edge cases before the ordinary visit

Consider a fictional salon called Juniper Studio. Its team chooses the recorded end-of-visit handoff as the invitation point for a standard appointment. The examples below are practice situations, not real customers, an integration demonstration or a claim about results.

First, a visit is complete but the customer raises a concern at checkout. The support owner takes the concern seriously. The public review opportunity remains available under the same neutral rule; it is not postponed until the customer says they are satisfied.

Second, a customer reschedules before arriving, while the old calendar slot still looks finished. The team corrects the record and uses appropriate booking communication. It does not send a completed-visit thank-you. That decision does not erase the person’s actual booking experience or right to describe it honestly.

Third, a fictional repair business completes an assessment but has not completed the repair. If it invites feedback about the assessment, the wording must identify that stage. It must not thank the person for a finished repair or promise an outcome that is still being investigated.

Ask a colleague to explain the decision for each case without seeing the customer’s predicted sentiment. If they need a happiness score to choose the path, rewrite the rule. If they cannot tell whether the service happened, fix the evidence before automating the request.

Name the experience and leave the review to the customer

For a confirmed completed visit, an illustrative direct invitation is: Thank you for visiting. If you would like to share your experience, this link opens our Google review page. Choose the words that reflect what happened, identify the correct business and leave participation optional.

Do not add an instruction to leave five stars, mention a particular employee or finish the review before leaving. Google prohibits pressure to review on the premises and requests for specific review content. Staff can explain the destination without composing a review or asking to see proof.

Google supports sharing a review link or QR code, and a customer must be signed into a Google Account to post there. They can use a non-Gmail address for that account. Check the actual destination on a phone so your team understands the sign-in step rather than promising that every customer can post immediately.

No single template fits every service state. A booking confirmation should help with the booking. A support message should help with the issue. A review invitation should make the optional public destination clear. Avoid combining these into a message that implies help depends on a review.

Sources: Google Business Profile: review invitations, links and account requirements; Google Maps: genuine experiences and rating manipulation policy

Give support its own owner and route

An unhappy customer needs a useful way to reach the team whether or not they write a public review. Name the responsible role, verify the contact route and describe only the response expectation your business can meet. Do not trade help, a refund or a benefit for silence or a changed rating.

Ripple’s configured form journey keeps public routing available at every rating. A rating of three stars or below reveals optional issue details and consent to contact about that issue; marketing consent remains separate. The service team still needs a real owner for the follow-up.

If an existing campaign includes a useful benefit, its configured benefit is emailed during the brief thank-you confirmation before automatic review routing. The benefit does not depend on the rating or review completion. That established journey is different from a direct Google link, and a separate benefit does not automatically make every campaign compliant with every destination’s rules.

This planning guide does not add a booking-system connection, a completion detector or a sending schedule to Ripple. Use the service records and communication process you actually have, and test any proposed integration separately before relying on it.

Run an appointment coverage check before sending

Pick one location and one service type. Take fictional records through the preparation steps for a completed appointment, a reschedule, a no-show, a customer concern and a multi-stage job. Stop before contacting a real customer or submitting a public review during the rehearsal.

Use the same destination and wording your team intends to use. A correct completion status cannot rescue a link for the wrong branch. A working link cannot rescue a message about a visit that never happened. Check both the event and the destination.

• Name the observable interaction this invitation covers and the record that supports it.
• Check cancelled, rescheduled, no-show and multi-stage examples without consulting expected sentiment.
• Confirm concerns do not remove the public review opportunity and support has a separate owner.
• Identify the correct business/location link and rehearse its phone and sign-in experience.
• Check contact eligibility and prior requests through the existing process; do not start duplicate outreach.
• Record who reviewed the wording, the rehearsal date and the next operational check.

Review coverage before claiming more reviews

At the next check, compare the number of records that met the event rule with the number prepared for an invitation, where those records are available. Investigate missing completion updates, duplicate preparations and messages that used the wrong status. Report gaps rather than manufacturing a complete funnel.

Keep preparation, actual sends, destination visits and published reviews separate. A free static QR does not itself record scans. A redirect or link click is not evidence that Google accepted a review, and a payment does not prove the customer completed a visit. Use the destination’s published records when reporting actual reviews and state when attribution is unknown.

Use Ripple’s service-business journey to discuss the right form, destination and optional support handoff for your operation. If you simply need a direct Google destination, the free review-link and static QR tool is a useful starting point. Neither option removes the need to choose an honest customer moment and verify the location.

Sources: Explore Ripple for service businesses; Build a free Google review link and static QR

Sources and further reading

• Google Maps: genuine experiences and rating manipulation policy
• Google Business Profile: review invitations, links and account requirements