How should you handle reviews from refunded customers?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
A refund does not annul the experience, and it must never be traded against the review. Handle the refund entirely on service merits and policy — full, partial or none, documented — and treat the review as an independent object: if it arrives, import it, link it to the transaction record (the transaction occurred; the refund is a later event on the same record, not an erasure), keep it, and reply in the safe grammar. The prohibited shape is any linkage — 'refund if you remove the review', 'we'll refund once the review is updated' — which converts a service remedy into purchased suppression, whatever direction the suggestion came from.
What is a review after a refund?
A review from a refunded customer is a review whose underlying transaction was later refunded in whole or part. Provenance-wise it is uncomplicated: the transaction existed, so the review can be transaction-backed like any other, with the refund an operational fact in the business's own records. Governance-wise it is the sharpest test of the separation principle — the temptation to fuse remedy and reputation is strongest precisely here, where money is already moving — and therefore the place the written separation earns its keep.
The refund is a service decision; the review is not a currency
Set the refund by the same policy you would apply if reviews did not exist: what failed, what the terms promise, what goodwill the situation earns. Write that reasoning on the job or order record. Then close the service file. If a review follows, it enters the ordinary flow — imported, linked, kept, answered for its substance. Staff need one bright line for the hard conversation: the moment a customer proposes the exchange (refund against removal), the answer is a polite, written separation — the refund will be decided on the service merits alone and is never connected to any review — and the moment a staff member proposes it, a policy breach has occurred that the record should not be asked to hide. Both directions get the same sentence because both are the same transaction.
Triage starts from your own data, not from the public profile. Import the reviews, look at which rows carry which signals, and separate three questions that are often mashed together: is this review about a real transaction, was it solicited in a way the FTC rule prohibits, and what record do we hold if anyone asks? ReviewProof answers the first two from the imported rows — transaction link present or UNLINKED, gating or incentive language present or absent — and answers the third with the provenance chain. What it will not do is declare a review fake: signals are heuristics for human review, and acting as if they were verdicts creates a new problem while solving none.
What the record should show afterwards
Read the finished file as an examiner would. The transaction: present, dated, linked to the review. The refund: present in the service record with its policy reasoning, dated independently of the review's arrival — a refund timestamped minutes after a one-star review, without prior service history, reads as a purchase even when it was panic rather than policy, which is why deciding refunds on documented policy before reviews arrive is the only safe order of operations. The review: kept, its text untouched, the firm's reply addressing the experience. Assembled so, the file tells a story no one needs to be embarrassed by; assembled in the other order, the same money tells a story no explanation can fully repair.
ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.
Mistakes that undo the work
Offering the refund 'once the review is updated' — even once, even by a junior — is the violation in its complete form; train it as a dismissal-level bright line, not a nuance. Refusing a merited refund because a review appeared punishes speech and looks exactly like suppression's cousin. And asking a refunded customer not to review 'since we sorted it' fuses the questions in the softest voice available; sorted service is its own reward.
Keep the negative reviews. That instruction surprises people mid-crisis, but suppression is itself a violation under the FTC rule, and a profile scrubbed clean during an attack reads as manipulation to anyone who later examines it. ReviewProof has no silent-delete path: moderation decisions are kept, published or flagged internally, each one is logged in the chain of custody, and the evidence export counts the negatives you kept. The strongest response to a suspicious review is a boring, complete record — the row, the dates, the signals, the decision, all preserved while you dispute through the platform's own process.
Worked example: a full refund, a kept one-star, a stronger file
A fictional worked example, written to show the numbers and the decisions in practice.
A training provider refunded a delegate in full after a course was cancelled at short notice — per its terms, decided the day of cancellation, before any review existed. The delegate nonetheless wrote a one-star review calling the cancellation 'shambolic'. The review was imported, linked to the booking (and its refund, recorded on the service side), kept, and answered: the firm agreed the cancellation was badly handled, stated the refund had been made under its terms, and described the new minimum-enrolment guarantee. Two later enquiries mentioned that exchange by name as a reason for booking: the firm's worst review had become its best-evidenced character reference, because the record showed remedy, review and response in their proper, untraded places.
Your five-action checklist
- Decide every refund on policy and merits, documented, before reviews enter the question
- State the separation in writing when a customer proposes an exchange
- Import, link and keep refunded customers' reviews like any other
- Reply to the substance; never reference the refund as a reason the review should change
- Audit refund-then-review timelines periodically for accidental patterns
Frequently asked questions
Can a refunded customer legitimately review us?
Yes. The transaction and the experience happened; the refund remedies the service failure, it does not retroactively unhappen the visit or purchase.
Is the review still transaction-backed after a full refund?
Yes — the transaction record exists and the review describes it. The refund belongs in the service record, not in the provenance judgement.
A customer demands a refund to remove a review. What exactly do we do?
Preserve the message, decide the refund on merits alone, decline the exchange in writing, keep any resulting review, and note the correspondence internally.
Should our reply mention the refund?
Only factually and where it corrects the record ('a full refund was made under our terms on [date]'), never as an argument that the review is unfair for existing.
Keep reading
Related guides from the ReviewProof library:
- What should you do if a competitor is leaving fake reviews?
- What should you do in the first 48 hours of a one-star attack?
- How do you clean up a profile with bought reviews in its past?
- Why are employee reviews of your own business a violation risk?
- What does it mean when one reviewer appears at many businesses?
- What should you do when a customer threatens a bad review?
- Can having too few negative reviews look suspicious?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.