Skip to main content

When a customer says stop

Handle Unsubscribes From Testimonial Requests

Customers do not only opt out through a link. They reply "please stop", tell your account manager on a call, or unsubscribe in your other email tool. Each of those has to reach StoryProof, quickly and every time. From Pro, an automation can unsubscribe a contact, and the routine below makes sure every route ends there. Whether your requests count as marketing under the law is a question for your own legal adviser.

  • Every route a customer can say stop by
  • One tag that unsubscribes them in StoryProof
  • Points to raise with legal before you rely on it

The problem, solved

How opt-outs slip through, and how to close each gap

  • They replied "stop" and got another email

    A reply sits in someone’s inbox while the reminder schedule carries on, and the customer feels ignored.

  • They told their account manager

    Opt-outs said out loud on a call are the easiest to lose, because nobody writes them anywhere the system can see.

  • They opted out in our other tool

    Your CRM or newsletter tool knows, StoryProof does not, and the next review request goes out.

  • Will reminders still reach them?

    The worst outcome is an automated reminder landing after someone asked to stop.

  • Can we show we acted?

    If a customer complains, you want to see when the opt-out was processed.

Flip the switch to see how StoryProof handles each one.

Team checklist

Make every opt-out reach StoryProof

Work through it with whoever reads customer replies and whoever owns your other email tools. The last group is for your legal adviser.

One way in
Every route a customer uses
Questions for your legal adviser

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

In StoryProof

Build the unsubscribe automations

  • You will need
  • A StoryProof workspace on Pro or above
  • An agreed do-not-ask tag
  • A list of everyone who reads customer replies
  1. 1

    Create the tag flow

    In the automation builder, start when a contact gets the do-not-ask tag. Add the step that unsubscribes the contact.

  2. 2

    Add a webhook flow for other tools

    If another tool records opt-outs, give it this automation’s URL, directly or through Zapier or Make. Paste a sample event and check which fields the app shows before relying on it.

  3. 3

    Test on your own address

    Nothing runs until you publish, and a test runs for real. Tag yourself and confirm your contact ends up unsubscribed.

  4. 4

    Check the logs each week

    Look for runs that ended early or webhooks that arrived without a matching contact.

What happens next: Take the legal questions to your adviser, and record their answers with this routine.

Before you start

What this page cannot settle

  • Not legal advice

    Whether a review request is a commercial message depends on its content and your situation. Ask a qualified adviser.

  • One country’s guidance

    The checklist summarises the US FTC guide only. Customers in other countries may be covered by other rules.

  • The tag only works if people use it

    An opt-out nobody tags is still missed. Train everyone who talks to customers.

  • Webhook fields are yours to check

    This page does not describe what another tool sends. Paste a sample event and check the fields before trusting the flow.

  • Logs last 30 days

    Keep your own record if you need proof of an opt-out for longer.

FAQ

Questions people ask

Short answers to what usually comes up next.

Does CAN-SPAM apply to testimonial requests?

The FTC says it depends on the message’s primary purpose: commercial messages are covered, transactional ones largely are not. Ask your legal adviser how your request emails are classed.

How fast should an opt-out be honoured?

The FTC guide gives 10 business days for commercial email. Most teams aim for the same day, because a reminder after a stop request upsets customers whatever the law says.

What if a customer replies "stop" instead of clicking a link?

Treat it as an opt-out. Add the agreed tag so the automation unsubscribes them.

Do unsubscribed contacts still get follow-up reminders?

The review request follow-ups automation skips anyone who unsubscribed.

Can our CRM tell StoryProof someone opted out?

It can call an automation’s inbound webhook, directly if it has a webhook feature or through Zapier or Make. StoryProof has no native CRM integration.

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

Respect every stop request, wherever it arrives

One tag, one automation, and every opt-out route ends in an unsubscribed contact.

Sources

  1. CAN-SPAM Act: A Compliance Guide for Business, Federal Trade Commission. Checked 2026-11-18.

Last updated 2026-11-18.