Set a Three-Day Reply Habit and Watch Your Response Rate Climb
Read enough reviews before you buy anything and you start meeting the same handful of terms: verified purchase, provenance, review velocity, aggregate rating. Most people scroll past them, half guessing what they mean, because admitting you don’t know feels worse than not knowing. Merchants have the opposite problem: they are told to improve review response rate without anyone explaining what a response rate actually measures, or why a business with worse reviews but faster replies can look more trustworthy than one with a higher average and total silence. Both problems have the same answer, once you know what each term is actually telling you.
Verified purchase
A verified purchase means the review is tied to an actual order, something bought and paid for through the platform or store, not a badge a merchant applied for or bought. It matters because an unverified review can be written by anyone: a friend doing a favour, a competitor doing damage, or someone who never used the product at all. It doesn’t tell you whether the experience was good or bad. It only tells you whether the person writing had one to talk about.
Provenance
Provenance is where a review comes from beyond the purchase itself: whether the account has a history, other reviews, a pattern of ordinary behaviour, or whether it appeared once and never posted again. A single glowing review from a brand new account proves very little either way. A pattern across many accounts, written in different voices, over different months, is much harder to fake and much more worth reading.
Review velocity
Review velocity is the pace at which reviews arrive. A business trading for two years that suddenly gets several hundred five-star reviews in a week has a velocity problem, not a popularity spike. The same applies in reverse: a cluster of one-star reviews landing on the same day, all citing the same issue, usually means one bad batch or one failed delivery, not an ongoing pattern of failure. Velocity is what tells you whether you are looking at a trend or a single afternoon.
Improve review response rate: what seller feedback actually measures
Seller feedback used to mean the star rating and nothing else. Increasingly it includes something separate: whether the merchant replied, how quickly, and what they said. A response rate is exactly what it sounds like, the proportion of reviews, particularly the negative ones, that get an answer instead of silence. It has become a trust signal in its own right, and for a reasonable reason: a business that stopped replying is easy to imagine going wrong in every other direction too.
The habit that moves this number is smaller than it sounds. Reply within three days, before the thread goes cold, before the customer has already decided the business doesn’t care. That is the whole discipline. Merchants who improve review response rate this way aren’t managing a reputation, they are just answering their post before it piles up.
This is the point where the mechanism matters more than the metric. Reviewit gives a customer who leaves two stars or fewer a choice before anything is published: publish the review now, or give the merchant three days to put the problem right first. The choice stays with the customer throughout. Nothing is held back on their behalf, and they can publish at any point regardless of what the merchant does or doesn’t manage in that time. What changes is timing, not control. Most low-rated reviews get written after someone stopped replying, not because the fault itself was unforgivable, and given a genuine chance to have something fixed, plenty of people would rather have it fixed than argue about it in public afterwards.
Aggregate rating
An aggregate rating is the single number, the four point something out of five, that every platform reduces a business down to. It is useful for sorting quickly and not much else, because it hides the shape of what sits underneath it. A business with a string of one-star reviews that all got answered, apologised for, and in some cases resolved reads very differently to one with the same average and total silence. The number doesn’t show you which is which. The individual reviews, and whether anyone replied to them, do.
Telling a bad experience from a bad business
Put the terms together and the difference gets easier to spot. A bad experience tends to look like this:
- A single low rating sitting inside an otherwise steady velocity, not a cluster
- A verified purchase with clear provenance, a real order gone wrong
- A reply from the merchant, even a late one, showing the issue was taken seriously
A bad business tends to look like this instead:
- The same complaint repeating across months, not one bad week
- Low ratings with no seller feedback attached, ever
- An aggregate rating that looks fine only because nobody scrolls past the first page
What this is worth in practice
None of this requires special skill, only the habit of reading past the average. For a reader, that means checking whether low reviews got answered before deciding a business is bad. For a merchant, it means treating the three days after a bad review as the moment that decides whether it stays a bad experience or turns into evidence of a bad business. The reply is small. What it does to the response rate, and to how the whole page reads afterwards, is not.