Submitted weeks ago, still not live
How Fast to Approve New Testimonials
A customer took ten minutes to record a lovely video, and it has been sitting in the queue for a month. Meanwhile they are wondering if you liked it. Approval speed is a habit, not a tool setting. Pick the day a testimonial arrives and get a dated path to published below, then set a sweep that keeps the queue short.
- A dated path from submission to your site
- Where automations can take steps off your plate
- A weekly sweep so the backlog never builds
The problem, solved
Where approval time disappears
The review itself takes minutes. The days go on waiting for someone to look, and on the steps after.
Nobody looks at the queue
Approval is everybody's job and so nobody's. Testimonials wait until someone happens to log in.
With StoryProof: Everything submitted waits in one queue for approval, and roles are on every plan, so you can name one person whose job the queue is.
Easy ones wait behind hard ones
A simple five star note sits for a week because the reviewer is stuck on a tricky video.
With StoryProof: From Pro, an automation can approve 4 and 5 star testimonials with text and leave the rest for a person.
A bad review hides in the backlog
A one star complaint left unread for weeks is a customer you could have helped.
With StoryProof: From Pro, a review of 2 stars or fewer can alert your team at once and send the customer a personal apology.
Customers never hear it went live
Silence after submitting feels like rejection, and it costs you the referral and the share.
With StoryProof: From Pro, a thank you email with a link to the testimonial goes out two hours after approval.
Approved, but on no page
The testimonial is approved and then sits in the library, because nobody owns placing it.
With StoryProof: Make placement part of the same slot: choose which approved testimonials appear in each widget right after approving.
Flip the switch to see how StoryProof handles each one.
Timeline
From submitted to published
Pick the day a testimonial arrives. The plan shows when each step should be done if you aim to publish within a week.
Day +1
First read
The named reviewer reads it within one working day. Decide: approve, hold for a question, or leave unpublished.
Day +2
Question sent if needed
If something needs checking, such as a name, a claim or consent, send one question now rather than letting it wait for the weekly sweep.
Day +3
Approved and tagged
Approve and add the tags your team uses for product, segment or format, so it can be found when placing.
Day +3
Customer thanked
The thank you email goes out, by automation or by hand, while they still remember submitting.
Day +5
Placed on a page
Choose it for the widget where it fits best. A testimonial nobody sees is not yet doing its job.
Day +7
Weekly sweep
Anything still waiting from the past week gets a decision today: approve, ask, or leave unpublished with a note why.
Dates are calculated in your browser. Nothing is stored.
A queue with and without a target
No turnaround target
- Testimonials wait until someone remembers
- Hard cases block easy ones
- Customers hear nothing after submitting
- The backlog is cleared in one painful afternoon each quarter
A one week target and a sweep
- One named reviewer reads within a working day
- Easy approvals happen automatically or in minutes
- Customers get a thank you soon after approval
- Nothing in the queue is older than a week
In StoryProof
Clear an existing backlog, then keep it clear
- You will need
- Access to the approval queue
- One person named as reviewer
- 1
Sort the backlog by risk
Read low ratings first: those customers may need a reply more than a decision. Then the oldest, then the rest.
- 2
Turn on auto approval if it suits you
From Pro, let 4 and 5 star text testimonials approve themselves so only the harder cases reach the reviewer.
- 3
Thank the people who waited
For old submissions, a short personal note apologising for the delay works better than a standard thank you.
- 4
Tag and place as you approve
Add tags and choose widgets in the same sitting, so approval and placement do not become two queues.
- 5
Book the weekly sweep
A fixed time each week to decide on anything older than the target. Use the analytics dashboard to see how many came in.
What happens next: If the sweep keeps finding the same kind of testimonial stuck, such as videos waiting for a legal check, give that kind its own owner.
Before you start
What speed should not override
Fast is not careless
A week is a target for good testimonials. Anything with a consent question, a sensitive detail or a risky claim waits until it is answered.
Legal sign off sets its own pace
If your company needs legal review, the turnaround is set by that team. Agree a target with them rather than skipping them.
Auto approval is a trade off
It speeds up 4 and 5 star text testimonials but skips a human read. Leave it off if every word must be checked.
There is no queue age alert
StoryProof has no verified reminder for testimonials waiting too long. The weekly sweep is how you catch them.
FAQ
Questions people ask
Short answers to what usually comes up next.
How long should testimonial approval take?
There is no standard figure. A week from submission to published is a target most small teams can keep; set yours and measure against it.
Should I tell customers when their testimonial is live?
Yes. It closes the loop and often leads them to share it. The thank you automation can do it for you from the plan that includes automations.
What do I do with testimonials that have waited months?
Decide on each one now. Approve the ones still accurate, send a short note apologising for the delay, and leave unpublished anything that is out of date.
Who should own the approval queue?
One named person, with a backup. For who checks what, see the approval workflow page.
Still have a question? Ask the StoryProof team or book a demo.
Get fresh testimonials live within a week
Name a reviewer, automate the easy approvals and keep the queue short with a weekly sweep.
Last updated 2026-11-11.