Phone Calls & DNC Compliance

Assistable.ai includes a built-in, multi-layered Do Not Call (DNC) compliance system that automatically screens outbound AI calls before they are placed. This article explains exactly how the compliance flow works, what bypass options are available, and how to monitor blocked calls during campaigns.

How the DNC Compliance Flow Works

Every outbound AI call initiated through your GoHighLevel (GHL) workflow passes through a series of automated checks before the call is placed. Here is the full decision flow:

Step-by-Step Compliance Flow

1. Call is requested via GHL. A "Make AI Call" action fires in your workflow, sending the call request to Assistable.ai.
2. Lead attribution check. The system checks whether GHL knows where this lead came from (i.e., the lead has source attribution data).
   • If YES (known lead source): The DNC screening is bypassed. A known lead source provides a solid, documented case for contact — you have an established relationship or the lead actively came to you.
   • If NO (unknown lead source): The call enters the full compliance flow described below.
3. Internal DNC list check. The system checks Assistable.ai's own internal records:
   • Has this phone number opted out (requested not to be called) before?
   • Has this phone number hit our screener (been flagged in a previous compliance check) before?
   • If YES to either: The number is flagged as DNC and the call is blocked.
   • If NO to both: The call proceeds to the next check.
4. National & state DNC registry check. The system queries the national Do Not Call registry and applicable state-level DNC registries.
   • If the number is found on any national or state DNC list: The number is flagged as DNC and the call is blocked.
   • If the number is NOT found on any list: The call proceeds normally.

Visual Decision Tree

Call Requested (GHL Workflow)
│
├─ Lead attribution known?
│  ├─ YES → Call proceeds (bypass DNC)
│  └─ NO  → Enter compliance flow
│           │
│           ├─ On internal DNC list?
│           │  ├─ YES → Call BLOCKED (DNC flag)
│           │  └─ NO  → Continue
│           │
│           └─ On national/state DNC registry?
│              ├─ YES → Call BLOCKED (DNC flag)
│              └─ NO  → Call proceeds normally

Bypass Options

In some cases, businesses may want to override the default DNC screening. Assistable.ai provides two bypass mechanisms for users who understand and accept the associated compliance risks.

Option 1: Opt Out of DNC Screening Entirely

You can choose to disable DNC screening for your account entirely. This is common among Real Estate Investors (REI) and other industries where cold outreach is standard practice and management accepts the legal risk.

When you opt out, calls will not be checked against internal DNC lists or national/state registries. All calls will proceed regardless of the number's DNC status.

⚠️ Important: Opting out of DNC screening means your organization assumes full legal responsibility for any calls placed to numbers on Do Not Call registries. This includes potential fines from the FTC/FCC and liability from "honeypot" numbers designed to catch violators. Ensure your management team and legal counsel are aware of this decision.

Option 2: Import Number Bypass

For more granular control, you can bypass DNC checks for specific imported numbers only:

1. Import your phone numbers into the system.
2. Navigate to Account Settings.
3. Enable the option to opt out of DNC for imported numbers.

This bypasses all DNC checks — both internal and registry-based — but only for the specific numbers you have imported. All other calls will continue to go through the standard compliance flow.

💡 Tip: This option is ideal if you have a vetted list of leads from a trusted source and want to ensure they are not incorrectly blocked by DNC screening, while keeping screening active for all other outreach.

Monitoring Blocked Calls in Campaigns

When running outbound calling campaigns, it is important to have visibility into which calls were blocked and why. You can set this up directly in your GHL workflow.

How to Set Up Error Monitoring

1. In your GHL workflow, locate the "Make AI Call" action.
2. Immediately after it, add an If/Else branch.
3. Set the condition to: Make AI Call action return_an_error = true
4. In the "If true" branch, add a notification action (e.g., internal notification, email, or Slack message).
5. Include the variable "Make AI Call Action's Error Message" in the notification body.

This gives you full, real-time visibility into every blocked call, including the specific reason it was blocked (e.g., "Number found on national DNC registry" or "Number previously opted out").

Example Workflow Structure

Trigger → Make AI Call → If/Else
                          ├─ Error = true  → Send notification (with error message)
                          └─ Error = false → Continue workflow

Comparison with GoHighLevel's Native Calling

If you have used GHL's built-in outbound calling, you may have noticed it is very restrictive:

• GHL's native approach: GHL will not allow you to call any leads that haven't explicitly opted in through GHL itself. This means even warm leads from external sources are blocked.
• Assistable.ai's approach: A more nuanced, multi-layered compliance system that balances legitimate outreach with regulatory compliance.

Key Differences

Assistable.ai's attribution-based bypass is a key advantage: if GHL knows where a lead came from (e.g., a form submission, ad click, or referral), the system recognizes that there is a legitimate basis for contact and allows the call to proceed without DNC screening.

This provides significantly more flexibility for businesses that understand the compliance landscape and want to maximize their outreach while staying within responsible boundaries.

Best Practices

• Keep lead attribution clean. The more leads that have proper source attribution in GHL, the fewer will need to go through the DNC compliance flow. Ensure your forms, landing pages, and integrations are properly tagging lead sources.
• Use error monitoring. Always set up the If/Else error branch after your Make AI Call actions. This is your safety net for understanding campaign performance and compliance impact.
• Use import bypass sparingly. Only bypass DNC for imported numbers when you have high confidence in the list quality and source.
• Consult legal counsel. If you plan to opt out of DNC screening entirely, discuss the implications with your legal team first. Regulations vary by state, and penalties for DNC violations can be significant (up to $51,744 per call under FTC rules).
• Review blocked call reports regularly. High block rates may indicate list quality issues or that your outreach strategy needs adjustment.

Frequently Asked Questions

What happens if a lead asks to not be called again?

The number is added to Assistable.ai's internal DNC list. All future call attempts to that number will be automatically blocked, regardless of lead attribution or bypass settings.

Does the DNC check slow down my calls?

The compliance checks happen in milliseconds and do not introduce any noticeable delay to your calling campaigns.

Can I see which specific registry flagged a number?

Yes. The error message returned when a call is blocked includes details about why it was blocked. Use the workflow error monitoring setup described above to capture these messages.

Does this apply to inbound calls too?

No. DNC compliance screening only applies to outbound calls initiated by your workflows. Inbound calls are not affected.