STOP opt-out and do-not-contact

Understand how STOP replies, do-not-contact flags, and consent affect SMS and automation.

5 min readUpdated June 2026

What STOP does

When a recipient replies STOP or a carrier-equivalent opt-out keyword, Flowforce should block future SMS automation to that number.

Video walkthrough placeholder showing STOP reply handling, do-not-contact flags, blocked SMS send, and cadence skip reason.
Video: Understand SMS opt-out
Video walkthrough placeholder showing STOP reply handling, do-not-contact flags, blocked SMS send, and cadence skip reason.
SMS thread showing STOP reply, opt-out status banner, blocked send warning, and linked contact or lead.
SMS thread showing STOP reply, opt-out status banner, blocked send warning, and linked contact or lead.

Blocked outreach states

  • SMS opt-out blocks SMS broadcasts and cadence SMS steps.
  • Do-not-contact can block multiple outreach channels.
  • Do-not-email blocks email separately.
  • Missing form consent can prevent marketing SMS even when the record exists.

What to do

  • Do not manually override without documented consent.
  • Remove the record from SMS cadences.
  • Use notes to record consent changes when your policy allows them.
  • Escalate edge cases to an admin or compliance owner.
Contact or lead profile showing do-not-contact, do-not-email, SMS opt-out, and consent status fields.
Contact or lead profile showing do-not-contact, do-not-email, SMS opt-out, and consent status fields.

Ready to try this in FlowForce?

Start free — set up your workspace and follow along with this guide.