Our Claims Are Denied CO-22 Until Patients Update Their COB, How Do We Get Them Released?
The claim is clean. The coding is right, the visit happened, the note is complete.
How to Get COB-Blocked Claims Released Without Chasing Every Patient by Hand
The goal is simple: no CO-22 hides in general AR, every blocked patient hears exactly what the payer needs, and the held claims release the day COB clears. Here is what does that, move by move.
1. Tag Every CO-22 as a COB-Blocked Account, Not a Denial
The first mistake is treating a CO-22 like any other denial and dropping it back into the general work queue, where it disappears among coding rejections and eligibility errors. It is a different animal: nothing on the claim is wrong, and reworking the claim does nothing, because the block sits on the patient's coordination-of-benefits record at the plan. Create a distinct COB-blocked category the moment a CO-22 posts, tied to the patient, so every future claim for that member routes there too. You cannot chase a problem you cannot see as its own category, and CO-22s scattered through general AR are invisible.
2. Confirm Who the Payer Thinks Is Primary Before You Call the Patient
s own logic: Before any patient outreach, verify the coverage on file against the payer's eligibility record: is there a second plan the patient never mentioned, an employer group plan that pays before Medicare, a spouse's policy, a lapsed plan still listed as active. If the sequence is wrong on your claim, you fix it and resubmit, no patient call needed. If the payer simply needs the member to verify, now you know exactly what to tell them.
3. Reach the Patient With a Script That Names the Exact Payer Task
Patients ignore payer COB letters because the letters are vague and read like junk mail. A generic please update your information gets nothing. What works is a specific, plain-language outreach: your visit will not be paid until you call your insurance at the number on your card and tell them you have only one plan, or confirm which plan is primary; here is what they will ask; it takes five minutes. Deliver it by the channel the patient actually answers, phone, portal message, text, and log the contact so the account is not called blind three more times. The clearer and more specific the ask, the faster the member acts.
4. Escalate the Silent Accounts Before the Filing Window Closes
Some patients will not respond no matter how clearly you ask, and a COB-blocked claim still has a timely-filing clock running on it. The accounts that go quiet need an escalation path, not another identical voicemail: a second scripted attempt, a documented outreach trail, and a decision point before the filing deadline about billing the patient, contacting the plan on the member's behalf where allowed, or writing off with the paper trail to prove you tried. Tracking every COB-blocked account against its filing window is what keeps a stalled claim from turning into a silent write-off nobody chose.
5. Hand COB Denial Resolution to a Dedicated Team
Practices that stop losing revenue to stale-COB freezes do it by handing the whole workflow to a dedicated team: remote specialists who tag the CO-22s, verify the sequence, run the patient outreach, and work the escalation before the window closes, live in 1 to 2 weeks. The billers go back to posting and appeals that actually need judgment, a trained backup covers every gap, and the COB-blocked queue stops being the category nobody owns. Below is what it sounds like when nobody owns it yet, in providers' own words.
Key Pain Points and Discussions by Providers
representative composite examples based on common workflow discussions
“A CO-22 is not really a denial, it is the payer telling me to go herd a patient who has no idea their claim is frozen. The plan sent them a letter they threw away, and now every visit for that patient sits until they make a five-minute phone call they do not know they need to make.” composite example: billing lead, independent practice
“The worst part is it is not one claim. Once the COB flag is on that patient, everything freezes. I found one account with months of visits pended, and not a single one was wrong. They were all waiting on the same questionnaire the patient never filled out.” composite example: practice administrator, multi-provider group
“We were reworking CO-22s like coding denials, resubmitting the same clean claim over and over, and of course it bounced every time. Nothing was wrong with the claim. The block was on the patient's record at the plan and no amount of resubmitting was going to move it.” composite example: revenue cycle lead, group practice
“Nobody was tracking COB-blocked accounts as a thing. They just sat in general AR looking like ordinary open claims, so we did not know how much money was actually stuck behind patients who never answered their insurance.” composite example: office manager, physical therapy clinic
“I have started calling the patient with a script that tells them exactly what to say to their insurance, because please update your COB means nothing to them. When I tell them to call and say I only have one plan, it takes five minutes, they actually do it and the claims release.” composite example: billing specialist, independent practice
Our Answer
Here is what we actually do. A dedicated remote specialist catches every CO-22 the moment it posts and tags the account as COB-blocked so it stops hiding in general AR, then verifies the coverage sequence against the payer's eligibility record before anyone calls the patient. If the sequencing is wrong on the claim, they fix and resubmit with no patient contact needed. If the plan just needs the member to verify, they reach the patient with a specific, plain-language script that names the exact task the insurer will ask for, and log the contact so the account is never called blind. The silent accounts get a documented escalation path before the filing window closes, and the held visits resubmit the day COB clears. Our teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, working inside your practice management and clearinghouse systems, with approved AI tools assisting with first-pass and a human verifying every submission. This is our revenue cycle management support paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the claim is clean, why does it keep denying? Because CO-22 is not a judgment about your claim; it is a hold the payer places when it believes another plan may pay first and the patient has not confirmed otherwise. The standard remittance meaning of the code is that the service may be covered by another payer per coordination of benefits, so until the member settles the sequence with the plan, the payer will not adjudicate. The block lives on the patient's coordination-of-benefits record, which is why resubmitting the same clean claim changes nothing and the freeze spreads to every claim for that member.
The volume is the second half of the problem. Coordination-of-benefits denials are one of the most common front-end denial categories in a practice, and industry denials research from groups like MGMA and HFMA consistently ranks eligibility and COB issues among the top reasons claims do not pay on first submission. When a CO-22 drops into a general work queue, it does not get a patient-outreach workflow; it competes with coding rejections and gets reworked as if the claim were the problem. That is the exact gap a dedicated denial management workflow is built to close, because a COB block needs a phone call to the patient, not another resubmission.
And the cost is quiet, which is what makes it dangerous. A CO-22 is not a hard denial you can appeal; it is a frozen claim with a timely-filing clock still running. AAPC and MGMA billing guidance is clear that secondary and COB-affected claims carry filing windows that keep counting while the account waits, so a claim that could have paid in full quietly ages past its deadline and becomes a write-off nobody decided to make. The revenue is real, the work to release it is small, and the loss happens only because no one owned the outreach in time.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Resubmitted the CO-22 claim as-is | Bounced again every time, because nothing on the claim was wrong and the block sat on the patient's COB record at the plan | Whoever was working the general denial queue |
| Let the payer's letter to the patient do the work | Patient never read it or filed it as junk mail, and every claim for them kept freezing | The payer, and then nobody |
| Left CO-22s in general AR with everything else | They looked like ordinary open claims, aged quietly, and some passed timely filing before anyone noticed | No one, they were invisible |
| Gave COB resolution to a dedicated remote specialist | Every CO-22 tagged, sequence verified, patient reached with an exact script, held claims released before the window closed | Someone whose whole job it is |
The Solution
So what does "someone whose whole job it is" look like on a CO-22? The specialist starts where the practice usually cannot: catching the denial the moment it posts and pulling that account out of general AR into a COB-blocked category tied to the patient, so every held visit for that member is visible in one place. Then they verify the coverage sequence against the payer's eligibility record before any patient call. If your claim had the plans in the wrong order, they correct it and resubmit, no patient outreach needed, and that is exactly the kind of clean release dedicated revenue cycle management support is built to catch before it ever becomes a phone chase.
When the plan genuinely needs the member to act, the specialist takes the vague payer letter off the table. They reach the patient by the channel that patient actually answers and deliver a specific, plain-language script: call your insurer, tell them you have one plan or confirm which one is primary, here is what they will ask, it takes five minutes. Every contact is logged, so the account is never called blind, and the silent ones get a documented escalation before the filing deadline instead of drifting into a write-off. s own model:
Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow flags the CO-22, tags the account, and drafts the outreach; a person confirms the coverage sequence, owns the patient conversation, and decides the escalation. Every security control that protects the patient and coverage data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving coverage and member data through a denial workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team clear your COB blocks better than your own staff? Because reading remits, verifying coverage sequence, and running patient outreach is their entire day, not the thing they squeeze between posting batches. The people working your CO-22s include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US revenue cycle and coordination-of-benefits workflows. They know what a CO-22 actually means, how to check whether the sequence is wrong on the claim or on the member's record, and how to script a patient call that gets the member to pick up the phone and finish the payer's questionnaire.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI-assisted plus human-verified workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs. Trained backup coverage is included in the managed-service model.
And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Stop Losing Revenue to Frozen COB Claims?
Comparing the best RCM and denial-management outsourcing companies? See how a dedicated remote team compares, then browse every pain point we solve.
How We Build a More Durable Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented COB-resolution workflow: how a CO-22 gets tagged and pulled into its own category, how the coverage sequence gets verified before any patient call, the exact outreach script per situation, and the escalation path with a decision point before the filing deadline, all written down and worked the same way every time. Before we take a single denial for a new practice, we chart your CO-22 volume by payer and how long these accounts currently sit, so we can see where the money is actually freezing, and we build the workflow against that, not a generic template.
From there the workflow becomes a living playbook rather than tribal knowledge in one biller's head. It records which payers trigger COB holds most, the plain-language script that actually gets members to call their insurer, how to log outreach so no account is called blind, and when to escalate a silent account before its window closes. It is written down, kept current as payer rules shift, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a frozen claim never waits for one person to come back.
That is the difference between reworking this month's CO-22s and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A biller leaving used to mean the COB-blocked queue fell apart and clean claims started aging out again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a stale-COB flag stops being the thing that quietly costs you paid claims.
The Whole Thing in Four Sentences
Claims keep denying CO-22 because the payer has flagged the patient's coordination of benefits as unverified, and every claim for that member freezes until they complete the plan's questionnaire, not because anything on your claim is wrong. Resubmitting the clean claim, waiting on the payer's letter to the patient, or leaving CO-22s in general AR all fail the same way. The fix is to tag every CO-22 as a COB-blocked account, verify the coverage sequence before you call, reach the patient with a script that names the exact payer task, and escalate the silent accounts before the filing window closes. An independent multi-provider practice can use this workflow without exposing patient information or naming client organizations.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to release your frozen COB claims? Start with a Two-Week Free Trial: your real CO-22 queue, dedicated specialists tagging the accounts and running the patient outreach, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no security deposits, no long-term contracts. Two-Week Free Trial. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist owning your CO-22 queue and COB patient outreach end to end, single-location independent practice
5+ remote specialists covering COB-blocked accounts across a multi-provider group and several sites
10+ remote specialists, multi-location practice, MSO, or PE-backed platform working coordination-of-benefits denials across many billing entities
45 hours of coverage at one flat weekly rate.
For a simple annual comparison, 40 hrs x 52 weeks = 2,080 hours. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour.
Release Your COB-Blocked Claims This Month
You have seen the whole method. The trial lets you test it on your own CO-22 queue, with a tracker your team can watch every day.
Start My Two-Week Free TrialWant Us to Stop Losing Revenue to Frozen COB Claims?
Tell us your situation and we will map your CO-22 volume and the outreach workflow behind it. A team member will follow up with next steps.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- CMS Medicare Claims Processing Manual, Coordination of Benefits. Official guidance on coordination-of-benefits processing and how claims are held when another payer may be primary. cms.gov