Compliance

Admin→ Compliance helps you control how DripDrop handles email and SMS opt-outs, bounces, spam complaints, and active flow enrollments. Use this page when you need to understand why a contact stopped receiving messages or how account-level compliance settings affect running flows.

Note
This page is operational guidance for using DripDrop. It is not legal advice.

Admin→Compliance controls account-level handling for:

  • Email unsubscribes
  • Email spam complaints
  • Email hard bounces
  • SMS opt-out keywords such as STOP
  • SMS opt-in keywords such as START
  • What happens to active flow enrollments after an opt-out or bounce event

These settings help keep future messages from being sent to contacts who opted out, bounced, or otherwise became suppressed.

Before changing these settings, confirm:

  • Which email and SMS providers your account uses
  • Whether your messaging program should treat opt-outs account-wide or per provider
  • Whether active flow enrollments should be ended immediately or simply prevented from sending future messages

For most accounts, account-wide settings are the safest default because they reduce the chance that a contact opts out through one provider and continues receiving messages through another.

Email compliance settings control how DripDrop handles unsubscribe clicks, spam complaints, and hard bounces.

Opt-out Scope

Choose how broadly DripDrop should apply an email suppression.

  • Account-wide: an unsubscribe, spam complaint, or hard bounce suppresses that email address across the account.
  • Per integration: suppression applies only to the provider or integration that received the event.

Use account-wide scope when a contact's opt-out should apply to all email sending from the account.

Enrollment Handling

Choose what DripDrop should do to active flow enrollments when an email suppression happens.

  • Unsubscribe all active enrollments: remove the contact from active flows.
  • Only flows sending email through the receiving integration: affect only flows tied to the provider that received the event.
  • Suppress future sends only: keep enrollments active, but block future suppressed sends.

SMS compliance settings control how DripDrop handles SMS opt-out and opt-in keywords.

Opt-out Scope

Choose how broadly DripDrop should apply SMS opt-outs.

  • Account-wide: STOP-style keywords suppress SMS across the account. This is the recommended default for most accounts.
  • Per integration: STOP-style keywords apply only to the provider or integration that received the message.

Supported Opt-out and Opt-in Keywords

DripDrop recognizes common SMS opt-out keywords such as:

  • STOP
  • STOPALL
  • UNSUBSCRIBE
  • CANCEL
  • END
  • QUIT

DripDrop also recognizes opt-in keywords such as:

  • START
  • UNSTOP
  • YES

An opt-in keyword can remove an active SMS suppression according to the selected scope.

Enrollment handling

Choose what DripDrop should do to active flow enrollments when an SMS suppression happens.

  • Unsubscribe all active enrollments: remove the contact from active flows.
  • Only flows sending SMS through the receiving integration: affect only flows tied to the provider that received the event.
  • Suppress future sends only: keep enrollments active, but block future suppressed sends.

DripDrop checks suppression state when a message is about to send. A contact who opted out or bounced should not be messaged again, even if they were already enrolled in a running flow.

Important behavior:

  • Suppression checks are enforced at send time.
  • Opted-out or bounced contacts should not be revived mid-run.
  • Email suppression matching is case-insensitive.
  • Hard bounces suppress future email sends.
  • Temporary delivery issues should not be treated like permanent bounces.

Compliance is separate from user notification preferences.

Use Settings → Notifications for user-level notification consent, such as service notifications or marketing messages sent to account users. Use Admin→Compliance for account-level contact messaging behavior, opt-outs, and suppressions.

SMS and email consent may be tracked separately. Make sure your flows and provider setup match the type of consent you have for each contact.

A contact did not receive a message

Check:

  1. Whether the contact unsubscribed, replied STOP, bounced, or triggered a spam complaint.
  2. Whether suppression is account-wide or per integration.
  3. Whether enrollment handling removed the contact from active flows.
  4. Whether the flow is trying to send through an inactive provider, sender, or template.
A provider is missing in the flow editor

Only active providers and active templates are available when configuring flow blocks. Some providers also require sender setup before they can be used.

Check:

  • Provider status
  • Template status
  • Sender or from-address setup
  • Whether the provider supports the required channel
An unsubscribed contact is still enrolled

If enrollment handling is set to suppress future sends only, the contact may remain enrolled but future suppressed sends are blocked. Use Flow Enrollments or Flow History to confirm what happened.