VICIdial settings for TCPA compliance
The VICIdial-side config a compliant outbound program needs - Local Call Time, Drop SLA, internal DNC, Campaign CID - plus the records to keep as evidence.
This page is the config half: which VICIdial screens and fields you set, and what to keep afterwards. It is operator guidance, not legal advice.
For what the statute actually says - the seven requirements, the penalties, the 2024 and 2025 FCC rulings - read TCPA compliance for outbound dialing first. This page assumes you already know the rules and wants to know where the knobs are.
The settings that map to a rule
| Requirement | Where it lives in VICIdial |
|---|---|
| Local call-time windows | Campaign → Local Call Time. Area-code → local-time mapping is built in. |
| Drop-rate cap (≤ 3%) | Campaign → Drop SLA = 2.0. The setting enforces the 2-second timer, not the 3% cap. |
| Internal opt-out list | Campaign → Use Internal DNC = Y |
| Federal DNC | Load DNC.gov data into vicidial_dnc scoped campaign_id='all' |
| Caller ID | Campaign → Campaign CID - a number you own and answer |
| Agent identification | Agent script (Admin → Scripts), first 30 seconds of the call |
The one that trips people up: Drop SLA is a timer, not a cap. Setting it to 2.0 makes VICIdial count a call as dropped after two seconds without an agent. Staying under 3% is still your job - watch the abandonment column daily and cut the dial level when it climbs. See your first campaign for where dial level lives.
The DNC side has three layers and its own page: DNC list management.
Pre-clean lists before you load them
Both the Reassigned-Numbers Database check and litigator screening happen before the CSV reaches VICIdial - there is no VICIdial setting for either.
- RND - the FCC's reassigned-numbers database. Roughly $0.0035 per check at volume. Commercial services (Numeracle, Caller ID Reputation, PossibleNOW) will bulk-clean a file for you.
- Litigator alert lists - numbers known to file TCPA complaints. Not part of the regs; a paid feed and a pre-screen pass is cheap insurance next to a class action.
Run both against the file, then load the cleaned file with the List Loader.
Recording config
Recording is regulated state by state, not federally - the recording laws page has the two-party list. On the VICIdial side you need three things:
- Per-campaign Recording Override (Admin → Campaigns → your campaign → Detail View), covered in how to record calls
- A beep or announcement at call start for two-party states, played from the campaign's audio
- A separate campaign for two-party-state lists when their rules differ from the rest
What to keep as evidence
If you are sued, the question is whether you can prove consent and compliance for one specific call. Four artifacts answer it:
- The opt-in record - timestamp, IP, and the exact form text the consumer saw
- The dial log - VICIdial writes this to
vicidial_log - The recording, if the call was recorded
- The DNC checks you ran. VICIdial logs internal DNC hits; federal DNC and RND checks happen outside VICIdial, so log them wherever you run them.
Retention has to outlast the statute of limitations you are exposed to, which is longer than any default log rotation. Plan the export.
What VICIfast does on its side
We do not do compliance for you. What the platform contributes:
- A per-customer audit log of every action your team takes in the dashboard
- Platform 7-Day Backup - a daily database and recordings export, so
vicidial_logis recoverable. Seven days is a rolling window, not an archive; mirror it to your own S3 if you need dial logs kept for years. - Region pinning, so EU calls run on EU servers
- TLS on every endpoint that handles personal data
If a regulator asks you for something specific, ask us - we will see what is possible.