Skip people who said yes
Stop Asking Customers Who Already Reviewed
Nothing undoes the goodwill of a lovely testimonial faster than an email two weeks later asking for one. It happens when a reminder keeps running, a second automation fires, or someone sends a batch from an old list. The fix is a few rules that recognise a reviewer and leave them alone, set once and checked with your own address.
- Where repeat asks to reviewers come from
- The skip rule, the stop rule and a reviewer tag
- The cases no rule can see, such as a second email address
The problem, solved
Where reviewers get asked again, and how to stop it
Most fixes need automations, from Pro. The contact record they rely on is on every plan.
Situation 1 of 5
A new order triggers another request
A happy customer buys again, and the post-purchase automation asks them as if for the first time.
How StoryProof solves it
Use a review request step that skips anyone who has already reviewed or was asked recently.
Situation 2 of 5
The reminder went out after they replied
A homemade sequence of plain emails does not know the customer already answered.
How StoryProof solves it
The ready-made follow-ups stop as soon as the customer leaves a testimonial. Build on that rather than a fixed series of emails.
Situation 3 of 5
We cannot see who already reviewed
Before a manual batch, nobody can tell reviewers from everyone else in the contact list.
How StoryProof solves it
Start an automation when a testimonial is received and have it tag the contact or add it to a Smart List of reviewers.
Situation 4 of 5
A completed request should close the loop
Customers who finish the form are sometimes still sitting in other sequences.
How StoryProof solves it
Automations can also start when a request is completed, which is another point to tag the contact or take it off a list.
Situation 5 of 5
A reviewer complains, and we cannot see why
Without a record, the same leak happens again next month.
How StoryProof solves it
Logs show each enrolment and every step that ran, with the reason a run ended. They are kept for 30 days.
Leak audit
Find every route by which reviewers get asked again
Go through each route. Any box you cannot tick is a place a reviewer can still be asked.
Ticks stay in your browser.
Sample setup for a small online shop
Illustrative setup, not a real customer
A shop runs one automation that asks a week after each order, and one that thanks reviewers.
The ask uses a review request step that skips people who already reviewed. The thank-you automation, started when a testimonial is received, also adds the tag reviewed.
Before the yearly batch to all past buyers, the owner removes everyone tagged reviewed from the send list.
- Trigger 1
- Order webhook, then a review request step with the skip rule
- Trigger 2
- Testimonial received, then add tag “reviewed”
- Manual batch
- Contacts without the tag only
In StoryProof
Fix it in four moves
- 1
Keep every customer as one contact
Contacts and Smart Lists are on every plan; skips and tags work on that record.
- 2
Turn on the skip in every ask
Replace plain asking emails with a review request step that skips people who already reviewed.
- 3
Tag reviewers automatically
A small automation, started when a testimonial is received, adds the agreed tag or Smart List.
- 4
Test with your own contact, then publish
Tests run every step for real. Review yourself once, trigger an ask again and read the log.
What happens next: If you later want a reviewer’s story about something new, that is a deliberate fresh ask, not a repeat. Remove the tag for that person on purpose.
Before you start
What no rule can see
A different email address
If a customer reviewed under another address, the skip and the tag will not know it is the same person.
Reviews on other platforms
A review left directly on Google or elsewhere is not something these rules detect.
Sends outside StoryProof
Your CRM or email platform does not see StoryProof’s skip rule. Use the tag to exclude reviewers there by hand.
The skip belongs to one step
The skip is described for the review request step, so do not rely on it for any other email that asks for a testimonial.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does StoryProof skip people who already reviewed automatically?
A review request step in an automation can skip anyone who has already reviewed or was asked recently. Use that step for every ask rather than a plain email.
What if the customer reviewed under a work and a personal email?
They are two contacts as far as the rules are concerned. Merge your own records where you can, or handle known cases by hand.
Do reminders stop when someone replies?
The ready-made follow-ups stop as soon as the customer leaves a testimonial. Sequences of plain emails you build yourself need the same care.
Can I ever ask a reviewer again?
Yes, for something genuinely new, such as a later project. Make it a deliberate ask rather than the same request repeating.
Still have a question? Ask the StoryProof team or book a demo.
Thank reviewers instead of asking them again
Skip people who already reviewed and tag them automatically, so your asks only go to people who have not answered.
Last updated 2026-11-18.