# Contractor Review Follow-Up SOP for Google Review Requests

Use this worksheet after the direct Google review link is confirmed. The goal is not more random review texts. The goal is one owner-proof follow-up rhythm after every good job.

## 1. Pick the Google review request owner

| Job moment | Primary owner | Backup owner | Rule |
|---|---|---|---|
| Technician closes a successful service call | Technician | Dispatcher | Mention the review before leaving if the customer is clearly happy. |
| Invoice or receipt is sent | Office | Owner | Send the tracked Google review link the same day. |
| Multi-day install wraps up | Project lead | Office | Wait until cleanup, walkthrough, photos, and payment handoff are complete. |
| Warranty callback ends well | Owner | Office | Ask only after the issue is resolved and the customer is calm. |
| Premium or referral-heavy customer | Owner | Office | Send a personal note before the generic request. |

## 2. Timing rules by job type

- **Same-day service call:** technician warm handoff before leaving, office text within 2 hours.
- **Emergency repair:** send after the customer confirms the problem is solved, not while they are stressed.
- **Install or remodel milestone:** send after final walkthrough, cleanup, photo proof, and payment handoff.
- **Maintenance visit:** send the same day if the visit was smooth; otherwise wait until any promised follow-up is complete.
- **Warranty callback:** send only after the fix is done and the customer feels taken care of.

## 3. First request script

> Hi {{first_name}}, thanks again for choosing {{company}} for {{service}}. If everything looks good, would you mind leaving us a quick Google review? It helps local homeowners know who they can trust. {{review_link}}

## 4. Technician handoff script

> Before I head out, I’m going to send a quick note to the office that the job is complete. If everything looked good today, a Google review really helps our local team. They’ll send the link so it’s easy.

## 5. Second-touch rule

Send one second touch 2 to 4 days later if no review appears and there were no unresolved issues.

> Hi {{first_name}}, just checking that everything still looks good after our {{service}} visit. If you have 30 seconds, a quick Google review would mean a lot to our crew: {{review_link}}

## 6. Failed-request rescue rule

Do not keep asking if the customer is unhappy, confused, or waiting on something. Move them to owner follow-up first.

- Missing part or unresolved issue: assign owner or manager.
- Customer mentions a concern: call before asking again.
- No response after second touch: stop asking for 60 days.
- Review left: thank them, tag city/service/crew, and ask whether a photo or referral follow-up makes sense.

## 7. Tracking fields

Track these fields in your CRM, spreadsheet, or job notes:

- Customer name
- Trade/service
- City
- Job type
- Crew or technician
- Review request owner
- Google review link source
- First request date
- Second request date
- Review received
- Rating
- Follow-up issue
- Referral or photo opportunity

## 8. Product-fit guardrail

LocalKit is useful when review traffic, QR cards, referrals, and profile links need one lightweight local destination. Webzaz is useful when review proof should support service pages, city pages, project galleries, and a stronger quote funnel. Do not force either product into review follow-up unless that routing problem is real.


## Keyword QA notes
Use this SOP for contractor review follow-up, Google review link follow-up, technician handoff, office second touch, failed-request rescue, owner follow-up, and review tracking after completed jobs.