How to enable the 24-Hour Call Count Limit

You enable the 24-Hour Call Count Limit in two places: first a system-wide switch in System Settings, then a number on each Campaign you want capped. Once both are set, the system stops dialing a number once it has hit the cap inside any rolling 24-hour window.

Step 1: flip the system switch

Go to Admin then System Settings and turn on "Enable 24-Hour Called Count Limits". This is a global gate. Until it is on, nothing you set on a campaign has any effect. Think of it as the master breaker: the per-campaign dials are downstream of it.

This limit is different from the older Daily limit. The Daily limit resets at a fixed end-of-day time, so a number could be called late one evening and again early the next morning and still stay under a per-day count. The 24-hour version is a rolling window measured against the database server clock, so it counts the trailing 24 hours from right now, every time.

Step 2: set the number on the campaign

Open Modify Campaign and go to the Detail view. Find "24-Hour Called Count Limit" and set any value of 0 or higher. A 0 means off for that campaign. If you set it to 1, a Lead reached at 11:01 cannot be reached again until after 11:01 the following day. Set it to 3 and you allow three attempts before the window closes.

Two more settings sit next to that number and decide how the count is read:

• 24-Hour Called Count Limit Method: PHONE_NUMBER counts attempts to a specific phone number no matter which lead it sits on. LEAD counts attempts against the lead record itself.
• 24-Hour Called Count Limit Scope: SYSTEM_WIDE counts every attempt anywhere on the box. CAMPAIGN_LISTS counts only attempts inside the lists tied to this campaign.

Both of those choices change which calls get tallied, so pick them deliberately. We cover the method trade-off in detail in our writeup on the PHONE_NUMBER vs LEAD method.

How a call gets checked

flowchart TD
  A[Lead about to dial] --> B{System switch on}
  B -->|No| F[Dial allowed]
  B -->|Yes| C{Campaign limit set above 0}
  C -->|No| F
  C -->|Yes| D{Count in last 24h below limit}
  D -->|Yes| F
  D -->|No| E[Call blocked]

This affects normal automated dialing across the campaign. It is not the same as Manual dialing (click to dial), where an agent keys in a number themselves, and it works alongside the hopper, which is the pool of leads the dialer pulls from. When the limit blocks a number, that number simply does not get pulled until the window clears.

What this does not cover

This basic setup applies the same cap to everyone the campaign dials. If you need a different number for one state, such as a stricter rule for Florida calls, that is a separate override container. Otherwise, the count, method, and scope above are the whole feature. None of this replaces your DNC (do not call) obligations, your state-dnc lists, or the national-dnc-registry; it is a pacing control, not a do-not-call screen.

Compliance rules vary by jurisdiction and change often, so confirm what your campaigns actually need with a telecom lawyer before you rely on these caps. For the full set of phone-side controls, see our phone-based functions guide. On VICIfast you get a dedicated dialer provisioned in under 40 seconds with these settings ready to configure, so you can test caps on real campaigns the same day. See our pricing to start.