Does replying to a review guarantee the user will change it?

No — it makes it possible and likely for the winnable ones. Your reply triggers a notification and a one-tap update option on both Apple and Google, but the user chooses whether to act. Google reported an average 0.7-star lift for developers who respond, and a 4.5M-review study found users about 6× more likely to raise their rating after a reply. A specific, fast, genuinely-fixes-it reply converts a meaningful share; a generic one converts almost none.

Can I ask the user directly to give me 5 stars?

No. Asking for a specific star rating or offering incentives to change a review violates both stores' guidelines and can get your app removed. Apple explicitly prohibits manipulating ratings and incentivizing review changes. Instead, invite them to 'take another look' once the issue is fixed. The store already provides the update button; you just earn the tap.

How quickly should I respond to a negative review?

Within 24 to 48 hours if you can. The reviewer is most emotionally engaged and most likely to reconsider right after posting. Speed also compounds with recency weighting — because both stores lean on recent sentiment, winning the next few weeks of reviews moves your visible score faster than your lifetime average would suggest.

What if the bug was already fixed in an old version they reviewed?

This is your easiest conversion. Reply naming the version that fixed it and your current version, add any refund or data reassurance if relevant, and note that a fresh install is a very different experience now. The next step is simply 'update the app,' which is the lowest-friction ask there is.

Should I reply to reviews written in another language?

Yes, and reply in their language, not yours. Keep the same four-step structure, but have a native speaker or a careful translation check it. A clumsy machine-translated reply in someone's own language often reads worse than no reply at all, while a fluent one signals real care to that whole regional audience.

What do I do about obviously fake or review-bombed 1-stars?

Do both: post one calm, factual public reply for the benefit of readers, and separately report the review to the store — Apple via App Store Connect, Google Play via its report/flag option for policy-violating reviews. Don't argue publicly, and don't expect instant removal; the measured reply protects your readers while the report is reviewed.

All posts

PlaybookJul 8, 2026 · 18 min

How to Turn a 1-Star App Review Into 5 Stars: The Complete Playbook (2026)

You can't edit a review, but your reply gives the user a one-tap update option on both stores. The framework, real examples, and templates that earn the change.

The Argus Team

Reply Argus

Can you actually turn a 1-star review into 5 stars?

Yes, you can, and it happens more often than founders expect. You can't edit or delete a user's review, but the moment you reply, both the App Store and Google Play notify the reviewer and hand them a one-tap option to update their rating and text. That notification is your entire opportunity. And the numbers say it works: at Google I/O 2019, Google reported that developers who respond to reviews see their rating rise by an average of 0.7 stars, and a study of 4.5 million reviews by Hassan et al. found users are roughly six times more likely to raise their rating after a developer replies (4.4% versus 0.7% with no response).

Most 1-star reviews are not verdicts. They are complaints written in a moment of friction, a crash, a charge they didn't expect, a feature they couldn't find. The person is annoyed, not gone. When you name the specific thing, tell them it's fixed (or when it will be), and make the next step trivial, a meaningful share come back and raise the score. This playbook covers the framework, real before-and-after examples across categories, copy-paste templates, the timing that makes replies land, and the edge cases where the smart move is to report or escalate instead.

Why can't you just edit or delete a bad review?

Neither store lets a developer touch the words a user wrote. That's by design, to keep reviews trustworthy. What you get instead is a reply, and the reply is powerful precisely because of what it triggers on the user's end. If you want the deeper mechanics of how a reply feeds back into your visible score, we broke that down in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

Apple is explicit about this. In its documentation on ratings, reviews, and responses, Apple states that you can respond to any review, and that when you do, "the customer is notified and has the option to update their review." Responses can take up to 24 hours to appear publicly, and only your most recent response is shown, so you can edit your reply later without penalty (Apple, "Ratings, reviews, and responses," developer.apple.com/app-store/ratings-and-reviews).

