A single quote, a feature that is gone
Testimonials Praising a Feature You Removed
You are not auditing the whole library today. One quote is in front of you: maybe it just arrived from a customer still on an old habit, maybe sales wants it in a deck, maybe it is the hero quote on a page you are rewriting. It praises something you no longer offer. Before you drop it, check what the customer was really praising. Five questions below give a verdict for this one quote.
- Is the praise for the feature or the result?
- New arrival or old favourite
- Approve, re-ask or archive
Verdict for one quote
Can this quote stay, now the feature has gone?
Read the quote twice before you answer: once for what it names, once for what it achieved. The helper scores each answer and shows a verdict with a second choice.
Answers are scored in this page only and are not stored or sent.
The problem, solved
One quote, four ways it trips you up
- Problem 1
It arrived after we removed the feature
A customer on an old habit praises something that is no longer there, and someone approves it on autopilot.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so a quote like this can stay in the queue while you check what it describes.
- Problem 2
Sales wants it back in the deck
A favourite quote resurfaces in a pitch, and a prospect asks for the feature by name.
How StoryProof solves it
Tag the quote with the removed feature’s name so anyone searching the library sees the warning before they copy it.
- Problem 3
It is live on a page for new buyers
The quote is accurate history and inaccurate promise, depending on who reads it.
How StoryProof solves it
You choose which approved testimonials appear in each widget, so the quote can come off the buyer pages without touching the others.
- Problem 4
The customer still loves the result
The feature went, the outcome stayed, and their quote is stuck naming the old way.
How StoryProof solves it
Email them your collection link and ask how they get that result today. Their new words arrive as text, audio or video and wait for approval.
- Problem 5
We want a record before it disappears
Once the quote is out of every widget, nobody remembers the customer liked the old feature.
How StoryProof solves it
StoryProof exports a space’s testimonials as a CSV file from the workspace settings, so you can keep a dated record of what customers praised.
In StoryProof
Decide one quote in StoryProof
- 1
Tag it with the feature name
Add a tag for the removed feature so the decision is visible to anyone who finds the quote later.
- 2
Run the five questions
Read the quote with the feature name covered, then answer the helper above.
- 3
Act on the verdict
Approve it, email the customer your link for a fresh version, or leave it unapproved and thank them.
- 4
Check the widgets it sits in
If the verdict is to archive, remove it from each widget that shows it.
What happens next: If more than a handful of quotes need this, stop and run the library wide clean up instead.
Before you start
Where this stops
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
No editing inside StoryProof
This page claims no way to change a testimonial’s words in the app. Cutting the feature out has to be the customer’s choice, in a version they send.
- 02
No automatic feature search
StoryProof does not find mentions of a feature for you. Reading and tagging is a manual step.
- 03
Copies outside widgets
A quote pasted into slides, ads or emails does not change when you change a widget. Track those down separately.
- 04
One quote, not a policy
The helper judges a single testimonial. It does not decide how your whole library should handle a removal.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is it misleading to keep a quote that names a removed feature?
It depends on what the reader takes from it. If the result it describes is still available, the quote is honest about outcome. If a buyer would expect the named feature, take it off pages for new buyers.
A customer just sent praise for a feature we retired. Should we publish it?
Usually not. Thank them, tell them what replaced it, and leave the testimonial unapproved. If they later praise the new way, that is the one to publish.
Can we add a note under the quote saying the feature changed?
This page does not claim a field for notes under a testimonial. Asking the customer for an updated version is cleaner than explaining an old one.
Should we delete quotes about removed features?
Keep a record. Remove the quote from widgets, and keep it in your library or an exported file, so you know who valued the old feature if you ever bring it back.
Still have a question? Ask the StoryProof team or book a demo.
Publish praise for what you sell today
Hold each testimonial for approval, tag what it mentions and choose where it appears, widget by widget.
Last updated 2026-11-20.