Your first automation, picked for your bottleneck
Choose a Testimonial Automation Template
A gallery of ready-made flows is only useful if you know which one fixes the thing that is actually slowing you down. Tell the helper below where testimonials get stuck today, and it names the single template to open first, what to change in it before you publish, and which one to add after that.
- Four questions about where testimonials stall
- One template to publish first, one to add next
- What to edit before anything runs
Template picker
Which template should you open first?
Answer for the way your business runs today, not the way you hope it will. The helper weighs your answers and names one template, plus a runner-up to add once the first is running cleanly.
Your answers stay in this browser tab. Nothing is saved or sent.
The problem, solved
Why teams stall at the template gallery, and what each template fixes
Automations are available from Pro. Every fix below stays inside what the templates and the builder are documented to do.
- Problem 1
We opened the gallery and froze
Several flows look useful, so the team publishes none of them while it debates, or all of them at once and cannot tell which one sent what.
How StoryProof solves it
A template creates a flow on the visual canvas that you can read and edit. Work saves automatically and nothing runs until you publish, so open one, study it and publish only that.
- Problem 2
Our reminders feel like nagging
Manual chasers go out late, twice, or to someone who already replied, and that is how a happy customer becomes an annoyed one.
How StoryProof solves it
The follow-ups template waits three days, reminds, waits four more and sends a last email. It stops when the customer leaves a testimonial and skips anyone who unsubscribed.
- Problem 3
Orders happen in a tool StoryProof cannot see
The moment to ask is the order, but the order lives in your shop or billing system, not in your testimonial tool.
How StoryProof solves it
Every automation has its own secure webhook URL. Your shop, or a Zapier or Make step, calls it when an order is placed and the customer gets a request a week later.
- Problem 4
Every review waits for one person
Good testimonials sit unapproved for days because the only person who approves them is busy.
How StoryProof solves it
The auto-approve template approves 4 and 5 star testimonials that include text and leaves the rest in your queue for a person.
- Problem 5
A two star review sat unseen
A low rating that nobody reads for a week turns a fixable complaint into a lost customer.
How StoryProof solves it
The low rating follow-up sends your team an urgent alert for a review of 2 stars or fewer and sends the customer a personal apology email.
- Problem 6
The template almost fits, but not quite
Your reminder gap is five days, not three, or you want a different email for different customers.
How StoryProof solves it
Edit the flow: change the waits, add a condition with up to eight named branches, and write each email with merge tags so it reads like you.
The five templates this page can describe, side by side
Only templates whose behaviour is documented are listed here. Check the gallery in the app for the others.
In StoryProof
From chosen template to a running automation
- 1
Open only the template you picked
Create it from the gallery and read every step on the canvas before you change anything. Nothing runs while it is unpublished.
- 2
Rewrite the emails and adjust the waits
Replace the stock wording with your own and use merge tags for the customer’s name. Change any wait that does not match your sales cycle.
- 3
Set quiet hours
Limit sending to working hours, skip weekends if your customers do, and cap how often one person hears from you.
- 4
Test on yourself, then publish
A test runs every step for real, emails included, so run it on your own contact. Publish once the test did what you expected.
- 5
Read the logs after a week
Check who was enrolled, which steps ran and why each run ended. Add your runner-up template only when the first one looks right.
What happens next: One automation you understand beats five you are guessing about. Add the next template when the first has run for a week without surprises.
Before you start
What to know before you choose
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Automations need a paid plan
Templates and the builder are available from Pro. On a lower plan, the picker still tells you what to aim for.
- 02
The purchase template needs a webhook
There is no native shop integration behind it. Your shop or billing tool must call the automation’s URL, directly or through Zapier or Make.
- 03
A test is not a dry run
Running a test performs every step for real. Use your own contact, never a customer’s.
- 04
Templates are starting points
The stock wording and waits are generic. A template published unedited sounds like everyone else’s.
- 05
Not every template is described here
This page covers only templates whose behaviour is documented. Read any other template on the canvas before you trust it.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I publish several templates at once?
Start with one. If two automations email the same customer in the same week, you will not know which one caused a complaint or a reply.
Can I change a template after creating it?
Yes. A template creates a normal flow on the canvas, and you can edit its steps, waits, conditions and emails like any automation you built yourself.
Which template is safest to start with?
The thank-you template only writes to customers whose testimonial you already approved, so it carries little risk and shows you how the builder behaves.
Do templates send anything before I publish?
No. Nothing runs until you publish. The exception is a test you start yourself, which runs every step for real.
Still have a question? Ask the StoryProof team or book a demo.
Publish your first automation this week
Pick one template, make the wording yours, test it on yourself and let it run.