AI Call Error Tags
When the Make AI Call action encounters an error, Assistable.ai automatically applies an error tag to the contact. These tags identify exactly what went wrong — whether it was a rate limit, a DNC hit, a billing issue, or something else — so you can build workflows that respond intelligently to each failure scenario.
In addition to the tag, two custom fields are populated on the contact: Make AI Call returned_an_error (boolean) and error_message (human-readable description). However, because tags are far easier to use as workflow triggers in GoHighLevel, the automatic error tags are the recommended way to build automation around call failures.
Error Tags Reference
The following tags are automatically added to a contact when the corresponding error occurs during a Make AI Call action:
| Error Condition | Tag | Description |
|---|---|---|
| Rate limit exceeded | ai_call_error_rate_limit | The account has hit its concurrency or per-minute call limit. The call was not placed. Retry after a short delay or reduce campaign volume. |
| Internal DNC | ai_call_error_internal_dnc | The contact's number appears on the internal Do Not Call list (non-opt-out, no GHL attribution). The call was blocked before dialing. |
| National DNC | ai_call_error_national_dnc | The contact's number is registered on the national Do Not Call registry. The call was blocked to maintain TCPA compliance. |
| Workspace negative balance | ai_call_error_workspace_negative_balance | The workspace-level wallet balance is insufficient. All sub-accounts under this workspace are affected until funds are added. |
| Sub-account negative balance | ai_call_error_account_negative_balance | The sub-account's wallet balance is insufficient. Top up the sub-account wallet to resume calling. |
| Workspace inactive | ai_call_error_workspace_inactive | The workspace subscription is cancelled or the account limit is set to 0. Reactivate the subscription to restore service. |
| No from number | ai_call_error_no_from_number | The assistant does not have a phone number assigned, and/or the number pool is empty. Assign a number to the assistant or populate the number pool. |
| Invalid destination | ai_call_error_invalid_destination | A platform number is attempting to call a non-US/non-Canadian (+1) destination. International dialing is not supported for platform numbers. |
| Invalid assistant | ai_call_error_invalid_assistant | The location (sub-account) does not own the assistant ID specified in the action. Verify the assistant ID belongs to the correct sub-account. |
| Contact is DND | ai_call_error_dnd | The contact has Do Not Disturb enabled for the calling channel in GoHighLevel. The call was not placed. |
| Unknown / catch-all | ai_call_error_unknown | An unexpected error occurred upstream or an unrecognized error was returned. Check logs or contact support if this persists. |
| Number pool empty | ai_call_error_invalid_number_pool | A number pool is configured for the assistant but contains no numbers. Add numbers to the pool or assign a direct number. |
| Sub-account banned | ai_call_error_banned | The sub-account has been banned due to honeypot hits or persistent non-compliant calling activity. Contact support for resolution. |
How to Use Error Tags in Workflows
Error tags are designed to integrate seamlessly with GoHighLevel workflows. Here's how to build automations around them:
Basic Pattern: Trigger on Tag Added
- Create a new workflow in your GHL sub-account.
- Set the trigger to "Tag Added" and select the specific error tag you want to handle (e.g.,
ai_call_error_rate_limit). - Add your desired actions — for example, wait and retry, send a notification, or move the contact to a different campaign.
Common Automation Examples
- Rate limit retry: Trigger on
ai_call_error_rate_limit→ Wait 5 minutes → Remove the error tag → Re-run the Make AI Call action. - Balance alerts: Trigger on
ai_call_error_workspace_negative_balanceorai_call_error_account_negative_balance→ Send an internal notification (email, SMS, or Slack) to the account admin to top up funds. - DNC handling: Trigger on
ai_call_error_national_dncorai_call_error_internal_dnc→ Move contact to an email-only or SMS-only campaign to continue engagement without calling. - Catch-all monitoring: Trigger on
ai_call_error_unknown→ Send an alert to your team for manual review. - Ban notification: Trigger on
ai_call_error_banned→ Immediately notify the account owner and pause all calling campaigns.
Tips
- You can create a single workflow with multiple triggers (one per error tag) that routes to different branches using If/Else conditions.
- Always remove the error tag after handling it if you plan to retry the call — otherwise the tag-added trigger won't fire again for the same tag.
- Use the
error_messagecustom field in notification templates to give admins the full error detail.
DNC Bypass Tag
⚠️ Coming Soon: This feature is scheduled for release on Monday, March 2nd, 2026 and is not yet available in production.
A special tag will be available to bypass DNC screening for contacts:
i_agree_responsibility_for_dnc_bypass
When this tag is present on a contact, the Make AI Call action will skip both internal and national DNC checks for that contact.
🚨 Legal Liability Warning: By applying this tag, the owner of the sub-account assumes COMPLETE LIABILITY for all TCPA lawsuits, fines, or fees associated with calling contacts who are on the Do Not Call registry. Assistable.ai and the workspace owner bear no responsibility for any legal consequences resulting from the use of this bypass. Use at your own risk.
This tag should only be used when you have explicit, documented consent from the contact to receive calls, or when a legal exemption applies (e.g., existing business relationship). Consult with a TCPA attorney before using this feature at scale.