Smart List trigger
Request Testimonials When Contacts Join Lists
A Smart List is usually a decision someone already made: these customers are ready. From Pro, joining that list can start an automation that waits, sends the review request and follows up, so the decision turns into an ask without a second step.
- A dated plan from the day a contact joins
- One request, two reminders, then stop
- Sends only in the hours you allow
The problem, solved
When a list is ready but nobody sends the ask
The ready list keeps growing, nobody asks
Sorting customers into a list feels like progress, but the request still waits for someone to open a campaign.
With StoryProof: From Pro, an automation can start the moment a contact joins a Smart List, so each person is asked without a separate send.
They were added during a call, asking now feels rushed
A request that lands while the customer is still on the phone with you reads as automatic, because it is.
With StoryProof: Put a wait before the send step: hours, days, or until a set weekday and time.
Some of them were asked last month
A contact can join a list more than once, or already be in another campaign, and a repeat ask feels careless.
With StoryProof: Use the review request action, which skips anyone who has already reviewed or was asked recently.
One email gets lost in a busy inbox
People often mean to reply and then do not. Chasing them by hand does not scale past a handful.
With StoryProof: The follow-up sequence waits three days, reminds, waits four more and sends a last email, stopping as soon as they leave a testimonial.
People get added at all hours
A contact added late on a Friday should not get a request at midnight.
With StoryProof: Limit sending to working hours, skip weekends and use each recipient’s timezone.
Flip the switch to see how StoryProof handles each one.
Dated plan
See what each contact will receive
Pick the day a contact joins the list. This is the plan the automation follows, so share it with whoever adds people to the list.
Day 0
Joins the Smart List
The automation enrols the contact. Nothing is sent yet; the wait step begins.
Day +1
Review request goes out
Sent inside your quiet hours. Skipped automatically if they already reviewed or were asked recently.
Day +4
First reminder
Three days after the request, only if they have not left a testimonial.
Day +8
Last email
Four days after the reminder. After this the sequence stops on its own.
Day +9
Check the run
Open the logs for this contact to see which steps ran and why the run ended.
Day +15
Decide on the quiet ones
Contacts who never replied can be moved to another list for a different approach later.
Dates are worked out in your browser. Nothing you pick is saved.
In StoryProof
Build the list-triggered request
- You will need
- A StoryProof workspace on Pro or above
- A Smart List that means ready to ask
- A collection form for the request to link to
- 1
Choose the trigger
In the automation builder, start from a contact joining a Smart List and pick the list.
- 2
Wait, then send the request
Add a one-day wait and the review request action. Requests go by email.
- 3
Add the follow-ups and quiet hours
Add the reminder and last email, and set working hours, weekend skipping and recipient timezones in the automation’s settings.
- 4
Optionally tidy the list
At the end of the flow, remove the contact from the ready list or add a tag, so the list shows who is still waiting.
- 5
Test with your own contact, then publish
Add yourself to the list after publishing, or run a test on your own contact: a test sends every email for real.
What happens next: Tell everyone who adds people to the list that adding them now sends a request.
Before you start
Things to know before you rely on it
Joining is the trigger
People already on the list when you publish are not covered by this page. Ask them with a separate campaign.
Email only
Requests are sent by email. There is no text message step.
A big addition means a big send
Adding hundreds of contacts at once enrols them all. Quiet hours only decide when emails may go out, so check your plan’s monthly request email quota first.
How contacts reach the list is up to you
Contacts and Smart Lists are on every plan. This page does not describe the list rules themselves, only what happens after someone joins.
Automations plan
The trigger and the follow-ups need Pro or above.
FAQ
Questions people ask
Short answers to what usually comes up next.
What happens if someone leaves the list mid-sequence?
Do not assume the run stops. Leaving a list can start a separate automation, and the logs show why each run ended, so check one before relying on it.
Can another automation add people to the list?
Yes. Automations can add or remove Smart Lists, so a different trigger can feed this one.
Why wait a day before asking?
Most lists are filled right after an interaction. A short pause makes the request feel considered rather than instant.
Can two lists use different wording?
Build one automation per list, each with its own request and reminders.
Still have a question? Ask the StoryProof team or book a demo.
Turn a list into requests
Keep customers in StoryProof Smart Lists and let joining one start the ask.
Last updated 2026-11-18.