When customers would rather nobody knew
Discreet Testimonials for Sensitive Services
Some customers are delighted with you and mortified at the idea of anyone finding out they needed you. Debt advice, pest control, dating coaching and similar services all hit this. Answer four questions below to pick how much a testimonial should reveal, then ask in a way that lets the customer stay comfortable.
- Four questions about the customer and the story
- A recommended level of disclosure, with a fallback
- Wording to offer customers who hesitate
The problem, solved
Why grateful customers still say no
The service worked. The hesitation is about who might see their name next to it.
Situation 1 of 5
They loved it but will not be named
Admitting to debt trouble or an infestation feels like admitting to a personal failing, even when the outcome was good.
How StoryProof solves it
Offer the level of disclosure in the request itself, then hold the reply in your queue. Nothing they send is published until you approve it.
Situation 2 of 5
Video is out of the question
A face on camera is the most identifying thing a customer can give you, and the first thing a reluctant customer refuses.
How StoryProof solves it
The same link lets them type a few lines instead, with no camera involved and nothing to install.
Situation 3 of 5
They worry others will see the request
A request that arrives on a shared device or in front of family can expose the very thing they want kept quiet.
How StoryProof solves it
StoryProof sends requests to the email address you hold for them, never as a text message, so you control where it lands.
Situation 4 of 5
I lose track of who agreed to what
One customer is happy with a first name, another only with "a homeowner in Leeds". Mixing them up breaks a promise.
How StoryProof solves it
Tag each testimonial with the disclosure level the customer agreed, such as "first name only" or "description only", before approving it.
Situation 5 of 5
Fine on one page, not on the homepage
A customer may accept a quote on a detailed service page but not on the first thing every visitor sees.
How StoryProof solves it
You choose which approved testimonials each widget shows, so a guarded quote stays on the page the customer accepted.
Disclosure picker
How much should this testimonial reveal?
Answer for one customer at a time. The result is a starting point to offer them, not a decision to make on their behalf.
Your answers are scored in this browser tab. Nothing is stored.
Prompts
Wording that lowers the stakes
Say early what will and will not be shown. Customers relax when the privacy question is answered before they ask it.
When you first ask
- Would you share a line or two about how things went? You choose how you are named, or whether you are named at all.
- Lots of our customers prefer just a first name, or no name. That is completely fine.
Leave out
- Can we feature you on our homepage?
- Could you record a quick video for us?
When they hesitate
- We could say "a customer in {area}" and nothing more. Would that feel all right?
- If you would rather not, no problem at all. Your feedback has already helped us.
Leave out
- Nobody will ever know it is you.
Questions that keep the focus on the service
- What made you feel at ease when you first contacted us?
- How did we handle things so it felt discreet?
- What would you tell someone who is putting off calling a service like ours?
In StoryProof
Collect it discreetly with StoryProof
- 1
Send the request privately
Email the collection link to the address they chose. Say in the message how they will be named.
- 2
Let them pick a low exposure format
They can write a few lines or leave an audio note in the browser rather than appearing on video.
- 3
Check it before approving
Read the reply for details that would identify them, such as a street, an employer or a family name. Ask them to resubmit if it gives too much away.
- 4
Label the agreed level and place it
Tag it with the disclosure level, approve it, and add it only to the widgets on pages the customer accepted.
What happens next: If a customer later asks to be less visible, take the testimonial off the widgets it appears in and ask whether they would like to resubmit at a lower level.
Before you start
Where discretion has limits
StoryProof does not rewrite names
What the customer submits is what you approve. Agree how they will be named before they fill in the form, rather than planning to change it afterwards.
No medical or health services
This page is not for clinics or treatment. Health information carries its own rules that a discretion picker does not address.
Unnamed carries less weight
A description persuades less than a name and a face. That is the trade for the customer’s comfort, and it is worth making.
Details can identify people
A first name plus a small town and a specific event can point straight to one person. Read every reply as a neighbour would.
Never invent the missing parts
If a customer will not be named, do not attach a made up name or stock photo to make the quote look fuller.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is an unnamed testimonial still worth publishing?
Yes, if the text is specific about the service. A clear description of what you did and how it felt tells a nervous prospect more than a named one liner would.
Can I use a made up first name to make it feel personal?
No. A name that is not theirs misleads the reader. Use the customer’s real first name if they agree, or a description if they do not.
Should I mention the problem in the testimonial at all?
Only as far as the customer is comfortable. Many reluctant customers will happily praise how discreet and respectful you were without describing what they needed.
Do sensitive services need a different collection form?
Not necessarily. What matters is that the request explains the naming choice before they start, and that you check every reply before it is published.
Still have a question? Ask the StoryProof team or book a demo.
Ask without putting anyone on the spot
Send a private request, collect a few written lines or an audio note, and publish only at the level each customer agreed.
Last updated 2026-11-07.