ReviewProof ⚖

What should you do when a customer threatens a bad review?

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

Do not trade. A refund, discount or free service given to remove or prevent a negative review is bought sentiment and suppression in a single transaction — and it marks you as a business that pays, inviting the next threat. Instead: keep every message, note dates and witnesses, decline the exchange politely in writing if it is safe to do so, handle the underlying complaint on its merits alone, and let the review land if it lands. In your provenance record it will sit as one row among linked, kept reviews; if it crosses into a fabricated account, your evidence pack — messages included in your own files — supports the platform dispute. Businesses with complete records discover threats lose their leverage surprisingly fast.

What is a review threat?

Review extortion is conditioning a benefit, or withholding a harm, on a review: a customer demanding value against silence or removal, or (in the mirror offence) a business threatening a customer over a review. Both directions are prohibited territory — the customer's demand does not license the business's payment, and the FTC rule's suppression provisions cover threats by businesses outright. The shared correct response is documentary: preserve the exchange, refuse the linkage, decide the underlying service question independently.

Separate the two questions the threat tries to fuse

A threat arrives as one sentence — 'refund me or I'll tell everyone' — containing two questions that must be answered separately, in writing, in that order. Question one is the service question: was something owed — a genuine failure, a contractual refund, a remedy you would offer any customer in this position? Answer it on the merits, at the value the merits dictate, and record the reasoning. Question two is the review question, and its answer is always the same: reviews are not something the business buys, sells or settles; the customer remains free to write their honest account. Answering in this order, in these terms, is not stiffness — it is the only sequence in which a genuine remedy cannot be misread as a purchase, by the customer, by the platform, or by anyone reading the file later.

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.

Documentation is the whole defence, started early

Save the messages in their original channels (screenshots for convenience, originals for evidence), log the dates and names of anyone present for verbal threats, and put your refusal of the exchange — politely, once — in the same channel where the threat arrived, so the pair travel together. In ReviewProof, the review itself, if it lands, is imported and kept like any other; add the context to your internal moderation note for that row ('threat correspondence held on file, dated…') without editing or suppressing the row. Should the review invent facts rather than report grievance — different weight, different channel — the platform dispute now runs on a documentary track laid down before the review existed, which is the strongest timing there is.

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

Paying the full demand to keep the profile clean is the canonical error — it funds the next threat and litters your file with an unexplainable settlement if the exchange ever surfaces. Threatening back ('we'll respond with our side and your details') is the mirror violation and a privacy risk. And pre-emptively offering review-linked remedies ('a refund if you update the review') when a complaint arrives converts even a blameless business into a participant.

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.

Worked example: the threat that documented itself out of leverage

A fictional worked example, written to show the numbers and the decisions in practice.

A guesthouse owner received a message: a guest demanded a full refund for a two-night stay, citing a noisy corridor, or 'the review will reflect it'. The owner ran the separation: on the merits, the corridor noise was real and a one-night partial refund matched her standing policy for such nights — offered, documented as policy-based. On the review: a written sentence stating the refund was per policy and entirely independent of any review, which the guest was free to write honestly. The guest took the partial refund and wrote a two-star review mentioning the noise and, fairly, the partial refund. It sits in the guesthouse's file today, transaction-linked, kept, answered graciously — and the owner's comment in the training she now gives staff is the case's moral: 'He reviewed the noise. He could not review being bought, because he wasn't.'

Your five-action checklist

  1. Preserve the threat in its original channel, with dates and witnesses noted
  2. Answer the service question on its merits and policy, documented
  3. Decline the exchange in writing, once, politely: reviews are never settled
  4. Import and keep any resulting review; note the correspondence in the internal record
  5. Use the documentary file for a platform dispute only if the review fabricates fact

Frequently asked questions

Is it illegal for a customer to threaten a bad review?

Depending on jurisdiction and form, demanding value under threat can itself be an offence. For the business, the operational rule is independent of that: never trade, document everything, decide service questions on merits.

Should we offer the refund if the complaint is partly genuine?

Offer what policy and merits dictate, documented as such — and state explicitly that it is independent of any review. The separation, in writing, is the protection.

What if the threatened review never appears?

File the correspondence anyway. Patterns of threats matter if a later dispute arises, and the dated file costs nothing to keep.

The reviewer edited their review after our remedy. Is that a problem?

An edit after a merits-based remedy, freely made, is the customer's choice. An edit traded for the remedy would have been the violation — which is why the written separation matters.

Keep reading

Related guides from the ReviewProof library:

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.