Skip to main content

Videos are rare, so do not let one wait

Team Alerts for New Video Testimonials

Written testimonials are the usual kind. A customer who records a video has given you something rarer and more useful, and it needs different hands: someone to watch it, trim it, and decide where it goes. A general alert for every review buries it among the written ones. From Pro, an automation can start when a testimonial arrives, let only the videos through a condition, and send them straight to the people who work with video.

  • Only videos reach the video team
  • A label so new videos are easy to find
  • A same-week plan for watching and using each one

The problem, solved

Why new videos wait too long, and the fix

  • Videos get lost among written reviews

    One collection link takes video, audio and written reviews, so a single feed mixes them all together.

  • The video editor hears last

    The person who approves reviews is often not the one who cuts video, and passing it on depends on memory.

  • Finding last week’s videos takes ages

    Scrolling through every testimonial to pick out the videos wastes the editor’s time.

  • Will an alert publish the video?

    A team alert can make people think the video is already live.

  • Not on a plan with automations

    Without a filter, the only signal is the general alert for every review.

Flip the switch to see how StoryProof handles each one.

Team checklist

Route each new video to the right people

Build the alert once, then follow the second group every time a video lands.

Build the alert
Each time a video arrives

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

In StoryProof

Build the video-only alert

  • You will need
  • A StoryProof workspace on Pro or above
  • The names of the people who work with video
  • A label for new videos
  1. 1

    Start on a new testimonial

    In the automation builder, choose the trigger for a testimonial being received.

  2. 2

    Split off the videos

    Add a condition with a named branch for video. Leave written and audio testimonials on the path where nothing matches.

  3. 3

    Label and alert

    On the video branch, add the label, then a team email to the video people.

  4. 4

    Test, then publish

    Nothing runs until you publish. Record a test video through your own link and confirm only the video branch fires.

What happens next: If the editor gets too many alerts at once, switch to a low severity in-dashboard notification and keep email for the lead.

Before you start

What this alert does not cover

  • The video rule is yours to confirm

    This page does not name the condition that identifies a video. Check it in the builder and test it.

  • It does not edit the video

    The alert gets the video to the editor. Trimming and publishing are still people’s work.

  • Up to ten teammates

    Each team email goes to ten people at most.

  • Needs automations

    Filtering by condition is part of automations, from Pro.

  • Approval still applies

    A video is never shown publicly until someone approves it.

FAQ

Questions people ask

Short answers to what usually comes up next.

Why separate video alerts from the others?

Videos need different people and more work than written reviews. A separate alert gets them to those people quickly.

Who should receive the video alert?

Whoever watches, edits and places video: often a content producer and the person who runs paid ads.

Can audio testimonials get their own alert too?

Conditions support up to eight named branches, so you can add another branch if the builder offers a rule for audio.

Does the alert mean the video is on our website?

No. It is internal. The video appears publicly only after it is approved.

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

Get every new video to the people who use it

Filter for video, label it and alert the team the moment it arrives.

Last updated 2026-11-18.