Google Play works the same way with one extra channel. When you reply, Google emails the reviewer and sends a push notification; they can reply back by email or update their review directly. Google's developer guide notes the user is notified after the first reply to a given review, and that responding well often prompts users to "go back to check out the app, and change their initial low rating" (Google, "Reply to Reviews," developers.google.com/android-publisher/reply-to-reviews).

So the model is identical on both platforms: you write a public reply, the store privately pings the reviewer, and the reviewer decides whether to revise. You are never overwriting their opinion. You are giving them a reason and an easy path to change it themselves. Everything that follows maximizes the odds they take it.

The one fact that reframes everything

A reply is not for the angry reviewer alone. It's also read by every future prospect scrolling your reviews before they download. Even when the original author never updates, a calm, specific, human reply beneath a 1-star complaint reassures dozens of silent readers that a real team is listening. You are always writing for two audiences at once.

The 4-step framework that earns the update

What is the exact framework for a reply that gets changed?

Every reply that converts a 1-star into a higher rating does the same four things in the same order. Skip a step and the reply reads as a template; nail all four and it reads as a person who actually fixed your problem. If you want a wider treatment of tone and triage on the worst reviews, pair this with [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews).

1
Step 1 — Acknowledge the specific thing
Name the exact problem they described, in their words, in the first sentence. "Sorry the export button crashed on your iPad" beats "Sorry for the inconvenience" by a mile. Specificity proves a human read the review and isn't pasting a macro. It also lowers the reader's defenses: people brace for a corporate deflection, and naming their pain disarms that instantly. Research backs this up. Srisopha et al. (EASE 2021) found the strongest predictor of a review-response actually working is the length ratio and textual similarity between the response and the review, meaning replies that mirror the specifics land best.
2
Step 2 — Own the fix and name the version
Tell them what you did or are doing about it, and attach a concrete marker: a version number, a date, or a clear timeframe. "Fixed in 4.2.1, rolling out this week" is credible; "we're always improving" is noise. Owning it, without excuses, without blaming their device or their network first, is what converts irritation into goodwill. If it's genuinely not fixed yet, say when, and mean it.
3
Step 3 — Give exactly one next step
Point them to a single action: update to the latest version, tap a specific setting, or email one address. One. A wall of troubleshooting options reads as homework and kills momentum. If the fix is already live, the next step is simply "update the app and it's gone." Friction is the enemy of a rating change.
4
Step 4 — Invite the update (without demanding a number)
Close by gently noting that if the fix works for them, you'd be grateful if they'd revisit their review, never "please give us 5 stars." Asking for a specific score violates store guidelines and reads as needy. "If this sorts it out, we'd love for you to give the app another look" is honest, compliant, and enough. The store already hands them the update button; you just have to earn the tap.

Keep the whole reply to 3–5 sentences. Apple recommends responses be concise and free of marketing language; long replies bury the acknowledgment and the ask. On Google Play there's a hard limit anyway: replies are capped at 350 characters. Warmth, specificity, and brevity beat thoroughness every time.

Real before / after examples across categories

What does a reply that earns an update actually look like?

Below are the most common 1-star scenarios you'll face, each with the real-shaped complaint and a reply that runs the four-step framework. Read them for the moves, not the wording. The exact phrasing has to become yours (more on that after).

App crashes every single time I try to import a CSV. Lost 20 minutes of work. Unusable garbage.

You're right — importing a CSV over ~5,000 rows was crashing the app, and losing your work is exactly the kind of thing that shouldn't happen. We tracked it down and shipped the fix in v3.4.2, out now. Update from the App Store and the import will complete cleanly; if it hangs again, email us at help@app.com and I'll look at your file personally. Really sorry for the lost time — if the update sorts it, we'd love for you to give it another look.

Charged me $59.99 after I cancelled during the free trial. Scam. Want my money back.

