Open the Play Store listing of almost any funded Indian app and scroll to the reviews. Somewhere in the one- and two-star cluster sits a complaint that is three months old, still unanswered, still visible to every new visitor deciding whether to install. The reply box sat empty the entire time, not because nobody saw the review, but because nobody on the team considered it their job to answer it.
A support ticket is private. A review reply is a billboard.
When a customer emails support, the resolution is seen by exactly two people: the customer and whoever answers. When the same complaint lands as a Play Store review, the reply is seen by every single person who reads reviews before installing - which, for most categories, is the majority of people who scroll past the four-and-a-half-star average straight to the lowest-rated comments first. That is where a shopper actually calibrates trust: not the number, but what the company sounds like when something has gone wrong. A thoughtful, specific reply to a bad review does more to convert that reader than ten more five-star reviews saying “great app.”
The reply nobody notices is the one that matters most
Most companies that do reply default to a template: “Sorry for the inconvenience, please reach out to support@company.com.” That reply costs nothing and earns nothing - a reader skimming the thread learns only that the company has a support inbox, which they already assumed. A reply that names the actual fix, states when it shipped, or explains the tradeoff behind a design decision reads as a company that is run by people, not a ticketing queue. It takes thirty extra seconds to write and it is the only part of the review section a prospective customer will actually remember.
Why this works better the angrier the review is
A five-star review needs no reply; it has already done its job. A one-star review with a real grievance is the highest-leverage reply slot on the entire page, because it is the exact moment a skeptical reader is testing whether the company’s confidence is earned or performed. Answering it well in public does something a case study never can: it shows the company holding up under the worst available scrutiny, in front of an audience actively looking for a reason not to trust it.
Why most companies still skip it
The honest reason is organizational, not strategic. Review replies fall in the gap between support, which handles tickets, and marketing, which handles channels it was told to own. Nobody owns the Play Store reply box because nobody was assigned it, and a channel with no owner gets no attention, however visible it is to the exact people a company is trying to convert. The fix costs nothing beyond deciding, explicitly, that someone on the team checks it every week - and that whoever writes the reply is told to write like a founder, not like a legal disclaimer.