Rank Sonar
All posts
·4 min·Mark Vivanco

Responding to negative reviews: a 3-template playbook

Most negative reviews fall into three buckets. Each gets a different response pattern. There's also a fourth bucket you should leave alone.

Bucket 1: Real bug, fixable

"App crashes every time I try to add a photo. Useless."

The user has identified a specific failure. The fix is in your hands.

Template:

Thanks for the report. We've reproduced the photo-add crash on iOS 17.4 with the new selector. Fix is in version 4.2.1 (submitted to review today, live within 48 hours). Apologies for the trouble — we'll come back here once the update is approved.

Then actually come back when the update is live, and update your reply. The visible recency of your response is what shifts the next visitor's perception.

Bucket 2: Real feature gap

"Won't let me share to Slack. Why is everything Twitter only?"

The user wants something you don't have. Acknowledge, give honest timeline, don't oversell.

Template:

Slack share is the most-requested integration we don't have today. It's on the roadmap for Q3. We'll reach out via email if you'd like to be among the first beta testers when it ships — drop us a line at hello@yourapp.com.

The "drop us a line" line moves the conversation off-platform — wins you a real customer relationship and a public signal that you're approachable.

Bucket 3: Misunderstanding

"I paid for premium and it didn't unlock anything."

Often a payment-restoration issue, an Apple ID issue, or the user clicking the wrong button.

Template:

Sorry for the confusion. Premium unlocks should appear immediately after purchase via Settings → Restore Purchases. If that doesn't work, please email hello@yourapp.com with the receipt — we'll look it up and get this sorted within a few hours.

This template provides a clear next action AND moves the messy work off the public review thread.

Bucket 4: Don't respond

Two types of reviews where engagement makes things worse:

  1. Pure venting — "This app sucks." No specifics, no actionable feedback. Responding looks defensive.
  2. Trolling — Reviews that attack the team personally, mention competitors by name aggressively, or contain offensive content. Apple lets you flag these for removal in App Store Connect, then move on.

The math on response

Responding to negative reviews lifts overall conversion rate by ~5-10%. Visitors read the responses. Even a single thoughtful reply on a review-feed page shifts the impression from "developer doesn't care" to "team is engaged."

Targets:

  • 1-star reviews: respond within 48 hours
  • 2-star reviews: respond within 7 days
  • 3-star reviews: respond when there's specific feedback worth addressing
  • 4-star reviews: occasional thank-yous, especially for detailed praise (signals attention)
  • 5-star reviews: don't respond systemically; you'll look performative

Rank Sonar surfaces every new review with sentiment classification and topic tags so you can triage in minutes instead of hours. [Try it free for 14 days](/pricing).