The 6 app reviews you should never auto-reply to
Six kinds of app review should reach a person before anyone replies: refund and billing requests, possible account takeovers, personal data and deletion requests, legal threats, harassment, and reviews from people with an audience. Each one carries money, safety or legal risk, and a canned or AI-written answer to it is public and hard to take back.
Everything else (praise, known bugs, feature requests, common questions) is a reasonable candidate for a template or a drafted reply.
| Review | Sounds like | Who should handle it |
|---|---|---|
| Refund or billing request | “Paid for the yearly plan and the app still says Free” | Support (App Store billing goes to Apple Support) |
| Hacked or compromised account | “Someone logged into my account and deleted my runs” | Whoever owns account security |
| Personal data or deletion request | “How do I delete my account and all my data?” | Whoever owns privacy |
| Legal threat or formal complaint | “I am reporting this to consumer protection” | Whoever owns complaints or legal matters |
| Harassment or abuse | An abusive review, or a report of abuse inside the app | Report the review; send in-app abuse to moderation |
| Someone with an audience | “I review fitness apps on my channel” | Whoever handles communications |
Why is a wrong reply hard to undo?
Review replies are public, and they reach the reviewer directly. On the App Store, “when you respond, the reviewer is notified and has the option to update their review” (Apple). On Google Play, the reviewer gets a push notification and an email when you reply.
You can edit a reply later on both stores (Apple, Google). By then the reviewer has been notified, and anyone reading your listing in the meantime has seen the first version. Google Play allows one public reply per review, so the fix replaces the mistake in the same spot rather than adding a correction underneath.
Why don’t star-rating rules catch these?
Auto-reply tools build their rules from what they can filter on. Appbot, for example, lets you define auto-reply rules by star rating, language, topic or custom topic. Rules like these are useful for routine reviews, but the six cases below are defined by what the review says, and they turn up at any star rating.
A 5-star review that says “great app, but I lost my purchase after the update” is a billing problem. A 3-star review that says “someone logged into my account” is a security incident. A rule keyed to stars treats the first as praise and the second as mild disappointment.
1. Refund and billing requests
Reviews like “Paid for the yearly plan and the app still says Free” or “My kid upgraded without asking, I want my money back” are money problems, and who can fix them depends on the store.
- On the App Store, Apple handles refunds for App Store purchases. Customers request them through Report a Problem, and Apple’s guidance for developers is direct: “If a reviewer reports a downloading error or billing issue, direct them to Apple Support” (Apple).
- On Google Play, developers can refund orders themselves from Order management in Play Console, and “you must issue refunds in accordance with your policy” (Google). Refunds there are final: “After you issue a refund, it can’t be reversed.”
So have a person check the purchase before anyone replies. The public reply acknowledges the problem, points to the right channel (Apple Support, or your own support contact on Google Play) and promises nothing. A reply that says “we’ll refund you” in public is a commitment made before anyone has looked at the order.
2. Hacked or compromised accounts
“Someone logged into my account and deleted my runs” may be a real account takeover, a shared password, or a sync bug. You can’t tell from the review, and a public reply is the wrong place to find out.
Both the App Review Guidelines and Apple’s review guidance say not to include personal information in a response. That rules out a reply asking for the reviewer’s email, username or account details in public.
Route it to whoever handles account security. The public reply acknowledges the report and gives a private support channel, and the investigation happens there.
3. Personal data and deletion requests
“How do I delete my account and all my data?” looks like a routine question, so it’s easy to answer with a template. It’s also a request with formal rules attached.
- Apple requires that an app which supports account creation “must also offer account deletion within the app” (App Review Guidelines 5.1.1(v)).
- For apps that let people create accounts, Google Play requires developers to provide “an in-app path to delete their app accounts and associated data” and “a web link resource where users can request app account deletion and associated data deletion” (Google).
- In the EU, people have the right to ask for their personal data to be erased, and the guidance for organisations is to “respond without undue delay and at the latest within one month after receipt of the request” (European Data Protection Board).
Let the person who owns privacy decide whether the review is a formal request, and check that the deletion path is real and current. The public reply then points to that path in plain words. A template that links to an outdated settings screen is worse than no reply.
4. Legal threats and formal complaints
“You charged me twice. I am reporting this to consumer protection.” Once a review mentions a regulator, a lawyer or a formal complaint, the reply is part of a possible dispute.
Google’s policy for developer replies asks that they address the user’s comment “in a clear, valuable, and truthful manner” (Google). An automatic reply can’t know what’s true about this customer’s charges, so it can’t meet that bar.
Hand it to whoever owns complaints or legal matters in your team before anything is posted. If a public reply goes out at all, it should be short: acknowledge the problem, give a direct contact, and leave out explanations, admissions and promises.
5. Harassment and abuse
Abuse shows up in reviews in two ways, and they need different handling.
When the review itself is abusive, both stores want it reported rather than answered. Apple says to “use the Report a Concern option under the review in App Store Connect instead of replying to the review”, and the reviewer is not told you reported it (Apple). Google Play has a Report option on each review in Play Console, and its policy for developer replies says not to engage with inappropriate comments through replies (Google).
Sometimes the review reports abuse inside your app. “Someone in the club chat keeps insulting me and nobody does anything” is a trust and safety report that happens to arrive as a review. A thank-you for the feedback tells everyone reading that reports go nowhere.
Report the first kind. Send the second to whoever moderates your community, and reply only once there is something true to say about what happened.
6. Reviews from people with an audience
“I review fitness apps on my channel, and this one is getting a bad score.” When journalists, creators or well-known users review your app, they can quote the review and your reply to an audience far larger than your listing’s.
No store rule covers this, so it comes down to judgment. A templated reply to a creator is easy to screenshot, and a reply that reads as dismissive can become the story.
Flag these for whoever handles communications, and let them decide whether to reply publicly, reach out directly, or leave it.
What should the public reply say?
When one of these six does get a public reply, the same pattern works for all of them:
- Acknowledge the specific problem in one sentence, in the reviewer’s own terms.
- Give the right private channel: Apple Support for App Store billing, your support contact for everything else.
- Leave out personal information, which Apple’s guidelines rule out, and leave out promises, refunds, admissions and dates.
- Come back once the issue is resolved. The reviewer can update their review after a reply, and a reply that reports the fix gives them a reason to.
For example: “Sorry about the missing upgrade. Billing for App Store purchases goes through Apple, so please contact Apple Support, and write to us at support@yourapp.com so we can check your account too.”
How to set this up if you use auto-replies
Automation can keep handling routine reviews, as long as the rules look at what each review says.
Send any review that mentions money, accounts, data, legal action, abuse or an audience to a person, whatever its star rating. For reviews close to the line, let the tool draft and a person approve. When a rule can’t tell whether a review is routine, treat it as one of the six.
This is the split we’re building Heedo around: routine reviews get a drafted reply in your voice, and reviews like these six go to a “needs you” list with the reason attached, so a person sees them before anything is sent.