Troubleshoot compliance and preflight blocks

An HTTP 403 with error: "compliance_blocked" means no normal dial was started. The response includes a callId, all detected blocks, and the disclosure script generated from the submitted context. Preserve that response for review.

Block-code reference

Code	Cause	Corrective action
invalid_to_number	Destination is not valid E.164.	Normalize and validate the real destination; do not guess digits.
invalid_callback_number	Callback number is not valid E.164.	Supply a monitored, non-premium callback number.
missing_ai_voice_consent	Purpose and consent basis do not meet current product policy.	Obtain and record the required consent; do not relabel the purpose.
missing_consent_evidence	Timestamp is invalid/future or evidence reference is empty.	Repair the source record and submit its durable reference.
national_dnc_scrub_required	Telemarketing DNC timestamp is missing, invalid, future, or older than 31 days.	Perform the approved suppression process and record its current timestamp.
quiet_hours	Called-party local time is before 8 a.m. or at/after 9 p.m.	Schedule outside the blocked window.
invalid_time_zone	Time-zone value cannot be evaluated.	Use the called party’s valid IANA time zone.
entity_dnc_blocked	Number is on the account-specific do-not-call list.	Do not call; route to the responsible policy owner if the record is disputed.
compliance_store_unavailable	Required DNC/compliance storage could not be checked.	Wait for service recovery; the system intentionally fails closed.

One request can contain multiple blocks. Fixing the first item does not mean the rest are cleared.

Safe diagnostic sequence

1. Log the callId and block codes, not the full consent evidence or secrets.
2. Compare the request with the source-of-truth consent and caller records.
3. Confirm the stated purpose matches the intended conversation.
4. Validate phone numbers and the IANA time zone independently.
5. For telemarketing, verify the current approved DNC-suppression process.
6. Escalate do-not-call matches or legal uncertainty to the assigned owner.
7. Create a new request only after the underlying facts changed and review allows it.

What not to do

Do not switch telemarketing to transactional, change the called-party time zone, use internal_test, fabricate an evidence reference, or remove recording context merely to pass preflight. Those actions make the request inaccurate and can create additional risk.

Not legal advice: This table documents current CallOnline product behavior. A qualified reviewer should determine the requirements for your organization, campaign, audience, and locations.