Skip to main content

A trend, not a single review

Alert Your Team When Ratings Drop

One bad review is a conversation. A slipping average is a pattern: a new hire, a supplier change, a process that broke. It creeps down a tenth at a time, so nobody notices until it shows. From Pro, an automation can start when your average rating or your share of 5-star reviews crosses a threshold, and alert the people who can find out why.

  • A threshold on the average or the 5-star share
  • An urgent alert to the people who can act
  • A first-hour checklist for finding the cause

The problem, solved

Why a falling rating goes unseen, and how to catch it

  • The average slid and nobody noticed

    A drop of a tenth here and there never looks alarming on the day, only in hindsight.

  • Fewer five stars, same average

    Fours replacing fives is often the first sign of trouble, and the average hides it for a while.

  • The alert went to the wrong person

    A rating drop needs someone who can change how the work is done, not only the person who approves reviews.

  • We know it fell, not why

    Without a breakdown, the team argues about causes instead of checking them.

  • Single angry reviews also need handling

    A trend alert should not replace the response to one unhappy customer.

Flip the switch to see how StoryProof handles each one.

Team checklist

Set the alert and the response

Decide the line, who hears about it, and what they do in the first hour.

Set the line
Who hears
The first hour

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

In StoryProof

Build the rating drop automation

  • You will need
  • A StoryProof workspace on Pro or above
  • Your current numbers from analytics
  • The list of people to alert
  1. 1

    Choose the insight trigger

    In the automation builder, start when the average rating or the 5-star share crosses a threshold, and set the line.

  2. 2

    Add a high severity notification

    So anyone who logs in sees it is urgent.

  3. 3

    Email the people who act

    Add a team email to the investigation lead and the managers concerned.

  4. 4

    Publish and check the logs

    Nothing runs until you publish. After it fires, the logs show when it ran.

What happens next: Revisit the threshold every few months. If the rating improves, raise the line with it.

Before you start

What a threshold alert cannot tell you

  • It does not find the cause

    The alert says the line was crossed. People still have to work out why.

  • Small numbers swing

    With few testimonials, two bad ones can move the average a lot. Set the line with your volume in mind.

  • Your testimonials only

    This watches ratings collected in StoryProof, not scores on outside review sites.

  • Ten teammates per email

    For a wider group, pass it on yourself.

  • Needs automations

    Insight triggers come with automations, from Pro.

FAQ

Questions people ask

Short answers to what usually comes up next.

Where should I set the threshold?

A little below your current level, from analytics. Too close and normal variation sets it off; too far and the alert comes late.

Should I watch the average or the 5-star share?

The share of 5-star reviews often moves first, when fours start replacing fives. Watching both is reasonable.

Is this the same as the low rating alert?

No. The low rating alert reacts to one review of 2 stars or fewer. This one reacts to the overall trend.

Does it watch Google or other review sites?

This page covers the ratings on testimonials in StoryProof. It does not describe watching scores on other sites.

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

Hear about a slide before customers do

Set a line for your ratings and let StoryProof alert the people who can fix it.

Last updated 2026-11-18.