When should you ask for feedback?
Ask after a real customer experience, using a consistent trigger such as recorded job completion. Do not ask only customers expected to rate you highly.
Begin with the customer’s actual task. Write down the question they are trying to answer and the information your office needs to respond. Review one recent inquiry with the person who handled it. Where did the conversation stall? Which detail was missing? Turn that observation into a clear step rather than adding another vague promise. The aim is a process that your team understands and can repeat. Different services may need different questions, so do not force every request into the same script.
Use the same eligibility rule for customers with different opinions of the work. The trigger should reflect a real completed interaction rather than a manager’s guess about satisfaction. If there is a service concern, address it responsibly without removing the public review opportunity. Review requests belong in a customer communication process with clear consent and ownership, not a rating-selection process.
What should the text say?
Hi [Name], thanks for choosing [Company]. If you’d like to share honest feedback about your experience, you can leave a review here: [link].
Put the decision into a short checklist that staff can use while working. Include who owns the next step and what happens when information is missing. The checklist should reflect current capacity and actual company policies. If a detail changes, update the website, messages and internal notes together. This prevents a customer receiving one explanation online and a different one from the office. Keep the wording plain enough that a new employee can understand it without interpreting marketing language.
The template is an example to adapt, not a universal legal or platform-approved script. Confirm the business identity, recipient and working link. Avoid a phrase such as leave us five stars. The customer should choose what to write. A short neutral request leaves room for honest experience rather than making the rating part of the company’s instruction.
Should you include a private feedback option?
Offer a direct contact for questions as an additional route, not a filter that hides the public review link from unhappy customers.
Use a realistic example during review, but do not publish invented customer evidence as proof. A sample helps test the process; a real testimonial requires permission and an actual experience. Check whether the information is appropriate for the channel. Public content should never expose a customer’s address, private finances or household details. A message that looks professional is still a problem if it reaches the wrong person or reveals more than the conversation needs.
A direct feedback channel can be useful when the customer has an unfinished service question. It must be available alongside the public invitation, not used to divert negative experiences into a hidden form. The office should know who handles replies. A review request that invites contact but leaves the reply unanswered can damage the conversation it was meant to support.
Can you offer a reward?
Do not offer an incentive for a favorable review or coach a customer’s rating. Check current platform policies before starting any review program.
Check the handoff, not just the first visible screen. A customer should know what happens next and a team member should see the required action. Test the phone link, form or reply path on a mobile device. Follow the request through the tools your team actually uses. If one person must copy details manually, name that responsibility rather than pretending the system is fully connected. A dependable small workflow is more useful than a large setup with unclear ownership.
A discount tied to a positive rating changes the meaning of the feedback and can conflict with platform rules. Do not build incentives into the template just because another business uses them. Check current authoritative guidance and keep the request neutral. Also avoid sending the customer a review text you want them to copy as if it were their own opinion.
Start with your current website.
A free review of your site, Google presence and lead follow-up.
How do you prevent repeat requests?
Use one completion trigger, a customer record and a duplicate check. Stop reminders when a customer opts out or asks not to be contacted.
Review the scope with your team before turning a suggestion into a public claim. Availability, qualifications and pricing should match what the company can deliver. Avoid a guarantee when outcomes depend on the customer, market or site conditions. If a technical or policy detail is uncertain, verify it with the relevant provider or qualified person. Keep a record of the answer so future edits do not revive an old assumption. Accuracy matters more than a confident-sounding sentence.
Test a customer whose job status changes twice, a duplicate contact and someone who already asked to stop. Those are common paths that a simple demonstration misses. The workflow should not keep sending because a record reentered the same stage. Maintain a completion identifier or other appropriate duplicate control and let staff stop an irrelevant sequence.
How should you reply to reviews?
Thank the reviewer without exposing address, payment or household details. Move a sensitive service discussion into a private conversation.
Use your own records to decide whether the change is useful. Look for missed handoffs, repeated questions and contradictory messages. Do not assign a revenue lift to a new process without dependable evidence. A review should distinguish what you observed from why you think it happened. Keep the first change narrow enough to understand, then refine it when the team sees how customers respond. This makes maintenance practical instead of turning every adjustment into a complete rebuild.
A public response should not reveal the service address, payment situation or private project notes. When a review describes a concern, acknowledge it professionally and offer a private conversation. Do not argue from confidential information to win a public exchange. Give the response responsibility to someone who understands both the service issue and the limits of what can be shared.
What is a neutral reminder?
Hi [Name], if you still want to share feedback about [Company], here is the link: [link]. No obligation. Keep any reminder policy modest and consistent.
When software is involved, define the source of truth for each piece of information. The website may collect a request, the CRM may own follow-up and another tool may own the job. A status update should not trigger the same message twice. Test cancellations, changed dates and a customer who already replied. The exception path deserves the same attention as the normal path. Your team needs a way to stop or correct a workflow without losing the underlying customer record.
Decide whether a reminder is appropriate under the company’s communication policy and relevant rules. Keep it optional and easy to stop. A customer who did not review should not become the target of repeated pressure. The business benefits from an orderly request process, but the customer still controls whether to participate. Silence is not permission to keep increasing the frequency.
How do you evaluate the workflow?
Check the recipient, review URL, trigger and opt-out handling. More messages are not necessarily a better customer experience.
Choose the next action before ending the conversation. It may be a call, a site visit, a written proposal or a request for more information. The right step depends on the service and what is already known. Tell the customer only what has actually been agreed, and keep internal notes factual. If they decline, respect that decision. A clear ending helps your office prioritize active work and avoids continuing messages that no longer fit the customer’s situation.
Confirm the link opens the correct business review page on a phone. Check that a reply reaches staff and that opt-outs stop further requests. Use a test recipient with the necessary permission rather than texting a real customer without context. Review the complete flow after a phone, profile or software change because a working old link does not prove the current one is correct.
ABOUT THE AUTHOR
George · Vercano Partners
George co-runs GRIPGO Roofing and has more than three years of experience building sales scripts and processes.
Meet George