How to dispute a bad call through Ringba exchange

So you bought a batch of Medicare Advantage calls last week, and three of them are dead air. Or maybe you're the publisher on the other end, watching a buyer try to claw back payouts on calls you know were solid. Either way, you're in dispute territory now. And Ringba's dispute workflow isn't something you want to learn on the fly at 4:58pm on a Friday before invoicing closes.

I've sat on both sides of this table. I've filed disputes that got approved in an hour, and I've filed ones that sat ignored for a week because I skipped the one thing that actually matters: citing the timestamp. Ringba doesn't reward general complaints. It rewards specifics. Let's get into how to do this right.

What is a Ringba dispute, exactly?

A Ringba dispute is a formal challenge to a call's billable status, filed inside the platform buyers and publishers use to track, record, and route pay-per-call traffic. It's how a buyer says "this call shouldn't count" and how a publisher defends the call as legitimate.

Ringba launched in 2016. It's since become one of the backbone platforms for pay-per-call marketplaces, especially in insurance verticals like Medicare, U65, and ACA lead gen, where campaign volumes often run into the thousands of calls per week across a single account. If you've bought or sold calls in this space anytime in the last five or six years, there's a decent chance the exchange you used was built on Ringba's infrastructure, or at least integrated with it. The dispute process lives inside that same system, tied to call recordings, disposition tags, and timestamps that either back up your claim or sink it.

Quick takeaway: a dispute isn't a complaint email. It's a data-backed claim filed inside the same platform that recorded the call.

Step 1: know your window, and I mean exactly

Most Ringba-based exchanges give you 24 to 72 hours from the call timestamp to file a dispute. That's it. Some buyers negotiate longer windows, up to 7 days, but that has to be spelled out in the insertion order (IO) before the campaign even starts. If your IO stays silent on dispute windows, assume the shortest one your exchange defaults to. Because that's what you'll get held to.

I made this mistake early on. I assumed a 5-day grace period because that's what a previous partner used. Different buyer, different IO, 48-hour window. I lost four disputes worth about $340 combined because I filed on day 3. Lesson learned the expensive way.

Pull up your IO before you file anything. Check the specific dispute window listed, whether that's 24, 48, 72 hours, or something custom, and note whether the clock starts at call time or at the end of the billing day. If nothing's specified, email your buyer contact and get it in writing before you need it.

Takeaway: your dispute window is contractual, not conventional. Read the IO. Don't assume.

Common reasons calls get disputed in Medicare and ACA campaigns

If you've worked in this vertical for more than a month, you already know most disputes fall into a handful of buckets.

Short duration calls are the big one, typically anything under 60 to 90 seconds, where the buyer argues there wasn't enough talk time to actually qualify or enroll someone. Then there's dead air or disconnected calls, where the line connected but no real conversation happened. Wrong number or demographic mismatch comes up constantly too, like a caller who isn't actually Medicare-eligible (say, someone who mentions being on Medicaid instead), or someone outside ACA subsidy income thresholds, which for a single applicant in 2024 generally meant above roughly $58,000 a year. Calls placed outside licensed states cause plenty of headaches, since state licensing matters a lot in Medicare Advantage; a call from a Texas resident routed to an agent only licensed in Florida is an automatic problem. And there are calls outside TCPA-compliant hours, 8am to 9pm local time for the recipient, which creates both a compliance and a billing issue.

Each of these has a different evidentiary bar. Duration disputes are usually cut and dry, you just pull the call log. Demographic mismatch disputes are messier because they often need cross-referencing enrollment data, not just the recording itself.

Step 2: gather your evidence before you file

This is where most disputes live or die. Ringba lets buyers tag calls with disposition codes (like "qualified," "not interested," "wrong number," "duplicate") and every call gets a recording attached. That recording is the primary evidence anyone reviewing your dispute will actually look at.

Here's the thing nobody tells new buyers and publishers: a generic dispute like "this call was bad" gets auto-rejected more often than not. Ringba's workflow rules, and the QA teams reviewing disputes, want a specific timestamp. Something like "at 1:42 into the call, the line goes dead" or "at 0:38, caller states they're on Medicaid, not Medicare eligible." That level of detail is the difference between a dispute approved in a day and one that sits in limbo for two weeks before getting denied on a technicality.

Listen to the full recording, not just the first 30 seconds. Note the exact timestamp where the problem occurs, and screenshot or export the disposition code Ringba assigned. If you're disputing a demographic mismatch, pull whatever CRM or enrollment record backs up your claim. Then write your dispute reason in one or two sentences, timestamp included. No fluff.

Takeaway: cite the second, not just the sentiment, or expect an auto-rejection.

Step 3: file it inside the exchange, not by email

I get why people want to just email their buyer or publisher contact directly. It feels faster. But most serious exchanges want disputes filed inside the platform itself, because that creates a record tied to the call ID and triggers the buyer's internal QA review automatically. Buyers often cross-reference Ringba data against their own CRM or sales records before making a final call, and that moves faster when everything's centralized in the system both sides already use.

If you're running campaigns at scale, and buying or selling calls through a platform like Ringba X, the dispute tools are already built into your dashboard. Use them. Don't build a parallel paper trail over email that nobody on the QA side is actually checking against the recording.

Timing matters more than people think

Medicare and ACA campaigns typically bill weekly or biweekly. That cadence matters a lot for disputes, since industry practice generally favors resolving them before the invoicing period closes. Once an invoice is cut and paid, getting a credit or adjustment becomes a much harder conversation, sometimes impossible depending on your contract terms. If you're sitting on a handful of questionable calls, don't wait until month's end to bundle them into one big dispute. File as you go.

I run a simple rule on my own campaigns. If something looks off in the recording, I flag and file within 24 hours, regardless of the official window. Waiting almost never helps your case. It just shrinks your position at the table.

FAQ

How much revenue is actually at stake in a single disputed call? Payouts in Medicare Advantage and ACA verticals commonly run $15 to $150 or more per qualified call, depending on exclusivity and lead quality. A handful of disputed calls in a week can swing a few hundred dollars either direction, and at higher volumes, say 500 calls a week, even a 5% dispute rate adds up fast.

Can a publisher dispute a buyer's rejection? Yes. Most exchanges allow counter-disputes if a publisher believes a buyer wrongly rejected a valid call. You'll need the same level of evidence, specific timestamps and disposition data, to push back successfully.

What happens if I miss the dispute window? Generally the call stands as billed or unbilled, whatever status it already had. Late disputes rarely get honored once an invoicing period closes, so don't count on flexibility here.

Do TCPA calling hour violations always get disputed successfully? Not automatically. You still need to show the call timestamp falls outside the 8am to 9pm local window for the recipient's time zone, not the caller's. Time zone mismatches trip people up constantly, especially with calls crossing from Eastern into Central or Mountain time.

Is there a way to reduce disputes before they happen? Tightening your targeting and QA on the front end helps a lot. If you're looking to buy calls or specifically buy health insurance calls from vetted sources, working with an exchange that already enforces disposition tagging and recording standards cuts down on the back-and-forth quite a bit.