One submission does not add up
Verify a Testimonial Is Genuine First
A glowing testimonial lands from a name nobody on the team recognises. It praises a feature you shipped last week and arrived an hour after the order was placed, before the parcel left the warehouse. Maybe it is a keen customer. Maybe it is not. Work through the checks below on that one submission before it goes anywhere near your website.
- Checks for one doubtful submission, not a bulk filter
- Uses your own order and contact records
- Ends with approve, hold or decline
The problem, solved
Where a doubtful submission causes trouble
StoryProof cannot tell you who someone really is. What it can do is keep the doubtful one out of sight while a person checks it properly.
Situation 1 of 5
It looked fine, so someone approved it
A busy teammate clears the queue on a Friday and the strange one goes live with the rest.
How StoryProof solves it
Nothing a customer submits goes public until it is approved, so a submission under review stays private for as long as the check takes.
Situation 2 of 5
Nobody remembers which ones are being checked
The doubt lives in one person’s head. A week later another person sees an unapproved five star quote and approves it.
How StoryProof solves it
Tag it "checking origin" and filter by that tag at your weekly review, so open checks are visible to everyone.
Situation 3 of 5
We cannot tell if they are a customer
The name is common and the email is a free webmail address that appears nowhere in your records.
How StoryProof solves it
Contacts are on every plan. If you send requests only to people you have added, a stranger outside that list is itself a signal worth noting.
Situation 4 of 5
The wrong person is doing the check
An intern can approve, but only finance can see whether an order exists.
How StoryProof solves it
Roles let you give the person who can confirm orders the moderation access they need, without opening everything else.
Situation 5 of 5
It might be real but we cannot confirm
Rejecting a genuine fan is a poor reward for their effort, and publishing a fake is worse.
How StoryProof solves it
Send the customer your collection link and ask them to resubmit from the address on their order. It accepts video, audio or text.
Authenticity checks
Check this one submission before approving it
Open the submission beside your order system and inbox. Tick each check you have done. You do not need every box: two or three solid matches usually settle it.
Ticks stay in this page only. Nothing you tick is stored or sent.
What the checks usually point to
Illustrative combinations, not rules. Your own records decide.
In StoryProof
Run the check in StoryProof
- 1
Hold and tag it
Leave it unapproved and add a tag such as "checking origin" so the whole team knows it is open.
- 2
Match it against records
Search your order system for the name and email, and compare the product and dates with what the testimonial says.
- 3
Write to the customer
Use the email address from your own records. Thank them, ask them to confirm they sent it, and offer the collection link if they would like to resubmit.
- 4
Decide and clear the tag
Approve it, or keep it private with a note on why. Filter by the tag weekly so nothing stays open for long.
What happens next: If the same pattern turns up again, such as a burst from free addresses with no orders, write it down. It is a candidate for an automatic rule, not a weekly chore.
Before you start
What this check cannot do
StoryProof does not verify identity
There is no identity check, purchase check or fake detection in the product. The checks on this page are done by you, against your own records.
A match is evidence, not proof
Someone can use a real customer’s name. A reply from the email address on the order is the stronger signal.
Not every real customer is in your system
Gifts, resellers and company cards mean a genuine reviewer may not match any order. Ask before you decide.
The law here needs a reviewer
The FTC rule on consumer reviews and testimonials, in force since 21 October 2024, can make a business liable for fake testimonials it writes or buys, and its guidance points to warning signs a business should not ignore. Have a qualified person confirm how it applies to you.
Do not collect more than you need
Asking for a passport or a screenshot of a bank statement is out of proportion for a testimonial. An order number is enough.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can StoryProof tell me whether a testimonial is fake?
No. It keeps every submission private until you approve it and lets you tag the ones you are checking, but the judgement uses your own records and a reply from the customer.
Is it rude to ask a customer to confirm they wrote it?
Not if you lead with thanks. "Thank you for this, can you confirm it came from you before we share it?" reads as care, not suspicion.
What if the reviewer is real but bought through a partner?
Ask for the order reference or where they bought. A partner sale will not be in your records, and a quick reply usually clears it up.
Should I delete a submission that fails the checks?
Keep it unapproved with a tag and a short note on why. That record helps if similar submissions arrive later.
Does this apply to reviews I import from other sites?
The same records check applies, and imports wait for approval too. The difference is that the review platform has its own rules on who may post.
Still have a question? Ask the StoryProof team or book a demo.
Check first, publish second
Every submission waits for your approval, so a doubtful one never reaches your site while you look into it.
Sources
- Consumer Reviews and Testimonials Rule: Questions and Answers, Federal Trade Commission. Checked 2026-11-20.
Last updated 2026-11-20.