Do-Not-Call: blocking and unblocking leads

Some contacts will tell your AI agent, mid-call, that they never want to be contacted again. GodSetter treats that as a Do-Not-Call (DNC) request and responds with the strongest measure on the platform: the lead is blocked.

Blocking lives in GodSetter itself, not in your CRM. A CRM tag is applied so your automations can react, but the tag mirrors the event — it is not the switch.

How a lead gets blocked

• Automatically, from the call. When the contact asks not to be contacted again, the call outcome becomes DNC. GodSetter blocks the lead and applies the configurable "Do not contact (DNC)" tag to the contact in your CRM (tag names are set in Settings → CRM tags).
• Manually, by an operator. On the lead detail page, the Do Not Call card has a Block lead action. Use it when a stop-calling request reaches you through another channel — an email, a complaint, a client's request.
• From your CRM. With the GodSetter Marketplace app installed, a contact put on Do-Not-Call in GoHighLevel — or deleted there — is blocked here too, within seconds of the change: every call queued or scheduled for that lead is dropped, and the block is recorded in the Audit page with the CRM event that caused it. The same happens when someone adds your disconnect tag to a contact: one tag, chosen in Settings → CRM tags (default disconnect-godsetter, empty = disabled), that takes that contact out of GodSetter on the spot — see the disconnect tag.

Operator block and unblock actions are recorded in the Audit page.

What blocking does

A blocked lead is excluded everywhere:

The dialer also re-checks the block right before dialing, so a lead blocked while already waiting in the queue is still never called — and records that refusal on the lead, so you see why a queued call never went out.

Where you see it

• The Leads page shows a Blocked badge in the Status column, a Blocked filter, and a blocked count in the page summary.
• The lead detail page shows the Blocked badge next to the name and a Do Not Call card with the current status and the hint "This lead is on the Do-Not-Call list — the dialer will never call it."
• When a workflow trigger is refused because the lead is blocked, the Leads page replaces the last outcome with a Skipped: contact blocked (DNC) badge, and the lead detail shows the same reason in a Last skip row — so a workflow still firing on a blocked contact is visible instead of silent.

How to unblock

Only an operator can unblock a lead, and only from one place: the lead detail page → Do Not Call card → Unblock lead. The action is recorded in the Audit page, so you always know who reversed a block and when. It needs editor access on the Leads area: a team member with read-only access can see the Do Not Call card but cannot flip it.

The typical case is a mistaken DNC: the AI misread an ambiguous phrase and classified the call as a do-not-call request. Open the lead's call history, read the transcript of the call that triggered the block, and if it was a mistake, unblock the lead — from that moment new triggers for the contact are accepted again.

Removing the CRM tag does not unblock

The DNC tag exists for your CRM automations. GodSetter's behavior depends on the event recorded on the platform, not on the tag: renaming, clearing or deleting the tag in your CRM leaves the lead exactly as blocked as before. Unblock lead on the lead detail page is the only way to lift a block.

The same holds for your CRM's own Do-Not-Call switch: turning it off in GoHighLevel never unblocks a lead here. The sync from the CRM can only ever block — reopening a block is an operator's decision.

Where to go next

1. Consent, strict mode and proof — the other compliance guardrail.
2. Customize your CRM tags — including the DNC and "Skipped: blocked lead" tags.
3. Calls are not firing — full checklist — a blocked lead is one of the checks.