How to reply to Google Play reviews (with examples)
Reviews on Google Play, sometimes called Play Store comments, shape your rating, your ranking and the decision of every new visitor to your listing. This guide shows how to reply in Play Console, gives you examples for the situations developers see most, and explains the 350-character limit and the developer API.
By the ReviewReplier team · Updated
How to reply to a review in Play Console
- Sign in to Google Play Console with an account that has the “Reply to reviews” permission.
- Open your app and go to Ratings and reviews, then Reviews.
- Open a review, write your reply and publish it. It appears under the review on your Play Store listing.
The reviewer can read your reply and change their review afterwards, which is the real reason to reply well: a fixed problem can turn into a better rating.
What a good Play Store reply contains
With only 350 characters, every sentence has to earn its place. A reply that works usually has four parts:
- The name, if there is one. It shows a person read the review.
- One specific detail. The feature they praised or the crash they hit, in your own words.
- A next step. For a problem, a support email and what to include: phone model, Android version, app version.
- A short sign-off from a real person or the team.
Google Play review reply examples
Swap in the reviewer’s name and one real detail, and fill the bracketed parts before you post. Each example fits within the limit once you do.
Praise for a feature
5★Use when: The reviewer names something they like.
Thanks for the kind words, [Name]! We're glad [the feature they mentioned] works well for you. We're always improving [App], so tell us what you'd like to see next. — [Your name], [App] team
Happy, with one wish
4★Use when: A good review that also mentions something missing.
Thank you, [Name]! Glad you enjoy [feature]. We hear you about [what they missed] and have passed it to the team. Thanks for helping us make [App] better. — [Your name]
Crashes or freezes
1–2★Use when: The app crashes, freezes or will not open.
Sorry about the crashes, [Name]. That's not the experience we want for you. Could you email [support email] with your phone model and Android version? That helps us look into it. — [Your name], [App] team
Cannot log in
1–2★Use when: Sign-in, OTP or account problems.
[Name], we're sorry you can't get in. Please email [support email] from the address you signed up with and tell us what happens when you try. We'll help you sort out your account. — [Your name], [App] team
Billing or subscription charge
1–3★Use when: A complaint about a payment or renewal.
[Name], we're sorry about the trouble with your payment. Billing questions are easiest to sort out by email. Please write to [support email] with your Google Play order number and we'll take a look. — [Your name], [App] team
Too many ads
2–3★Use when: The reviewer is annoyed by advertising.
Thanks for the honest feedback, [Name]. We know ads can get in the way, and we take it seriously. [App] stays free thanks to them, and your note goes straight to the team. — [Your name]
Feature request
3★Use when: The reviewer likes the app but wants something it does not do.
Thank you, [Name]. [Feature] is a popular request and we've added your vote to the list. We can't promise when, but we read every suggestion. Thanks for using [App]! — [Your name]
Rating only, no comment
1–2★Use when: A low rating with no text to respond to.
Hi [Name], we're sorry [App] let you down. If you tell us what went wrong at [support email], we'll do our best to put it right. — [Your name], [App] team
The 350-character limit
Google Play rejects a developer reply longer than 350 characters, spaces and punctuation included. A few habits keep you inside it:
- Skip the long apology. “Sorry about the crashes” is enough.
- Put the support address in the reply and keep the rest for the email thread.
- Use one sentence per idea, and sign off with a name or the team, not a slogan.
- Count after you fill in the placeholders. A long app name can push a reply over.
What Google Play expects from your replies
- Do not ask for a better rating or offer anything in return for one. Incentivised ratings go against Google Play’s policies.
- Do not promise fixes or dates you cannot keep. “We’ve passed it to the team” is honest; “fixed in the next update” becomes a new complaint if it slips.
- Keep personal details out of public replies. Move order numbers and email addresses of customers to private email.
- Stay calm with unfair reviews. One polite, neutral reply is read by everyone who sees the review; arguing is read by more.
Replying through the Google Play Developer API
Developers who want to reply from their own tools use the Google Play Developer API. Replies are sent to the reviews.reply method with a replyText of up to 350 characters. A few things to know from Google’s documentation:
- The list of reviews only includes those created or edited in the last week.
- Requests are limited per app, for example 200 reads per hour and 2,000 replies per day.
- The Google account or service account needs the “Reply to reviews” permission in Play Console.
- A review carries the app version and device, which is what you need to reproduce a bug.
Read the full reference in Google’s guide to replying to reviews.
Reply to Google Play reviews automatically
ReviewReplier connects to your Play Console with Google sign-in and uses that API for you, so replying stops being a daily chore:
- Connect Google Play and pick your apps. Choose which of your apps to track; each one is imported with its reviews, and new ones arrive every few minutes.
- Describe your app once. Add what it does, your support email and anything the AI must not say. It only uses the facts you give it and never promises fixes, dates or refunds.
- Get a draft for every review. Drafts are written in the reviewer’s language to fit the 350-character limit, and use the app version and device from the review.
- Choose what goes out by itself. Reviews at or above the star rating you set are published after a human-like delay. Reviews of two stars or less always wait for your approval.
Mistakes developers make in replies
- Pasting the same reply everywhere. Reviewers and visitors notice. Mention the feature or the problem each time.
- Debugging in public. Ask for the details by email, not in a comment that everyone reads.
- Ignoring rating-only reviews. A short, friendly line costs nothing and shows you pay attention.
- Replying weeks later. The first days after a bad update are when a quick answer is most likely to win the rating back.
- Writing more than 350 characters. The reply is rejected, so write for the limit from the start.
Frequently asked questions
How long can a reply to a Google Play review be?
A developer reply can be up to 350 characters of plain text. That is about two or three short sentences, so a reply has to be specific and brief.
Who can reply to reviews on Google Play?
Anyone whose Google account has the “Reply to reviews” permission for the app in Play Console. The account owner can grant it under Users and permissions.
Does replying change the star rating?
No. A reply does not change the rating. The reviewer can read it and update their review if the problem was solved. Never ask for a better rating in return for anything.
Can I reply to Play Store reviews automatically?
Yes, through the Google Play Developer API. ReviewReplier uses it to write a draft for every new review, publishes the safe ones after a delay you set, and holds reviews of two stars or less for your approval.
Can I reply to old reviews through the API?
The API lists reviews that were created or edited in the last week. Older reviews are answered in Play Console, which also lets you export them.
Can the reply be in the reviewer’s language?
Yes. ReviewReplier detects the language of each review and answers in it, so a Hindi, Spanish or Portuguese review gets a reply in that language within the 350-character limit.
Answer every review without the busywork
ReviewReplier drafts on-brand replies the moment a review lands, publishes the safe ones on your schedule and holds the tricky ones for you. Try it in the sandbox first — nothing is sent to Google.
More guides
- 16 Google Review Response Templates16 copy-and-paste replies for every star rating, from happy regulars to fake reviews.
- How to Respond to Negative Google ReviewsA five-step framework, a before-and-after example and how to handle unfair or fake reviews.
- How to Reply to Restaurant Reviews on GoogleReply examples for praise, long waits, cold food and allergy worries — and a workflow for busy kitchens.