A practical workflow guide
Make room for honest customer feedback.
A review invitation can be a useful final step after completed service. Plan when it goes out, who receives it, and who handles exceptions before automating the request.
By ApexScale AI · Published
Start with the platform’s rules
Google Maps requires reviews to reflect real experiences. Its policy prohibits incentives, fake reviews, and selectively requesting positive reviews. Businesses may invite genuine feedback without influencing the rating or content. Avoid pressure or asking for a specific rating.
Read Google’s prohibited and restricted content policy, including fake engagement and rating manipulation. Source reviewed October 3, 2026. Check the rules of each review platform before using a request there.
1. Define a consistent completion trigger
Use a recorded service-completion event, not a lead arrival or an unconfirmed appointment. Choose a delay that gives the customer time to experience the work. Record which person or system confirms completion and what happens when a job is reopened.
Invite all eligible real customers using the same criteria. Define eligibility by completed service, contact permission, and duplicate prevention. Do not filter by satisfaction score, predicted sentiment, complaint history, or an employee’s guess about who will leave five stars. A feedback survey must not decide who receives a public review link.
2. Keep the invitation neutral
Identify the business, explain why you are contacting the customer, and make responding optional. Do not offer a discount, gift, or payment. Do not draft or post a review for the customer, require particular words, or promise a five-star result.
Example invitation
Hi [first name], this is [business name]. Thank you for choosing us for [service]. If you would like to share your experience, you can leave an honest review here: [review link]. Feedback is optional. If you need help with the service, contact us at [support contact].
This is a planning example, not a live message or an ApexScale automation. Confirm the channel’s contact requirements and opt-out handling before using it. A support contact should remain available to everyone, independently of the review invitation.
3. Give the workflow an owner
Write down the sequence: confirm completed service, check permission and duplicate history, queue the neutral invitation, record the delivery result, and route failures to a named person. Test with fictional customer details before a limited pilot. Keep only the information needed for this process and define retention and access.
A failed send needs a recoverable record. A stop request should prevent further outreach. Set a modest reminder limit in advance and avoid repeatedly chasing customers who choose not to respond. Confirm tool support and delivery behavior with the supplier before relying on either.
4. Review handling, not a promised rating
During the pilot, inspect whether completion events are accurate, invitations follow the same criteria, messages are duplicated, and opt-outs reach the queue. Compare the queue with actual completed jobs. Delivery, a link click, and a published review are different outcomes; do not assume one proves another.
Use feedback to improve the service. Respond respectfully to concerns without offering something in exchange for changing or removing a review. Avoid rating targets or forecasts that have no measured basis.
Plan the whole customer journey.
Full refund if you cancel within 14 days of Margot answering your first call.