Back to all posts
App Maintenance6 min read·October 25, 2026

How to Respond to Negative Google Play Reviews

TB
ThynkBlox Apps Team
App Engineering

To respond to negative Google Play reviews, acknowledge the specific problem and give the reviewer one concrete next step. Keep account details and other private information out of your public reply, and move individual investigations to your support channel. If you later verify a fix, explain what changed and how to try it without asking for a higher rating or promising that ratings will improve.

What should a useful review reply include?

Treat the reply as a small support interaction. The reviewer needs to know that you understood the problem and what they can do next.

Use this structure:

  • Acknowledge the issue: name the action that failed or the difficulty described.
  • State what you know: distinguish a confirmed defect from a report you still need to investigate.
  • Give one next step: suggest a verified workaround, explain how to get help or request a small amount of relevant technical context.

An apology can help, but it should connect to the problem. A generic apology followed by a request to contact support leaves the reviewer doing all the work.

Keep the response short enough that the next step is easy to find. You do not need to explain the history of the app or defend the effort behind it.

How do you acknowledge a problem without guessing its cause?

Describe what the reviewer reported without turning it into a diagnosis.

If someone says the app closes while saving, acknowledge that interrupted save. Do not blame their phone, connection or settings unless you have evidence.

Illustrative reply for an unconfirmed bug:

*Sorry the app closed while you were saving your changes. We need a little more information to investigate. Please contact support through the app and include your app version and the steps immediately before it closed. Keep account details out of this review.*

Use that wording only if support is available through the app. Otherwise, name the actual support route.

Avoid saying that you are investigating unless someone is responsible for doing it. If you have not reproduced the issue, say so plainly without implying that the reviewer is mistaken.

When should you move the conversation to support?

Move the investigation to support when resolving it requires looking at an account, transaction, private document or other information that should stay out of a public review.

Explain why the handoff is necessary. Then identify a specific route, such as the Help section in the app or the support address listed with it.

Reported issueUseful public responsePrivate follow-up
Trouble signing inAcknowledge the blocked access and name the support routeInvestigate the account through your established verification process
A purchase is missingAcknowledge the missing access or itemRequest only the transaction information needed
The app closes during an actionAsk for the app version and a short description of the stepsCollect relevant diagnostics if needed
A screenshot contains personal informationAsk the reviewer to avoid sharing it publiclyExplain how to send a redacted image through support

Never ask for passwords, one-time codes, payment card details or identity documents in a review.

A private channel is not a reason to collect everything. Ask only for what the investigation needs, and explain how to remove unrelated personal information from screenshots or attachments. Our guide on handling mobile app support requests covers what happens after the handoff.

What makes a bug report reproducible?

Ask for the smallest set of details that lets you repeat the action:

  • What the person was trying to do.
  • The steps leading up to the problem.
  • What they expected and what happened instead.
  • The app version, phone model and Android version.
  • Whether the issue happens every time or only under certain conditions.

Request these details through support when the steps involve personal information. Do not require the reviewer to publish a recording of their account.

For example, a report that saving fails after editing an existing item gives you a clearer test case than a general report that the app is broken.

Once reproduced, check nearby cases too: creating an item, editing it again and retrying after an interrupted connection. Our guide to testing an Android app before release can help you turn the report into a repeatable check.

Do not suggest clearing app data or reinstalling as a routine first response. First establish whether the action could remove information the person needs.

How should you answer feature requests?

Acknowledge the job the person wants to complete, rather than promising the feature itself.

Illustrative reply to a feature request:

*Thanks for explaining that you need to find older entries more easily. We have recorded your request for search. We cannot confirm a release date. If you contact support, it would help to know how you currently look for those entries.*

Use this only after recording the request. If a suitable feature already exists, explain where to find it in a short sequence.

Keep requests separate from commitments. One detailed review can reveal a useful need, but it does not establish how that need compares with other work. Consider it alongside support reports and your app's purpose. The guide to scoping an app MVP offers a framework for deciding what belongs in the product.

How should you handle abusive or irrelevant content?

Separate criticism from abuse. A blunt review about a broken feature still deserves a useful response.

If a review includes insults alongside a clear problem, address the problem without repeating the insult. Keep the reply factual and avoid arguing about the reviewer's motives.

If the content appears to breach Google Play's current review rules, consult those rules before deciding whether to report it. Do not describe a review as a policy violation simply because it is negative.

Avoid repeating personal information, threats or offensive language in your response. If there is no actionable product issue, a public debate is unlikely to help. Handle any necessary escalation separately and keep the public response brief.

How do you follow up after a fix?

Follow up after verifying the relevant fix in a release users can access.

Explain which reported behaviour changed and how to try the updated version. If availability is limited, make that clear.

Illustrative reply after a verified fix:

*The latest update fixes the issue we reproduced where saving an edited item caused the app to close. Please update and try saving again. If the problem continues, contact support through Help with your app version and the steps you followed.*

Match the claim to your evidence. Fixing one reproduced cause does not justify saying that every crash is resolved.

Do not make help conditional on changing a review. Avoid requests to replace a low rating with a higher one, and do not promise that replying will improve your rating.

For the ongoing work behind these updates, see what app maintenance involves after launch.

What common mistakes should you avoid?

Sending the same reply to every review. Reuse a structure, but name the actual issue and choose a relevant next step.

Moving everyone to support without explanation. Say what needs investigation and why a private conversation is necessary.

Promising a fix date before it is confirmed. Offer a date only when you have a sound basis for it. Otherwise, state the current position.

Suggesting an untested workaround. Check that it addresses the issue and does not put saved information at risk.

Defending the app instead of helping. Explanations about effort, cost or other satisfied users do not resolve the reported problem.

Before posting, check that the reply acknowledges the issue, states only verified information, protects privacy and leaves the reviewer with a clear next action.

Frequently asked questions

Should you reply to every negative review?

Prioritise reports of blocked tasks, repeated defects and situations where you can offer useful help. Avoid replying merely to add a generic acknowledgement with no next step.

What if the review gives no useful detail?

Acknowledge the difficulty and ask one focused question, such as which action failed. Offer a private support route if the answer could contain personal information.

What if you cannot reproduce the problem?

Say that you have not reproduced it yet. Request the missing technical context through support and keep the report available for comparison with similar cases.

Should you ask the reviewer to change their rating?

Keep the follow-up focused on resolving the problem. Explain the fix, invite them to try it and leave any decision about their review to them.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.