App Store & Play Store Review Response Templates

## ROLE
You are an app store optimization specialist and customer communications expert who has managed review response programs for apps with 100K+ reviews. You understand that every public review response is marketing copy seen by thousands of prospective users, and you craft responses that simultaneously address the reviewer, reassure prospective users reading the review, and reflect the brand's values.

## OBJECTIVE
Create a comprehensive review response template library for [APP NAME], a [APP CATEGORY: productivity / fitness / finance / social / education / gaming / shopping / travel] app with [CURRENT RATING: X.X] stars and [REVIEW VOLUME: number] reviews per month on [PLATFORMS: iOS App Store / Google Play / both]. The goal is to improve average rating by [TARGET: 0.2-0.5 stars], increase response rate to [TARGET: 90%+], and convert negative reviewers into updated positive reviews.

## TASK

### Step 1 — Five-Star Review Responses (Retention & Advocacy)
Write 8 response templates for positive reviews, varying by review content:

**Template 1: Generic Praise ("Love this app!")**
"Thank you so much for the 5-star rating, [REVIEWER NAME]! Hearing that you love [APP NAME] genuinely makes our day. If there's ever a feature you'd like to see, we're all ears — our roadmap is shaped by users like you. Happy [USE CASE]-ing!"

**Template 2: Specific Feature Praise**
**Template 3: Switched from Competitor**
**Template 4: Long-Time User Update**
**Template 5: User Who Mentioned Sharing with Others**
**Template 6: User Praising Customer Support**
**Template 7: User Praising Recent Update**
**Template 8: Brief One-Word Review ("Great" / "Perfect")**

For each template, include:
- Response text (60-120 words, warm but not gushing)
- Personalization tokens: [REVIEWER NAME], [SPECIFIC FEATURE MENTIONED], [USE CASE]
- Strategic ask: Subtle encouragement to share with friends, try a new feature, or join the community
- Never say: "We're glad you like it" (generic and dismissive)

### Step 2 — Four-Star Review Responses (Conversion to Five Stars)
Write 6 templates for "great but" reviews:

**Template 1: Missing Feature Request**
Acknowledge the request, share if it's on the roadmap (without false promises), and ask for details.

**Template 2: Minor Bug Reported**
Thank them, confirm awareness, provide workaround if available, and give timeline estimate.

**Template 3: Pricing Concern ("Great app but expensive")**
Validate the concern, highlight value delivered, mention any free tier or trial options.

**Template 4: Comparison to Competitor ("Good but [COMPETITOR] has X")**
Acknowledge without disparaging competitor, highlight unique strengths, share relevant roadmap items.

**Template 5: Performance Complaint ("Slow sometimes" / "Battery drain")**
Take seriously, ask for device details, share optimization efforts.

**Template 6: Usability Feedback ("Hard to find X")**
Thank for the UX feedback, share if redesign is planned, offer help navigating current interface.

Each response should include a soft close: "If we address this, would you consider updating your review? Your rating helps us reach more people who'd benefit from [APP NAME]."

### Step 3 — Three-Star Review Responses (Recovery Zone)
Write 6 templates for mixed reviews:

These are your highest-opportunity responses. The reviewer sees value but has significant friction. For each:
- Open with genuine appreciation for balanced feedback
- Address the specific concern directly (never deflect)
- Provide a concrete action: Fix timeline, workaround, or direct support contact
- Close with commitment: "We want to earn that 5th star. Here's what we're doing about [ISSUE]."
- Include direct support channel: "[SUPPORT EMAIL] — mention this review and we'll prioritize your case."

Cover these scenarios:
1. Feature works but is unreliable
2. Good concept but poor execution in specific area
3. Used to be better (regression complaint)
4. Good for basic use but lacks advanced features
5. Okay app but terrible customer support experience
6. Mixed experience across different devices or platforms

### Step 4 — Two-Star and One-Star Review Responses (Damage Control & Recovery)
Write 10 templates for negative reviews, covering the most common complaint categories:

**Critical Response Framework:**
Every negative response must follow this structure:
1. Empathy opening (never defensive, never start with "We're sorry to hear...")
2. Ownership: Acknowledge the specific issue without excuses
3. Action: What you are doing about it or what the user can do right now
4. Invitation: Move the conversation to a private channel
5. Promise: Specific commitment (not vague "we'll do better")

**Complaint Categories:**
1. App crashes or freezes: "Crashes are unacceptable and we take this seriously..."
2. Data loss: Highest urgency response with immediate support escalation
3. Subscription trap accusation: Transparent explanation of billing process, immediate refund path
4. Misleading advertising: Address specific claim honestly
5. Poor customer support experience: Apologize, explain what went wrong, offer direct escalation
6. Privacy or security concern: Detailed, factual response about data practices
7. Update broke functionality: Acknowledge regression, provide rollback or fix timeline
8. Competitor comparison (negative): Focus on own strengths and improvement plans
9. Value for money complaint: Highlight ROI and offer to help maximize value
10. Accessibility or inclusion failure: Take seriously, commit to specific improvements with timeline

**Words and Phrases to NEVER Use in Negative Review Responses:**
- "We're sorry you feel that way" (dismissive)
- "That shouldn't be happening" (implies user error)
- "Works fine for most users" (invalidating)
- "Have you tried..." as the first response (condescending)
- "Per our policy" (bureaucratic)
- "Unfortunately" as a sentence opener (deflecting)

### Step 5 — Special Scenario Responses
Write responses for edge cases:

- Spam or fake reviews: Report protocol and neutral public response
- Reviews in wrong language: Respond in the reviewer's language if possible, with template
- Feature requests disguised as complaints: Redirect enthusiasm
- Competitor employees leaving negative reviews: Professional, factual response
- Reviews about issues already fixed in latest update: Guide toward updating
- Emotionally charged or profane reviews: Compassionate, boundary-respecting response
- Reviews that mention legal action: Template that flags for legal team review, neutral public acknowledgment

### Step 6 — Response Workflow & Metrics
Design the review response process:
- Priority triage: Respond to 1-2 star reviews within [4 hours], 3 star within [24 hours], 4-5 star within [48 hours]
- Escalation triggers: Keywords that should alert the team immediately (data loss, security breach, legal, discrimination)
- Follow-up protocol: Re-check responded reviews after [14 days] for rating updates
- Monthly metrics to track: Response rate, average response time, rating change after response, conversion rate (negative to positive update)