> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate blocked outbound calls

> Understand the calling-preference and DNC checks in the GHL Make AI Call path.

The GoHighLevel **Make AI Call** path checks the destination and available contact calling preferences before placing a call. Use the returned error to identify a block before retrying.

This guide describes that GHL calling path. It does not establish that every calling entry point performs identical checks.

## Investigate a blocked request

1. Open the failed workflow execution and read the action's returned error message.
2. Identify the destination phone number and GHL contact used in that execution.
3. Check the contact's calling Do Not Disturb preference and your opt-out records.
4. Check the selected outgoing number and the account's screening configuration.
5. Pause automated retries while a DNC or calling Do Not Disturb block is being reviewed.

| Returned reason | Meaning |
| - | - |
| Number on platform DNC list | The destination matched the platform's blocked-number list. |
| Contact is DND for calling | The retrieved contact has global DND enabled or an active calling DND preference. |
| Number on internal DNC list | The destination matched the account-scoped internal list. |
| Number on national DNC list | The external lookup returned a registered match. |

Do not remove an opt-out or change screening settings simply to make a blocked request run. Resolve the underlying calling preference with the person responsible for your calling policy.

## How the checks run

The platform DNC check runs first. A match blocks the call regardless of the conditional screening rules below. Next, a calling Do Not Disturb preference blocks the call when the contact data is retrieved.

After those checks, the path determines whether to run internal and external registry checks. An imported outgoing number with the account's compliance-bypass configuration can skip those later checks. Otherwise, recognized GHL attribution evidence can skip them. If neither condition applies, an internal or external match blocks the call.

Attribution is an input to this screening decision. It is not proof that the person gave permission to receive a call.

## When lookup data is unavailable

If the GHL contact lookup fails, the request can continue with number-based screening without reading that contact's DND preference. Check the GHL connection and contact lookup when an expected preference was not applied.

The external DNC lookup also does not always stop the call on failure. A timeout, provider error, or unavailable result can be treated as no returned match. A call proceeding therefore does not prove that the external registry was successfully checked or that the destination was clear.

Platform checks support your calling workflow; they do not establish permission to call or guarantee legal compliance. Keep your own contact preferences and opt-out process accurate.

## Related guides

* [Place an outbound call](/v3/guides/calling/outbound-calls)
* [Diagnose failed calls](/v3/guides/troubleshooting/failed-calls)
* [v3 errors reference](/v3/errors)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.