The customer review response playbook: 10 minutes a week with Claude

The prompt template

This is the single prompt. Paste at the start of each Friday’s chat with the week’s reviews underneath.

I'm pasting [N] customer reviews from this week. Some are positive,
some are critical. For each one, draft a response in my voice
following these rules:

POSITIVE REVIEWS (4-5 stars):
- Acknowledge something specific from THEIR review (the dish they
  mentioned, the staff member they named, the experience they
  described)
- Thank them by name (first name only)
- Keep it under 50 words
- End with a soft invitation back ("see you next time", "looking
  forward to seeing you again", whatever fits the voice)
- Australian English, no exclamation marks, no "we appreciate
  your business" generic-speak

CRITICAL REVIEWS (1-3 stars):
- ACKNOWLEDGE the specific issue they raised, name it, don't
  vaguely "we're sorry you had this experience"
- Apologise sincerely if the fault is ours (we got something wrong)
- DO NOT concede facts that aren't established
- Offer a concrete next step: a contact email / phone, or what
  we're doing to address the issue
- Keep it under 80 words
- Match the seriousness, don't be flippant on a real complaint,
  don't be defensive on a misunderstanding
- Australian English, professional warmth, never defensive

For each review:
1. The star rating + reviewer first name
2. One-line summary of what they said
3. The response draft

Reviews:
[paste reviews, one per block]

You’ll get the draft set in 60-90 seconds. Spend 8-9 minutes reviewing + editing + posting.

The 4-5 star response that actually lands

Most positive reviews get a generic “thanks for the kind words!” response. The reviewer notices it’s generic. The next customer reading the response also notices.

The good response acknowledges something specific. “Thanks for the kind words, Sarah, and for noticing Pip’s flat white. She’s been working hard on her latte art this month, so that means a lot. See you next time.” That response makes the next reader think: real people work here, and they read what I write.

Format that works:

[First name], thanks for [specific thing they mentioned].
[One sentence acknowledging or extending that specific thing.]
[Soft signoff inviting them back or thanking them again.]

40-50 words. No exclamation marks. Specific to their review.

The 1-3 star response that doesn’t make things worse

The instinct is to be defensive or apologise generically. Both fail. The pattern that works:

1. Name the specific issue the reviewer raised. Not “we’re sorry you had a bad experience” but “we’re sorry the wait time was 25 minutes on Saturday lunch service”.
2. Apologise if it was our fault. Don’t apologise for things that aren’t your fault (the customer’s wrong expectation, an issue outside your control). Don’t concede facts that aren’t established.
3. Offer a concrete next step. A direct email, a phone number, what you’re doing about it (“we’ve reviewed our Saturday rostering this week”).
4. Match the seriousness. A complaint about a 25-minute wait is different from a complaint about food safety. The response register has to fit.

Example:

“Mark, thanks for taking the time to write this. You’re right that the Saturday lunch wait was longer than it should have been, we got hit with a roster gap on Sundays that flowed through. We’ve fixed the Saturday roster for the next month and added a barista. If you’d like to come back and let us redeem ourselves, email me at [direct] and I’ll make sure I’m there., Olivia, owner”

That response is hard to write at 3pm Friday. Claude drafts it in 30 seconds. You edit for accuracy + tone in 1-2 minutes. Post.

What this does to your local search

For local-search-driven businesses (cafes, services, trades, allied health, beauty), Google’s local algorithm explicitly weights review response rate as a ranking signal. Documented in 2024-2025 local SEO research, confirmed by Google in multiple Search Liaison statements.

The directional effect:

• Under 30% response rate: significant ranking penalty in competitive local searches
• 50-70% response rate: par for Australian SMB
• 80-100% response rate: ranking bump, especially against local competitors with lower rates

Most Australian SMBs sit at 20-40%. The 10-minute weekly habit moves you to 95%+ within a month.

Across DotVA clients running this workflow consistently, we’ve watched Google local-pack visibility on competitive queries improve by 15-40% within 3-6 months. Reply rate isn’t the only signal, but it’s the one most operators are leaving on the table.

The Friday afternoon ritual (why this timing matters)

Why Friday afternoon specifically:

• You’re fresh enough to engage emotional reviews without snapping back
• The week is closing, so the critical reviews don’t fester into Monday
• It’s a natural transition point between “this week” and “next week”, a useful psychological boundary
• Most reviews land Monday-Thursday; Friday catches them all
• The work is bounded: 10 minutes, recurring slot, done

Operators who try to handle reviews ad-hoc throughout the week usually drop the habit within a month. The single weekly ritual sticks.

What to NOT do

Three patterns that backfire:

1. Auto-posting AI responses. Tone drift + Google’s authorship policies + hallucination risk. Don’t.
2. Engaging with troll / abusive reviews. Use Google’s review removal process for genuinely policy-violating reviews (off-topic, hate speech, conflicts of interest). Don’t litigate in the response thread.
3. Replying to every single comment / question / passing remark on the platform. Reviews specifically. Questions / messages / DMs are a different workflow (see the inbox cleanup playbook).

What this doesn’t solve

• Genuine product / service quality issues. If you’re getting consistent critical reviews about the same issue, the fix is the operations, not the response.
• Defamation / legally actionable reviews. Get specialist advice.
• Reviews on platforms you don’t have access to. Some platforms aggregate reviews from elsewhere. Focus on the ones you can directly respond to.

For everything else: the 10 minutes pays back in trust, in local search visibility, and in customer relationships you’d otherwise let drift.

What’s next

• The inbox cleanup playbook, 10 minutes a day with Claude, sister daily workflow for customer email.
• Build a social media powerhouse with Claude Code, the weekly content workflow that pairs with this review habit.
• Claude Projects setup in 30 minutes, the voice file foundation that makes review responses sound like you.
• Book a free audit if your business has a specific local-search competitive landscape and you want help mapping the review + content workflow together.