Daily and Concurrent Call Caps: Protect Buyers and Keep Routing Fair

Daily and concurrent call caps give you hard controls over how many calls each buyer or location can take in a day and how many can be active at once. Used correctly, they protect budgets and agent capacity without throwing away good calls. This guide shows how to set caps per target, route overflow intelligently, and tune using real-time analytics.

Key takeaways

• Daily caps protect budgets; concurrent caps protect agent capacity.
• Design caps per target; use priority, weights, or round‑robin to spread volume fairly.
• Always define overflow behavior when a cap is reached: alternate buyers, queue, voicemail.
• Watch cap‑hit rate, concurrency utilization, and answer rate; adjust weekly.
• Small changes in concurrency often outperform big budget swings for stabilizing performance.

What daily and concurrent call caps mean

Definitions and how they differ

• Daily caps: The maximum number of completed calls a target can receive in a calendar day. Once reached, new eligible calls should overflow elsewhere.
• Concurrent caps: The maximum number of active live calls a target can handle at the same time. If all “slots” are busy, the next call must ring a different eligible target, queue, or voicemail.

A daily cap does not control how many calls can ring simultaneously—that’s concurrency. Conversely, a concurrent cap doesn’t limit your total daily volume; it only governs live, in‑progress calls at a given moment. For guidance on setting up pay‑per‑call campaigns that route to multiple buyers, see pay-per-call campaign setup for multi-buyer routing.

Why use both?

• Protect buyer budgets with daily caps so you don’t over‑deliver spend.
• Protect agent capacity with concurrent caps so you don’t flood a small team.
• Keep routing fair across buyers or locations when multiple targets are eligible.

Example:

• A buyer has 5 agents on the phone during business hours. Set the concurrent cap to 5 (matching seats).
• The buyer’s budget aligns to roughly 35 monetizable calls per weekday. Set the daily cap to 35.
• When 5 lines are busy, eligible calls overflow per your routing rules (e.g., queue briefly, then route to alternate buyers). When the daily cap is hit, route all remaining eligible calls to other targets or fallbacks.

Where caps apply in routing

In CallFlow, caps are configured per target (each phone, SIP endpoint, or browser agent target can have its own daily and concurrent cap). Your routing rules determine what happens when a target’s capacity is unavailable:

• Priority lists to try preferred targets first.
• Weighted or round‑robin distribution across peers.
• Simultaneous ring can trigger multiple targets to ring at once; once one answers, the others stop. Concurrency caps still apply to active calls only, so use it selectively.
• Overflow to alternate buyers, a call queue with hold music, or voicemail if nothing else is eligible.

Quick setup checklist

• Define targets per buyer/location/service line with clear names and eligibility (schedule and caller‑state).
• Set conservative daily and concurrent caps per target; adjust with data after the first week.
• Choose routing: priority to VIPs, then weighted or round‑robin for peers; reserve simultaneous ring for short, high‑value tiers.
• Define overflow: remaining eligible buyers → brief queue → voicemail.
• Enable recording, live monitoring, and duplicate‑caller rules; test cap events end‑to‑end before launch.

When and where to apply caps

Pay‑per‑call campaigns

• Buyers with fixed budgets: Daily caps keep delivery within spend plans. If a buyer funds a limited tranche for the week, translate that to a per‑day cap that matches typical weekday volume.
• Specialist teams with limited seats: A small sales pod or intake desk may handle only a handful of concurrent conversations. Set concurrency at or just under seat count.
• Seasonal or high‑variance campaigns: Use conservative concurrency per target and define overflow to a queue or alternate buyers for traffic spikes from ads or broadcasts.

How to throttle inbound calls without losing leads:

• Set a modest concurrent cap per target that reflects current staffing, not wishful thinking.
• Keep a bench of alternate buyers/locations as secondary or tertiary routes.
• Add a queue as a pressure valve for short bursts. Time‑box it and fail to voicemail if the spike outlasts your acceptable wait threshold.

Mapping caps to campaign structure:

• By buyer: Each buyer is a separate target (or set of targets by site/team). Daily caps track budget; concurrency maps to their seats.
• By location: Multi‑location brands can create targets per branch, each with its own caps.
• By service line: Split out high‑value or specialty services as distinct targets to keep budgets and concurrency independent.

Agencies and multi‑location services

• Franchise locations with different hours: Use per‑target schedules and daily caps that align to open hours. After‑hours overflow can go to a 24/7 buyer, a national queue, or voicemail.
• Geographic eligibility: When using caller‑state routing, caps apply only to targets eligible for that state. Ensure every state/time window has at least one overflow destination.
• Field teams with staggered shifts: Adjust concurrency as staffing ramps up during the day. If shifts differ materially, consider separate targets per shift with their own caps and schedules.

