One average, read on a schedule
Watch Your Average Testimonial Rating Trend
A single average rating tells you very little. The same figure read every month for a year tells you whether customers are getting happier, whether a change you made landed, and when something started to slip. Pick a start date below to get a dated plan: a baseline, a monthly reading, an automation that watches the threshold between readings, and the quarterly review where the trend becomes a decision.
- A baseline reading on day one
- Monthly figures in a log the team can see
- An automation watching between readings
The problem, solved
Why rating trends get missed, and how StoryProof helps you watch
Analytics are on every plan. The threshold and low rating automations need Pro or above.
We only look when one stings
Ratings get attention the day a two-star review lands and none the rest of the month.
With StoryProof: Analytics show the ratings of the testimonials you collect, on the dashboard every plan includes, so a set reading day replaces the panic glance.
We cannot tell a dip from noise
A month with eight reviews can swing on one unhappy customer, and the team overreacts.
With StoryProof: Write the average and the number of rated testimonials into a log each month. Three readings in a row moving the same way is a trend; one is not.
Nobody hears when the average slips
A decline that starts the week after a monthly reading goes unseen for a month.
With StoryProof: An automation can start when your average rating crosses a threshold and send an in-dashboard notification or email up to ten teammates.
Good news passes unnoticed too
A rising share of five-star reviews is worth telling the team, and nobody does.
With StoryProof: The same kind of automation can start when your share of 5-star reviews crosses a threshold or you reach a review count worth celebrating.
One low rating sat for days
The trend is made of single reviews, and an unanswered complaint often becomes the next one.
With StoryProof: A review of 2 stars or fewer can send your team an urgent alert and the customer a personal apology email.
Our site and our average disagree
The widget shows glowing five-star quotes while the dashboard average is lower, and someone thinks the data is wrong.
With StoryProof: You choose which approved testimonials appear in each widget, so the site shows a selection. Read the trend from analytics, not from the page.
Flip the switch to see how StoryProof handles each one.
Rating trend plan
Get a dated plan for your first year
Pick the day you will take your first reading. Every date after it is set from that day.
Day 0
Take the baseline
Open analytics and write down the average rating and how many rated testimonials it is based on. Start a shared log with this as row one.
Day +1
Set the threshold automation
On Pro or above, build an automation that starts when the average crosses a threshold a little below your baseline, and alerts the person who owns the log.
Day +7
Check the low rating route
Confirm every testimonial of 2 stars or fewer from the past week reached someone who replied, by automation or by hand.
Day +30
First monthly reading
Add the average and the count to the log. Do not react to one month; note anything that happened that might explain a change.
Day +60
Second monthly reading
Add row three. If two readings move the same way, look at the low-rated testimonials behind them and tag the common reason.
Day +90
First quarterly review
Three months of readings: is the line flat, rising or falling? Decide one action, such as fixing a recurring complaint or asking a happier customer group more often.
Day +180
Half-year review
Compare against the baseline. Move the automation threshold if your average has settled at a new level.
Day +365
Year review
Twelve readings show seasonality and the effect of the changes you made. Write a short summary and set next year’s baseline.
The dates are worked out in your browser. Nothing is saved or sent.
What a rating log can look like
Illustrative log, not real customer data
Month 1: average 4.6 from 14 rated testimonials. Note: new onboarding call started mid-month.
Month 2: average 4.4 from 9. Note: two low ratings both about delivery times; tagged "delivery".
Month 3: average 4.5 from 16. Quarterly decision: fix delivery updates, re-read in three months.
- Owner
- One named person
- Reading day
- First working day of the month
In StoryProof
Run the routine as a team
- You will need
- Testimonials collected with a rating
- A shared spreadsheet or note for the log
- One named owner
- 1
Name the owner and the reading day
One person reads analytics on a fixed day and fills in the log. Everyone else reads the log.
- 2
Let an automation watch in between
Set an automation on the average crossing a threshold, with an alert to the owner, so a slide between readings is not missed.
- 3
Tag the reason behind low ratings
Tags are on every plan. A reason tag on each low-rated testimonial tells you what is pulling the average down.
- 4
Decide once a quarter
At each quarterly review, pick one action from what the trend and the tags show, and check its effect in the next three readings.
What happens next: Share the log with whoever can act on it: product, service delivery or support. A trend nobody outside marketing sees changes nothing.
Before you start
What this routine cannot do
No trend chart is claimed
This page does not claim the dashboard draws ratings over time or filters by date. The monthly log is how you see the trend.
Threshold options are not listed
Which thresholds the insight trigger accepts is shown in the automation builder, not here.
Small numbers swing
With few rated testimonials a month, one review can move the average a lot. Record the count beside every reading.
Only rated testimonials count
Testimonials collected without a rating do not move the average. If many arrive unrated, the trend describes only part of your customers.
FAQ
Questions people ask
Short answers to what usually comes up next.
How often should I check the average rating?
Monthly for the log, quarterly for decisions. Checking daily mostly measures noise.
What threshold should the automation use?
A little below your baseline, so it fires on a real slide rather than every small wobble. Move it after the half-year review if your average has settled.
Should my website show the average rating?
That is a separate decision. The star ratings guide covers when showing scores helps and when it hurts.
Do imported reviews affect the trend?
If they carry ratings, they can. Note in the log any month you imported a batch, so a jump is not mistaken for a change in customer sentiment.
Still have a question? Ask the StoryProof team or book a demo.
Start your rating log this month
Collect rated testimonials, read the average on a schedule and let an automation watch in between.
Sources
- Features: analytics, StoryProof. Checked 2026-11-18.
- Automations, StoryProof. Checked 2026-11-18.
Last updated 2026-11-18.