One email a week, on time
Weekly Digest of New Testimonials
A weekly round-up of new testimonials is the easiest way to keep a whole team close to what customers say, and the easiest habit to drop. It slips the first busy Friday and never comes back. From Pro, two small automations hold it in place: one labels each new testimonial as it arrives, the other runs every week and emails the team that the digest is due. A person still writes it, but the batch is ready and the reminder never forgets.
- A label on every new testimonial for the week
- A weekly scheduled email that says it is digest day
- A four-week plan to make the habit stick
The problem, solved
Why weekly digests stop, and what keeps them going
We missed a week, then a month
The digest lives in one person’s head, and one busy Friday breaks the habit for good.
With StoryProof: From Pro, an automation can run weekly and email up to ten teammates, so the digest day announces itself.
Gathering the week’s reviews takes too long
Scrolling back through everything to find what came in since last Friday is the part people dread.
With StoryProof: A second automation can start when a testimonial is received and add a label, so the week’s batch is ready to filter.
The digest is just a list of quotes
Quotes without context do not tell the team whether things are getting better or worse.
With StoryProof: Analytics show how many testimonials you collect, their ratings, sources and approval rate, so two lines of numbers can open the digest.
Did the weekly email actually go?
If the reminder silently stopped, nobody would notice for weeks.
With StoryProof: Logs show every run and every step, with the reason a run ended. They are kept for 30 days.
Flip the switch to see how StoryProof handles each one.
Four-week plan
Set up the digest and make it stick
Pick the day you set it up. The plan shows when each step happens over the first month.
Day 0
Build the label flow
Start on testimonial received, add a label such as this week.
Day 0
Build the weekly schedule
A weekly automation emails the writer and readers that the digest is due.
Day +7
First digest
Filter by the label, pick three to five testimonials, add numbers from analytics, send. Remove the label from the batch.
Day +14
Second digest
Same routine. Note how long it took.
Day +21
Check the logs
Confirm both automations ran each week.
Day +28
Ask the readers
Is it too long, too short, missing something? Adjust the format once.
Dates are worked out in your browser. Nothing is saved or sent.
In StoryProof
Build the two automations
- You will need
- A StoryProof workspace on Pro or above
- A label name for the week’s testimonials
- One person who writes the digest
- 1
Label every new testimonial
In the automation builder, start when a testimonial is received and add the digest label.
- 2
Schedule the weekly reminder
Create a second automation that runs weekly, and add a team email to the writer and readers saying the digest is due.
- 3
Write the digest from the batch
Filter by the label, choose the best few, open with the week’s numbers from analytics, and send it.
- 4
Clear the label
Remove the label from the batch you used so next week starts empty.
- 5
Publish both, then check runs
Nothing runs until you publish. After the first week, read the logs to confirm both ran.
What happens next: Keep the digest short. Three quotes and two numbers get read; twenty quotes do not.
Before you start
What the schedule does not do
It does not write the digest
The scheduled email is a reminder. It does not collect the testimonials into a summary; a person does that.
Labels need clearing
This page does not claim the label clears itself. Remove it by hand after each digest.
Ten teammates per email
Reminder emails go to up to ten teammates. Forward the finished digest to a wider group yourself.
Needs automations
Schedules and labels in flows are part of automations, from Pro.
Logs last 30 days
Check runs within the month if you want proof they happened.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does StoryProof write the weekly digest for me?
No. The scheduled automation reminds the team that it is due and the label gathers the week’s testimonials. A person picks the quotes and writes it.
What should a weekly testimonial digest include?
The week’s count and average rating, then three to five quotes that show something new. Name the people customers praised.
Which day should it go out?
Whichever day the team reads email calmly. Many teams choose Monday morning or Friday afternoon. Set the schedule to match.
Can it go to the whole company?
The reminder reaches up to ten teammates. Send the finished digest to a wider list yourself.
Still have a question? Ask the StoryProof team or book a demo.
Keep the weekly digest on time
Label every new testimonial and let a weekly schedule remind the team.
Last updated 2026-11-18.