Second pair of eyes
Flag Testimonials for a Second Review
Some testimonials need a second opinion before anyone approves them: a health claim, a number, a named competitor. From Pro, one automation can flag those on arrival and another can tell the right reviewer the moment a flag lands.
- Write the escalation rules the team already applies in its head
- Flag on arrival, alert on flag
- One named reviewer per kind of risk
The problem, solved
How escalations stall, and what moves them
I meant to ask legal and forgot
Escalation that depends on a sticky note or a chat message is the first thing to slip in a busy week.
With StoryProof: From Pro, an automation can flag a testimonial that matches your rules, so the question is recorded on the testimonial itself.
The reviewer never knows something is waiting
A flag nobody sees is just a coloured mark in a queue. The second reviewer rarely opens the dashboard unprompted.
With StoryProof: A second automation can start when a testimonial is flagged and email up to ten teammates, or post an in-dashboard notification with a severity level.
Different risks need different reviewers
A medical claim goes to compliance, a pricing comparison to the product owner. One inbox for everything means each person wades through the other’s.
With StoryProof: Conditions with named branches let each kind of risk alert its own reviewer from the same flow.
Will it go live while we wait?
The fear is that a flagged testimonial slips onto the site before the second person has looked.
With StoryProof: Nothing is public until someone approves it. A flag adds a question; it does not publish anything.
The reviewer should not see everything
Legal or compliance needs the flagged testimonials, not your contacts, settings and campaigns.
With StoryProof: Roles and permissions give each teammate only the parts of the workspace they need.
Flip the switch to see how StoryProof handles each one.
Routing checklist
Map each risk to a reviewer
Fill this in with the people who will be asked to review. If they would not agree to a rule, it will be ignored once automated.
Ticks stay in your browser. Nothing is saved or sent.
In StoryProof
Put the escalation into StoryProof
- You will need
- A StoryProof workspace on Pro or above
- Reviewers invited with suitable roles
- Your written escalation rules
- 1
Build the flagging flow
Start from a testimonial being received, add a condition with a branch per rule, and put a flag action on each branch.
- 2
Build the alert flow
Start from a testimonial being flagged and add the team alert: an email to the named reviewer, or a notification with a higher severity for the urgent rules.
- 3
Agree what the reviewer does next
The reviewer either approves, rejects, or replies to the first approver with the change needed. Write that down where both can see it.
- 4
Check the first escalations
Read the logs for both flows after the first flagged testimonial to confirm the right person heard about it.
What happens next: Review the rules every quarter. A rule that flags everything gets ignored; one that flags nothing is not doing its job.
Before you start
Where the second review still depends on people
Rules cannot read intent
A condition checks what you tell it to. A risky claim worded in an unexpected way will pass, so approvers keep flagging by hand too.
Alerts stay inside StoryProof and email
Team alerts are in-dashboard notifications or emails. There is no chat app connection here.
Ten teammates per email step
One alert step can email up to ten people. Larger groups need a shared address.
Not legal advice
This page helps you route testimonials to the right person. Deciding whether a claim is acceptable is that person’s job.
A test sends real alerts
A test run performs every step, so warn the reviewer before you try the alert flow.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does flagging hide the testimonial?
A flag marks it for attention. It is not public in any case until someone approves it.
Can the reviewer approve directly?
That depends on the role you give them. Some teams let the reviewer approve; others want the first approver to make the final call. Decide and set the role to match.
Why two automations instead of one?
Keeping the alert in its own flow, started from the flagged trigger, separates deciding what to flag from deciding who hears about it. Flag one testimonial by hand and check the logs to see whether manual flags start it as well.
Can it alert us in Slack or Teams?
Team alerts are emails or in-dashboard notifications. If you need a chat tool, the email can go to an address that tool watches, set up on that tool’s side.
Still have a question? Ask the StoryProof team or book a demo.
Make the second review automatic
Flag risky testimonials on arrival and let StoryProof tell the right reviewer straight away.
Last updated 2026-11-18.