How to Automatically Stop Marketing Messages Using the Contact DND Trigger in GoHighLevel

There is one message no business can afford to send: the one that goes to somebody who already asked you to stop. It damages trust, it generates complaints, and with SMS and email it puts your sending reputation and your account at real risk.

GoHighLevel handles the mechanical side automatically. When a contact has Do Not Disturb enabled, the platform skips communication steps that conflict with it. What it does not do on its own is tell your team, tidy up your tags or pull that person out of the campaigns they are sitting in. That is what the Contact DND trigger is for.

What the Contact DND Trigger Actually Does

The trigger fires a workflow whenever a contact's DND status changes, in both directions. It fires when somebody opts out, and it fires when somebody opts back in, which is the half most people forget to build for.

Critically, it runs no matter what caused the change. HighLevel logs the source of every DND change in the conversation record and the activity log, and it recognises three:

• DND enabled or disabled by a workflow, for one channel or all of them, using the DND Contact action.

• DND enabled or disabled by a user, meaning somebody on your team toggled it manually on the record.

• DND enabled or disabled by the contact, which is the automatic route: an unsubscribe click, a spam complaint, a hard bounce, or an SMS opt out keyword such as STOP.

  

That last group is why the trigger matters. A contact replying STOP to a text sets DND on the SMS channel within seconds and with no human involved. If your workflow is listening, you can tag them, notify the right person and remove them from active campaigns before anybody notices there was something to handle.

Inbound Versus Outbound, and Why It Matters

GoHighLevel splits DND into two directions, and picking the wrong one is the most common mistake on this trigger.

Outbound DND controls whether you can send communications to a contact. Emails, texts and calls leaving your account are what gets blocked. This is the direction that maps to opt outs, unsubscribes and marketing consent, and it is what nearly every compliance workflow should use.

Inbound DND controls whether incoming calls and SMS from a contact reach you, and it applies to the Calls and SMS channels only. Its real use is spam filtering: a number that keeps calling your tracking line and clogging the pipeline with junk opportunities can be blocked at the door.

Build a workflow meant to catch unsubscribes but set the direction to Inbound and it will look correct on the canvas and never fire once.

Setting Up the Trigger Step by Step

Open Automation, then Workflows, then Create Workflow and Start from Scratch. On the empty canvas click Add New Trigger and look under the Contact group, where Contact DND sits between Contact Created and Contact Tag.

Give the trigger a name that describes the exact event. HighLevel's own example is DND for WhatsApp, and that level of specificity is right, because a compliance account tends to accumulate several of these.

Then click Add filters and choose DND direction is, picking Inbound or Outbound.

The DND Flag: Four Options That Cover Everything

The second filter is DND flag is, and it decides which kind of change you are listening for.

• Enabled DND for all channels.Fires when a contact opts out of everything. This is your full unsubscribe event.

• Enabled DND for specific channels.Fires when DND is switched on for named channels only, which is the correct choice for an SMS opt out where email consent still stands.

• Disabled DND for all channels.Fires when a contact opts fully back in, so you can strip the do not contact tag and re enrol them automatically.

• Disabled DND for specific channels.Fires when DND is switched off for particular channels, letting you resume one without touching the others.

Choosing either specific channel option reveals a third filter,DND Channel is. The channels include SMS, Email, Phone Calls, Google My Business messages and Facebook messages, with WhatsApp available where it is connected.

You can narrow further with a Tag filter, using the operators Equals to, Not Equals to, Any of and None of. That is how you run a different process for existing clients than for cold leads, which is usually worth doing, since a client unsubscribing is a retention signal rather than a marketing one.

Where DND Lives on the Contact Record

Open any contact and the DND panel sits in the left column. There is a single DND all channels switch at the top, individual switches for Emails,Text Messages,Calls and Voicemails and GBP underneath, and a separate control for DND Inbound Calls and SMS.

Every switch there fires the trigger when it changes, so one workflow covers manual changes by staff as well as automatic opt outs by contacts. It also doubles as your test harness: toggling a channel on a test contact is the quickest way to confirm a new workflow is live.

One practical note. A temporary DND can be updated directly on the record, but a permanent DND applied through a carrier level opt out generally requires the contact to opt back in themselves, usually by sending a keyword such as START. Do not promise a client you can simply switch a hard opt out back on.

What the Platform Handles, and What It Does Not

HighLevel automatically skips any communication step that conflicts with a contact's DND settings. If a contact has email DND enabled while sitting inside a nurture sequence, the email steps are skipped and the rest of the workflow, including tasks, tags and internal notifications, keeps running.

So you do not need to strip contacts out of every workflow the moment they enable DND. Compliance is already enforced at the send step, and removing people wholesale usually destroys your reporting and breaks sequences doing useful non messaging work.

What the platform does not do is the surrounding operational work: tagging, notifying, updating a field, logging the reason, or reacting to somebody opting back in. Worth pairing with all of it are the automated compliance settings under Business Profile, which add opt out language and sender information to SMS and emails automatically.

Frequently Asked Questions

What is the difference between inbound and outbound DND?

Outbound DND controls whether you can send communications to a contact, covering emails, texts and calls leaving your account. Inbound DND controls whether incoming calls and SMS from that contact are allowed through, and it applies to the Calls and SMS channels only. Compliance and opt out work almost always uses Outbound.

Should I remove a contact from all workflows when they enable DND?

Not necessarily. HighLevel already skips communication steps that conflict with a contact's DND settings, so the messages will not send regardless. Removing them from everything usually costs you reporting and stops non messaging steps that were still useful.

Does the trigger fire when my own team toggles DND manually?

Yes. It runs when a contact's DND status changes no matter what caused it. HighLevel logs the source as changed by a workflow, by a user or by the contact, and all three fire it. That makes it a reliable place to hang your tagging and notification logic.

Can I set DND for one channel without affecting the others?

Yes. The DND panel on the contact record has individual switches per channel, and the trigger has matching options through the DND flag and DND Channel filters. A contact can be opted out of SMS while remaining fully contactable by email.

Need Expert Help with GoHighLevel?

New to GoHighLevel and ready to get started? Buy your GoHighLevel account here and launch with confidence.

Already know what you need and want our team to handle everything, from complete setup and customization to funnels, workflows, automations, CRM, and pipelines? Click here.