Diagnose the request, not the customer
Why Customers Ignore Testimonial Requests
Happy customers who never answer are rarely being rude. Something in the request made "later" the easy choice: it came from a brand address, landed a month after anything good happened, or asked for an essay with no clue how long it would take. Score the last request you sent and find which of those it was before you send another.
- Score one request you already sent
- See the faults costing you replies
- A fix for each, in plain terms
The problem, solved
The usual reasons a request gets ignored
Most ignored requests fail on one of these before the customer reads a word of the body.
Situation 1 of 6
We sent it to the whole list
People whose last contact with you was a year ago have no fresh story, and a blast tells everyone it is a mass email.
How StoryProof solves it
Keep contacts in smart lists and send to the group that just had a good moment, such as a finished project or a renewal.
Situation 2 of 6
They said yes but never wrote it
A blank box asking for "a few words" turns into homework. The customer plans to do it properly later, and later never comes.
How StoryProof solves it
From Pro, a multi-step form asks one short question at a time, so nobody faces an empty page.
Situation 3 of 6
Our customers hate writing things
Some people talk far more easily than they type, especially on a phone.
How StoryProof solves it
One link takes a typed answer, an audio note or a short video in the browser, so the customer picks the format that costs them least.
Situation 4 of 6
Many customers do not read English well
A form in a second language feels like a test, and people skip tests.
How StoryProof solves it
Collection forms come in several languages on every plan, so the form can match the customer.
Situation 5 of 6
They worry it goes straight online
A customer unsure how their words will appear holds back, or writes nothing.
How StoryProof solves it
Say so in the request: nothing they submit goes public until you approve it, and you will check with them before using their name.
Situation 6 of 6
One email and then nothing
A good request read at a bad moment is gone by the next morning.
How StoryProof solves it
From Pro, follow ups send a reminder after three days and a last email four days later, and stop once a testimonial arrives.
Request scorecard
Score the last request you sent
Open the actual email and the actual form. Mark each line yes, partly or no for what was really sent, not what you meant to send.
Scored in your browser. Nothing you select is sent or saved.
Read the silence
Where the request dies tells you which part to fix.
Before you start
What a better request will not change
Unhappy customers stay quiet
If the experience was average, no wording produces a testimonial. Low replies can be a product signal, not a request problem.
Reminders do not fix a bad request
Following up on a request that scored low just repeats the fault. Fix the request first, then add the reminder.
Email only
StoryProof sends requests by email. If your customers live in chat apps, share the link there yourself.
Some silence is normal
Even a well built request goes unanswered by plenty of people. Aim for a better share, not for everyone.
In StoryProof
Rebuild the request in StoryProof
- 1
Build a smart list of recent wins
Add contacts with something fresh to say, instead of sending to everyone.
- 2
Shorten what you ask for
Turn the open box into three short questions. From Pro, a multi-step form shows them one at a time.
- 3
Offer a voice or video answer
The same link accepts audio and video as well as text, recorded in the browser.
- 4
Send from a person, with one reminder
Email the request signed by someone they know. From Pro, the follow ups automation sends the reminders and stops when they reply.
What happens next: Score the new request with the same card before you send it, and keep both versions so you can compare what came back.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I avoid the word "testimonial"?
It can make the ask sound formal. "Would you tell me how it went?" asks for the same thing and feels lighter. The form can still say testimonial.
Is it the subject line or the timing?
Check opens first. Few opens points at the sender and subject. Plenty of opens with no clicks points at the body, the effort or the moment you chose.
Does offering a reward fix low response?
It can lift replies, but it does not repair a request sent to the wrong people at the wrong time, and it brings disclosure duties. Fix the basics first.
How many requests should I send to judge a change?
Enough that one or two replies do not swing the result. A couple of dozen requests to similar customers gives a rough read.
Still have a question? Ask the StoryProof team or book a demo.
Send a request people answer
Build a short form that takes text, audio or video, and send it from a real person to customers who just had a good moment.
Last updated 2026-11-06.