That's on us to make right, and I'm sorry — a charge after you cancelled should never happen. I've flagged your account for a full refund and you'll see it back within 5–7 business days (Apple processes the actual credit, so it lands on your original payment method). To be sure it's your exact order, drop us a note at billing@app.com and we'll confirm the refund reference. Once it's resolved I hope you'll feel differently about the app itself.

Would be 5 stars but there's no dark mode. My eyes are dying at night. How is this not a thing in 2026??

Totally fair — a note app you use at night with no dark mode is genuinely rough, and it's the #1 thing our recent reviewers ask for. Good news: dark mode ships in v5.0, currently in beta and landing in about two weeks. If you'd like early access I'll add you — just email hi@app.com with the word 'dark'. We'll reply here the day it's live so you know to update.

There's no way to sync between my phone and laptop. Useless if I can't access my notes everywhere. Deleting.

Sync absolutely exists — but if you couldn't find it, that's a failure of our design, not you. Go to Settings > Account > Turn on Sync and sign in with the same email on both devices; your notes will appear on your laptop within a minute. I'm also adding a first-run prompt so nobody has to hunt for this again. If it doesn't light up for you, email help@app.com and I'll get you sorted the same day.

App froze on the payment screen and double-charged me. Terrible. (Reviewed 8 months ago)

This was a real bug back in the spring, and I'm sorry it hit you — the payment screen could hang and retry, which caused the double charge. It was fixed in v4.0 last April, and the app is on v6.1 now, rebuilt payments and all. If that duplicate charge was never refunded, email billing@app.com with your review name and we'll refund it today, no questions. If you're open to it, a fresh install is a completely different experience now.

Spanish

La aplicación no me deja iniciar sesión con Google, se queda en blanco. Perdí todos mis datos. Muy mala.

Tienes toda la razón, y lo sentimos mucho — el inicio de sesión con Google se quedaba en blanco en la versión anterior y lo hemos corregido en la v3.4.2, ya disponible. Actualiza desde Google Play y podrás entrar con normalidad; tus datos siguen guardados en tu cuenta, no se han perdido. Si algo no aparece, escríbenos a ayuda@app.com y lo revisamos hoy mismo. Si todo queda bien, nos encantaría que le dieras otra oportunidad a la app.

It's fine but the notifications are way too aggressive. I get pinged like 10 times a day. Almost uninstalled.

Ten pings a day is too many, full stop — thanks for saying so instead of just leaving. You can dial this all the way down in Settings > Notifications > Frequency (try 'Daily digest'), and in v5.2 we changed the default so new setups are far quieter out of the box. If there's a specific alert you never want again, tell us which at help@app.com and we'll make sure the digest respects it.

What each example has in common

All four steps, every time: the specific acknowledgment in sentence one, an owned fix with a version or date, exactly one next step, and a soft invite to revisit, never a demand for stars. That skeleton is the whole game.

Copy-paste templates (that you must personalize)

What are the templates for each scenario?

Use these as scaffolding, then rewrite them to sound like a person and match the specific review. A template pasted verbatim across ten reviews is obvious. Reviewers and future readers can smell a macro. Swap in their exact problem, your real version number, and one real next step every time.

