Respecting a no
Track Customers Who Declined Testimonials
A customer who says “no thanks” to a testimonial request is usually still a happy customer. Ask again next month because nobody wrote the answer down and you risk turning them into an annoyed one. Not every no means the same thing, either: “not on video”, “not with my name” and “not now” each leave a door open. The checklist below sets up a simple record your whole team respects.
- Four kinds of no, recorded differently
- A check before every send
- A clear rule for when, if ever, to ask again
The problem, solved
How a no gets lost, and how StoryProof helps you honour it
They said no, and we asked again
The refusal came in a reply email to one person. The next quarter’s campaign went to the same list.
With StoryProof: StoryProof only emails the contacts you add. Build each send from your list after removing everyone on your declined record, and they will not hear from it.
Reminders kept coming after their reply
The customer answered your request by email saying no, but the automated reminders did not know that.
With StoryProof: From Pro, the follow-up sequence skips anyone who unsubscribed and stops when a testimonial arrives. A reply saying no does neither, so point decliners to the unsubscribe link or keep them out of automated sends.
They refused video, so we never asked again
“I hate being on camera” got logged as “declined”, and a customer who would happily write two lines was written off.
With StoryProof: Record the format they refused, not just “no”. The same link lets them write or leave an audio note instead of filming.
They did not want their name used
A customer was happy to praise you but not to be identified, and the team took that as a refusal.
With StoryProof: Nothing submitted goes public until you approve it, so you can accept their testimonial and agree how it will be attributed before it appears anywhere.
Flip the switch to see how StoryProof handles each one.
Team checklist
Set up a declined record your team will use
Tick each item once it is agreed and in place. Share the summary with everyone who sends requests.
Ticks stay in this tab. Nothing is stored or sent.
What each answer lets you do next
In StoryProof
Run every send against the record
- You will need
- The declined record from the checklist
- Your current list of customers to ask
- 1
Filter the list before adding contacts
Remove permanent and in date “not now” entries, then add the rest as contacts. Requests only go to people you add.
- 2
Send by email and let reminders run
From Pro, reminders stop once a testimonial arrives and skip anyone who unsubscribed.
- 3
Log every reply that says no
When someone answers with a refusal, the person who reads it adds it to the record that day, with the kind of no.
- 4
Offer the softer option where it fits
For a format or name refusal, reply once offering written or audio, or an attribution they are comfortable with.
What happens next: Once a quarter, check the “not now” dates. Ask those customers once, and if they say no again, record it as permanent.
Before you start
What StoryProof does not do here
It has no do not ask flag we can promise
We cannot point to a verified setting that marks a contact as declined. Keep the record in your CRM or a shared sheet and filter before you add contacts.
It cannot read a reply
A customer who answers your email with “no thanks” is not unsubscribed. A person has to log it and keep them out of later sends.
Other tools may still email them
Your record only works if everyone who asks for testimonials checks it, including people sending from their own inbox.
Local privacy rules may apply
A record of who refused is still personal data. Keep only what you need and follow the data rules where you operate.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I ever ask a customer again after they declined?
Only if they said “not now”, and only once, after the date you agreed. A clear “please don’t ask again” is permanent.
Is a no reply the same as declining?
No. Silence usually means busy. Let the normal reminders finish, then leave it until your usual request cycle comes round.
Where should we keep the list of customers who declined?
Wherever your team already looks before contacting a customer, usually the CRM or help desk record. A separate sheet nobody opens will be ignored.
How should we reply when a customer says no?
Thank them, tell them you will not ask again, and stop. If they refused only video or only their name, you can offer the alternative once in the same reply.
Still have a question? Ask the StoryProof team or book a demo.
Ask the willing, leave the rest alone
Send requests only to the contacts you choose, with reminders that stop when they should.
Last updated 2026-11-11.