Google Review Response Playbook for Field Service
Respond to every Google review like a dispatcher who cares: templates for five-star praise, tough one-stars, and the awkward no-comment ratings.
A one-star review lands at 7:12 a.m. Your CSR is already on two lines. By noon the review still sits unanswered while three shopping homeowners read it and bounce.
Local shoppers watch how you handle criticism as much as they count stars. Local SEO practitioners also treat review responsiveness as an activity signal. You do not need contested ranking folklore to justify a simple rule: respond to everything, fast, specifically.
This playbook gives you SLAs, templates, and handoff rules so review reply is a daily habit, not a monthly guilt project.
The response SLA
- Negative reviews: same business day, ideally under 24 hours.
- Positive reviews: within 72 hours.
- No-comment low stars: still respond and invite offline contact.
- Target response rate: treat 80%+ as the operating floor, not a stretch goal.
Response anatomy
Use first name when available, one specific job detail, and a forward-looking close. Avoid cost debates in public. Take disputes offline.
Copy-paste scripts
Copy these, then edit bracketed fields so they sound like your shop.
Five-star with detail
Thanks, {Name}. Glad our tech {Tech} got your {Service} sorted in {City}. We appreciate you taking the time. If you ever need us again, call {MainLine}.Five-star short
Thank you, {Name}. Grateful for the kind words about our {City} team.Three-star mixed
Hi {Name}, thanks for the feedback on {Service}. We want the whole experience to feel solid. Can you email {OwnerEmail} or call {MainLine} so we can make this right?One-star angry
Hi {Name}, we are sorry this fell short. Please contact {OwnerName} at {OwnerPhone} today so we can review what happened and fix it. We take this seriously.No-comment low star
Hi {Name}, we saw your rating and want to understand what went wrong. Please call {MainLine} and ask for {OwnerName}.Metrics worth tracking every week
Fifteen minutes every Monday. Same numbers. Same owners.
| Metric | How to count it | Target |
|---|---|---|
| Response rate | Responded / total reviews | 80%+ |
| Neg response speed | Hours to first reply on 1-2 star | Under 24h |
| Offline conversion | Negatives that become resolved tickets | Track weekly |
| Template overuse | Identical replies ratio | Keep low; personalize |
Honest limitations: when a human must take over
Public replies are not litigation. Do not admit liability you have not reviewed. Do not dox customers.
- Legal threats
- Medical or safety incidents
- Chargebacks and invoice wars
- Fake review investigations
Implementation checklist
- Pull last 90 days unanswered
- Assign Monday review block
- Approve templates
- Set negative alert to owner phone
- Log offline resolutions
- Monthly tone audit
Operator FAQ
Offer discounts in replies?
Usually a bad idea and can violate platform policies. Fix offline.
Ask to remove review?
Never demand it. Earn an update by fixing the issue.
Who should reply?
Trained CSR for positives; owner/lead for harsh negatives.
Petunia helps teams see reviews beside the SMS and call history that explain them. Features · What's new.
Related pages: Review request timing, SMS scripts, Pricing.
Local trust mechanics
Specific replies beat generic thanks.
1. Name + service + city
Name + service + city. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
2. Length that reads human
Length that reads human. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
3. No public cost debates
No public cost debates. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
4. Owner escalation path
Owner escalation path. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
5. Photo and GBP hygiene alongside replies
Photo and GBP hygiene alongside replies. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
Negative review operations
Speed plus offline rescue changes outcomes.
1. Same-day alert
Same-day alert. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
2. Ticket creation
Ticket creation. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
3. Calm public tone
Calm public tone. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
4. Private resolution notes
Private resolution notes. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
5. Follow-up if customer updates rating
Follow-up if customer updates rating. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
Team coaching
Tone drift is real under stress.
1. Monthly reply audit
Monthly reply audit. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
2. Banned phrases list
Banned phrases list. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
3. Roleplay one-stars
Roleplay one-stars. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
4. Celebrate good saves
Celebrate good saves. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.
5. Keep templates living documents
Keep templates living documents. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.
Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.
Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.
Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.
Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.
Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.
When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.