Crash / bug: "You're right — [exact action] was crashing, and that shouldn't happen. Fixed in [version], out now. Update from the [store] and it'll [work]; if not, email [address] and I'll look personally. Sorry for the trouble — hope you'll give it another look."
Billing / refund: "That's on us to make right, and I'm sorry. I've flagged your account for a full refund — you'll see it in [timeframe]. Email [billing address] with your order so we can confirm the reference. Once it's resolved I hope you'll feel differently about the app."
Missing feature (real gap): "Totally fair — [feature] is the thing our recent reviewers ask for most. It ships in [version], landing [timeframe]. Want early access? Email [address]. We'll reply here the day it's live so you know to update."
Missing feature (already exists / UX confusion): "Good news — [feature] already exists, and if you couldn't find it, that's on our design. Go to [exact path] and it'll [result]. I'm also making it easier to find. If it doesn't work, email [address] and I'll sort it same day."
Fixed-in-latest, old review: "This was a real bug back in [month], and I'm sorry it hit you. It was fixed in [version]; we're on [current version] now. [Optional refund/data reassurance.] If you're open to it, a fresh install is a very different experience now."
Too many notifications / annoyance: "[Their complaint] is too much, full stop — thanks for saying so. You can change it in [exact path], and in [version] we made the default quieter. Tell us the specific alert at [address] and we'll respect it."
Non-English review: Reply in the reviewer's language, not yours. Keep the same four steps, run it past a native speaker or a careful translation, and never machine-translate carelessly. A clumsy reply in someone's own language reads worse than none. We go deep on this in [how to reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language).
Genuine praise buried under one gripe (2–3 star): "Thanks for the kind words on [thing they liked] — and you're right about [the gripe]. Here's the fix: [one step / version]. Appreciate you giving us the chance to get it to five."

Personalization is not optional

The single fastest way to make a reply backfire is to paste the same paragraph under multiple reviews. Users compare notes, screenshot macros, and future readers scroll several reviews at once. If two of your replies are word-for-word identical, every reader downgrades all of them to noise.

Timing and psychology: why speed moves the score

How fast do you have to reply for it to matter?

Reply within 24 to 48 hours whenever you can. The psychology is simple: right after posting a 1-star review, the reviewer is still emotionally invested and still using (or just uninstalling) your app, so a same-day reply catches them in the loop. Reply three weeks later and they've moved on or muted the notification. The update button is still there, but the motivation isn't. We put hard numbers on the response window in [how fast should you reply to app reviews](/blog/how-fast-should-you-reply-to-app-reviews).

Speed also compounds because of how the stores weight recency. Google Play shows a weighted average that leans on recent reviews rather than a flat lifetime mean; Apple displays an all-time average but surfaces recent reviews prominently and lets developers reset the summary score on a new version. The practical upshot is that you don't have to out-vote your entire history; you have to win the next few weeks. Answer every fresh 1-star fast, convert a chunk upward, stack new positive reviews on top, and because recent reviews carry more weight than old ones, the visible number moves faster than the raw math suggests.

There's a second lever: reciprocity. When a real person names your problem and fixes it, most people feel a small pull to reciprocate, and updating the review is the easy way to do that. It shows up in the data too. McIlroy et al. (IEEE Software, 2017) found that among reviews whose rating changed after a developer responded, 38.7% of those changes were increases. Make the fix feel personal ("I'll look at your file personally") and the update effortless (the store already provides the button). Warmth plus a solved problem plus a frictionless path is the whole recipe.

Close the loop when the fix ships

If you told a reviewer "fixed in the next version," go back and reply again the day it ships: "Update — this is live in v5.0 now." That second reply fires a fresh notification and is often what finally earns the update, because the fix is now real and one tap away. Tracking which reviews are waiting on a shipped fix is exactly the follow-up an AI reply tool like Reply Argus surfaces automatically, but a spreadsheet works too if your volume is low.

Per-star tactics: 1★ vs 2★ vs 3★

Should you reply to 1, 2, and 3-star reviews differently?

Yes, you should. The star count tells you the emotional starting point and how much distance you have to cover, so the tone and the goal shift with each. And the payoff is real: Apptentive's research found that moving a rating from three to four stars can lift download conversion by roughly 89%, so even a partial rescue is worth chasing.

1★ — Damage control and rescue. The person is angry or feels wronged. Lead with unambiguous ownership and, if money or data is involved, a concrete remedy first. Don't defend or explain your side first. The goal isn't always 5 stars — moving a furious 1 to a fair 3 or 4 is a real win, and it always reassures the readers behind them.
2★ — The frustrated near-miss. These people usually like your app but hit one real blocker, which makes them the highest-conversion group. They wanted to love it. Acknowledge the good, fix the one thing, and they'll often jump straight to 4 or 5. Treat every 2-star as a 5-star waiting on a single fix.
3★ — The 'it's fine' problem. Lukewarm, not angry, often praise mixed with a specific gripe. Thank them for the specifics, solve the gripe, and gently ask them to revisit. 3-star reviewers rarely update on their own, so the invite matters most here; without a nudge they simply forget.

