Lorixen.
EN

Replying to App Store and Google Play reviews: a checklist

Short answer: Reply from App Store Connect and the Google Play Console (or the Play reply API), starting with low-star reviews and anything describing a bug in the current version. Keep replies short, specific and personal, never include the user's private details, and move anything account- or payment-related to a support channel. When a later update fixes the problem, reply again: on both stores the reviewer is notified and can revise their review.

App reviews are public customer service. The person who left one star sees your reply, but so does everyone deciding whether to download. A small business app doesn't need a team for this, just a routine and a few well-written patterns.

Know how replies work on each store

Apple App Store

Apple's ratings and reviews page sets out the basics (as of November 2026):

  • App Store Connect users with an Admin or Customer Support role can view, sort and respond to reviews.
  • You can respond to any review, however old.
  • The reviewer is notified when you respond and can update their review.
  • You can edit your response at any time; only the latest version shows.
  • Email alerts can tell you when someone edits a review you've already answered.
  • Content that breaks Apple's terms should be reported with "Report a Concern", not answered; the reviewer isn't notified of a report.

Google Play

Google documents a Reply to Reviews API alongside replying in the Play Console. Useful details from that page:

  • Replies appear publicly on the store page, so never include sensitive information about the user.
  • A reply sent through the API can be at most 350 characters, in plain text.
  • The user is notified when you first reply, and again when you update your reply after they've updated their review. Editing your reply on its own doesn't notify them.
  • The API covers production versions only and reviews that include written comments, and lists only reviews created or modified in the last week; older reviews can be downloaded from the Play Console.

Even if you reply in the Console, the 350-character API limit is a good discipline for length.

The routine: a checklist

Daily or a few times a week

  • [ ] Open new reviews, sorted by lowest rating first.
  • [ ] Reply to every one- and two-star review that has text.
  • [ ] Reply to any review mentioning a crash, login problem or payment issue.
  • [ ] Tag each review in a simple sheet or support tool: bug, feature request, praise, confusion, billing.

After each release

  • [ ] Check reviews more often for the first few days. Apple suggests replying promptly to new and updated reviews after a major release, when people are most engaged.
  • [ ] Find older reviews that the release fixes and reply to tell those users.
  • [ ] Mention the fix in the release notes too, as Apple recommends.

Monthly

  • [ ] Count tags. Five reviews asking for the same thing is product feedback, not noise.
  • [ ] Review your reply patterns; rewrite any that sound robotic.

Always

  • [ ] Personalize. Apple recommends personalized responses rather than generic ones for similar reviews.
  • [ ] No marketing language, no spam, no personal information.
  • [ ] Don't argue in public. One calm reply, then move the conversation to support.

What to say: patterns with examples

The examples below are hypothetical replies for an imaginary appointment-booking app called "BookEasy". Adjust the tone to your brand.

Bug report

What to include: thanks, acknowledgement of the specific problem, what you're doing, how to get help now.

Example reply: "Thanks for flagging this, Sam. Some users on the latest version can't see next week's slots after updating, and we're fixing it now. In the meantime, pulling down to refresh on the calendar screen should load them. If it doesn't, email help@bookeasy.example and we'll sort it directly."

Bug fixed in a later update

Example reply: "Good news: version 3.4, out today, fixes the calendar loading problem you described. Thanks for your patience, and for telling us about it. We'd love to hear if it works for you now."

Notice it doesn't demand a better rating. It tells the person the problem is solved; the store's notification gives them the chance to update their review.

Feature request

Example reply: "Thanks for the idea. Being able to book for two people at once is something we've heard from a few customers, and it's on our list. We can't promise a date yet, but we'll mention it in the release notes when it arrives."

Don't promise features you haven't committed to.

Angry or unfair review

Example reply: "We're sorry your appointment was canceled without notice; that's frustrating. The cancellation came from the salon's side, and we'd like to help you rebook. Please email help@bookeasy.example with your booking reference so we can look into it."

Acknowledge the feeling, correct facts gently if needed, and offer a route. Don't name staff or blame the customer.

Confusion about how the app works

Example reply: "Thanks for trying the app. To change an appointment, tap the booking on your Home screen, then 'Reschedule'. We've heard this isn't obvious enough and we're making the button clearer in the next update."

This is also a design signal; log it.

Positive review

Example reply: "Thanks so much, Priya. Glad booking your monthly appointment is quicker now."

Short is fine. You don't need to reply to every five-star review, but a few thoughtful thanks show the store page is looked after.

When to send people elsewhere

  • App Store billing or download problems: Apple's page says to direct reviewers reporting downloading errors or billing issues to Apple Support.
  • Account-specific issues: move to email, chat or your help center. Never ask for passwords, card numbers or booking details in a public reply.
  • Abusive or off-topic content: report it through the store's own tools rather than replying.

Routing reviews into support

If you get more than a handful of reviews a week, connect reviews to your support system. Google's API is built for this: it lets developers view and reply to reviews from their own customer-support tools, with authorization through an account that has the "Reply to reviews" permission. Some support platforms offer this connection; check their documentation for what each store supports.

FAQ

Should we reply to every review?

Prioritize. Apple suggests focusing on the lowest ratings and reviews about technical issues in the current version if you can't answer everything.

Can we ask users to change their rating?

Tell them when a problem is fixed and invite them to try again. Avoid offering anything in exchange for a better rating; check each store's guidelines before running any review-related campaign.

How long should a reply be?

Two to four sentences. Google's API caps replies at 350 characters, which is a sensible target on both stores.

Can we edit a reply later?

Yes. Apple shows only your latest response. On Google Play, editing your reply alone doesn't send the user a new notification.

A steady review routine is part of running an app well, and we can help you connect store reviews to your support workflow.

Sources

WhatsAppLet’s talk