Chloe M.Google reviewOrder arrived damaged and nobody has replied to my email in three days.

Keep one parent ticket for each root cause and link every report to it. Count the reports on that ticket and let the count drive priority. Then reply to each person individually, on the channel they used, and tell them when it is fixed. Merging tickets is the easy part. The hard part is keeping the list of people you owe an answer, and writing a store reply inside the limits Apple and Google set.
Engineering teams solved this long ago, and the conventions carry over to support.
In Google's Issue Tracker, marking an issue as a duplicate closes it and adds the people on it to the canonical issue. The canonical issue may be the older one, the more visible one or the one with the wider scope. On GitHub, a comment reading "Duplicate of #97" makes the link, and it can be undone.
Two ideas are worth copying. People on the duplicate carry over to the parent, so nobody is lost. And the merge can be reversed, because it will sometimes be wrong.
A workable matching rule for support:
Record the version, device, operating system, country, and the time it first happened on the parent ticket. Ask only for what you don't have, and ask privately.
One check before you escalate is the store's own data. Google's Android vitals sets bad behaviour thresholds for user-perceived crash rate of 1.09% overall and 8% on a single phone model. Go above them and Play may reduce your visibility or show a warning on your listing. Vitals counts per daily active user, and Google notes Crashlytics counts per session, so the two will not match. A crash that sits on one phone model can look small overall and still cross the per-model line.
Store replies are public and short, and they have rules of their own. These apply wherever you operate.
| Rule | App Store | Google Play |
|---|---|---|
| Replies per review | One visible response, editable | One public reply, editable |
| Length | No limit stated on the pages we read | 350 characters, plain text |
| When it appears | Up to 24 hours | Not stated on the pages we read |
| Does the user hear? | Yes, and they can update their review | Push and email. Editing a reply sends no new notice |
| Content | No personal information, spam or marketing, stay on the user's comment | Truthful, relevant, respectful, no soliciting or promoting. Violations can cost you the account |
| Automation | Personalise rather than paste the same text | Google discourages automated replies you intend to update by hand later |
| Asking for a rating | Apple's API only, three prompts in 365 days | No questions before the prompt. No incentives |
Three details change how you work:
Apple also says to point download and billing problems to Apple Support, so route those away from your bug queue. And you can reset your summary rating when you ship a new version, per territory. Apple recommends doing it sparingly.
The urge after a bad bug is to ask people to change their rating. Asking is fine in general. Offering something for it is where trouble starts. The principle almost everywhere: a review must be the person's genuine opinion, and any reward must be disclosed and must not depend on the sentiment. Store policy is stricter. Google lists asking users to rate while offering an incentive as a violation. Apple's guidelines cover paid, incentivised or filtered feedback. This is general information and not legal advice, so check your own market.
| Market | What applies |
|---|---|
| US | FTC rule, in effect since 21 October 2024. Incentives can't carry an express or implied requirement of a particular sentiment. Groundless legal threats to get a review removed are barred |
| UK | CMA fake reviews guidance of April 2025 covers fake reviews and concealed incentivised reviews |
| EU | Your Europe says traders may not alter customer reviews and ratings or pay for fake reviews |
| Australia | ACCC guidance: incentives must apply whether the review is good or bad and be disclosed. Removing genuine negative reviews may mislead |
| India | IS 19000:2022, a standard for organisations publishing reviews online, launched in November 2022 as initially voluntary. Check its current status |
| Situation | Owner | First move | Never |
|---|---|---|---|
| New report, matches an open ticket | Support | Link it, reply to the person | Open another ticket |
| Reports climbing on one ticket | Support lead | Alert the mobile owner with count and versions | Wait for a weekly review |
| Crash after a new release | Mobile lead | Halt the rollout | Keep rolling out while you investigate |
| Report needs details | Support | Ask privately for version and device | Ask in a store reply |
| Reporter describes lost money | Payments team | Treat it as a money case | Link it to a bug and move on |
| Request for a feature, worded as a bug | Product | Move it to the feature list | Count it as a bug report |
| Report can't be reproduced | Engineering | Ask for one specific detail | Close as "works for me" with no reply |
Stopping a bad release is the fastest fix available. On Google Play, halting a staged rollout stops delivery to new users, but those who have it keep it. Fix it with a new release if the bundle is bad. On the App Store, phased release goes from 1% to 100% over seven days and can be paused for up to 30 days in total, though anyone can still download manually. Apple allows an expedited review for a critical bug fix if you include steps to reproduce the bug on the current version.
Store replies below fit Google's 350 characters. Keep them that way.
First reply, in chat or email
Hi Kenji, thanks for telling us. Others have reported the same crash on the Payments screen and our mobile team has it. One thing would help: which app version do you have? It's under Settings, About. I'll message you when the fix is out.
Public reply on a store
Thanks for reporting this. We know Payments is crashing on launch for some people and we're working on a fix. Please contact help@pocketpay.example with your app version so we can keep you posted. Your payments and balance are not affected by this crash.
Only include that last sentence if engineering has confirmed it.
Update when there is no news
Hi Kenji, still no fix to share. The team has found the crash happens when the screen loads your saved cards, and they're testing a change. I'll write again by Thursday even if nothing has moved.
Closing reply
Hi Kenji, the crash is fixed in version 6.4.1, which is on the store now. Please update and open Payments. If it still closes, reply here and tell me what phone you're on, and I'll reopen this.
Store reply after the fix
Fixed in version 6.4.1, out now. Update the app and Payments should open normally. If it doesn't, write to help@pocketpay.example and we'll look at your case directly. Thanks for the report, it helped.
Hard case: can't reproduce, or won't be fixed
Hi Kenji, I'll be straight with you. We can't reproduce this, and it only appears on one older phone model, so we aren't planning a fix right now. A workaround is to use Payments in the browser at pocketpay.example. If that doesn't work for you, tell me and I'll see what else we can do.
Times are a suggested starting point and not a benchmark. Set them by your release pace.
It is working when engineering sees one ticket with a real count, and customers stop reporting a bug that has already been fixed.
This is an example scenario. The app, people and messages are made up to show how this works. It is not a customer story.
Pocketpay is a payments app. One morning its Payments screen starts crashing.
Priya Shah leaves one star on Google Play: "App crashes the moment I open Payments. Pixel 8." Lucía Fernández posts on X in Spanish: "La app se cierra en cuanto abro Pagos. @pocketpay" (The app closes as soon as I open Payments.) Kenji Watanabe writes in chat in Japanese: "支払い画面を開くとアプリが落ちます。" (The app crashes when I open the payments screen.)
Three channels, three languages, one bug. Pocketpay already has BUG-2291, "crash on opening Payments", so all three get linked and the count goes up. Reports pass the trigger, so the mobile owner is alerted and halts the staged rollout. Support asks Lucía and Kenji privately for the app version. Priya gets a public store reply under 350 characters, with an address to write to. When 6.4.1 ships, the linked list gets a message and the store reply gets edited. Because Google does not notify on edits, support also follows up on the channels where it has a contact.
Tagging, grouping similar reports into themes, linking cases to tickets, crisis alerts and routing to the right team run in Relay today, along with drafted replies that a person approves. Sending on X and email needs each channel's token. Replies to App Store and Google Play reviews still go through each store's own developer console, so plan on that.
Jira, Linear and GitHub sync is on the way. Until then, the Relay ticket is the shared record and the team copies the summary into its tracker. If your support team drowns in duplicate bug reports, contact us. For the moment a bug becomes an outage, see handling a ticket spike. For a crash on a money screen, see money debited but payment failed.
There is no standard number. Pick a count in a time window, such as 5 in 2 hours, and tune it to your volumes after a few releases. Check it against your crash data as well as your inbox.
Replying to tell them it is fixed is normal, and Apple suggests replying after a fix ships. Offering a reward for a better rating breaks Google Play policy and creates legal risk in several markets. Tell them it is fixed and leave the choice to them.
The API returns only reviews created or modified in the last week. Older reviews are available through a CSV export from Play Console. Google's page limits retrieval and doesn't say whether older reviews can be answered through the API, so reply in the console or test it.
Link them provisionally and flag the difference for engineering. The same symptom on two versions can have two causes. Keep the ability to split them.
No. Drafts ask for the app version and phone model privately, and a person approves each one before it goes out. Store replies stay in the store's own console.
Not yet. Jira, Linear and GitHub sync is on the way. Today the ticket lives in Relay.
GuidesIntroducing Relay: your online reputation in one placeWhat Relay is, the gap it was built for, what it does today, what it does not do yet, and who should choose something else.29 October 2026 · 6 min read
GuidesHow to do online reputation management, step by stepFind what people say about your business, answer it within the rules, fix what caused it. A plan, a triage table and replies you can copy.9 November 2026 · 11 min read
GuidesHow to automate customer support without trapping your customersWhat to automate, what to keep with a person, what the law says about AI disclosure, and how to tell whether automation is really working.9 November 2026 · 12 min readGet a personalised 30 minute demo on your own channels and policies. We show you Relay handling your real conversations, then set it up with you.
Brands we work with


