How to reply to app reviews: templates and tone
Both stores let developers reply publicly to reviews. Replies are read by future visitors, not only by the reviewer, so every reply is a small piece of marketing for your support quality. Done well, replies also lead some people to update a low rating after you fix their problem, which store tools often make easy by notifying the reviewer.
Principles
- Reply to the person, in public, for the audience. Assume a stranger will read it later.
- Be fast on bad reviews, regular on good ones. A short reply within a day or two to critical reviews shows you care.
- Be specific. A vague "Sorry for the inconvenience" reads like automation.
- Never argue. Even if the reviewer is wrong, correct facts politely.
- Move private details out. Give a way to contact you, and never ask for passwords or sensitive data in public.
- Do not ask for a changed rating directly. You may say what you fixed and invite the person to try again; do not offer anything in return for a rating, as store policies prohibit incentives.
Tone
Friendly, short, human, in the language of the review where you can. Use the reviewer's name only if it is shown. No emojis spam, no marketing slogans, no all-caps.
Templates
Adapt these; do not paste them unchanged to every review.
A bug report
Thanks for the detail. You are right: the export fails when the file name contains a slash. We fixed it in version 2.3.1, which is rolling out now. If it still happens, please write to support@example.com with your device model and we will look at it.
A missing feature
Thank you. Offline mode is on our list, and your note about long trips helps us prioritize it. We cannot promise a date, but we will mention it in the release notes when it ships.
A confused user (the app does it already)
Good news: this is possible. Open Settings, then Sync, and switch on "Use mobile data". If you cannot find it, write to support@example.com and we will guide you.
A rant with no detail
Sorry the app did not work for you. If you tell us what went wrong, such as the screen and your phone model, we will try to fix it. You can reach us at support@example.com.
Praise
Thank you for the kind words. The weekly summary is one of our favourite parts too. We are working on more charts for it.
An unfair or abusive review
Keep it short, factual and calm. If the review breaks store rules (hate speech, spam, a competitor attack), report it through the console rather than replying, and reply briefly only if it helps the audience.
What never to write
- "You are using it wrong."
- A copy-paste answer on every review.
- Anything that offers a reward, discount or compensation in exchange for a better rating.
- Personal data of users, or confirmation that someone is a customer, beyond what they posted.
- Legal statements or admissions of fault you have not checked.
Process for small teams
- Once a day (or a few times a week), open the reviews list sorted by newest.
- Tag each: bug, request, praise, confusion, abuse.
- Reply to bugs and confusion first.
- Put real bugs into your issue list with a link to the review.
- After a release, revisit the bug reviews and add a short follow-up where useful.
This is also the first step toward turning reviews into a roadmap.
Checklist
- Reply in public, specific, in a friendly tone.
- Critical reviews first, within a day or two.
- Offer a private contact path.
- Never offer anything for a rating.
- Report abusive reviews through the console.
- Log bugs and requests, and follow up after the fix.
Need testers for your app? Open a test group on AppReviewX. Start free