What NOT to do

What kills a reply before it has a chance?

The failure modes are consistent, and each one is avoidable. Every item below actively lowers your odds of an update, and some can get you into guideline trouble.

Getting defensive or blaming the user. "Have you tried restarting your phone?" as an opener, or "this is actually your network," reads as combat. Even when the user is wrong, own the confusion first — bad design that led them astray is still your design.
Asking directly for 5 stars. Apple's guidelines prohibit manipulating ratings and incentivizing review changes, and demanding a specific score reads as desperate. Invite them to "take another look" and let the store's update button do the rest.
Offering incentives. "Update your review and we'll give you a free month" violates both stores' rules and can get your app pulled. Never trade anything for a rating.
Walls of options. Five troubleshooting steps, three links, and a ticket number turn a rating opportunity into a chore. One next step. Always one.
Copy-paste macros — the most common self-inflicted wound: identical replies destroy the credibility of all of them.
Corporate mush. "We sincerely apologize for any inconvenience and value your feedback" names nothing and fixes nothing. It's worse than silence.
Marketing in a complaint reply. Apple says to keep responses free of marketing language — a crash reply is not the place to plug your premium tier.
Arguing in public. If it's escalating, move it to email in one line and stop. You'll never win a comment war under a 1-star review, and readers hate watching one.

Edge cases: fake reviews, dead ends, and escalation

What about 1-stars you can't fix — fakes, review bombs, and misfires?

Not every 1-star is a customer you can win back. Some are noise, some are unactionable, and a few need to leave the public thread entirely. Here's how to triage the ones that don't fit the framework.

Fake or review-bombed 1-stars: Do both — reply once, calmly and factually for readers ("We couldn't find an account matching this review; if you're a real user, email us and we'll help"), and separately report it. Apple lets you report a concern about a review in App Store Connect; Google Play lets you flag reviews that violate policy (spam, off-topic, competitor abuse). Never fight a bomber publicly — a single measured reply plus a report is the whole move. Don't expect fast removal; the reply protects your readers meanwhile.
Reviews you genuinely can't act on: A 1-star that just says "bad" or asks for a feature you'll never build deserves a short, honest reply — "Sorry it's not for you; if there's a specific thing that'd change your mind, tell us at [address]." You won't convert most, but the reply reassures everyone reading, and occasionally the vague complaint turns specific when you ask.
Off-topic complaints (about the store, policy-set pricing, or the platform, not your app): acknowledge briefly, clarify what's in your control, and don't over-apologize for what you can't change. Readers can tell the difference.
When to escalate to support: the moment a review involves money, lost data, privacy, security, or a legal threat, move it private fast. Reply publicly once with ownership and a single email address, then resolve the substance over email where you can verify identity and pull up their account. Public threads are for reassurance; support channels are for resolution. Settling a refund dispute in review replies helps no one and exposes details that shouldn't be public.
Duplicate or resolved issues: If someone re-reports a bug you've already fixed, reply with the version it was fixed in and the current version — this is your best-converting category, because the answer is simply "update the app."

The realistic conversion mindset

You won't turn every 1-star into a 5-star, and chasing 100% makes replies sound desperate. Reply to every negative review within a day or two, convert the winnable ones, and treat the rest as a public demonstration that your team listens. Over a few weeks, that plus recency weighting is what moves the number on your product page.

Doing this at volume without it lapsing

The framework above is the whole game, and you can run it by hand. The hard part isn't knowing what to write; it's catching every fresh 1-star within a day or two, in every language your users write in, during the week your app trends and 200 reviews land at once. That's where the manual approach quietly breaks, and where a bad review sits unanswered for three weeks because nobody saw it.

