For people who hate asking
Ask for Testimonials Without Sounding Needy
A request sounds needy when it is about you: how much a review would help, how small your business is, how sorry you are to bother them. It sounds confident when it is about them: what they achieved, one easy way to say it, and permission to skip it. Fill in the details below and the builder writes a request in that second voice, plus a single follow up and a list of phrases to cut from anything you already send.
- Opens with their result, not your need
- Gives an easy way to say no
- One follow up, then silence
Request builder
Write a request that sounds sure of itself
Fill in the one detail that makes this customer’s story theirs. Pick how well you know them; the wording adjusts.
- The request
No apology, no explanation of why reviews help you. Their result comes first.
Subject: [launched the new booking site two weeks early]
Hi [Maya], I keep thinking about how you [launched the new booking site two weeks early]. I would like to share that story with people who are where you were before we started. If you are up for it, this link takes a couple of minutes, and you can write, record a short audio note or film a quick video: [your StoryProof link] One question to start from: [What was it like before the new site?] If it is not for you, no reply needed. Nothing changes between us. [Sam]
- The one follow up
Send once, about a week later, only if they have not answered. Then stop.
Subject: Re: [launched the new booking site two weeks early]
Hi [Maya], Bringing this back to the top of your inbox once, in case it got buried: [your StoryProof link] If you would rather not, that is completely fine, and I will not ask again. [Sam]
- Needy phrases to cut
Search your current templates for these. Each one makes the ask about you.
CUT: "Sorry to bother you, but..." USE: Start with their result. CUT: "It would mean the world to us / really help our small business" USE: "I would like to share your story with people in your position." CUT: "We rely on reviews to survive" USE: Nothing. They do not need your reasons. CUT: "Just following up again..." (third time) USE: One follow up, then stop. CUT: "If you could find it in your heart..." USE: "If you are up for it..." CUT: "Please, it only takes a minute!" USE: Say what the link lets them do, once.
- Saying it in person
For the end of a call or a handover meeting.
"[Maya], you [launched the new booking site two weeks early]. Would you be open to saying that in your own words for people considering us? I will send a link; if it is not your thing, just ignore it."
The text is built in your browser from what you type. Nothing is saved or sent.
The problem, solved
What makes an ask sound needy, and how StoryProof takes the pressure out
- Problem 1
I explain too much, then apologise
Long requests justify themselves because the sender feels they are imposing. The length itself signals that.
How StoryProof solves it
One collection link lets the customer write, leave an audio note or record a video in the browser with no app, so the email only needs a line about what the link does.
- Problem 2
I chase until it feels awkward
Each manual nudge carries a bit more anxiety, and by the third the customer can hear it.
How StoryProof solves it
From Pro, the follow ups automation sends a reminder and a last email at set intervals, and stops the moment the customer leaves a testimonial.
- Problem 3
My request reads like a mass email
A generic message with no detail about the customer sounds like a campaign that needs numbers.
How StoryProof solves it
Automated emails can use merge tags, so each request carries the customer’s name and the detail you stored for them.
- Problem 4
They freeze at a blank box
A customer who does not know what to say feels the pressure you were trying to avoid.
How StoryProof solves it
The recording page shows your prompts beside the camera, so your one question travels with them.
- Problem 5
It lands at a pushy moment
A request at eleven at night or on a Sunday reads as urgent, whatever the wording.
How StoryProof solves it
Automations can send only in working hours, skip weekends and cap how often one person hears from you.
The same request, two voices
Needy
- Sorry to bother you, I know you are busy
- Reviews really help a small business like ours survive
- It would mean so much if you could find a minute
- Just following up again on my last two emails
Confident
- Opens with the customer’s own result
- One line on what the link lets them do
- A stated, guilt free way to say no
- One follow up a week later, then nothing
In StoryProof
Send it from StoryProof
Step 1 of 4
Put your question on the form
Add your one question as a prompt so it shows beside the camera on the recording page.
Step 2 of 4
Paste the request with merge tags
Use the builder text in the request email and replace the name and result with merge tags.
Step 3 of 4
Let the follow up run, once it fits
Use the follow ups automation so reminders stop as soon as the customer replies. Check that its emails match the calm tone of the first one.
Step 4 of 4
Read before anything is shown
Every answer waits for your approval, so a customer who replied out of politeness is never published by accident.
Before you start
What wording cannot do
Tone does not fix timing
A calm request sent to someone in the middle of a problem still lands badly. Ask after a result, not during a dispute.
Two reminders, not one
The built in follow ups automation sends a reminder and a last email. If you want only one follow up, send it by hand instead.
No tone checker
StoryProof does not review the wording of your emails. The swap list is for you to apply.
Some people will say no
A real way out means some customers take it. That is the cost of a request nobody feels pushed by.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is it rude to ask a client for a testimonial?
No. Asking someone to describe a result they are pleased with is a normal part of business. What reads as rude is pressure: repeated chasing, guilt, or no way to decline.
Should I say why I need testimonials?
Briefly at most. One line about sharing their story with people in their position is enough. A paragraph about how reviews help your business turns their favour into your problem.
How many times should I follow up?
Once is enough for a personal ask. If you use an automated sequence, keep its wording as calm as the first email and let it stop the moment they reply.
Does offering a reward make the ask less needy?
Not by itself, and it changes what you are asking for. If you offer anything, offer it whatever they say, and check the rules that apply to incentivised reviews where you publish.
Where do I find more general advice on asking?
The blog post on how to ask for a review covers timing, channel and what to ask. This page only handles the voice of the request.
Still have a question? Ask the StoryProof team or book a demo.
Send a request that sounds like you mean it
Write it around their result, give them a way out, and let the follow up stop the moment they answer.
Last updated 2026-11-20.