Silence is an answer to that ask
Try Another Ask After No Response
When a customer ignores a request and its reminders, sending the same email again rarely changes the result. The ask itself needs to change: who it comes from, how long it is, what you are asking for. From Pro, an automation can notice the silence, sort those contacts into a list, and try a different approach on a separate path.
- Starts when a request gets no response
- Moves quiet contacts to their own list
- A different ask, not the same email again
The problem, solved
When the reminders have run out
Situation 1 of 5
Half our customers never answered
The request and its reminders all went out, and the silent pile keeps growing with nobody deciding what to do about it.
How StoryProof solves it
From Pro, an automation can start when a review request gets no response after a number of days you choose.
Situation 2 of 5
The quiet ones are mixed in with everyone
Without a way to see who went silent, nobody can plan a second approach for them.
How StoryProof solves it
The same flow can add a tag or move the contact into a Smart List, so the quiet group is visible and countable.
Situation 3 of 5
Sending it again feels pointless
The same subject and the same ask from the same address will most likely meet the same silence.
How StoryProof solves it
A second automation can start when a contact joins that list and send a changed ask: shorter, from a named person, or offering a voice note or a few written lines instead of video.
Situation 4 of 5
Which new approach should we try?
Everyone in the team has a theory, and nobody can tell which one is right.
How StoryProof solves it
Send people down percentage-based paths to test two different asks against each other on the same quiet group.
Situation 5 of 5
I do not want to pester anyone
A customer who ignored three emails can turn from neutral to annoyed with a fourth.
How StoryProof solves it
Cap how often one person hears from you, and the request step skips anyone already asked recently.
Dated plan
Map the second attempt
Pick the day the first request went out. The plan assumes the standard reminders run first, then shows when the quiet group moves and the new ask goes out.
Day 0
First request
The original ask goes out.
Day +3
Standard reminder
The follow-up flow sends its first reminder.
Day +7
Last reminder
The follow-up flow sends its last email and stops.
Day +14
No response trigger fires
Contacts still silent get a tag and move into a "quiet" Smart List.
Day +21
The different ask
Joining the list starts a second flow. Half get a two-line note from a named person, half get an ask for one written sentence.
Day +35
Compare and stop
Look at which path produced more testimonials. Anyone still silent is left alone.
Dates are worked out in your browser. Nothing is saved or sent.
In StoryProof
Set up the change of approach
- 1
Let the standard reminders finish
The review request follow-ups template waits three days, sends a reminder, waits four more and sends a last email. Leave it to finish before the second approach starts.
- 2
Catch the silence
Build a flow on the no-response trigger, with a number of days that falls after the last reminder.
- 3
Move the contact
Add the contact to the quiet Smart List and tag them, so you can see the group and filter on it later.
- 4
Start the new ask from the list
In a second automation, start when a contact joins that list. Split the group by percentage and send two different asks.
- 5
Cap contact and send within working hours
Set quiet hours and a limit per person on both flows before you publish.
What happens next: Keep the winning ask, and remove people from the quiet list when they finally answer.
Before you start
What a second approach cannot do
It will not reach everyone
Some customers do not want to give a testimonial. A different ask finds the ones who were busy, not the ones who said no by staying silent.
Email is the only channel
The new approach changes the wording and sender, not the channel. Requests are sent by email.
Check the address first
Silence can also mean the email never arrived. Rule out bounces and spam folders before changing the message.
Small groups give noisy results
An AB split on a handful of contacts can point the wrong way by chance. Let it run long enough to compare.
Needs automations
Triggers, lists and splits in flows are part of automations, from Pro.
FAQ
Questions people ask
Short answers to what usually comes up next.
How many days of silence should start the second approach?
Pick a number that falls after your last reminder, so the two flows do not overlap. The plan above uses two weeks from the first request.
What kinds of different ask work?
Change one thing clearly: a shorter message, a named person as sender, or a smaller request such as one written sentence instead of a video.
Is it rude to ask again after no reply?
One changed ask, sent at a sensible hour, is reasonable. Repeated asks are not. Cap messages per person and stop after the second approach.
Can I see who is in the quiet group?
Yes. Once the automation moves them into a Smart List or tags them, the group is visible in your contacts.
Still have a question? Ask the StoryProof team or book a demo.
Turn silence into a better second ask
Spot the quiet contacts automatically and try something different with them.
Last updated 2026-11-18.