VICIdial for debt collection - TCPA scrubbing
Managed VICIdial hosting for collections agencies. Per-trunk TCPA scrubbing, backups to your own S3 bucket for multi-year retention, an activity log, and the VICIdial settings collections teams change.

Debt collection is the highest-volume, highest-regulated VICIdial use case in the US. Per-call TCPA scrubbing, FDCPA-aware dialer config, and 2–7 year recording retention are the table stakes. This page covers what the platform adds - litigator scrubbing, backups and an activity log - and the VICIdial settings you set per campaign yourself.
Why managed VICIdial fits collections
Self-hosting works for shops with a full-time Linux + Asterisk admin. Most agencies grow past their initial setup faster than their ops capacity grows - managed hosting scales without that hire.
Concretely, the dialer needs to:
- Run predictive at 100–350 agents on bigger floors (Turbo suits about 200, Hyper about 350)
- Scrub every dial against a TCPA litigator list before connecting
- Honor state-by-state call windows (NY, CA, MA, FL all have their own)
- Retain recordings for 2–7 years (state-specific)
- Audit-log every state transition for your compliance defense
VICIdial does the predictive dialing and call windows once you set them. The platform adds litigator scrubbing on the trunk (Growth, Pro, Ultimate, Velocity, Turbo and Hyper), backups copied to your own bucket for long retention (every plan) and the Activity log. You bring the leads + your carrier, or use VICIfast Voice.
Pre-dial TCPA scrubbing (per trunk)
The single biggest compliance risk in outbound collections is dialing a known litigator. The platform's TCPA feature checks every dial against Blacklist Alliance before Asterisk places the call - and lets you set the mode per outbound trunk.
Inherit — use the server-wide BLA API key
Custom — use this trunk's own key (different client, different contract)
Disabled — skip BLA for this trunk
Per-trunk matters because a collections agency typically dials for multiple debt portfolios with different compliance contracts. Server-wide settings are too coarse.
You bring the BLA API key. We bring the AGI hook + 6-hour cache + per-trunk override + your choice of allowing or blocking the call when a lookup fails. A matched number is hung up before it rings. Individual checks aren't logged or reported, so keep your own scrub records; changes to a trunk's mode are logged on the Activity page.
See litigator scrubbing on the Trunks tab for how it works.
Plan sizing for collections
| Floor size | Plan suggestion |
|---|---|
| 10–25 agents | Growth |
| 25–50 agents | Pro |
| 50–100 agents | Ultimate |
| 100–200 agents | Turbo (dedicated CPU) |
| 200–350 agents | Hyper (dedicated CPU) |
| 350+ agents | Custom sizing - talk to us |
Every plan here has litigator scrubbing, and every plan can copy backups to your own bucket. Launch, Scale, Pulse and Surge have no scrubbing.
Predictive at scale is RAM-hungry - vicidial_live_agents + vicidial_auto_calls hold a lot in memory. Size by the agent count each plan suggests in the plan picker, and resize up before the floor outgrows it.
Carrier choice
For collections, attestation matters more than per-minute cost. STIR/SHAKEN A-attestation is the difference between a 4% answer rate and a 12% answer rate.
Carriers that suit collections volume (Telnyx has its own trunk template; Bandwidth and Skyetel connect through the generic IP-auth template):
- Bandwidth - direct US carrier, A-attestation, best wholesale rates at >500K min/mo
- Skyetel - wholesale-focused, US-only, very competitive at scale
- Telnyx - good for moderate volume + multi-region
Aggregator-routed carriers get worse answer rates over time as their reputation degrades. Pick direct-route, even if the per-minute is slightly higher.
VICIdial settings that matter
| Setting | Value |
|---|---|
| Local Call Time | 8am-9pm called party local |
| Drop call (seconds) | 2 (FCC 3% drop cap) |
| Use Internal DNC | Y |
| Recording Override | ALLFORCE (mandatory for litigation defense) |
| Calls per Day per Lead | 1 (FDCPA harassment ceiling) |
| Litigator scrub | Set on the trunk, not the campaign: Trunks tab → Compliance defaults |
Set these per campaign, in the dashboard's campaign editor or in vicidial_admin.php. New campaigns start with Drop call (seconds) at 5, VICIdial's default, so change it to 2.
Recording retention
State + federal collection regs typically require 2–7 year retention. Plan storage:
- ~250KB per minute mono
- 100 agents × 4 hours/day × 250 days = ~360 GB / year
Two retention paths:
- Platform Backup (add-on, $9–$49/mo by plan) - a daily backup of the database and recordings at 04:00 UTC, kept 7 days, with download links emailed to the owner; support restores the day you choose. Fine for short-term rollback; not enough for litigation defense at year 3.
- External Backups (BYO S3, on every plan) - each Platform Backup is also copied to your own S3-compatible bucket (AWS S3, Backblaze B2, Wasabi, Cloudflare R2, MinIO). Your bucket, your lifecycle policy. Hold for 2–7 years per your compliance schedule.
The two work together: External Backups copy each Platform Backup, so a daily copy in your bucket needs both.
Sub-user roles
- Owner - agency principal, full control
- Operator - floor supervisor: day-to-day dialer work in every tab, plus reboots; no SSH, firewall, server settings or billing
- Billing - back-office, sees invoices + payment methods, no agent management
- Viewer - read-only auditors, compliance staff
Dashboard actions and server changes land on the Activity page with who did it and when, filterable by server and date. It's one part of your discovery record, next to VICIdial's call logs and your recordings.
Recorded root console sessions
Every root console session opened from the dashboard is recorded keystroke by keystroke under the person who opened it, and can be replayed or downloaded later. SSH keys are only opened on request, for a set period. For SOC2 + customer-attestation reviews that ask "who touched the production system, and what did they do" - replay the actual session. This is a normal feature for VICIfast; on self-hosted you'd assemble it from auditd + tlog + journal-based heuristics.
Why collections teams switch from self-hosted
- Server up in under 40 seconds (measured) vs hours-to-days when you compile Asterisk yourself
- A real dashboard instead of "email a tech / SSH in"
- Audit log ready before the FDCPA suit lands, not after
- Per-trunk TCPA scrubbing built in on Growth, Pro, Ultimate, Velocity, Turbo and Hyper - bring your own Blacklist Alliance key
- Transparent pricing - per server, no per-agent licensing
- Migration from ViciBox - the dashboard's migration tool copies your existing vicidial_* schema and syncs the recordings; see /migrate-from-vicibox
Get started
Start a free trial - card on file, no charge for 7 days. For floor sizes above 100 agents, talk to us first so we can size the right plan + region.