Stop means stop, on every line
Every reply is read for opt-outs, from STOP to "take me off this list". The contact is suppressed across every line, sequence and manual send within seconds, and the event is logged.
Included on every line. No A2P registration required.
Chris Doyle
iMessage
iMessage · Today
Worth a quick call about your Q4 hiring plans?
Delivered
Not interested, please take me off your list.
Opt-out caught in plain language. Suppressed on every line within seconds.
Opt-outs handled before anyone has to notice
Detection and suppression are on by default. Nothing to switch on, nothing to build.
Keywords and plain language
STOP, QUIT, END, REVOKE, OPT OUT, CANCEL and UNSUBSCRIBE are caught, and so are replies like "not interested, don't text again".
Account-wide in seconds
Queued sends and sequence steps cancel, and the CRM is updated, across every line within seconds. FCC rules allow up to ten business days; this takes seconds.
One status, every channel
Suppression sits on the contact, not the channel, so an opt-out sent over SMS blocks iMessage and RCS too.
POST /v1/messages
{ "to": "+15125550142", "content": "..." }
webhook message.received
{ "service_type": "iMessage", "content": "Yes, Thursday" }
Your other systems hear about it
A contact.opted_out webhook fires on every opt-out, so your CRM and anything else you run can suppress the contact as well.
An audit trail you can export
Every opt-out records the contact, the reply text, the channel, how it was detected, the time and the sequence it came from. Export it to CSV for a compliance review or to answer a complaint.
Opt-outs show up in your reporting
Every campaign report counts opt-outs next to delivered, read and replied, so a message that drives people away is visible the same day it goes out.
What is automatic opt-out handling?
Automatic opt-out handling means Blue Reacher reads every inbound reply and decides whether the contact is asking you to stop. It catches keywords like STOP and plain-language requests, suppresses the contact on every line and channel within seconds, cancels anything queued, and records the event in an audit trail you can export.
It enforces the stop side on the platform. How you collected consent, and what you send, stay yours to run.
Questions about opt-out handling
The questions buyers ask before they start. Anything not here is answered in the answers library.
Does it catch opt-outs that don't say STOP?+
Yes. Plain-language detection reads intent, so "take me off", "not interested, don't text again" and "remove me" all trigger suppression, alongside the STOP to UNSUBSCRIBE keywords.
Does one opt-out stop every campaign?+
Yes. Suppression is account-wide across every line, sequence and automation from the moment it is recorded.
Can I import the suppression list I already have?+
Yes. Upload it as a CSV of phone numbers during onboarding and those contacts are blocked before any campaign can reach them, including numbers from an old SMS program.
What if a rep tries to text someone who opted out?+
The send is refused and the attempt is logged. Suppressed contacts are blocked from manual sends the same way sequences block them.
Does this make my messaging compliant?+
It enforces opt-outs on every line, but compliance also depends on how you collected consent and what you send. Blue Reacher handles the stop side automatically; the consent side stays yours.
Send with opt-outs already handled
Book your Blue Funnel Map and we import your existing suppression list during setup, so nobody who opted out elsewhere hears from you.
Most teams are live within a week.