Not every ask should be a robot, or a person
Automated or Manual Testimonial Requests
A personal note from the founder and an automated request triggered by an order are both good asks, for different customers. The mistake is choosing one style for everybody. Answer the questions below and the helper splits your requests: which ones to hand to an automation, which ones a person should write, and where the two meet.
- Five questions about customers and volume
- Automated, personal or a mix of both
- Where a person hands off to the automation
Request style decider
Should this group get an automated or a personal ask?
Run it once per customer group, for example new buyers, retainer clients and partners. The answer is a starting point for that group, not a rule for your whole business.
Answers stay in this browser tab. Nothing is saved or sent.
The problem, solved
The trade-offs, and what StoryProof gives each side
Automations are available from Pro. Personal asks work on every plan.
- Problem 1
Personal asks keep getting forgotten
The person who meant to write to each new customer had a busy month, and twenty good moments passed.
How StoryProof solves it
An automation can start from an event such as a request going unanswered for a number of days, or run daily, weekly or monthly, so the moment no longer depends on memory.
- Problem 2
Our best clients deserve a real note
A big account that gets the same template as a one-off buyer reads it as a sign of how much you value them.
How StoryProof solves it
Keep the first ask personal and share your collection link by hand. The link works the same however it reaches them.
- Problem 3
We want personal asks but automatic reminders
The founder will write the first note, but nobody will chase three days later.
How StoryProof solves it
An automation can start when you add people by hand. Add the customer once the personal note is sent; the flow waits for a testimonial and reminds only if none arrived.
- Problem 4
Automated asks hit people we already asked
A personal request and an automated one land in the same week, and the customer wonders whether anyone talks to each other.
How StoryProof solves it
Use the review request action, which skips anyone who has already reviewed or was asked recently, and cap how often one person hears from you.
- Problem 5
The trigger lives in another tool
Orders and paid invoices are recorded in your shop or billing system, so an automation cannot see the moment.
How StoryProof solves it
Each automation has its own secure webhook URL that your other tool, or a Zapier or Make step, can call when the event happens.
Automated and personal asks compared
In StoryProof
Put the split into practice
- 1
Keep every group in your contacts
Contacts and Smart Lists are on every plan, so automated and personal groups can sit side by side in one place.
- 2
Automate the high-volume groups
Start a request from the event that marks the moment, with reminders and quiet hours set before you publish.
- 3
Write the personal asks yourself
For high-stakes groups, a named person sends a short note with the collection link. Requests from StoryProof go by email; the personal note can go however you normally speak to that client.
- 4
Hand off the reminders
For hybrid groups, add the customer to the reminder automation by hand once the personal note has gone.
What happens next: Revisit the split when a group grows. A group that was five customers a month last year may be thirty now.
Before you start
What to weigh before you switch
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Automation is on paid plans
Automations start at Pro. On a lower plan, the hybrid becomes a personal ask plus a calendar reminder.
- 02
Requests use a monthly allowance
Review request emails are counted per month, so a high-volume automation needs a plan whose allowance covers it.
- 03
Email only from StoryProof
StoryProof sends requests by email, not SMS. A personal ask in another channel has to come from you.
- 04
The helper is a rule of thumb
Scores come from your answers, not from response data. Watch who actually replies and adjust.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do automated requests get fewer replies than personal ones?
We do not publish response figures. Compare your own: run both styles for a few weeks and count testimonials received from each group.
Can I personalise an automated request?
Emails sent by an automation support merge tags, such as the customer’s name. That makes it addressed to them, though it is still the same template.
What if someone gets both a personal and an automated ask?
Use the review request action that skips people asked recently, and add hybrid customers to the automation only after the personal note is sent.
Is a hybrid more work than either style alone?
Slightly more to set up, less to run. The person writes one note per customer and never has to remember to chase.
Still have a question? Ask the StoryProof team or book a demo.
Automate the asks that do not need you
Keep the personal notes for the clients who deserve them, and let reminders run on their own.