Claim and evidence
The law makes no exception for business-to-business email.US FTC guidance · ftc.gov · 2023-08
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Restricted · 2026-11 Legal requirement in the US; other regions (GDPR, CASL) are stricter and not covered by this source.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
The law covers B2B email too, so compliance protects against per-email fines and aligns with provider expectations.
How to run it
- Use accurate From and subject lines
- Include a valid postal address
- Provide an opt-out and honor it within 10 business days
- Hold a central suppression list
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option APlain-text opt-out line
Add a short line inviting the recipient to reply or click to stop further emails.
- Option BShared suppression list
Sync opt-outs across every sending tool and mailbox so nobody is emailed again by mistake.
- Option CTemplate compliance check
Build the address and opt-out into sequence templates so no step can be sent without them.
Timeline
- 12023 US FTC guidance — States there is no B2B exception and sets the 10-business-day opt-out window.
- 22026-11 status checked: Restricted
Dated examples
- 2023
US FTC guidance
States there is no B2B exception and sets the 10-business-day opt-out window.
“The law makes no exception for business-to-business email.”
○ page blocks automated checks; quote as relayedftc.gov · 2023-08
Does it still work?
Legal requirement in the US; other regions (GDPR, CASL) are stricter and not covered by this source. source
Risks
- Penalties up to $53,088 per violating email per the guide
- EU/Canada rules differ
Sources
- ftc.gov
“You must honor a recipient’s opt-out request within 10 business days.”
○ page blocks automated checks; quote as relayed
Change log
- 2026-11-20 — harvest v0.1 (acq-outbound)