They praised a feature you do not have
Customer Overclaims What Your Product Does
"It syncs with every accounting package out there and never goes down." Your product connects to two packages and had an outage last spring. The customer is not lying: they love it and they are generalising. But a testimonial you publish is read as your claim, and a visitor who buys on the strength of that sentence will be let down. Check each factual statement below before it goes live.
- Pulls out each factual statement about your product
- Checks it against what you sell today
- Gets the accurate version from the customer
The problem, solved
How an overclaim gets onto your site, and how to stop it
Situation 1 of 4
Nobody checked the facts in the praise
Moderators read for tone and spelling. "Works with any CRM" sounds positive, so it sails through.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so a product owner can read the factual lines before it does.
Situation 2 of 4
Correcting it ourselves feels wrong
Changing "every CRM" to "Salesforce and HubSpot" is accurate, but now the customer is saying something they did not say.
How StoryProof solves it
Email them your collection link with the correction you need. They resubmit in their own words, by text, audio or video.
Situation 3 of 4
The overclaim is still in the library
Months later, someone pulls the original into a sales deck because it sounds better.
How StoryProof solves it
Tag the original "inaccurate claim, do not use" and leave it unapproved.
Situation 4 of 4
It is true for one plan only
The customer is on your top tier and praises a feature most buyers will not get.
How StoryProof solves it
You choose which approved testimonials appear in each widget, so that quote can sit beside the plan it describes, not on the general homepage.
Accuracy check
Check what the quote says about your product
Copy the testimonial into a note and underline every statement of fact about the product. Then tick each check once it holds for every underlined line.
Your ticks stay in this browser tab. Nothing is stored or sent.
The same customer, before and after the check
As submitted
- "It syncs with every accounting package out there"
- "It never goes down"
- "We were up and running in ten minutes"
- "Support is there for us around the clock"
As resubmitted by the customer (illustrative)
- "It syncs with our accounting package without any fuss"
- "It has been reliable for us all year"
- "Setup was quicker than we expected"
- "Support always gets back to us fast"
In StoryProof
Get an accurate version published
- 1
Hold and tag the original
Keep it unapproved and tag it so nobody uses it while you check.
- 2
Run the accuracy check
List every factual statement and check each against the product as sold today.
- 3
Ask the customer for an accurate version
Thank them, point to the specific line, explain what the product actually does, and send the collection link so they can resubmit in their own words.
- 4
Approve and place it in context
Approve the accurate version and add it to the widgets on pages where its context is true.
What happens next: Recheck published testimonials when a feature is removed or an integration changes. A quote that was accurate at launch can become an overclaim later.
Before you start
What the rules say, and what StoryProof cannot do
The claim becomes yours
The FTC’s endorsement guidance tells advertisers not to make claims through endorsers that would require proof the advertiser does not have.
Factual claims in a quote must not mislead
UK CAP guidance says claims in testimonials that are likely to be read as factual must not mislead, and that marketers must hold evidence for claims that are not clearly subjective.
Not legal advice
How these rules apply depends on your market and product. Have a qualified reviewer look at anything borderline.
No text editing in StoryProof
The app cannot change the words of a testimonial. Accurate versions come from the customer through the collection link.
FAQ
Questions people ask
Short answers to what usually comes up next.
The customer is just being enthusiastic. Is it really a problem?
Opinions such as "I love it" are fine. Statements of fact that are wrong, such as an integration you do not offer, mislead the next buyer whoever wrote them.
Can I add a note under the quote correcting it?
It looks odd and the inaccurate line is still there. Ask the customer for an accurate version instead.
What if the feature is coming soon?
Wait until it ships. A testimonial praising something a visitor cannot buy today is still an overclaim.
What if the customer will not resubmit?
Keep the original unapproved. If another part of it is accurate and strong, ask whether they are happy for you to use only that part, and get their yes in writing.
Still have a question? Ask the StoryProof team or book a demo.
Publish praise that is true
Hold each testimonial until its facts check out, and collect accurate wording from the customer when they do not.
Sources
- FTC’s Endorsement Guides: What People Are Asking, Federal Trade Commission. Checked 2026-11-20.
- Claims in testimonials and endorsements, Advertising Standards Authority / CAP (UK). Checked 2026-11-20.
Last updated 2026-11-20.