How to Reply to Google Play Reviews

A budget app’s login dies on Android 14. The review says “spins forever after the September update, Pixel, Android 14.” You can see that review in Play Console before it is public. Google generally holds new reviews for about 24 hours, and you can reply during that window. The reply you publish is still public once the review is. Write it as if the next person comparing budget apps will read it under the stars, because they will.

Play’s ratings and reviews help says you can write one public reply per review, edit it any time, and that the user gets a push and an email with your text. If this build is only on part of the user base, read Google Play staged rollouts before you assume “almost nobody has it.” The iOS version of a public reply is how to reply to App Store reviews.

One public reply, and they get notified

You need the Reply to reviews permission. On the website, go to the Reviews page under Ratings and reviews. Under the review, the field is labeled Your reply. Type, or start from a suggested reply if Play offers one, then Publish Reply. Suggested replies are only for recent English reviews when you view the console in English, and they are not offered again after you have replied. Edit them before you publish. A suggested sentence that does not mention Android 14 is not done.

The email the user gets includes your app name, the date of their review, their rating and text, your reply, and a link to the contact email on the store listing. That is a lot of surface area for a vague “sorry for the trouble.” The Play Console app can send a reply too: open the app, pick the review, tap Reply, then Send. The Reply to Reviews API exists if you already answer from a help desk. The words do not get a pass because a tool sent them.

Partial rollouts still collect reviews

Google’s staged rollout article says users who receive the staged rollout can leave public reviews. A login fix released to 10% is not a silent test. Those people have the build, they can rate it, and their reviews are the ones you should read before you raise the percentage. The percentage does not increase by itself. You halt, you resume the same set of users, or you move the percent on purpose.

If the review says the spinner started after the September update, check whether that update is the staged bundle. Reply with the version code that contains the fix, not with “we’re looking into it” for a week while the percent sits at 20 and more Android 14 phones pick the same bug up. Halting stops new users from receiving that bundle. It does not uninstall the bundle from people who already have it. Those people can still review, and they should hear which version replaces it.

A reply that could only be this login bug

Same shape as a good App Store reply, with Play’s facts filled in. What failed, what you found, which version code to install, how to retry, and a request to update the review after login works. No argument about whether they typed the password wrong if your own log shows a hang on the token refresh for Android 14.

The reply names Android 14, the token-refresh hang, and version 3.4.1. It asks them to update the review after sign-in works. A star demand is not the message.

Paste something you could not send to a different app: “Sorry sign-in spins after the September update on Android 14. That build hung on token refresh. Version 3.4.1 replaces it. Update, then sign in again on Wi-Fi. If you get into the budget, please update this review so it describes 3.4.1. If it still spins, reply with the phone model and I will look at that device.” One reply. If 3.4.2 is the real fix, edit the text. Do not stack a second public reply. Play gives you one.

Do not argue, and do not wait out the 24 hours

You can reply before the review is public. Use that. A day of “we’re on it” is worse than a day of silence only if the silence becomes a week. If you do not yet know the cause, say the September build is the one you are inspecting on Android 14, and edit the reply when you have the version code. Do not tell them the password was wrong. Do not quote their email address back at them in the public text. The notification already has a contact link.

Suspicious-rating holds are a different state. Play says new ratings do not immediately change the published rating, and if the delay window looks abusive, publication can pause while they investigate. The console shows whether a review is public. Your job during a real login bug is still the binary and the reply, not a theory about a rating attack, unless the console actually says the app is paused.

Listing copy waits if the screenshot must match the build

If the new build changes what the first screenshot must show, Google recommends updating the store listing after the rollout reaches 100%. A reply can mention 3.4.1 while the listing still shows the previous screen, as long as you are not describing a feature the live listing promises and the halted build does not have. Do not refresh the short description to “Android 14 login fixed” for the whole store while 90% of installs are still on the spinning build. The reply is per review. The listing is everyone.

What the reply is for

The public rating on Play leans toward recent ratings, so a fixed login can recover the number people see faster than a lifetime average would imply. That recovery still depends on new ratings and on edited ones, not on your paragraph alone. The paragraph’s job is to tell the truth under the 1-star note while the percent climbs. Search rank is not a number Play or Apple hands you for “replies.” Treat the reply as customer service that happens to be on the store.