GlossaryReviews
Review Reply
A review reply is the store's public response published underneath a customer review, and its real audience is almost never the person who wrote it: it is the shoppers who arrive months later, plus anything that reads the product page as text.
Also known as merchant response, review response
The reply looks like customer service and behaves like published copy. By the time most people read it, the original complaint is settled or abandoned, and the reader has no stake in that order at all. They are doing two things: working out whether the fault described is systemic or a one-off, and working out how this store behaves when something goes wrong. Those are the two questions a reply can answer, and neither of them is answered by an apology.
What separates a reply that works from one that does not is specificity. Naming the actual part that failed, saying what caused it if you know, saying what changed and from when, and telling the reader what to do if it happens to them: that is a reply with information in it. The common alternative, a sentence of regret followed by an invitation to email support, tells the next shopper nothing except that the store has a support address. Defensive rebuttals do worse than nothing, because a reader who has to weigh a customer's account against a merchant's account tends to side with the customer. And replying to every five-star review with a thank you fills the page with text that nobody reads and dilutes the replies that carry substance.
Consider a Shopify store selling leather weekend bags. A two-star review says the strap hardware failed after five weeks. The first draft of the reply is the usual one: sorry to hear this, please email us so we can make it right. The second draft names the D-ring, says a batch made between two specific months used a lighter gauge than the spec, says the store moved to a solid brass ring from a stated date, and says anyone with a bag from that window can request a replacement strap. The customer gets the same outcome from either reply. The shopper reading it in November gets something entirely different: from the first, a store with a complaint on the page, and from the second, a dated fault that was found and fixed. The second reply also has a side effect the first does not: the correction is now on the page, where it can be read by anyone and anything that reads the page.
The honest limits are worth stating, because this is a place where advice tends to overpromise. A reply does not neutralise the review and does not change the star. Treating replies as damage control produces a tone that shoppers recognise instantly, which is why the corporate-apology register reads as worse than silence. Google Business Profile lets an owner respond and shows the response to anyone reading the review, but whether responding moves anything in local ranking is not something Google has confirmed, so the return is best treated as persuasion rather than position. And there is a temptation particular to this field, which is to write the reply for the search engine: stuffing the product name and a keyword into a response to an unhappy customer is transparent to a human reader first, and a human reader is the one deciding whether to buy.
The other thing to know is that replies live in different places under different rules. On your own storefront, your review app publishes them and you control the display. On Google, Trustpilot, or a marketplace, you can respond and you can flag a review for a policy breach, but you cannot remove it, and your reply is as permanent and as public as the review. That asymmetry is a good reason to write the reply you would be content to have quoted, because it can be, and because the reply is often the only part of the exchange the store actually controls.
For AI search, the mechanism is unremarkable and easy to miss: an answer engine reading a product page sees the review and the reply as one block of text, so a recurring complaint that is answered in public puts the correction into the same corpus as the complaint. Answer it by direct message instead and only the complaint is retrievable. This is not a trick, and it does not work if the answer is not true. It does have one hard prerequisite that many stores fail without knowing: replies have to be in the HTML the page actually serves. A widget that renders reviews client-side, or seals them inside an iframe, keeps the reply out of everything that reads the source, so the complaint may be retrievable through other channels while your answer to it is not. Getting existing reviews and the replies attached to them into a form that search and AI can read is the gap BeyondReviews works on.