Why Was the Crown Denied for Frequency Limitations and How Do We Check Before Treatment?

How to Check Frequency Limits Before You Prep a Crown

The goal is simple: know the replacement interval and the last placement date before you prep, so a frequency cap becomes a priced conversation instead of a surprise bill. Here is what does that, move by move.

1. Pull Frequency and History Limits Before You Plan the Case

A standard benefit check tells you crowns are covered. It does not tell you when this plan will pay for the next one on this tooth. CO-119 lives in that gap. Before you treatment plan any prosthetic, pull the frequency and history limits from the payer portal or a benefits call: what is the crown replacement interval, when will the plan pay again, and are there history limits on related procedures. The coverage line is not the answer; the replacement interval and the last paid date are. Reading them before the prep is what turns a post-remit surprise into an up-front conversation.

2. Record Prior Placement Dates in the Chart

The frequency clock runs from the last time the plan paid for a crown on that tooth, so you need the prior placement date to know where you stand. Record it in the chart as part of treatment planning, and reconcile it against the plan's interval. If the last crown was placed six years ago and the plan's interval is eight, you know before you prep that this case is going to hit the cap. A placement date captured in the chart is what lets your front desk price the case correctly instead of discovering the interval on the remit.

3. Present a Signed Estimate When the Interval Has Not Elapsed

When the frequency check shows the interval has not passed, the crown may still be clinically right, but the plan will not fund it yet. That is not a denial to fight; it is a fee to disclose. Present the patient a signed estimate for the case before you prep, so they make an informed choice about a crown their plan will not pay for right now. A patient who signed knowing the plan would not cover the replacement is a very different conversation than a patient who gets that bill after the prep. The disclosure is what keeps the case from becoming a write-off or a dispute.

4. Read Every CO-119 to Its Remark Code Before You Act

CO-119 usually rides with a remark code, often M38 for a reached benefit maximum or M80 for a service frequency limit, that tells you exactly which cap was hit. Read the remit to that code before you bill the patient or write it off. A true frequency cap on a disclosed case is a clean patient balance; a wrong date on file or a coding mismatch is something you correct and resubmit. Reading it to the code keeps you from billing a patient for a frequency limit that was actually your own data error, and from writing off a balance the patient legitimately owes.

5. Hand Frequency Verification to a Dedicated Team

Practices that stop losing crown cases to frequency limits do it by handing frequency and history verification to a dedicated team: remote specialists who pull the intervals, reconcile the placement dates, and prep the estimate before the prep, live in 1 to 2 weeks. The office stops discovering the interval on the remit, a trained backup covers every gap, and the surprise-balance queue stops being the thing nobody owns. Below is what it sounds like when nobody owns it yet, in practice teams' own words.

Why This Keeps Happening

If crowns are covered, why does the plan deny CO-119? Because CO-119 is a financial limit, not a clinical one. Dental billing guidance is consistent that the code means the maximum benefit for the time period or occurrence has been reached, and the service may have been entirely necessary while the coverage for it simply ran out. Dental plans cap how often they pay for prosthetics, so a crown covered in general and this specific replacement falling inside the interval are two different facts, and a standard benefit check only reads the first.

The reason it surfaces after treatment is that nothing in a routine verification pulls the frequency history for the specific tooth: the replacement interval and the date the plan last paid for a crown there. Treatment planning confirms crowns are payable, plans the case, and preps it, and the interval only appears when the claim adjudicates and comes back with a frequency remark code like M38 or M80. This is exactly the gap a dental benefit verification workflow that pulls frequency and history limits is built to close before the tooth is ever prepped.

And the cost is a surprise balance on a case that is already done. A crown denied for frequency is the full fee landing on a patient who was told nothing about an interval, and practice-management sources that track patient collections find that balances the patient did not expect are collected at a small fraction of the rate of balances disclosed up front. So the frequency cap you did not check for is both a soured patient and money that will age until it is written off, on a crown that was clinically the right call.

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:

The Solution

So what does "someone whose whole job it is" look like on a crown case? The specialist starts before the tooth is prepped: they pull the frequency and history limits from the payer portal or a benefits call, and reconcile the prior placement date against the plan's replacement interval, so a case inside the interval is caught while there is still a choice to make. Catching the frequency cap before the prep is exactly what dedicated dental benefit verification is built to do, before it ever becomes a denied, seated case.

When the interval has not elapsed, the specialist does not let it become a surprise: they prep the signed patient estimate so the fee is disclosed and consented to before the handpiece touches the tooth. And when a CO-119 lands anyway, they do not reflexively bill the patient: they read the remit to its remark code, often M38 or M80, and separate a true frequency cap from a wrong date on file or a coding mismatch that should be corrected and resubmitted. Your front desk stops billing patients for what were actually data errors, and stops writing off what patients genuinely owe.

Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow pulls the frequency limits, reconciles the placement date, and flags the interval; a person confirms the read is right and owns the patient estimate and the remit routing. Every security control that protects the patient records moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving dental records through a verification workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team catch a frequency interval better than your own front office? Because pulling frequency limits and reconciling placement dates is their entire day, not the thing they squeeze between check-ins. The people working your verifications include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US dental eligibility, benefits, and frequency workflows. They know that crowns carry replacement intervals, how to pull the frequency history for a specific tooth, and how to read a CO-119 remark code to the right next action. That is not a task handed to whoever is free; it is a specialty.

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.

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 verification workflow: frequency and history limits pulled before every prosthetic case, prior placement dates reconciled and recorded in the chart, a patient estimate step when the interval has not elapsed, and a remit-routing rule for CO-119 by remark code, all written down and worked the same way every time. Before we verify a single case for a new practice, we chart your top frequency-limitation denials by procedure and plan so we can see where prosthetic cases are actually being lost, and we build the workflow against that, not against a generic checklist.

From there the workflow becomes a living playbook rather than knowledge in one coordinator's head. It records which plans use which replacement intervals, how to pull the frequency history for a tooth, how the patient estimate should read when the interval has not passed, and the exact routing for a CO-119 by remark code. It is written down, kept current as plans change their limits, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a crown case does not have to get prepped blind because one person was away.

That is the difference between eating this month's frequency denials and fixing the process for good, and it is what a dedicated eligibility verification partner actually buys you. A coordinator leaving used to mean frequency checks got skipped and the intervals started catching cases again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and CO-119 stops being the denial that quietly costs you crown cases.

The Whole Thing in Four Sentences

A crown gets denied CO-119 because the plan caps how often it pays for a prosthetic and the last crown falls inside the replacement interval, so the benefit maximum for the time period has been reached; it is a financial limit, not a clinical one. Verifying crowns are covered and prepping, billing the patient after the fact, or guessing at the placement date all fail the same way, because a standard benefit check never pulls the frequency history for the specific tooth. The fix is to pull frequency and history limits before treatment planning, record and reconcile prior placement dates, present a signed estimate when the interval has not elapsed, and read every CO-119 to its remark code. A multi-provider dental group 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 stop losing crowns to frequency limits? Start with a Two-Week Free Trial: your real frequency-limitation denial queue, dedicated specialists pulling intervals and reconciling dates before the prep, 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.