Skip to main content

Wins worth noticing

Celebrate Testimonial Milestones With Your Team

Your hundredth testimonial usually passes without a word, because nobody was watching the counter. The people who earned those reviews, the support agent, the installer, the account manager, never hear about it. From Pro, an automation can start when you reach a review count worth celebrating and tell the team straight away. The checklist below turns that moment into something people remember.

  • An alert to the team when a milestone is reached
  • Numbers from analytics to share with it
  • A short, repeatable way to say thank you

The problem, solved

Why milestones slip by, and how to catch them

  • We passed 100 and nobody noticed

    Nobody checks the count every day, so the moment is found weeks later, when it no longer feels like news.

  • The team never hears about it

    Only the person who logs in sees the number, and the people who earned the reviews stay in the dark.

  • A number alone feels flat

    A count is a fact, not a story. Teams respond to where the praise came from and how good it was.

  • We want to show off the best one

    A milestone is a good excuse to put a standout review in front of more people.

  • Share the milestone outside the team too

    Customers and followers like seeing that others trust you, but making a graphic takes time.

Flip the switch to see how StoryProof handles each one.

Team checklist

Plan the celebration before the milestone arrives

Set up the alert once, decide what happens when it fires, and the celebration takes care of itself.

Before
On the day
After

Ticks stay in your browser. Nothing is saved or sent.

In StoryProof

Set up the milestone alert

  • You will need
  • A StoryProof workspace on Pro or above
  • The list of teammates to tell
  • An agreed way to celebrate
  1. 1

    Choose the milestone trigger

    In the automation builder, start the flow when you reach a review count worth celebrating.

  2. 2

    Add the team email

    Add a team alert step that emails the people you chose. Keep the message short: the number, and a pointer to where the full picture is.

  3. 3

    Add an in-dashboard note for the rest

    A low severity notification lets anyone who logs in see the news too.

  4. 4

    Publish and leave it running

    Nothing runs until you publish. Once it is live, there is nothing to remember.

What happens next: When the alert fires, the owner follows the "On the day" group of the checklist.

Before you start

What the milestone alert does not do

  • It does not plan the party

    The automation tells people. A person still has to turn it into a celebration.

  • Counts come from the builder

    This page does not say which review counts the trigger offers. Check the options in the automation builder.

  • Ten teammates per email

    Team emails go to up to ten teammates. For a bigger group, forward it or share it in your own channel.

  • Needs automations

    Insight triggers are part of automations, from Pro.

  • Count quality, not only quantity

    A milestone reached with weak reviews is less worth celebrating. Look at ratings in analytics too.

FAQ

Questions people ask

Short answers to what usually comes up next.

Which milestones should we celebrate?

Round numbers the team will feel, such as the first fifty or the hundredth testimonial. Check which counts the trigger offers in the builder.

Who should get the milestone email?

The people whose work appears in the reviews, plus whoever will organise the celebration. Up to ten teammates per email.

Should we tell customers about the milestone?

If you like. Share an approved testimonial with it, not just the number, so the post says something about the work.

What should the team message include?

The count, the average rating and main sources from analytics, and two or three quotes that name a person.

Still have a question? Ask the StoryProof team or book a demo.

Let the team enjoy the wins they earned

Get told the moment a milestone arrives, and make it count.

Last updated 2026-11-18.