Sabotage through your own form
Competitor Submits a Fake Testimonial
Junk from bots is noise. This is different: a submission that looks deliberate, written by someone who knows your business and wants something from it. It might be a one star attack that lands in your inbox as an alert, or a glowing quote from a customer who never existed, waiting for you to publish it so it can be exposed later. Work through the checklist below before you approve, reject or reply to anything.
- Hold it, then gather facts
- Close the door it came through
- Reply calmly, or not at all
The problem, solved
How a planted testimonial causes damage
A fake from a rival only hurts once you act on it. These are the moments it can catch you out, and what StoryProof does at each.
Situation 1 of 6
A glowing quote from nobody we know
A rival who gets you to publish an invented customer can later point at it as proof you fake your proof.
How StoryProof solves it
Nothing a customer submits goes public until someone approves it, so an unknown reviewer can wait while you look for any record of them.
Situation 2 of 6
Auto approval would publish it
A planted quote is written to pass: five stars, plenty of text, nothing odd on the surface.
How StoryProof solves it
From Pro, auto approval passes 4 and 5 star testimonials that include text and leaves the rest. It judges rating and text only, so while you suspect a campaign, switch it off and approve by hand.
Situation 3 of 6
A one star attack set off our alerts
The low rating flow fired, the team panicked, and an apology email went to someone who was never a customer.
How StoryProof solves it
From Pro, a review of 2 stars or fewer can alert your team and send the customer an apology email. Know that the apology goes out automatically, and check your wording would be harmless if it reached a rival.
Situation 4 of 6
We cannot keep track of suspects
Three odd submissions over two weeks look harmless one at a time and like a pattern together.
How StoryProof solves it
Tag each suspect submission with one label you reuse. From Pro, an automation can also flag a testimonial or add a label, so a reviewer cannot approve it by accident.
Situation 5 of 6
Our link is on a public page
A collection link shared openly or printed as a QR code can be used by anyone who finds it, rivals included.
How StoryProof solves it
The link can be shared by hand or as a QR code. If a public copy is being abused, move it behind a page for customers and send it to known customers instead.
Situation 6 of 6
We need a dated record of what happened
If this ever goes further, memory is weak evidence. A list of what arrived and when is stronger.
How StoryProof solves it
From Pro, automation logs show every enrolment and step that ran, kept for 30 days. Copy anything relevant into your own notes before it expires.
Before you react
Suspected competitor fake: response checklist
Tick each item as you go. The order matters: hold first, look second, act last.
Your ticks stay in this page in your browser. Nothing is sent or stored.
A panicked response and a measured one
Reacting on the day
- Reject and forget it within minutes
- Post about "dirty tactics" on social media
- Leave auto approval running
- No record of dates, wording or the address used
Handling it on purpose
- Held unapproved and tagged until checked
- Private, neutral reply asking for an order reference
- Auto approval paused while the pattern is unclear
- Dated screenshots and notes kept outside the app
In StoryProof
Contain a suspected fake in StoryProof
- 1
Keep it in the queue
Leave the submission unapproved. It cannot appear in any widget or on your Wall of Love while it waits.
- 2
Label it and its relatives
Add the same tag to this entry and anything that looks related, so the group can be reviewed together.
- 3
Pause automatic approval
If you run the auto approval automation (Pro and up), pause it for now. It approves on rating and text, not on who the reviewer is.
- 4
Read the logs while they last
Open the automation logs and note what ran for these entries. Logs are kept for 30 days.
- 5
Decide, then reject or approve
Reject entries you are sure are planted. If a record turns up and the customer is real, approve it as normal.
What happens next: Turn auto approval back on only when submissions look normal again, and keep the suspect label for the next time.
Before you start
Limits worth knowing
No identity check
StoryProof does not verify who a reviewer is. Matching a submission to a real customer is done against your own records.
It cannot name the sender
Nothing on this page claims StoryProof can tell you who sent a submission or where from. Treat your suspicion as a suspicion.
Public links stay usable
A link that has been shared publicly can still be used by whoever saved it. Moving it reduces new traffic; it does not recall old copies.
Not legal advice
Whether a rival’s fake is actionable depends on where you are and the facts. Ask a lawyer before you threaten anyone.
Reviews on other sites are separate
This page covers your own collection form. Fake reviews on third party sites are handled through those sites’ own reporting tools.
FAQ
Questions people ask
Short answers to what usually comes up next.
How can I tell a planted testimonial from an honest unhappy customer?
Start with your own records. A real customer usually matches an order, booking or email thread. A planted one often has no match, uses phrasing close to a rival’s marketing, or arrives with others in a short burst. None of these proves anything alone.
Should I reject it straight away?
Hold it first. While it is unapproved it cannot appear anywhere, and keeping it gives you a record while you check whether it is part of a pattern.
Why would a competitor send a positive fake?
If you publish an invented customer, someone can later claim your testimonials are fabricated. Holding every unknown reviewer until you can match them to a real customer removes that risk.
Should I confront the competitor?
Not in public, and not on a hunch. Keep your notes, and if you think it is serious enough to act on, speak to a lawyer first.
Still have a question? Ask the StoryProof team or book a demo.
Publish only what you have checked
Every submission waits for your approval, so a planted quote stays in the queue until you decide what it is.
Last updated 2026-11-20.