DC — Disconnected

What DC Means

The phone number is no longer in service — the carrier returned a disconnected signal (SIT tones, ‘number not in service’ recording, or specific disconnect carrier codes). The number is dead and should not be redialed.

When This Status Is Set

DC is assigned when the carrier returns an explicit disconnected-number signal — SIT (Special Information Tones), a “the number you have dialed is not in service” recording, or specific SIP response codes like 404/604 — and the call reaches an agent who confirms the disconnection by selecting DC from the disposition screen. It can also be auto-assigned in some configurations where the system detects disconnect signaling before agent routing. DC represents a definitive determination that the phone number is dead, distinguishing it from softer outcomes like NA or ADCT where the number might still be active. The status is written to vicidial_list and logged in vicidial_log with the corresponding term_reason field capturing the specific carrier signal received.

Impact on List Management

DC leads must be permanently excluded from your dial_status_filter — redialing disconnected numbers wastes trunk capacity, inflates your dial count without improving contact rates, and can negatively impact your outbound caller reputation with carriers who monitor call completion ratios. High DC rates are the single strongest indicator of list data quality problems, and they should be tracked per list_id and per vendor_lead_code to hold data vendors accountable. Every DC lead that remains in your active hopper displaces a potentially contactable lead, directly reducing your operation’s throughput. Build an automated process that flags lists exceeding a DC threshold (typically 15-20%) for review or suspension, preventing your agents and trunks from burning through bad data.

Best Practices

• Never include DC in dial_status_filter — each redialed DC wastes 20-30 seconds of trunk time

• High DC rate (over 20%) indicates list hygiene issues — invest in phone verification services before loading new lists

• Report DC rate by list source to evaluate data vendor quality and negotiate SLAs around data freshness

• Consider auto-scrubbing DC leads from active lists after first DC result to immediately free hopper capacity

• Build a master DC suppression file and scrub all new list imports against it to prevent re-purchasing numbers you already know are dead

Admin Configuration

DC is a system-level status defined in Admin → System Statuses with callable set to N and human_answered set to N. Agents can select DC from the disposition screen when they hear a disconnected recording, so selectable may be set to Y in campaigns where disconnect calls are routed to agents. To analyze DC volumes and trends, use the Admin → Status Category report or query vicidial_list grouped by status = 'DC' and list_id. The system-level DC status properties are inherited by all campaigns unless overridden at the campaign level in Campaign Detail → Statuses.

ViciStack’s List Management module monitors disposition distribution in real time — automatically adjusting recycling logic, dial_status_filter priorities, and hopper fill strategies based on how your dispositions are trending. No manual SQL, no spreadsheet audits.