GoHighLevel Do-Not-Disturb Sync
Contacts marked do-not-disturb in GoHighLevel aren't added to campaigns and stop being called, and callers who opt out are marked do-not-disturb in GoHighLevel.
Written By voiceaiwrapper
Last updated 26 days ago
When someone doesn't want to be called, it shouldn't matter whether they told your team in GoHighLevel or told your AI agent on a call. VoiceAIWrapper keeps GoHighLevel's do-not-disturb and its own do-not-call in step, always in the safe direction: it can stop calls, but it never starts them again on its own.
This works automatically once GoHighLevel is connected and the sub-account is mapped. There's nothing to turn on. See Connect GoHighLevel and Map Sub-Accounts.
How it works
What counts as do-not-disturb
VoiceAIWrapper treats a GoHighLevel contact as do-not-disturb when either is true:
- The contact's overall do-not-disturb is on.
- Do-not-disturb is on for the Call channel.
Do-not-disturb on other channels only, such as email or SMS, doesn't stop calls.
Before a contact is added
When the Add Lead to Voice Campaign workflow step runs, VoiceAIWrapper reads the contact from GoHighLevel first. If the contact is do-not-disturb, the step is refused with:
This contact is marked do-not-contact in GoHighLevel, so they were not added to the campaign.
You'll find this message in the workflow's execution log, in the step's event details. See GoHighLevel Workflow Actions and Triggers.
After a contact is added
If you turn on do-not-disturb for a contact later, GoHighLevel tells VoiceAIWrapper. Every lead linked to that contact in that sub-account is marked do-not-call, across all campaigns, and isn't called again.
This keeps working even if your plan no longer includes GoHighLevel integration, so opt-outs are always honoured.
In the campaign's Leads tab, the lead shows Do not call. Hover the info icon to see Turned on from GHL (do not disturb). Your clients see Turned on from your CRM (do not disturb). in their portal instead. See Do-Not-Call: Sources and Reasons.
A workflow can stop calling a lead too: use Update Lead in Voice Campaign with Do Not Call on. The reason shown is the same.
When a caller opts out
If the lead is marked do-not-call when a call's results are written back, for example because the caller asked not to be called again, VoiceAIWrapper turns on the contact's overall do-not-disturb in GoHighLevel (not only the Call channel) and adds the vaw-do-not-call tag. The call note also says Caller asked not to be contacted again.
This only happens for leads whose call results go back to GoHighLevel. See Call Results in GoHighLevel Contacts. To detect opt-outs during calls, see Smart Callback and Smart Do-Not-Call.
Calling someone again
VoiceAIWrapper never turns do-not-call off by itself, and neither does a do-not-disturb change in GoHighLevel. The Update Lead in Voice Campaign step can't turn it off either. This is deliberate: someone who asked not to be called is never called again by accident.
If you have permission to call the person again:
- In GoHighLevel, turn off do-not-disturb on the contact. If it stays on, a later do-not-disturb update from GoHighLevel marks the lead do-not-call again.
- In VoiceAIWrapper, open the campaign's Leads tab and turn off the lead's Do not call switch. For several leads at once, select them, then use Bulk Actions β Do Not Call β Do Not Call = False and confirm Allow Calling. See Do-Not-Call: Sources and Reasons.
The one GoHighLevel step that can turn do-not-call off is Bulk Update Leads, and only for a lead whose entry in the list says "do_not_call": false.
Only allow calling again when you have the person's permission. Calling someone who opted out can break consumer-protection rules in many countries.
Limits
- Only leads that came from GoHighLevel are matched. Leads imported by CSV, added by hand or added through the API aren't linked to a GoHighLevel contact, so a do-not-disturb change in GoHighLevel doesn't reach them.
- Bulk Add Leads doesn't check do-not-disturb when it adds a list. A lead in that list with a
contact_idis still stopped if do-not-disturb is turned on for its contact later. - If GoHighLevel can't be reached when Add Lead to Voice Campaign runs, the contact is added without the check.
- Opt-outs only reach GoHighLevel while the sub-account is live. If the sub-account is unmapped, its client is disabled, or your plan no longer includes GoHighLevel integration, call results stop being written back, so a caller's opt-out isn't copied to GoHighLevel. Do-not-call inside VoiceAIWrapper works as usual.
Frequently asked questions
I turned off do-not-disturb in GoHighLevel. Why isn't the lead being called?
I turned off do-not-disturb in GoHighLevel. Why isn't the lead being called?
Turning off do-not-disturb in GoHighLevel never turns calling back on. Turn off the lead's Do not call switch in VoiceAIWrapper, as shown in Calling someone again.
A contact is do-not-disturb for SMS only. Will they be called?
A contact is do-not-disturb for SMS only. Will they be called?
Yes. Only overall do-not-disturb or do-not-disturb on the Call channel stops calls.
Does disconnecting GoHighLevel clear do-not-call on my leads?
Does disconnecting GoHighLevel clear do-not-call on my leads?
No. Leads that are already do-not-call stay that way. After disconnecting, new do-not-disturb changes in GoHighLevel no longer reach VoiceAIWrapper.