How to Respond to App Store Reviews: Examples for Bugs Crashes Pricing and Feature Requests

To respond to App Store reviews, reply through App Store Connect or Google Play Console (or a connected tool) with a short, specific message that names the exact issue, states the app version where it's fixed if one exists, and avoids asking directly for a rating change — the goal is a public record that reassures the next reader, not a negotiation with the one who wrote it. Where the reply actually happens Apple developers reply to App Store reviews through App Store Connect, either in the dashboard or via the App Store Connect API for teams that want to draft and publish replies programmatically. Google Play developers do the same through Play Console's Reply to Reviews tool. In both cases, the reply posts publicly underneath the original review, and it's visible to anyone browsing the listing — not just the person who wrote it. Tailwind can bring reviews from both stores into one inbox so you're not switching between two dashboards to see what needs an answer , and draft a reply in your brand's voice that a team member approves before it goes out. For mobile apps and SaaS teams specifically, the goal is to reply to App Store reviews in your voice consistently, not just quickly — the drafting happens faster with a tool, but the judgment about what to say, version numbers, tone, how much to admit, is still worth getting right regardless of what you use to send it. What makes a reply actually land A few things separate a reply that works from one that reads as noise: Name the specific issue, not a category. "Sorry for the inconvenience" could apply to anything. "This was a sync bug affecting accounts created after the v4.2 update" tells a skimming reader you know exactly what happened. Cite the version where it's fixed, if one exists. A reviewer stuck on an old build and a new visitor reading the thread both get something useful from "fixed in v4.5, released in March." Keep it short. Two or three sentences outperforms a paragraph. Nobody reading a store listing wants to scroll through a developer's defense. Don't ask for a rating change directly. Both platforms restrict replies that look like they're pressuring or incentivizing a rating edit. "We've fixed this in the latest update" is fine. "Please update your rating now that it's fixed" pushes into territory both stores' policies are written to discourage. Templates by situation These aren't meant to be copied word for word — a review response generator can produce a first draft faster than starting from a blank box, but every reply should still get edited to match what actually happened with that specific user's report. A crash or bug after an update "Thanks for flagging this — this matches a crash we've traced to the v6.1 release on devices running iOS 17.1. A fix is in v6.2, which should already be rolling out to you. If it's still crashing after updating, reply here with your device model and we'll dig in further." The structure to copy, not the wording: acknowledge, name the version and condition, point to the fix, leave a door open if the fix didn't land for them. A subscription or billing complaint "We hear you — unexpected charges are the worst kind of surprise. If this was a renewal you didn't expect, refunds for app purchases go through Apple directly since all billing runs through the App Store, but reach out to us at [support email] and we'll help you sort out the subscription settings so this doesn't happen again." Billing disputes on iOS and Android route through the platform's own refund process, not through the developer directly, so the reply's job is to point the person toward the right place and fix whatever setting or communication gap caused the confusion — not to promise a refund you can't issue from your own dashboard. A device- or OS-specific bug "Thanks for the detailed report. This looks specific to the Pixel 6a on Android 14 — we haven't been able to reproduce it on other devices yet, but we're actively looking into it. If you're open to it, email us at [support email] with a screen recording and we'll prioritize this." When a complaint is clearly tied to one device or OS version rather than a general quality problem, say so. It tells other readers with different devices that this isn't necessarily their experience too, and it moves the actual debugging to a channel where you can get more detail than a star rating allows. A feature request mistaken for a complaint Sometimes a one-star review isn't really about a bug — it's a user who wanted a feature the app doesn't have yet and rated it like a failure instead of a gap. "Thanks for the suggestion — dark mode isn't in the app yet, but it's a request we've heard before and it's on our list. We'll update this if it ships." This kind of reply does two things: it doesn't argue that the missing feature isn't a real complaint, and it signals to anyone else reading that the team is listening, even without a fix date. A one-star from a misunderstanding, like the refund policy "Sorry this wasn't clear up front — subscriptions through the App Store are billed and refunded directly by Apple rather than by us, so the fastest way to get a refund is through your Apple ID purchase history. Happy to help if you run into any trouble finding that." Reviews like this are common and easy to get defensive about, since the complaint is really about store policy rather than your app. A calm, factual pointer to the right process reads better to other shoppers than a reply that sounds like it's arguing the user is wrong to be upset. Does the reviewer get notified, and can they change their rating? On both the App Store and Google Play, a reviewer gets a notification when a developer replies to their review, and they're able to go back and edit their rating or review text afterward. That's part of why a specific, version-dated reply is worth the extra sentence it takes to write — the person who left a one-star review for a bug that's now fixed has a direct, visible invitation to revisit it, without you ever having to ask them outright to change the number. Should I reply to every single App Store review, including the five-star ones? Replying to negative and mixed reviews matters most, since that's where a reply can actually change how the next reader interprets the complaint. Replying to glowing five-star reviews is optional and lower-priority — a short thank-you doesn't hurt, but it's reasonable to spend your limited reply time on the reviews that are actually shaping how new visitors read your rating. What if a review is fake, abusive, or violates store policy? Both Apple and Google have separate reporting flows for reviews that violate their content policies — spam, harassment, reviews from someone who clearly never used the app. That's a different track from a normal reply: report it through the platform's own flagging tool rather than trying to argue it down in a public reply, which rarely works and can make the thread look worse to other readers. Can I ask the reviewer to update their rating after I fix the bug? You can invite it gently — "if you get a chance to try the latest version, we'd love to hear if this is resolved" is fine — but both platforms restrict anything that reads as pressure or a condition tied to changing a rating. Keep it an open invitation, not a request tied to the reply itself, and let the version-and-fix information in your reply do most of the persuading. For the other half of this — getting more reviews in the first place with native prompts that don't rely on gating — see our guide on how to get more app reviews, and for the bigger picture across both stores plus your B2B review sites, our App Store review management guide covers the full workflow. Every review from the App Store, Google Play, G2 and Capterra in one inbox → Try Tailwind free. Tailwind runs $5 a month per tool, or $50 a month for the Full plan covering every tool, with the first month free and no card required to start.