How to set caps and concurrency rules in Ringba

So you've got Medicare or ACA calls flowing into Ringba, and every buyer on your account is asking the same question: how many can you actually send me? No good answer, and you're stuck. Either you're overselling leads (hello, TCPA complaint) or leaving money on the table because your caps are too conservative. Let's fix that.

I've run health insurance call campaigns through at least three AEP seasons now. The difference between an agency that profits during open enrollment and one that scrambles to fix compliance issues in December usually comes down to how well they set up caps in week one. Not week three. Week one.

Why caps matter more in health insurance than almost any other vertical

Here's the thing. Medicare Annual Enrollment Period runs October 15 through December 7 every year. ACA Open Enrollment typically runs November 1 through January 15 in most states, though a handful stretch it further. That's roughly seven to eight weeks where call volume spikes hard, and buyers like UnitedHealthcare, Humana, and Aetna, or the agencies buying on their behalf, get particular about how many calls they'll take and when.

If your caps aren't dialed in before October 15, you'll find out the hard way. Usually around October 17, when a buyer calls asking why they got 40 duplicate calls on the same consumer.

Setting caps at the right level

Ringba lets you set caps at three levels: campaign, target, and buyer. Each does something different, and mixing them up is probably the single most common mistake I see agencies make.

Campaign caps control total volume for an entire campaign, no matter who's buying. Think of this as your ceiling. Target caps limit how many calls go to a specific destination number or endpoint, so if you've got one buyer running three different intake lines, targets let you split volume between them. Buyer caps sit above targets and control the total across everything that buyer receives from you, even if they've got five different targets set up.

For health insurance specifically, you want all three working together. During AEP, I'll usually set a campaign cap that reflects total lead capacity for the day (say, 500 calls), then buyer caps that reflect each buyer's contracted daily volume, then target caps underneath that split calls across the buyer's regional intake lines if they have them.

Quick takeaway: campaign caps protect your total volume, buyer caps protect the relationship, target caps protect the routing logic.

Concurrency caps: the setting everyone underestimates

Concurrency caps limit how many calls can be live with a single buyer at the same moment. This matters because health insurance buyers, especially ones dealing with Medicare, often require exclusivity to avoid TCPA risk from overlapping calls to the same consumer.

For smaller agencies, concurrency caps typically sit somewhere between 1 and 10 simultaneous calls per buyer. Larger call centers with bigger agent teams might run 20 to 50 or more. Neither number is "right." It depends on how many licensed agents that buyer actually has staffed and ready at that moment, which is honestly information you should just ask for instead of guessing.

Here's a mistake I made early on. I set a concurrency cap of 15 for a mid-size Medicare buyer because that's what a bigger buyer had asked for the month before. Turned out this buyer had six agents on staff. Calls stacked up, hold times blew past two minutes, abandon rates spiked. The buyer wasn't happy, and neither was I once I saw the quality scores. Ask buyers directly how many agents they've got live, then set concurrency at roughly 60-70% of that number so you're not building a queue every time volume spikes.

During TCPA-sensitive windows, especially early AEP when regulators and carriers are watching closely, a lot of buyers will flat out request a concurrency cap of 1. Exclusive, one call at a time, no exceptions. Annoying from a volume standpoint. But it's the safest way to avoid overlapping consumer contact complaints.

Layering global caps with target caps

Ringba's Global Caps feature stacks on top of Target Caps, and this combo is what saves agencies from the "same lead pool, multiple buyers" nightmare.

Say you're running one pool of ACA leads and selling to three different agencies all buying from the same source. Without a global cap layered on top, you can accidentally oversell that lead pool past what your inventory actually supports. Global caps set the ceiling across the whole pool, target caps divide up who gets what share underneath it. If you're managing volume across multiple buyer relationships on a platform like Ringba X, this layering is really the only way to keep the math honest once you've got more than two or three buyers active at once.

The time zone problem nobody talks about

This one's sneaky. I've seen it burn more than one agency. Caps in Ringba reset based on a defined time zone, and by default that's usually your account's default zone. If your buyer contracts specify resets in Eastern Time but your account default is set to Pacific, you've got a three-hour window every single day where you're either overdelivering or underdelivering calls without realizing it.

Over a full AEP window, three hours a day of misaligned caps adds up to real money. Either in overage fees you owe a buyer, or in lost revenue from underdelivering your own contracted volume. Check your account-level time zone setting against every buyer contract before AEP starts. Not during it.

Duplicate check windows and why concurrency alone won't save you

Concurrency caps limit simultaneous calls, but they don't stop the same consumer from calling back an hour later and getting routed to a different buyer. That's what duplicate check windows are for. For Medicare and ACA leads, a 30 to 90 day duplicate check window is common, and pairing that with your concurrency settings is what actually stops a consumer from getting pitched by three competing agents in the same week.

A word on cost

Ringba pricing runs usage-based, typically a few hundred bucks a month in platform fees plus per-minute tracking costs on top. During AEP that per-minute cost adds up fast, so a lot of agencies tighten caps not just for compliance but to control spend during the highest-volume weeks. If you're actively looking to buy calls or expand into buying health insurance calls, factor that per-minute cost into your cap strategy from day one. Not after your first invoice surprises you.

FAQ

Should I set caps differently for Medicare versus ACA campaigns? Yes. Medicare AEP (October 15 to December 7) is shorter and more compliance-sensitive, so tighter concurrency and lower caps make sense. ACA Open Enrollment runs longer, often through January 15, so you can pace caps more evenly.

What concurrency cap should a small agency start with? Start around 2 to 4 per buyer unless they've confirmed a bigger agent team. Adjust after the first week based on hold times and abandon rates.

Do target caps override buyer caps? No. Buyer caps are the ceiling across all targets tied to that buyer. Target caps just divide traffic within that ceiling.

How often should I check my time zone settings? Before every major enrollment period, and any time you onboard a new buyer with a specific contract requirement.