How to Use the Contact DND Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Contact DND trigger runs whenever a contact's Do Not Disturb status changes. Filter by inbound/outbound, channel, and tags to react precisely — opt-out tagging, workflow removal, or re-engagement.

The Contact DND trigger fires whenever a contact's Do Not Disturb status changes. Use it to keep your communications compliant, prevent inbound spam from cluttering pipelines, and re-engage contacts who opt back in.

What you get

  • Automatic compliance actions when contacts opt out
  • Granular control by channel — email, SMS, calls, GMB, Facebook
  • Direction filtering — inbound (block incoming) or outbound (block your sends)
  • Tag-based filters to target specific contact segments

Configure the trigger

  1. Open Automation and click + Create New Workflow. Choose Start from Scratch or open an existing workflow.
  2. Click Add New Trigger and search Contact DND.
  3. Name it descriptively (e.g., SMS Opt-Out).
  4. Set up filters — direction, DND flag, channels, tags.
  5. Save and publish.

Filters

DND Direction

  • Outbound — fires when outbound DND changes. Use this to manage opt-outs from your campaigns.
  • Inbound — fires when inbound DND changes (Calls and SMS only). Use this to block spammers from generating false leads.

DND Flag

  • Disabled DND for All Channels — contact opted back in everywhere. Re-engage.
  • Disabled DND for Specific Channels — contact opted back in on selected channels.
  • Enabled DND for All Channels — full opt-out. Stop all outreach.
  • Enabled DND for Specific Channels — partial opt-out (e.g., just SMS).

Specific Channels

Available after picking the Specific Channels DND flag. Choose any of: SMS, Email, Phone Calls, Google My Business Messages, Facebook Messages.

Tag filter

Restrict the trigger to contacts with specific tags. Operators: Equals, Not Equals, Any Of, None Of. Add multiple tag filters to combine conditions (AND logic).

What causes the trigger to fire

The trigger runs on any DND status change, regardless of source. Sparkforge logs the source in conversations and activity logs:

  • DND enabled/disabled by Workflows
  • DND enabled/disabled by User
  • DND enabled/disabled by Contact

Use cases

Tag and route an SMS opt-out

Filters: Outbound, Enabled DND for Specific Channels, SMS. Actions: add the tag SMS Opt-Out, remove the contact from active SMS sequences, send an internal notification to marketing.

Re-engage opt-ins

Filters: Outbound, Disabled DND for All Channels. Actions: remove the Do Not Contact tag, notify the sales team, add the contact back to the standard nurture workflow.

Sparkforge handles compliance automatically

If a contact has DND enabled on a channel and a workflow tries to message that channel, Sparkforge skips the step. You don't need to remove contacts from every workflow when they opt out — the platform respects DND on each send.

Frequently Asked Questions

What's the difference between inbound and outbound DND?
Outbound DND blocks your sends to a contact (emails, SMS, calls). Inbound DND blocks calls and SMS coming in from that contact — useful for filtering spam. Inbound DND only applies to Calls and SMS.
Should I remove a contact from every workflow when they enable DND?
Usually not. Sparkforge automatically skips communication steps that conflict with DND, so the rest of the workflow (tasks, internal notifications) keeps running. Only fully remove if the contact opts out of all communication.
Can I tag contacts based on DND changes?
Yes. A common pattern is to add tags like DND-SMS or DND-Email when the trigger fires, so other workflows and lists can reference them as exclusion criteria.
What if a contact is mid-workflow when DND changes?
Sparkforge skips communication steps that conflict with the new DND setting. Other actions — tasks, tag changes, internal notifications — keep running.
How do I keep my SMS and email compliant?
Enable the automated compliance settings under Business Profile. Sparkforge appends opt-out language and sender info automatically. Combined with the DND trigger, you cover both proactive blocking and back-end compliance.

Was this article helpful?