Skip to main content

Requests that never arrived

Clean Up Bounced Testimonial Request Emails

A bounced request is a customer who never saw your ask, and nobody on the team knows. Left alone, bad addresses pile up and the same contacts bounce again next month. From Pro, an automation can catch each bounce, label the contact and tell the right teammate, so cleaning the list becomes a short weekly job instead of a mystery.

  • A tag and a list for every bounced contact
  • An alert to the person who owns the contact data
  • A weekly fix, retry or retire routine

The problem, solved

Why bounces go unnoticed, and the fix for each

  • Nobody knows a request bounced

    The send looks done from the outside. The customer never got it, and nobody plans a second try.

  • Bad addresses hide among good ones

    Without a marker, a bounced contact looks like any other and gets picked again for the next campaign.

  • The person who could fix it never hears

    The account manager knows the customer’s new address, but the bounce is invisible to them.

  • We cannot tell how many bounced

    A sudden rise may mean a typo in an import or a sending problem, not a few old addresses.

  • Fixed addresses never get asked again

    Someone corrects the email but the request is never resent, so the effort is wasted.

Flip the switch to see how StoryProof handles each one.

Team checklist

Set up the bounce routine

One-off setup first, then the weekly group that keeps the list clean.

Set it up once
Every week
If bounces jump

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

In StoryProof

Build the bounce automation

  • You will need
  • A StoryProof workspace on Pro or above
  • A cleanup Smart List and a tag such as bounced
  • A named owner for the list
  1. 1

    Start on the bounced trigger

    In the automation builder, start the flow when a review request bounces.

  2. 2

    Label and move the contact

    Add the bounced tag and add the contact to the cleanup list. Optionally remove it from the list the request came from.

  3. 3

    Tell the owner

    Send the owner an email or an in-dashboard notification with a severity level that fits: low for a single bounce is usually enough.

  4. 4

    Review the logs weekly

    Compare this week’s enrolments with last week’s. A spike points at a source, not a single customer.

What happens next: When a corrected contact is asked again, remove the bounced tag so the next bounce report starts clean.

Before you start

What this routine does not cover

  • No bounce reasons on this page

    This page does not say what reason or bounce type StoryProof records. If you send through your own provider, its logs may give more detail.

  • It does not repair addresses

    The automation flags a bad address. A person still has to find the right one.

  • Not a spam folder fix

    A message that lands in spam did not bounce, so this flow never sees it.

  • Alert noise

    An email per bounce can flood the owner during a bad import. Use the in-dashboard notification for single bounces if that happens.

  • Needs automations

    The bounced trigger is part of automations, from Pro.

FAQ

Questions people ask

Short answers to what usually comes up next.

Should I delete contacts whose requests bounced?

Not straight away. Tag them, look for a better address, and only remove them from request lists when there is none.

Who should get the bounce alert?

The person who can find a correct address: often the account owner or whoever manages the customer list, not the whole team.

Why did many requests bounce at once?

A batch of bounces usually has one cause, such as a bad import or a sending problem. Check the newest source of contacts first.

Can I resend after fixing an address?

Yes. Remember the request step skips people asked recently, so check the timing, or send it by hand.

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

Stop asking addresses that do not work

Catch every bounce, tag it and send it to the person who can fix it.

Last updated 2026-11-18.