Trust
Anti-spam policy and acceptable use
Blue Reacher sends business messages to people who can say no and be heard instantly. That sentence is the whole policy; the rest of this page is how it's enforced: the consent rules that apply to every channel, the opt-out machinery that runs on every account, the list practices we expect from customers, and the programs we refuse to run.
Last updated
Consent is the sender's job, on every channel
iMessage sits outside the A2P 10DLC registration system because it does not travel over carrier SMS routes: no A2P registration required. What never goes away is the law. The TCPA and state texting statutes govern business texting to mobile numbers whatever the channel, so every Blue Reacher customer needs a valid consent basis for each contact they message and should be able to show it. Cold outreach carries the heaviest obligations in that rulebook, and our published guides treat those obligations as part of the play rather than a footnote: the legality guide covers consent bases and the B2B grey areas, and the TCPA compliance guide covers consent records, quiet hours and the damages math. Statutory damages run $500 to $1,500 per message, which makes consent an economic decision, not a formality. None of this is legal advice; run your program past counsel before scaling it.
Opt-outs: honored in seconds, not in ten days
Under the FCC rules effective April 11, 2025, a recipient can revoke consent by any reasonable means, and senders have at most 10 business days to honor it. Blue Reacher does not use them. Detection runs in two layers on every inbound reply: keyword matching for the seven terms the FCC treats as conclusive (STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, UNSUBSCRIBE, in any casing), and plain-language detection for the requests people actually type, which is most of the volume. A detected opt-out cancels queued sends and suppresses the contact account-wide: every line, every campaign, every automation, and manual sends from reps who never saw the thread. At most one confirmation message goes out, inside five minutes, with no marketing content. After that, nothing.
Every event lands in a timestamped audit trail: the contact, the exact inbound text that triggered it, the channel, the detection method, and every blocked attempt against a suppressed contact. The whole log exports to CSV, which is what teams pull for compliance reviews and security questionnaires. The full mechanics are on the opt-out handling page, and the practice is stated in the same words on the security page.
List hygiene: quality over volume, by design
Spam is a volume strategy, and the platform is built so volume strategies fail early. Sending is paced to stay conversational and line health is monitored continuously, so a customer cannot blast a list at rates no human conversation would produce. Availability checking routes contacts to the channel that can actually receive them, which keeps failed-send noise out of sending patterns. And suppression is treated as hygiene rather than loss: on reactivation sends especially, the people who ask out are the people who were never going to buy, and every honored request removes a future complaint. What we expect from customers is the same discipline our guides teach: targeted lists, a real sender identity, messages written like a person, and staffed replies, because two-way threads are what keep a line healthy on top of being where the deals happen.
What we refuse to run
Some programs don't get a line, whatever they pay:
- Deception in any form: impersonating another person or company, spoofed sender identity, or messages that misrepresent who is texting and why.
- Illegal content and scams: phishing, fraud, and anything unlawful to sell or promote to the recipient.
- Harassment: continuing to pursue contacts who have said no, in keywords or in plain language. The suppression system makes this mechanical, and attempts to work around it end the account.
- Volume abuse: attempts to defeat pacing, split traffic to evade line-health monitoring, or run blast patterns dressed up as conversation.
- Consumer mass-marketing without a consent story: programs whose own description cannot name a consent basis for the people on the list.
White-glove setup is where this gets enforced first: message intent is configured with our team, so a program that belongs on this list never reaches a line.
Reporting and enforcement
Received a message you believe breaks this policy? Email support@bluereacher.comwith the sender's number and the message, or simply reply asking to stop, which suppresses the sender's account from messaging you again. Reports are checked against the audit trail, which records every send, suppression and blocked attempt, and accounts that break this policy lose their lines. Security researchers and reviewers can find our published practices on the security page.
Frequently asked questions
Is iMessage outreach spam?
Not when it's run the way this page describes. Spam is unwanted volume sent without consent basis, relevance or a working way out. A targeted B2B message with a real sender identity, honest content and instant opt-out enforcement is outreach, and the difference is operational, not rhetorical: consent basis, list quality, pacing and suppression are all checkable practices.
Is iMessage cold outreach legal?
Business texting is governed by the TCPA and state texting laws on every channel, iMessage included, and cold outreach carries the heaviest consent obligations in that rulebook. It can be run lawfully with a valid consent basis, honest identification and fast opt-out honoring, and the sourced breakdown lives in our guide to iMessage marketing law. None of this page is legal advice; run your program past counsel.
Does "no A2P registration required" mean no rules apply?
No. A2P 10DLC is carrier plumbing for SMS routes, and iMessage sits outside that system, so there's no registration queue. The law is a separate layer: TCPA consent, revocation and opt-out obligations apply to business texting on every channel, and Blue Reacher enforces the opt-out side mechanically on every account.
How fast are opt-outs honored?
In seconds, account-wide. Detection catches the FCC's conclusive keywords (STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, UNSUBSCRIBE) in any casing plus plain-language requests like "take me off this list", cancels queued sends, and suppresses the contact across every line, campaign, automation and manual send. The FCC allows up to 10 business days; that ceiling never gets tested.
Can a rep accidentally message someone who opted out?
No. Suppression is enforced everywhere at once: queued sequence steps are canceled, new campaigns skip the contact at build time, and the inbox blocks manual sends from any rep, including one who never saw the earlier thread. Blocked attempts are logged in the audit trail alongside the opt-outs themselves.
Can I text a purchased list?
List source doesn't remove your consent obligations: you need a valid consent basis for each contact and you should be able to show it, whatever the list's origin. Cold B2B programs live or die on relevance and targeting anyway; the same message sent to a poorly chosen list draws the complaints that damage sender reputation faster than it produces meetings.
What sending behavior does the platform block?
Sending is paced platform-side to stay conversational, so blast patterns aren't possible regardless of what a campaign or an agent requests. Line health is monitored continuously, opt-out suppression cannot be overridden over the API, and opt-out reversal requires the contact asking to resume, with both events kept in the trail.
How do I report abuse by a Blue Reacher customer?
Email support@bluereacher.com with the number that messaged you and, if you can, the message content. Reports are investigated against the audit trail, which records every send, suppression and blocked attempt. Recipients can also simply reply to stop: any reasonable request suppresses the sender's account from messaging them again.