Go to production
Compliance: what we enforce
The checks Entrovox runs before every dial, and the consent basis you certify before a campaign goes live.
Entrovox enforces some rules for you at dial time, and you certify the rest. Know which is which before you post volume.
What we enforce
We run these checks for every lead:
- AI disclosure. Each agency sets AI disclosure per campaign, and it is on by default. When it is on, the AI voice agent's first words identify it as automated. If a call screener answers, the disclosure plays once the person takes the call. Some agency-specific scripts open with a name check before the AI introduces itself. Whatever the setting or script, the AI never denies being automated when asked.
- TCPA calling hours in the lead's timezone. A lead outside its window is queued, not rejected.
- Your agency's DNC list, and leads already marked DNC, before every dial. We do not screen the national DNC registry yet: the consent you certify below is what covers a number on it.
- Recording disclosure in two-party consent states.
- Organization isolation. A bound key cannot see another campaign.
If a number is on DNC at ingest, we reject it so you can resell it. If it lands on DNC mid-sequence, we stop and the lead's disposition becomes dnc_added.
What you certify
If you send a trustedform_cert_url that is not a TrustedForm certificate URL, we reject the lead with 400 CONSENT_INVALID and create no row. Today that is a format check only. Certificates are not yet verified with ActiveProspect, and no campaign-level consent-evidence requirement is enforced yet, so the validity of what you send stays your responsibility. jornaya_leadid is stored and not validated.
On the MediaAlpha native route, an explicit "no" in tcpa_call_consent is also 400 CONSENT_INVALID. See MediaAlpha native post.
How a rejection reaches you
A lead we will never call comes back as a 4xx with no row created: DNC_BLOCKED, CONSENT_INVALID, VALIDATION_ERROR, SOURCE_PAUSED or SOURCE_INACTIVE. Resell the lead and do not retry. In a batch, the same codes come back per row. See Safe retries and idempotency.
Next steps
Run the go-live checklist.