How to Set Up Do Not Disturb (DND) in Sparkforge
DND in Sparkforge controls communication on a per-contact, per-channel basis. Set it manually on a contact record or automate it with workflows tied to opt-out triggers.
Do Not Disturb (DND) lets you stop messages on specific channels for an individual contact. Use it for compliance, opt-out handling, and deliberate VIP routing.
How DND works
DND is set per contact and can apply globally or per channel: Email, SMS, Calls, Facebook Messenger, Google Business Profile (GBP), and WhatsApp. Inbound DND blocks calls at the device level and SMS at the system level (carrier charges still apply).
Configure DND on a contact
- Open Contacts and select the contact.
- Find the DND section in the bottom-left of the profile.
- Enable globally or pick channels (Email, SMS, Calls, GBP, etc.).
- For inbound DND, use the dedicated checkbox for Calls and SMS.
Channel-specific behavior
DND auto-enables when a contact unsubscribes, marks an email as spam, or bounces permanently. To remove it, confirm the address is valid and not on a suppression list, then toggle DND off in the profile.
SMS
DND auto-enables on opt-out keywords (STOP, UNSUBSCRIBE) and on carrier error codes 30003, 30004, 30005, and 30006.
- Temporary DND: remove from the contact record.
- Permanent DND: the contact must reply
START,YES, orUNSTOP, or your agency must submit proof of opt-in to support.
Calls
Inbound DND blocks incoming calls from the contact entirely. Outbound DND stops your team or workflows from dialing that number.
Messenger, GBP, WhatsApp
Once the channel is integrated, DND applies independently. A contact can opt out of one channel and remain active on others.
Automate DND with workflows
Triggers
- Contact DND: fires when DND is enabled or disabled. Filter by channel or direction (Inbound/Outbound).
- Trigger Link Clicked: use unsubscribe trigger links and route to a workflow that sets per-channel DND.
Actions
- DND Contact: enable or disable global or per-channel DND. Set direction to Inbound or Outbound.
- Update Contact Field: log Consent Source or Opt-in Timestamp.
- Remove from Workflow / Stop Campaign: halt scheduled sends the moment DND becomes true.
- Internal Notification: alert the contact owner when a high-value lead opts out.
DND attribution
Conversations and activity logs show who triggered each DND change:
- Workflows: a workflow enabled or disabled DND.
- User: a team member did it manually.
- Contact: the contact opted in or out themselves.
Attribution applies across every channel and requires no setup.
Frequently Asked Questions
What happens when a contact has DND enabled?
Can DND be customized per channel?
How can I tell if a contact has DND on?
Does enabling DND stop every type of message?
Was this article helpful?
Thanks for the feedback.