To respond to app reviews well, use one formula: thank the user, add the line for that review type (an apology, a referral request or an explanation), say you work hard to improve, and sign off positively. Hand-write replies to detailed 1-2 star complaints, template the middle, and keep unhappy users talking in the store until their rating rises.
Key takeaways
- Every reply follows the same skeleton: thanks, a review-type line, an improvement line, a positive sign-off.
- The more negative the review, the more parts the reply needs: apology, explanation, fix status, request for patience.
- Automate thanks for 4-5 stars with no text, tweak templates for 3-4 stars, hand-write 1-2 star complaints.
- Keep 1-4 star reviewers in the store, not in email; their rating can only change where the review lives.
- Keep templates at most 75% prewritten, so every reply carries a real detail.
Why do review replies matter?
Because a reply can change the rating that sits on your store page. For idealo, a German price-comparison app, Google Play showed that ratings updated after a reply rose 1.6 stars on average; ratings updated without a reply fell 0.14.
Appkitekt's playbook puts it simply: replies turn reviews better, silence turns them worse. Reply to as many reviews as possible, using templates to make that feasible. Replies rank below the in-app prompt in impact, so fix how you ask for ratings first.
What is the review reply formula?
Every reply follows one formula: thank, add the line for that review type, say you work hard to improve, and sign off positively. I call this the Review Reply Formula.
| Reply part | Negative | Positive | Informational |
|---|---|---|---|
| Thanks | Yes | Yes | Yes |
| Apology | Yes | ||
| Referral request | Yes | ||
| Explanation | Yes | ||
| We work hard to improve | Yes | Yes | Yes |
| Positive sign-off | Yes | Yes | Yes |
The workflow behind it:
- Read the review, then choose a response: thank, apologize, explain, stall or ignore.
- Prioritize which reviews get replies.
- Pick the matching template and adjust it to the situation.
- Thank first; add an apology (negative), a referral request (positive) or an explanation (informational).
- Close with the improvement line and a positive sign-off. Reply twice a week.
The formula fixes three common problems: positive reviews left unanswered, negative replies without an apology, and a reply tone that changes with whoever is on duty.
How should a reply change with the star rating?
The more negative the review, the more parts the reply needs. I call this Reply Anatomy by Rating: build each scenario from modular parts and test them one at a time.
| Review type | What the reply adds |
|---|---|
| Negative (1-2 stars) | Repair parts: apology, explanation, fix status, request for patience |
| Neutral (3 stars) | A question: what would earn a higher rating? |
| Positive, not ideal (4 stars) | The same question: what would earn the fifth star? |
| Ideal (5 stars) | A direct contact and an ask to share the app |
Signs you have this wrong: the same template goes to 1-star and 5-star reviews, negative replies are missing an apology or a fix status, and five-star reviewers are never asked to share.
How much of review replying should you automate?
Automate the low-impact replies, template the middle, and hand-write the detailed complaints. I call this the Tiered Response Protocol, and it balances efficiency with empathy.
- Build templates by topic: billing, crashing, feature request.
- Fix on-brand openings and closings, and always add a custom detail in the middle.
- 4-5 stars with no text: send automated, rotating thank-you messages.
- 3-4 stars with a specific topic: use a template plus a small custom tweak.
- 1-2 stars with detailed complaints: write 100% by hand.
The protocol exists because teams swing between two failures. Beautiful manual replies reach only a tiny share of reviews. Then the team switches to full automation, and every review gets the same instant canned reply, including long templated essays that ignore the user's actual issue.
How do you keep unhappy reviewers in the store?
Treat replies as in-store marketing. Keep 1-4 star reviewers talking in the store until their rating rises, and give happy ones a direct contact. I call this the Keep-Them-in-Store Reply.
- Thank first, apologize later, and acknowledge the user's point of view.
- Solve the problem, or stall until a fix ships. Keep 1-4 star reviewers in the store, not in email.
- Hook them to stay: ask questions, suggest uses, mention new content.
- Answer price objections with the app's competitive advantages.
- Ask 5-star reviewers to refer friends. Keep templates at most 75% prewritten.
The warning signs: low-star replies that only say "contact support@", 5-star reviews with no reply, and replies that never mention new features. A help-desk email may solve the problem, but the bad review stays on your page forever. What happens after the first reply, when the fix ships, is its own discipline; I cover it in the review reply lifecycle.
From the field
A European coffee chain started with long, essay-style replies. They were good, but they covered only 20% of reviews. The chain then switched to full automation, which went wrong and sent incorrect replies. It was left with a two-star average on Trustpilot, the review site. Neither extreme worked; the tiers exist to avoid both.
The idealo result above is the other side: replying, and replying in the store, is what gives a rating the chance to move.
What should a reply never do?
- Send the same instant automated reply to every review.
- Defend the product instead of acknowledging the user's point of view.
- Push a low-star reviewer out to email with nothing else said.
- Leave a price complaint without a reason for the price.
Defensive, canned, money-focused and angry replies have their own framework, the Four Horsemen of the APPocalypse, which I cover with app review analysis.
Frequently asked questions
What is the best formula for replying to app reviews?
Thank the user first. Then add the line for that review type: an apology for a negative review, a referral request for a positive one, an explanation for an informational one. Close with a line saying you work hard to improve and a positive sign-off. Keep the formula fixed and adjust the middle to the specific review.
Should I automate app review replies?
Partly. Automate rotating thank-you messages for 4-5 star ratings with no text, use a template plus a custom tweak for 3-4 star reviews with a specific topic, and write every detailed 1-2 star complaint by hand. Full automation sends wrong or cold replies; full manual replies only ever reach a small share of reviews.
Should I send unhappy reviewers to support email?
Usually not. A reply that only says "contact support@" moves the conversation out of the store, where the bad review stays forever. Keep 1-4 star reviewers talking in the store: thank them, acknowledge their point, solve the issue or say when a fix is coming, and give them a reason to stay until their rating rises.
Should I reply to five-star reviews?
Yes, but last. Negative reviews come first because they have more effect. For five-star reviewers, thank them, mention what is new, give them a direct contact and ask them to recommend the app to friends. That turns a happy user into an active one instead of leaving the review unanswered.
Replies are one part of the sentiment work we do in our app store optimization strategy service.
About the author
Binh Dang founded Appkitekt after leading ASO at Flo, Kovalee and Jellyfish, where he was Senior Director of ASO, and starting out as an ASO consultant at Phiture. He wrote The ASO Black Book.
See how Appkitekt runs ASO