One product, one batch, pulled from sale
Testimonial Requests During a Product Recall
A recall touches a defined group: the people who bought one product, or one batch of it. Your request automations do not know that. They keep inviting those buyers to praise the item you have just told them to stop using, and your product page keeps showing a five star quote about it. This checklist splits the work between the marketer and whoever runs the recall, so the testimonial side is quiet within a day and restarts on purpose.
- Requests to affected buyers held first
- Praise for the recalled item found and pulled
- A restart rule written before anyone restarts
Recall checklist
Quiet the testimonial side of a recall
Work through it with the person who owns the recall. Their notice and their list of affected orders come first; this list only covers your proof.
Ticks stay in this browser tab. Nothing is saved or sent.
In StoryProof
Run the recall steps in StoryProof
- You will need
- The list of affected orders or contacts from the recall owner
- Access to your contacts, widgets and automations
- Pro for the automated parts
- 1
Tag the affected buyers
Contacts and Smart Lists are on every plan. Tag the affected contacts and take them out of the lists your requests go to. An automation can add or remove tags and Smart Lists in bulk.
- 2
Find every quote about the item
Export your testimonials as a CSV and search the text for the product and batch names, then tag the matches in your library.
- 3
Take them out of widgets
Filter by the new tag and remove those testimonials from each widget that shows them.
- 4
Route new submissions to a person
Nothing goes public until approved. An automation can start when a testimonial arrives and alert the teammates who are reading the queue during the recall.
- 5
Restart per customer
When a customer’s remedy is done, remove the recall tag and return them to your lists. The request action can still skip anyone asked recently.
What happens next: Keep the recall tag on the testimonials you pulled. If the product returns in a new version, those quotes describe the old one and should stay off its page.
The problem, solved
Recall problems on the testimonial side, and the StoryProof part of each
Affected buyers still get review requests
An order based flow treats a recalled purchase like any other. The customer gets a recall notice and a request for praise in the same week.
With StoryProof: Tag the affected contacts and remove them from the Smart Lists your requests use. An automation can do the tagging and list changes for you.
We cannot find every quote about it
Customers call products by nicknames, sizes and colours, so a search on the official name misses some.
With StoryProof: Export the whole library as a CSV, search it however you like, and tag what you find so it can be filtered later.
The product page still shows praise
A glowing quote beside a recall banner makes the brand look unaware of its own notice.
With StoryProof: You choose which approved testimonials each widget shows, so the tagged quotes come out of each placement.
Recall complaints arrive as submissions
A worried customer uses the testimonial form because it is the link they have. That message belongs with the recall team.
With StoryProof: Submissions wait for approval, so nothing about the recall can publish by accident, and an automation can alert named teammates when one lands.
Flip the switch to see how StoryProof handles each one.
The week after the notice
With the normal flow running
- Recalled buyers get a request a week after their order
- The product page still shows a five star quote about the item
- A complaint arrives through the form and sits beside praise
- Requests restart on the day the recall is closed for everyone
With this checklist done
- Affected contacts are tagged and out of the request lists
- Quotes about the item are tagged and out of every widget
- Recall messages stay unpublished and reach the recall owner
- Each buyer returns to the lists when their own remedy is done
Before you start
Where this checklist stops
Not recall guidance
This page covers testimonials only. What you must tell customers, regulators or retailers is for the recall owner and their advisers.
No product recall flag
StoryProof has no setting that marks a product as recalled. The hold is made of tags and list changes you apply.
Text search is yours
StoryProof does not scan testimonials for a product name. The CSV export lets you search with your own tools.
Copies outside StoryProof
Images, ads and print you made from testimonials are not changed by removing a quote from a widget. List and replace them yourself.
Video mentions are harder
A product named aloud in a video does not show up in a text search. Watch the videos for the affected product before keeping them live.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I stop all testimonial requests during a recall?
Usually only for the affected buyers. Customers of your other products are not part of it, and stopping everything can leave your site looking emptied at the moment people check it.
Can I ask a customer how we handled the recall?
Only after their remedy is complete, and only if the recall owner agrees. Ask about the handling, not the product, and expect some answers you will not publish.
What about a testimonial that praises the recalled product but is otherwise great?
Keep it off every widget while the recall runs. If a fixed version returns, the quote describes the old one, so leave it tagged and unused.
Do I need to delete anything?
This page does not ask you to. Removing the quotes from widgets and keeping new submissions unapproved is enough to stop them showing.
Who should own this checklist?
The person who owns testimonials, working from the affected list that the recall owner provides. Two people with two copies of that list is how buyers get missed.
Still have a question? Ask the StoryProof team or book a demo.
Keep your proof steady through a recall
Tag the affected buyers, pull the quotes about the item and keep the queue in human hands until the remedy is done.
Last updated 2026-11-20.