That's the exact gap [Reply Argus](/features) is built for. It watches your App Store and Google Play reviews in one inbox, drafts an on-brand reply in the reviewer's own language grounded in your past approved replies and your knowledge base, and flags anything touching money, security, or data loss for a human before it ever posts. You approve by default; you can opt into rule-based auto-publish for the safe, easy wins (say, resolved-bug 5-star confirmations). When a fix ships, it resurfaces the reviews waiting on it so you can close the loop with a fresh notification. The judgment is still yours. The never-missing-one part is automated.

Turn your next 1-star around

Start free — no card. Connect one app, and Reply Argus drafts your first four-step reply in minutes, in the reviewer's language, ready for you to approve. Free covers 1 app and 100 replies a month; paid plans start at $29 when you outgrow it.

The short version

You can't rewrite a user's review, but your reply notifies them and hands them a one-tap path to update it on both stores. Run the four steps every time: acknowledge the specific thing, own the fix and name the version, give one next step, invite the update without demanding stars. Reply within a day or two, follow up when the fix ships, and let recency weighting turn a focused few weeks of good replies into a visibly higher rating. [Start free at ReplyArgus](/signup) if you'd rather never miss the review that was one good reply away from five stars.

Frequently asked

Does replying to a review guarantee the user will change it?: No — it makes it possible and likely for the winnable ones. Your reply triggers a notification and a one-tap update option on both Apple and Google, but the user chooses whether to act. Google reported an average 0.7-star lift for developers who respond, and a 4.5M-review study found users about 6× more likely to raise their rating after a reply. A specific, fast, genuinely-fixes-it reply converts a meaningful share; a generic one converts almost none.
Can I ask the user directly to give me 5 stars?: No. Asking for a specific star rating or offering incentives to change a review violates both stores' guidelines and can get your app removed. Apple explicitly prohibits manipulating ratings and incentivizing review changes. Instead, invite them to 'take another look' once the issue is fixed. The store already provides the update button; you just earn the tap.
How quickly should I respond to a negative review?: Within 24 to 48 hours if you can. The reviewer is most emotionally engaged and most likely to reconsider right after posting. Speed also compounds with recency weighting — because both stores lean on recent sentiment, winning the next few weeks of reviews moves your visible score faster than your lifetime average would suggest.
What if the bug was already fixed in an old version they reviewed?: This is your easiest conversion. Reply naming the version that fixed it and your current version, add any refund or data reassurance if relevant, and note that a fresh install is a very different experience now. The next step is simply 'update the app,' which is the lowest-friction ask there is.
Should I reply to reviews written in another language?: Yes, and reply in their language, not yours. Keep the same four-step structure, but have a native speaker or a careful translation check it. A clumsy machine-translated reply in someone's own language often reads worse than no reply at all, while a fluent one signals real care to that whole regional audience.
What do I do about obviously fake or review-bombed 1-stars?: Do both: post one calm, factual public reply for the benefit of readers, and separately report the review to the store — Apple via App Store Connect, Google Play via its report/flag option for policy-violating reviews. Don't argue publicly, and don't expect instant removal; the measured reply protects your readers while the report is reviewed.

Try it

Let Argus draft your next reply.

Watch it answer a real review in your voice. 10-day trial, no card to begin.

Start free

See the features or pricing.

Keep reading

Playbook10 min

Review Bombing on the App Store: How to Detect It and What Each Store Actually Does

How to spot a coordinated 1-star spike, what Apple vs Google will and won't remove, and how to recover your app rating after a review bomb.

Playbook7 min

Reviews That Aren't Your Fault: Replying to 1-Stars for Bugs You Didn't Cause

A full iCloud, an OS outage, a flaky ISP — some 1-star reviews aren't your bug. Here's how to reply with grace, and how each store handles it.