Teach a clear handoff, not a sales pitch
A technician finishes a repair, explains the work, and prepares to leave. That short conversation is a useful place to make feedback easy. It is also a place where a customer can feel pressured if the technician waits for a rating, asks for praise, or makes the request sound like a condition of service.
Review request training should help home-service technicians offer a simple option and then return control to the customer. The goal is a consistent, respectful handoff. The customer decides whether to review, when to do it, and what to say.
Google’s review guidance allows businesses to share a review link or QR code and encourages honest, balanced feedback. It does not mean every technician needs a personal campaign. Build the training around the company’s existing process, using the home-service review framework as the office-level foundation.
Give the team one short invitation
Suggested wording: “If you’d like to share your experience, our review link is on this card. You can use it whenever it’s convenient.”
Use this after the agreed service handoff, not while the customer is still waiting for an explanation, invoice correction, or next step. The timing is an operational recommendation, not a Google-mandated rule. Keep a follow-up service conversation separate from the optional review invitation.
The wording has three jobs: make the invitation optional, point to a usable destination, and leave the customer free to act later. It does not ask for a particular rating or suggest what the review should contain. A technician should not add a request to mention their name, a city, a service keyword, or a claim about the repair.
If the office already sends a scheduled invitation, agree on how the spoken handoff and that message fit together. Avoid several staff members asking independently. The review request templates provide neutral wording for the written part of the process.
Write the approved phrase on a small training card with the service contact and the correct branch destination. Treat it as a reminder, not a script the technician must recite mechanically.
Set clear boundaries for the conversation
Explain the reason for each boundary in plain language. A customer’s feedback belongs to the customer; the technician’s responsibility is the service handoff and a respectful invitation.
Offer the option, then move on
A customer who declines or says they will do it later does not need another pitch. A simple “Of course” is enough. Do not wait beside the customer while they write, ask to see the submission screen, or take their phone to complete the review.
Google’s Maps content policy prohibits pressure, selective positive solicitation, requests for specific review content, and asking staff to solicit a set number of reviews. Training should therefore focus on the quality of the interaction rather than a technician leaderboard or review quota.
Keep benefits and service decisions independent
Keep any warranty, callback, refund, or agreed work decision within the normal service process. Staff should not bargain over feedback or suggest that a review earns special treatment. Google’s policy also prohibits incentives for posting reviews or revising or removing negative ones.
Do not screen for praise
Do not teach a sequence where the technician first asks whether the customer is happy and offers the public link only after a favorable answer. The review-gating guide explains why private feedback must not control access to a public review invitation.
The FTC’s guide for marketers similarly advises against asking only customers expected to leave positive reviews and stresses that platform rules matter. A process that sounds polite can still be biased if the team quietly excludes critical customers.
Route concerns without turning them into a public debate
If the customer raises a concern, acknowledge it and arrange a handoff to the responsible person. Record what needs attention, who owns it, and the next contact step. Do not make promises beyond the technician’s authority.
Keep the agreed invitation eligibility rule consistent. A service issue may mean contracted work is genuinely unfinished; it should not become a permanent exclusion because the customer might be critical. Give any operational hold a factual reason and reassessment point. The office owns that decision rather than asking technicians to improvise.
Practice situations technicians actually encounter
Run a short demonstration, let each technician respond, and give feedback on the words and handoff. The following role-plays are hypothetical training exercises, not customer testimonials or claims about results.
The customer is busy
Customer: “I’m late for something.” Useful response: “Understood. Here’s your service information and our contact details.”
Coach the technician to finish the essential handoff without trying to fit in another conversation. The office can apply its normal invitation process later. Respecting the situation is more useful than forcing the phrase into every departure.
The customer asks what to write
Customer: “What should I put in the review?” Useful response: “It’s up to you. Please use your own words about your experience.”
Listen for extra coaching that slips in after the neutral answer. The technician should not supply a sentence for the customer to copy or turn the question into a request for a name, keyword, or favorable rating.
The customer reports an unresolved problem
Customer: “The issue is still happening.” Useful response: “Thanks for telling me. I’ll record that and contact [responsible service person] so we can confirm the next step.”
Replace the placeholder with the actual escalation path before training. Evaluate whether the technician identifies the problem and assigns a real handoff. Do not let the conversation become a negotiation about changing or withholding a review.
The customer has already reviewed the company
Customer: “I already left a review after the last visit.” Useful response: “Thank you for letting me know. I’ll note that for our office.”
Do not push for a second account or ask the customer to prove it on their phone. The office should review its own duplicate-contact controls. The automation guide covers useful stop conditions.
The link reaches the wrong branch
Have the technician identify the mismatch and notify the office instead of guessing a replacement link. Remove the incorrect card from use and assign someone to check related templates. The multi-location guide explains branch routing and ownership.
End each exercise with one concrete improvement: shorten the invitation, accept the decline, identify the service owner, or check the destination. Repeat the scenario until the person can handle it naturally.
Check the tools before putting them in a service vehicle
Have the profile owner obtain the destination using Google’s link and QR-code instructions. Test the printed card on a phone and confirm the business and branch. Check that the service contact reaches a monitored channel. Keep a dated master copy so the office can recognize an outdated version.
Google notes that customers need a Google Account to post a review. A technician can explain that requirement without helping the customer sign in, handling credentials, or trying to submit feedback for them. The review-link checklist helps the office test the full customer path.
For recurring visits, train the team to use the company’s frequency rule rather than interpreting each ticket as a new customer. If dispatch, billing, and technicians all hold different contact records, resolve that process issue before increasing reminders.
Keep public replies with an authorized owner
Teach technicians where to send a review that needs attention. Google’s review-management guidance explains that approved replies appear publicly under the business’s review. A field employee should not improvise a company reply without the appropriate authority.
The office can acknowledge criticism and arrange private follow-up using the negative-review response guide. Keep customer addresses, access arrangements, and private service history out of public exchanges. A technician’s knowledge of the job belongs in the restricted service record, not in a defensive comment online.
Evaluate training by observable behavior
Use an onboarding role-play and a periodic supervisor check. Assess whether the person explains the completed work, uses optional wording, respects a decline, leaves the rating and content open, and routes a concern to the right owner. Review cards and office messages together so coaching matches the actual customer experience.
Track process defects such as wrong-profile links, repeated invitations, missed service handoffs, and outdated materials. Use those observations to improve training. Do not turn the check into a count of favorable reviews attributable to each technician.
The review metrics guide separates operational measures from public feedback and business outcomes. A clear handoff is worth maintaining even when you cannot assign a specific review or sale to it.
Make the office and field process work together
Good training gives technicians fewer decisions to improvise and gives customers a clear choice. Explore Echo Ratings for review workflows, compare pricing, or request a free reputation audit. You can also start a trial or talk with the team about your current handoff.
Official guidance was checked November 2, 2026. This article provides general operational information, not legal advice; review current platform and applicable communication requirements for your business.
