What hangup cause 17 (user busy) tells you about your list

You are seeing a lot of AB dispositions, or a stack of Cause 17 codes in your disconnect detail. Cause 17 is user busy: the destination phone was on another call and returned a busy signal. VICIdial files a carrier-received busy as AB (Busy Auto), separate from the agent-defined B that an agent sets by hand.

That distinction matters. AB is the dialer believing the carrier, B is a human judgement call. A busy is a kind of Hangup cause, and unlike a reject or a timeout it tells you the line is alive — someone is on it right now.

What a busy actually signals

A single Cause 17 is meaningless. A high Cause 17 rate is a pattern, and the pattern almost always traces back to one of two things: redialing the same numbers too fast, or a list of numbers that genuinely are in use a lot. Neither is a fault in the dialer.

flowchart TD
  A[Call placed] --> B{Far end on another call}
  B -->|Yes| C[Carrier returns Cause 17 busy]
  B -->|No| D[Call rings normally]
  C --> E[Logged as AB Busy Auto]
  E --> F{Redial timing}
  F -->|Too soon| G[Hits busy again]
  F -->|Spaced out| H[Likely connects later]

If you recycle busy leads back into the dial pool within a few minutes, you will hit the same busy line again and rack up AB after AB. That is a timing problem, not a list problem — the same record just keeps catching the person mid-call.

The other side of it is the data. Some lists carry a high share of numbers that stay occupied — shared lines, small businesses with one phone, regions where the number you have is the only one a household uses. None of that is something the dialer can change. It just shows up as AB and stays steady no matter how you tune the box.

What to check, in order

1. Look at your Lead recycling rules for busy. If busies recycle on a very short interval, space them out so the line has time to clear.
2. Break the AB rate down by list. One list far above the rest usually means that data is heavy on numbers that stay occupied, or it has already been dialed hard today.
3. Check your Call times. Dialing a region during its peak personal-phone hours raises busy naturally; shifting the window can drop the rate without touching anything else.
4. Compare AB against your Contact rate. If contact rate is healthy and AB is just a slice, you are fine. If AB is eating into contacts, the redial cadence is the lever to pull.
5. Confirm the carrier is actually sending busy and not mislabeling congestion. Pull a few sample calls and check the underlying cause code on each.

Treat Cause 17 as feedback on cadence and data, not as a defect. The fix is almost always spacing out busy retries and watching which list is generating them.

For the full set of disconnect codes and how they fit together, see the troubleshooting playbook. To see where carrier-returned codes show up per call, read how to read the carrier log report. If you would rather have the dial cadence and recycling tuned for you on a managed box, VICIfast handles it → see plans and pricing.