Consent Fields
Every contact carries three consent fields from your CSV upload:
Contacts that fail these gates are marked Blocked with a plain-English reason, for example “Contact is missing prior express written consent and must not be dialled”, and are never dialed. See Block Reasons Reference for the full list.
Contacts added through the On-Demand Call API are held to the same consent gates, DNC checks and calling-hours rules when their call is due.
A contact you upload with
is_voice_call_opted_out set to true is also registered on your internal DNC list. Re-uploading an existing contact with that value changed from true to false takes the number off the list again, when a SAN is configured. If registration can’t complete, for example because no SAN is saved yet or the Do-Not-Call service was unavailable, the upload still succeeds and shows a warning, and the contact stays opted out. See Upload Behavior.
DNC Scrubbing
DNC scrubbing is on for every voice campaign. SquawkVoice manages it for you, so a campaign has no switch for it. When you launch a run, the platform checks numbers against the Do-Not-Call registries and litigator lists, plus your account’s internal DNC list. Each dial then uses that result. What a result does to the dial:
Only contacts that pass the consent checks are scrubbed and charged. The scrub covers US and Canadian numbers. A contact with a number in another country skips it, is dialed (subject to the consent fields and the calling-hours rules) and isn’t charged the scrub fee. Test calls with dialing rules enforced follow the same scope.
If the check vendor is unavailable, the contact is skipped rather than dialed unchecked, and isn’t charged. It shows as Failed, not Blocked, with the reason Scrubbing failed. Once the run ends, launching the campaign again starts a new run, and the contact goes through the check again.
Reassigned-Number check. The check that looks for numbers that changed hands after consent was captured isn’t active at the moment. No contact is currently held back for a reassigned number.
SAN — Subscription Account Number
DNC scrubbing requires a SAN from the National Do Not Call Registry:- Open Manage → Campaigns and click the settings gear (Account-level campaign settings), or follow the DNC SAN Setup prompt in the campaign editor. If Campaigns isn’t in your sidebar, see Navigating Studio.
- In the Campaign account settings drawer, enter your Subscription Account Number (SAN) and save.
- Don’t have one? Get it at telemarketing.donotcall.gov — subscribe to the area codes you plan to dial (the first five are included in the annual fee).
What scrubbing costs
Charges apply once per contact per run, when the check’s result is used to decide the dial. A contact the check stops, such as one on your internal DNC list, is charged too. Retries within a run never re-charge, but re-launching the campaign starts a new run and re-charges each contact it processes. DNC charges appear in each call’s cost breakdown in Call History (as DNC scrubbing cost) and on your invoice. A contact the check stops has no call, so it appears in Call History as a Blocked — DNC row that carries only the charge. See Blocked Dial Attempts.
In-Call Opt-Outs (DNC Requests)
If a contact tells the agent to stop calling:- The agent speaks your configured On DNC Request message.
- The call ends with the disposition DNC Request.
- The number is registered on your internal DNC list immediately — opt-outs are dispatched with priority so they can never be lost to a slow post-call step.
- The contact is marked Blocked in the run, with the reason Dnc.
Legal Calling Hours & Frequency Caps
- Each contact’s local timezone (resolved from ZIP code, falling back to phone area code) determines the legal calling window that applies to them; out-of-window contacts are queued, not dialed. See Scheduling.
- State frequency limits (for example, Florida’s 3-calls-per-24-hours rule) hold contacts in a “Frequency capped” state until the window expires.
Launch Attestation
Launching from a campaign’s own page requires confirming the Confirm Compliance dialog: that you have obtained all required consents and that the campaign complies with the TCPA and other applicable laws. With DNC scrubbing on (the default), you additionally attest that the SAN on your account is the one you intend to use for compliance scrubbing. Confirming records the attestation in the campaign’s audit trail. The Launch and Relaunch icons on each row of the Manage → Campaigns list start the run directly and record the attestation without showing the dialog. Your consent and TCPA obligations are the same however you launch. To go through the confirmation step, launch from the campaign’s own page. A launch through Squawk Co-pilot records the same attestation, but collects it in the chat instead of the dialog. The Co-pilot first checks the launch prerequisites (including the SAN when scrubbing is on) and tells you what’s missing; once they’re met, it asks you to confirm that the campaign tells people they’re talking to an automated agent, then shows a confirmation card with Launch campaign before anything dials. It doesn’t walk through the dialog’s consent and TCPA statements, so those obligations are still yours before you launch.Block Reasons Reference
The Reason column in Live Monitoring and on the run’s contact table, and the reason column of the contacts CSV export, explain in plain English why a contact was blocked or held back. For a contact stopped at dial time, that is the compliance check’s own sentence. The same sentence appears under Detail for the attempt in the contact’s dial history. The summary line at the top of the drawer reads Blocked — followed by the same sentence, with each word capitalized.A run works from its own copy of your contact list, taken at launch, so correcting the list doesn’t change contacts already blocked in the current run. To fix a contact, stop the run or let it finish, correct the list, then relaunch. See Launching & Live Monitoring.
Audit Trail
- Campaign lifecycle events (create, launch, attestation, pause/resume/stop, window transitions) are retained in a dedicated campaign audit log.
- Every dial decision — placed, queued, or blocked, with its TCPA context — is recorded per attempt and visible in the contact’s dial history.
- Campaign configuration changes also appear in the platform-wide Audit Logs.
Where to go next
Contact Lists
How the consent columns are uploaded and validated.
Launching & Live Monitoring
Where blocked contacts and TCPA decisions surface.