How call caps work and why your agency needs them

So you've got agents on the phone, publishers sending you traffic, and somewhere in the middle sits a number that decides whether the whole thing runs smooth or falls apart. That's your call cap. Most agencies I've worked with either ignore it until something breaks, or set it once in January and forget about it. Both are mistakes. Here's why.

What is a call cap, exactly?

A call cap limits how many inbound calls a publisher or affiliate can send you within a set window, usually an hour, sometimes a day, sometimes tied to a specific campaign. Caps typically run anywhere from 5 to 500 calls per hour depending on how many licensed agents you've got staffed.

Here's the thing. A call cap isn't just a traffic valve. It's what keeps your agents from drowning and your compliance team from getting a call from CMS. If you're buying calls in the Medicare Advantage or ACA space, your cap setting is basically a real-time bet on how many agents you'll have available in the next 60 minutes. Get it wrong either direction and you lose money. Get it wrong during AEP and you might lose a lot more than that.

I've seen agencies treat caps like a set-it-and-forget-it dial. Fine in July. Doesn't work in November.

How the mechanics actually play out

Platforms like Ringba, Invoca, and Retreaver handle most of the heavy lifting. If you're running calls through something like Ringba X, you can set dynamic caps that adjust in real time as volume climbs toward capacity, instead of a flat number that either chokes your agents or leaves sellable calls on the table.

Here's roughly how it works. You set a base cap per hour, say 40 calls, based on how many agents are logged in and licensed, and the platform tracks calls against that cap in real time, publisher by publisher or campaign by campaign. As you approach the ceiling, the system throttles new calls, reroutes them, or shuts the spigot until the next window opens, and a buffer period, often 5 to 15 minutes, sits at the reset point so you don't get slammed by three publishers all hitting the cap at once.

That buffer matters more than people think. Without it, you get a pile-up right at :00 when every cap resets simultaneously, and suddenly 20 calls hit in 90 seconds instead of spreading across the hour. I learned this the hard way on a campaign with zero buffer configured. Abandonment spiked every single hour on the hour, like clockwork. Added a 10-minute stagger and it smoothed right out.

Why static caps break during AEP and OEP

During Medicare's Annual Enrollment Period (October 15 to December 7) and the Open Enrollment Period that follows (January 1 to March 31), call volume can spike 3 to 5 times above your normal baseline. A cap that worked fine in September will either choke your best publishers in October or flood your agents in November. There's no in-between. Static numbers just can't keep up with that kind of swing.

This catches agencies off guard every single year. You set caps in September based on August volume, AEP hits, and now you're either turning away hundreds of sellable calls a day, plain lost revenue, or blowing past capacity and racking up hold times that push callers to hang up before an agent picks up.

Both directions cost you. Under-cap thresholds mean paying for traffic you can't use, or worse, telling a publisher to stop sending calls you'd have paid $40 or $60 or $80 for under a pay-per-call deal. Over-cap thresholds mean long holds, higher abandonment, and a Net Promoter Score that tanks right when you need referrals and renewals most.

I get why static caps feel safer. They're predictable. But predictable isn't the same as correct, and during AEP, predictable is exactly what gets you in trouble.

The compliance angle nobody talks about enough

CMS enforces the Medicare Communications and Marketing Guidelines (MCMG), and dropped or abandoned calls that trace back to bad cap management can turn into compliance complaints fast, especially during AEP when regulators are watching closer than any other time of year. A caller dropped after a 12-minute hold doesn't just churn. Sometimes they file a complaint, and now you've got a paper trail that doesn't look good.

Here's what gets missed constantly: your call cap needs to be tied to actual licensed agent availability by state, not just total headcount. If you've got 30 agents logged in but only 6 licensed in Texas, your Texas cap should reflect 6 agents, not 30. A captive agent who isn't licensed in the caller's state legally cannot take that lead, full stop. I've audited call flows where the cap was set off total headcount, and the agency was sending Florida calls into a queue where half the agents on shift couldn't legally touch them. Not a minor inefficiency. That's compliance exposure sitting in your call flow, waiting to become a real problem.

So break it down by state license counts when you set caps, not just bodies in seats. More work upfront. Saves you a much worse conversation later.

Pricing and why caps affect your margin directly

In the U65 and ACA space, pay-per-call arrangements typically price qualified calls between $15 and $100, depending on call duration, exclusivity, and lead type. Medicare Advantage calls generally command more than ACA subsidy-eligible calls, since the downstream commission value runs higher. If you want to see how that pricing shakes out across different call types, buy health insurance calls through a platform that lets you set those caps dynamically instead of guessing.

Every call you turn away because your cap was too conservative is money you paid nothing for but also earned nothing from. Every call that abandons because your cap was too generous is money you might have paid for and definitely didn't convert. Your cap setting is, in a real sense, your margin control. Treat it that way, not like a background setting you configure once and forget.

If you're looking to buy calls for the upcoming AEP or OEP cycle, get your cap strategy sorted before volume hits, not during. Adjusting caps reactively at 4pm on a Tuesday in November is a much worse time than setting dynamic thresholds back in September.

Set your caps by licensed agent capacity per state, not headcount. That's the one-line version. Everything else is refinement.

FAQ

How often should I adjust my call caps during AEP? Check them daily at minimum, hourly if you can manage it. Volume swings enough during AEP that a cap set on Monday can be wrong by Wednesday.

What's a reasonable buffer period between cap resets? Most agencies run somewhere between 5 and 15 minutes. Shorter buffers work fine with steady, low-volume traffic. Longer buffers help when multiple publishers are likely to hit the cap around the same time.

Can I set different caps for different publishers on the same campaign? Yes, and generally you should. Your best-converting publisher deserves a higher cap than one you're still testing.

Do call caps affect my cost per acquisition? Directly. A cap that's too tight turns away calls you'd have paid for and converted, raising your effective CPA on the ones you do take. A cap that's too loose drives abandonment, wasting ad spend on calls nobody answers.

Is a total headcount cap ever acceptable? Only if every agent on staff is licensed in every state you're taking calls from, which is rare. For most agencies, state-by-state licensing should drive the real number.