Skip to main content

Junk on autopilot

Auto Flag Spam Testimonial Submissions

An open collection link attracts link drops, keyboard mashing and the odd sales pitch. From Pro, an automation can test each new submission against rules you write and flag the suspicious ones, so the real testimonials are not lost among them.

  • Spam signals turned into testable rules
  • Flag first, reject only by hand
  • A short weekly sweep of the flagged pile

The problem, solved

What junk costs you, and how a rule takes the first pass

Situation 1 of 5

Real testimonials drown in junk

When half the queue is nonsense, a genuine customer story waits days for approval and the moment to thank them passes.

How StoryProof solves it

From Pro, an automation can start on each received testimonial and flag the ones that match your spam rules, leaving the rest easy to spot.

Rule checklist

Turn junk signals into flag rules

Pick the signals that match the junk you actually receive. Then check in the builder which of them a condition can test; anything it cannot stays a manual check.

Signals worth a rule
Wire the flow
Check for false alarms

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

In StoryProof

Set up spam flagging

  1. 1

    Open a blank automation

    Choose the trigger for a received testimonial. The draft saves itself and stays inactive until you publish.

  2. 2

    Add a condition with your rule groups

    Name the matching branch Suspected spam and build one group per signal you chose.

  3. 3

    Flag and label on that branch

    Add the flag action and a label so the suspected pile filters cleanly.

  4. 4

    Add the burst alert

    Build a small second flow from the flagged trigger with an in-dashboard notification, so the team sees spikes.

  5. 5

    Sweep the flagged pile weekly

    Filter by the label, glance down the list, reject the junk and approve anything real the rules caught by mistake.

What happens next: When a new kind of junk slips through twice, add a rule for it rather than sweeping it by hand forever.

Before you start

Limits of rule-based spam flagging

  • No built-in spam detection is claimed

    The automation applies the rules you write. It does not judge whether text is spam on its own.

  • Condition fields are for you to confirm

    This page does not list which testimonial fields a condition can test. Build only the rules the builder lets you express.

  • Flagging does not stop submissions

    Junk still arrives and still counts as received. The rule only sorts it for you.

  • Automations plan

    Rule-based flagging needs Pro or above. Without it, use the manual triage routine.

  • Careful with test runs

    A test performs every step for real, including the alert, so tell the team before you run one.

FAQ

Questions people ask

Short answers to what usually comes up next.

Why flag instead of rejecting automatically?

A rule will sooner or later catch a real customer. A flag keeps them recoverable; an automatic rejection hides them from the people who would have noticed.

How many rules should I start with?

Two or three, based on the junk you actually receive. Add more only when a new kind of junk keeps getting through.

Will flagged spam count toward anything?

This page does not cover plan allowances. Check your pricing page for what counts as a new review on your plan.

Can I use this alongside automatic approval?

Yes, but put spam flagging first in your thinking: a submission that matches a spam rule should never be on the approval path. Read the logs to confirm both flows behave as expected together.

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

Let a rule take the first pass

Collect testimonials with StoryProof and flag junk on arrival, so moderation starts with the real ones.

Last updated 2026-11-18.