Review Response Prompt Pack

A free prompt pack for drafting faster, more useful Google review responses for small businesses without sounding canned.

What This Asset Covers

• Prompt templates for positive reviews, neutral reviews, and recovery situations
• Tone guidance to avoid sounding robotic
• Simple input fields so the prompt can be reused by any staff member

Use this when

1. You want to respond to reviews faster without losing brand voice
2. Your team is inconsistent in how it handles public feedback
3. You want a low-friction way to test AI for operational tasks

Working Asset

Review Response Prompts

Use this pack when the business wants faster review replies without sounding robotic, defensive, or generic. These prompts are structured for modern AI models that perform best when the input context, constraints, and output format are explicit.

Core Variables

Fill these before running any prompt:

• <business_context>: trade, clinic, or firm type plus city or service area
• <service_event>: what the customer hired you for
• <review_summary>: one-sentence summary of what the reviewer said
• <customer_name>: first name if visible; otherwise leave blank
• <brand_tone>: calm, warm, premium, practical, fast-moving, clinical, etc.
• <next_step>: optional offline path for recovery situations
• <risk_flags>: legal, refund, safety, or compliance sensitivities to avoid improvising around

Prompt Architecture

For the strongest output, keep the prompt in this order:

1. Business context
2. Review details
3. Tone rules
4. Output rules
5. Final QA instruction

Use a structure like this:

You are drafting a public review reply for <business_context>.

Review details:
- Customer name: <customer_name>
- Review summary: <review_summary>
- Service event: <service_event>

Tone rules:
- Keep the voice <brand_tone>
- Sound specific, not canned
- Do not invent facts
- Do not mention refunds, legal positions, or blame unless explicitly provided

Output rules:
- 60 to 90 words
- Public-facing only
- One clear closing sentence

Before finalizing, check that the reply sounds human, specific, and safe for a public Google review thread.

Positive Review

Write a public reply for a 5-star review using the context above.

Requirements:
- Thank the reviewer naturally
- Reference the service event specifically
- If the name is present, use only the first name
- Reinforce one thing the company is known for
- Close with a light future-facing line without sounding salesy

Neutral Review

Write a public reply for a mixed or neutral review using the context above.

Requirements:
- Acknowledge the customer experience without defensiveness
- Recognize the positive portion first if one exists
- Clarify care and accountability without overexplaining
- Offer an offline next step if useful
- Keep the tone steady and respectful

Recovery Review

Write a public reply for a negative review using the context above.

Requirements:
- Lead with calm accountability
- Avoid argument, blame, sarcasm, or legal positioning
- Do not repeat sensitive allegations in detail
- Invite the customer into an offline next step using <next_step>
- End with one sentence that shows seriousness and professionalism

Channel Guidance

• Google: keep it short, specific, and easy to scan
• Yelp: stay even more measured because reviewers often expect a calmer tone
• Healthcare or legal: avoid anything that confirms private customer details not already public
• Home services: reference the service moment and team responsiveness where true

QA Checklist

Before posting, ask:

• Does the reply sound like the company rather than like AI?
• Is it specific enough to the actual service event?
• Did the model avoid inventing facts or overpromising?
• Would this reply still feel strong if a prospect read it before booking?
• If the review is negative, did the reply move the issue offline without sounding evasive?

Failure Modes

Watch for these common weak outputs:

• generic gratitude with no service-specific detail
• overly polished marketing language
• defensive replies that argue the facts in public
• fake empathy without a real next step
• overlong replies that read like a press release

Suggested Team Workflow

1. Draft with the prompt
2. Human review for facts and tone
3. Trim anything that sounds too polished
4. Publish within 24 to 72 hours
5. Save the strongest variants as future examples