Cap design: per‑target numbers, windows, and fairness

Pick the right daily cap

Daily caps should reflect the buyer’s budget and your expectation for “monetizable” calls (your definition: qualified duration, IVR path taken, or other criteria you enforce). Practical steps:

• Start with a conservative daily cap that the buyer historically absorbs while maintaining acceptable answer rates.
• Factor answer rates: If a buyer answers a lower fraction of attempts, set the cap slightly below the budgeted maximum of qualified calls to avoid back‑loading overflow late in the day.
• Avoid single, campaign‑wide daily caps; instead, set per‑target caps so strong performers aren’t throttled by weaker ones.

Dayparting when different caps or hours are needed:

• Create separate targets for day vs. evening, weekdays vs. weekends, or special promos. Each target can have its own schedule, daily cap, and concurrency.
• This keeps reporting and tuning clean. You’ll see which dayparts are hitting caps and can adjust independently.

Pick the right concurrent cap

Translate staffing to concurrent capacity:

• Match the cap to active seats that handle inbound calls. If five agents are logged in, set concurrency to five.
• Leave minimal headroom only if you have a dedicated overflow line or supervisor who can reliably take calls. Otherwise, cap exactly at staffed seats to prevent ring‑no‑answer cascades.
• Revisit concurrency whenever staffing changes. Small increments (e.g., lifting concurrency by one slot during lunch rush) often stabilize answer rates without inflating daily budgets.

Simultaneous ring vs. priority/weighted:

• Simultaneous ring speeds up answer times by alerting multiple targets at once; when one answers, the rest stop ringing. Concurrency caps apply to active calls only, but aggressive use can still create coordination issues—fine for VIP paths, risky for general routing.
• Preferred approach: use priority to try the best target first, then weighted or round‑robin among peers. Reserve simultaneous ring for short, high‑value tiers with tight caps.

Fair distribution across buyers

• Round‑robin: Cycles evenly across eligible buyers. Good for fairness when performance is comparable.
• Weighted: Favor preferred partners while still giving volume to others. Set clear weights that align to buyer capacity and quality.
• Priority lists: Route to VIP buyers first; only cascade when unavailable or capped. Pair with daily caps to prevent one VIP from absorbing the entire day early.
• Duplicate‑caller handling: Enable duplicate‑caller rules so repeat callers don’t burn through multiple deliveries or re‑hit caps within your cooling window.
• Respect eligibility: Caps only help when targets are actually eligible. Keep geo filters and schedules accurate so your fair‑split logic has real choices.

Configure caps and overflow routing in CallFlow

Step‑by‑step setup

1. Create or assign numbers

   • Provision US toll‑free or local numbers from your prepaid wallet and assign them to a campaign.
   • Optional: Add an entry IVR for basic menuing or qualification before routing.

2. Add buyers and create targets

   • For each buyer/location/team, add a target: phone number, SIP endpoint, or browser agent.
   • Name targets clearly (Buyer‑A Phoenix Sales, Buyer‑B 24/7 Overflow) to simplify analytics.

3. Set eligibility windows and filters

   • Configure per‑target schedules/time‑of‑day windows to match open hours.
   • Add geographic/caller‑state routing rules so only eligible targets ring for a given caller.

4. Set daily and concurrent caps per target

   • Daily cap: Start with a conservative number aligned to budget and recent performance.
   • Concurrent cap: Match active seats for that time window; adjust by daypart if needed with separate targets.

5. Configure routing order

   • Use priority to attempt your best‑performing buyer(s) first.
   • Among peers, choose weighted or round‑robin to distribute fairly.
   • Avoid broad simultaneous ring unless justified by value and concurrency headroom.

6. Define overflow on cap reached

   • Alternate buyers: Add secondary/tertiary targets to preserve monetization when a cap or concurrency limit is hit.
   • Queue with hold music: If no buyers are available, park the caller briefly. Time‑box the queue so it doesn’t mask chronic under‑capacity.
   • Voicemail: Final fallback when nothing else is eligible (after‑hours, no seats, or all caps maxed).

7. Quality controls and safeguards

   • Enable call recording and use live call monitoring for QA and fraud checks.
   • Turn on duplicate‑caller rules to avoid wasting caps on repeat callers inside your cooling window.
   • Use per‑number spam protections and rate limits if you expect sudden bursts.

8. Verify and report

   • Use real‑time call logs to confirm when caps trip and which overflow path handled the call.
   • Schedule email reports for daily summaries by campaign, buyer, and target.

