What the system-wide phone number daily call count limit does

The system-wide phone number daily call count limit is a per-campaign option that counts every call placed from the campaigns it is enabled on, then tracks those daily counts per phone number across your whole system. It resets at the Timeclock End of Day time set in System Settings, not at midnight.

The key word is system-wide. Where the ordinary daily limit watches a Lead inside one Campaign, this option watches a phone number everywhere it appears, so the same number loaded into several lists shares one daily tally.

How counting and reset work

Turn it on for a campaign and every call that campaign places adds to a per-number counter that spans the system. When the Timeclock reaches its End of Day time, all of those per-number counts reset together. That reset point is whatever you configured in System Settings, so the daily window is defined by your timeclock rather than the calendar.

• Counts are kept per phone number, not per lead, so duplicates of the same number across lists are all governed by one total.
• Counting spans the whole system once enabled on a campaign, not just that campaign's own lists.
• The reset happens at Timeclock End of Day, which you set in Admin -> System Settings.

Where it can conflict

Because this limit reaches across the system and counts by number, it does not always play nicely with features that re-queue records or chase alternate numbers.

flowchart TD
  A[Call placed from enabled campaign] --> B[Per-number count plus one]
  B --> C{Number at daily limit?}
  C -->|No| D[Next call allowed]
  C -->|Yes| E[Further dials blocked]
  E --> F{Scheduled callback?}
  F -->|Yes| G[Still auto-dialed]
  F -->|No| H[Wait for Timeclock reset]

The conflict comes from a mismatch in how those features think. Auto-Alt-Dial and Lead recycling both try to keep dialing within a single pass, while this limit is trying to hold a per-number ceiling for the whole day. When the two collide, you can see counts move in ways that surprise you, or records re-dialed when you expected them to be parked. If you must run them together, start with a small test list, watch the per-number counts over a full timeclock day, and confirm the cap holds before you point it at production data.

One important exception: it does not affect scheduled callbacks. A Scheduled callback can still be auto-dialed even if doing so pushes a number past its daily count, so a promised callback is never silently dropped by this limit. That carve-out keeps your commitments to customers intact while the cap still throttles ordinary dialing.

When to use it

Reach for this option when you must guarantee that a given phone number is not dialed more than N times a day across every campaign you run, regardless of which list it sits in. It is the only daily control that thinks in terms of the number rather than the record. It is a dialing cap, not a DNC (do not call) mechanism, so keep your suppression lists in place alongside it.

If you need a rolling window instead of a fixed reset, look at the 24-Hour Call Count Limit. The phone-based functions guide lays out how all these controls fit together.

VICIfast gives you a dedicated VICIdial box in under 40 seconds, so you can set your Timeclock End of Day and this per-number cap the same afternoon. See our pricing to begin.