Opt-outs and compliance

How STOP/START works, subscription status, and staying compliant.

Text messaging is permission-based. Helios handles the mechanics (opt-out keywords, compliance language, send blocking), but the permission itself is yours to collect and honor.

Subscription status

Every contact is either Subscribed (green badge) or Unsubscribed (red). The status shows in the contacts table’s Opt-in status column, on the contact profile, and you can filter the contacts list by it.

STOP and START

Helios processes the standard keywords automatically on every inbound text:

• A message of STOP immediately marks the contact Unsubscribed. No action needed from your team.
• A message of START resubscribes them.

Unsubscribed contacts are excluded from SMS sends automatically: blasts and flows simply skip them. You don’t need to prune lists by hand.

You can also toggle a contact manually from their profile (Opt out / Opt in), which is useful when someone asks in person or over the phone.

Opt-out language on marketing sends

Helios appends “Reply STOP to optout” to blasts, and the composer notes “Includes opt-out language” with the character count reflecting it. This keeps every marketing message compliant without you having to remember the footer.

Collecting permission

Consent should exist before the first marketing message:

• Forms: a Helios form is inherently opt-in: the person submits their own number.
• Keywords and QR codes: texting your number first is opt-in by definition. See QR codes.
• Imports: the import flow requires you to confirm you have explicit permission for everyone in the file. Don’t import purchased or scraped lists; carriers filter aggressively, and it can get your number flagged.

Blocking

Separate from opt-out, Block on a contact profile stops all communication with that contact in both directions. Use it for spam and abuse; use opt-out for marketing preferences.