Test before you go live

• Dry‑run cap events: Temporarily lower a test target’s daily and concurrent caps to 1, place controlled test calls, and verify:
  • First call completes to the primary target.
  • Second call while the first is active overflows per your concurrency logic.
  • After the daily cap is reached, subsequent calls skip that target entirely.
• Check eligibility guards: Flip time windows and state filters to ensure the router respects them before/after caps.
• Validate recordings, monitoring visibility, and that reports reflect cap events and overflow paths accurately.

Overflow options compared

Choose the right overflow for each campaign

Use a layered approach so you don’t lose monetizable calls when caps or capacity limits kick in.

Overflow option	What it does	Best for	Risks/tradeoffs	Notes
Alternate buyers/targets	Routes to other eligible buyers when the primary is capped or busy	Maintaining monetization and continuity	Lower quality or payout with lower‑tier buyers; must manage fairness	Order with priority, then weight or round‑robin
Queue with hold music	Parks callers until a target frees up	Short spikes, lunch rushes, brief understaffed periods	Queue abandonment if wait is long; hides chronic under‑capacity	Time‑box the queue; then fail over
Voicemail	Captures a message when no live capacity exists	After‑hours, specialty teams, very short windows	Conversion typically drops vs. live answer	Use clear prompts; route messages to the right team quickly
IVR branch	Reroutes callers to a self‑selection path (e.g., sales vs. service)	Segmentation to hit different targets/caps	Adds friction if menus are long	Keep menus short; combine with buyer‑specific targets

Typical sequence:

1. Try remaining eligible buyers/targets first (respecting caps).
2. If none free, place the caller in a queue for a short, defined period.
3. If still no capacity, send to voicemail.

Monitor, tune, and troubleshoot

Metrics to watch

• Cap‑hit rate per target: How often daily caps are reached, and at what time of day. Early cap‑hits suggest under‑budgeting or too‑tight eligibility.
• Concurrency utilization: Peak and average simultaneous calls per target. Sustained 100% indicates you need more seats, higher concurrency, or more overflow.
• Answer rate: If answer rates drop as concurrency nears max, your real‑world capacity is lower than you planned.
• Queue wait times and abandonment: Use the queue only as a pressure valve. Rising wait times mean expand eligible targets or lift concurrency.
• Percent overflow to voicemail: Keep this low during business hours. If it rises, revisit schedules, add alternates, or extend queue time slightly.
• Per‑state/time window fill: Confirm that each geo/daypart has sufficient eligible capacity and that volume isn’t bottlenecked by narrow filters.

Use real‑time call logs and analytics in CallFlow to see these patterns. For a deeper framework on capacity planning, also see Concurrent call capacity and how to use insights in Call analytics.

Common pitfalls

• Buyers “capped but still ringing”: Check that you applied the cap to the correct target object, not a duplicate; verify time zones and schedules; ensure you don’t have a second target for the same buyer still eligible.
• Queues backing up: Raise concurrency slightly during the affected daypart, add alternate buyers to the overflow pool, or widen geo/time eligibility.
• Overuse of simultaneous ring: It alerts many targets at once; reserve it for VIP paths and prefer priority + weighted splits otherwise. Concurrency caps still apply only to active calls.
• Skewed distribution with round‑robin: If some targets are frequently ineligible (due to schedules or geo), the remaining ones absorb more calls. Adjust weights or add peers with matching eligibility.
• Duplicate callers burning caps: Tighten duplicate‑caller rules for your cooling window so repeat attempts don’t retrigger delivery.
• Sudden traffic spikes from ads: Rate‑limit the entry numbers to smooth the surge before routing—this is distinct from per‑target caps and prevents front‑end overload.

A weekly tuning loop

• Review cap‑hit timelines per target. If caps hit early, either raise daily caps, widen eligibility, or rebalance weights toward underutilized buyers.
• Inspect concurrency patterns. Lift concurrency by one slot where answer rates stay healthy at peak; otherwise, add alternates instead of raising concurrency.
• Expand buyer windows during predictable peaks (e.g., open weekend coverage or early evenings).
• Add or reorder overflow targets. Promote consistently responsive alternates above sluggish ones.

Practical next steps

• Map every buyer/location to a clear target with its own daily and concurrent caps.
• Define overflow in this order: remaining eligible buyers → brief queue → voicemail.
• Set up duplicate‑caller rules, recording, and monitoring for quality control.
• Run controlled tests until you can predict exactly where each call goes as caps and concurrency change.
• If you’re ready to implement this in production, create your account here or contact us for help designing the routing.