Proof for one feature at a time
Feature Specific Testimonial Request Templates
Ask a customer what they think of your product and you get “great support, easy to use”. Ask what changed since they started using one feature and you get a sentence your product team can quote. These templates narrow the request to a single feature, timed to when the customer has actually used it.
- Names the feature and the job it does
- Sent after real use, not on launch day
- Questions that stop generic praise
Feature request builder
Ask about one feature
Choose the moment, name the feature and the job it does. The more concrete the job, the more concrete the answer.
- After steady use
Subject: How is [scheduled exports] working for you?
Hi [Tomás], You have been using [scheduled exports] for a few weeks now. I am curious what it has changed for you, especially around [sending the weekly report without anyone touching it]. Would you answer two questions? 1. What did you do before [scheduled exports]? 2. What is different now? A couple of sentences is plenty: [https://your-collection-link] [Rina]
- Short version for busy customers
Subject: One question about [scheduled exports]
Hi [Tomás], one quick question: what would you miss most if [scheduled exports] disappeared tomorrow? Answer here in a line or two: [https://your-collection-link] Thanks, [Rina]
The messages are built in your browser. Nothing you type is saved.
The problem, solved
Why feature testimonials are hard to get, and what StoryProof does
Product teams want proof for the feature they just shipped. These are the reasons they end up with general praise instead.
- Problem 1
Every answer is about the whole product
An open question invites an overall verdict, so the feature you care about never gets named.
How StoryProof solves it
From Pro, a multi-step form asks several questions in one sitting, so one step can be about the feature alone.
- Problem 2
We asked people who never used it
Sending a feature request to the whole customer base gets polite guesses from people who have not touched it.
How StoryProof solves it
Build the list of feature users from your own product data, add them as contacts, and email the request to that list only.
- Problem 3
Feature quotes vanish into the pile
Six months later nobody can find which testimonials mention scheduled exports.
How StoryProof solves it
Tag each approved testimonial with the feature it covers, then choose those for the widget on that feature page.
- Problem 4
Launch feedback includes complaints
Early users report bugs alongside praise, and you do not want the bug report on your feature page.
How StoryProof solves it
Nothing goes public until you approve it, so feedback and testimonials can arrive through the same link and be sorted.
- Problem 5
I want them to show the feature
A quick screen or phone recording of someone using the feature can say more than a paragraph.
How StoryProof solves it
The collection link accepts a video, an audio note or written words, recorded in the browser.
Prompts
Questions that keep the answer on the feature
Use one or two of these in your form or message. Each one makes the customer name the feature or the job it does.
Before and after
- What did you do before this feature existed?
- What do you no longer have to do?
- Who on your team noticed first?
Leave out
- How would you rate the product overall?
Value
- What would you miss if it disappeared?
- Which task does it make faster, and how did that task go before?
Leave out
- Would you recommend us? (too broad)
- Questions that suggest a number for them to agree with
In StoryProof
Run a feature request in StoryProof
Step 1 of 4
Add the feature users as contacts
Add the people who used it as contacts, and keep them together in a list for this feature.
Step 2 of 4
Make a form step about the feature
From Pro, add a step with one of the questions above. On other plans, put the question in the email.
Step 3 of 4
Send the request
Email the list with a template above, after they have had a few weeks with the feature.
Step 4 of 4
Approve, tag by feature, place
Approve the answers that name the feature, tag them, and choose them for the feature page widget.
Before you start
What to know first
StoryProof does not see feature usage
It has no access to your product analytics. The list of who used a feature comes from your own data.
No in-app prompt
StoryProof sends requests by email or a shared link. It does not pop up inside your product when someone uses a feature.
Early quotes date quickly
A feature that changed a lot after launch may outgrow its first testimonials. Check them when the feature changes.
Do not script the answer
Ask questions, not for agreement with your positioning. A quote that repeats your tagline reads as written by you.
FAQ
Questions people ask
Short answers to what usually comes up next.
How do I ask a customer for a testimonial about a specific feature?
Name the feature and the job it does in the request, and ask what they did before it existed. Send it only to people who have used it for a few weeks.
When should I ask about a new feature?
Ask for feedback soon after launch and for a testimonial a few weeks later, once the feature is part of their routine.
Can one request ask about several features?
It can, but each extra feature makes every answer vaguer. One feature per request gets the most quotable answers.
Where should feature testimonials appear?
On the page for that feature, next to the description of what it does. The feature page planner covers placement.
Still have a question? Ask the StoryProof team or book a demo.
Get proof for the next feature you ship
Set up a form with a question about one feature and send it to the people who use it. No credit card needed to start.
Last updated 2026-11-07.