Their 1,000th order, their 500th invoice
Testimonial Request After a Usage Milestone
Long after onboarding, a customer quietly crosses a line: the thousandth order shipped, the five hundredth booking taken, a full year of reports in the account. They rarely notice. You can, and a message that points out the number and asks what got them there produces a testimonial with weight behind it.
- Opens with their number, not your request
- Variants for volume, depth of history and team growth
- Asks what changed between the first and the latest
Template builder
Build the milestone email
Choose the kind of milestone, then fill in the number and what it measures. The question in each template is one a newer customer could not answer.
- The round number
Subject: [1,000] [orders shipped], [Marta]
Hi [Marta], You just passed [1,000] [orders shipped] through [Parcelwise]. We noticed, and wanted to say well done. A question only someone at your volume can answer: what would handling [1,000] [orders shipped] look like without it? A couple of sentences, a quick video or a voice note all work: [your StoryProof link] We read every reply before anything is shared. [Leo]
- Short follow up line for an in app banner or footer
Use where a full email would be too much.
[1,000] [orders shipped]. Tell us what got you here: [your StoryProof link]
Templates fill in inside your browser. Nothing is stored or sent from this page.
The problem, solved
What gets in the way of milestone asks, and how StoryProof helps
Your product data knows the milestone. Everything after that is where these emails usually fall apart.
- Problem 1
The numbers live in our database only
Someone runs a query, finds forty customers past the line, and the list dies in a spreadsheet.
How StoryProof solves it
Add those customers to StoryProof as contacts and group them in a smart list for this milestone, so the request goes to exactly that group. Contacts and smart lists come with every plan.
- Problem 2
Power users will not write essays
People processing thousands of anything have little time. A blank text box at the end of an email loses them.
How StoryProof solves it
The same collection link offers a typed review, a short video or an audio note, in the browser with no install.
- Problem 3
The first email got buried
Milestone customers are busy by definition, so one email is easy to miss.
How StoryProof solves it
From Pro, follow ups go out after three days and again after four more, stop once they submit, and respect your quiet hours.
- Problem 4
Big accounts hit a milestone every month
A customer crossing 1,000, then 2,000, then 5,000 should not get three requests in a quarter.
How StoryProof solves it
Tag every testimonial with the milestone that triggered it, so before the next send you can see who has already answered one.
- Problem 5
The numbers they quote may be off
A customer might round up or mention a result you cannot support. Publishing it unread puts that claim in your mouth.
How StoryProof solves it
Every submission waits for your approval, so you can check the figures against your records before anything goes public.
Pick a milestone worth celebrating
A good milestone is one the customer built through real use, not a number you would struggle to explain.
In StoryProof
Send milestone requests with StoryProof
Step 1 of 5
Pull the list and add the contacts
Each week or month, export the customers who crossed the line and add them to a smart list named for the milestone.
Step 2 of 5
Send the milestone email
Paste the template that fits, with the number filled in, and email the request with your collection link.
Step 3 of 5
Let the reminders run
On Pro or above, the follow up sequence chases quietly and stops once they respond.
Step 4 of 5
Check the numbers and tag the milestone
Compare any figure they quote with your data, then approve and tag it with the milestone.
Step 5 of 5
Show it to prospects at the same scale
Put milestone quotes in the widget on the pages larger prospects read, such as a high volume plan or an enterprise page.
Before you start
Honest limits
StoryProof does not read your usage data
It cannot see orders, seats or records in your own product. You decide who crossed the milestone and add them.
No event trigger for milestones
The order webhook automation sends a request a week after a purchase. It does not detect a thousandth order; that list is yours to send.
Email only
Requests go by email. An in app banner, like the short line above, is something you add in your own product.
Their number is their claim
A figure in a testimonial reads as typical to prospects. If most customers will not see the same, add context or leave the number out.
FAQ
Questions people ask
Short answers to what usually comes up next.
Which usage milestone is best for a testimonial request?
One the customer built through their own work and would recognise as an achievement, such as a thousandth order. Avoid counts that include test data or automated activity.
How is this different from an anniversary request?
An anniversary is a date. A usage milestone is an amount of real use, which can arrive in month three for a heavy user or year four for a light one.
Should the email include the exact number?
Yes. A precise figure shows you noticed them in particular. Round it only if the exact count would look odd, such as 1,003.
Can I ask the same customer at every milestone?
Ask once, then leave a long gap. A second ask at a much larger milestone can work if the first went well and enough time has passed.
Still have a question? Ask the StoryProof team or book a demo.
Turn their milestone into your proof
Set up a collection link and send the first milestone email this week. No credit card needed to start.
Last updated 2026-11-11.