Why Does an Eligible Patient Still Get Telehealth Claims Denied for Place of Service?
You checked eligibility. The patient's plan is active, telehealth is a covered benefit, and the plan-level response told you so.
How to Stop Telehealth Denials on Eligible Patients
The goal is a covered telehealth session that bills with the exact setting each payer wants, so an eligible patient never denies on place of service. Here is what does that, move by move.
1. Verify the Benefit by Service Code and Location, Not Just the Plan
A plan-level eligibility check that says telehealth is covered is not enough, because it does not tell you how the setting has to be coded. The first move is to verify the telehealth benefit by the specific service code and the patient's location, at home versus another site, for each payer, before the session bills. That is the difference between knowing a patient is eligible and knowing the claim will actually pay. The setting is where these denials live, so the setting is what you have to confirm.
2. Build a Per-Payer Telehealth Grid
Payers do not agree on the setting rules, so the second move is a grid that captures them per payer: which place-of-service code they want for a home telehealth visit versus another location, which modifier is required, and which provider types are eligible to bill telehealth. When your team can look up a payer and see exactly how that payer wants a home visit coded, the guesswork that produces these denials disappears. The grid turns a moving target into a lookup.
3. Match the Setting on Every Claim to the Grid
With the grid in place, every telehealth claim gets coded to it: the right place-of-service code for where the patient actually was, the modifier that payer requires, and a provider type that payer allows. A patient seen at home is billed the way that specific payer wants a home visit billed, not the way another payer wants it. This is the move that keeps an eligible patient from denying, because the claim now matches the setting rule the payer is actually checking against.
4. Keep the Grid Current and Rework the Denials
Payer setting rules change, so the grid is reviewed quarterly, about an hour of upkeep, and updated the moment a payer shifts its place-of-service requirement. When a denial does land, the session is rebilled with the correct setting rather than written off, and the reason is fed back into the grid so it does not recur. Tracking every setting denial by payer in one place is what turns a recurring rejection into a one-time fix.
5. Hand the Verification and Grid to a Dedicated Team
Practices that stop losing eligible patients to setting denials do it by handing the whole loop to a dedicated team: remote specialists who verify by code and location, own the per-payer grid, code every claim to it, and rework the denials, live in 1 to 2 weeks. The clinicians go back to seeing patients, a trained backup covers every gap, and place of service stops being the thing that quietly denies covered care. 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
“The patient was eligible, telehealth was covered, we confirmed all of it up front, and the claim still bounced on place of service. It was not the benefit, it was the setting code, and eligibility never once told us the payer wanted it coded differently.” composite example: billing lead, behavioral health practice
“We billed every home telehealth visit the same way across every payer, because that is what eligibility seemed to say was fine. Then one payer denied a whole month because they wanted a different place-of-service code for patients seen at home.” composite example: revenue cycle lead, group therapy practice
“The frustrating part is that plan-level eligibility answers a different question than the one that gets you paid. It tells you telehealth is covered. It does not tell you how this specific payer wants the location coded, and that is exactly where the denials come from.” composite example: practice administrator, behavioral health group
“Every payer has its own idea of which setting code and modifier a telehealth visit needs, and none of them are in the eligibility response. We were basically guessing, and one wrong guess denied a run of sessions.” composite example: coder, counseling practice
“Once we built a grid that spelled out, payer by payer, how a home telehealth visit had to be coded, the setting denials dried up. It turned out the coverage was never the issue. The setting rule was, and nobody had it written down.” composite example: office manager, behavioral health practice
Our Answer
Here is what we actually do. A dedicated remote specialist verifies the telehealth benefit by the specific service code and the patient's location for each payer, then codes every claim to a per-payer grid that spells out the place-of-service code, modifier, and eligible provider types that payer requires. When a payer wants a home telehealth visit coded one way and another wants it coded differently, the grid captures both, so an eligible patient bills correctly the first time. When a setting denial does land, they rebill it with the right code and feed the reason back into the grid. Our teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, working inside your EHR and payer portals, with approved AI tools assisting with first-pass verification and a human verifying every setting rule. This is our eligibility and benefits verification paired with an AI-first workflow, aimed at the setting rule eligibility never shows you.
Why This Keeps Happening
If eligibility says telehealth is covered, why does the claim still deny on place of service? Because telehealth coverage is a service-and-setting rule, and the plan-level eligibility response only answers the coverage half. Under the place-of-service framework the Centers for Medicare and Medicaid Services publishes, POS 02 marks telehealth provided somewhere other than the patient's home and POS 10 marks telehealth provided in the patient's home, and payers apply those codes differently by plan and provider type. Eligibility confirms the benefit exists; it does not tell you which of those setting codes a given payer requires for the location the patient was actually in.
The second half is that payers do not agree with each other. One payer wants a home telehealth visit under one place-of-service code, another wants it under a different one, and a third pays only certain provider types for the same service. None of that is carried in the eligibility file, so a practice billing every home visit the same way across every payer is guaranteed to trip at least one payer's setting rule. This is the exact gap a disciplined insurance eligibility verification workflow, done by code and location rather than plan alone, is built to close.
And the cost is not one claim. Because the setting is coded the same way for every visit of a given type, when a payer's rule does not match, it does not deny once, it denies the whole run of sessions billed that way, and telehealth is a high-volume, repeat-visit service. That is covered care, delivered to eligible patients, denied on a coding detail the front end never surfaced. The American Medical Association has long documented how much administrative burden these payer-by-payer coding differences add, and a denial on an eligible patient is that burden landing on care you should have been paid for.
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 |
|---|---|---|
| Trusted the plan-level eligibility response | Eligibility confirmed the benefit but not the setting rule; the claim denied on place of service anyway | The eligibility check, answering the wrong question |
| Billed every home telehealth visit the same way | Worked for some payers and denied a whole run for the one that wanted a different setting code | One-size coding across payers that disagree |
| Rebilled the denial without changing the setting | Bounced again on the same place-of-service rule, because nothing about the code changed | Whoever reworked it in a hurry |
| Gave verification and the grid to a dedicated remote specialist | Benefit verified by code and location, per-payer grid built, every claim coded to it, denials reworked and fed back | Someone whose whole job it is |
The Solution
So what does "someone whose whole job it is" look like on a place-of-service denial? The specialist starts where the practice usually cannot: verifying the telehealth benefit by the specific service code and the patient's location for each payer, not just confirming the plan is active. Then they code every claim to a per-payer grid that spells out the place-of-service code, modifier, and eligible provider types that payer wants, so a home visit bills the way that payer requires. Most of these denials are a setting-and-verification problem, and that is precisely what dedicated eligibility and benefits verification is built to solve before it ever becomes a denied run.
When a setting denial does land, the specialist takes the write-off off the table. They rebill the session with the correct place-of-service code for where the patient actually was, and they feed the reason back into the grid so the same payer's rule does not catch the next batch. The care was covered and delivered; the goal is to make it pay against the right setting rather than absorb a denial on an eligible patient because the code did not match. One corrected grid entry protects every future visit billed to that payer.
Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow reads the payer, pulls the setting rule, and drafts the verification; a person confirms the place-of-service code and provider type are right before the claim goes out. Every security control that protects the patient data moving through that verification is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving eligibility and benefit data through a verification workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team clear your setting denials better than your own staff? Because verifying telehealth benefits by code and location and keeping a per-payer grid current is their whole day, not the thing they squeeze between registrations. The people running your verification include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US eligibility, telehealth billing, and place-of-service coding workflows. They know that POS 02 and POS 10 mean different things, how each major payer wants a home visit coded, and how to read a setting rule off a payer policy. That is not a generalist 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.
Ready to Stop Denying Eligible Telehealth Patients?
Evaluating the best insurance eligibility verification services? 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 telehealth verification workflow: how the benefit is verified by code and location, which place-of-service code and modifier each payer wants for a home visit versus another site, which provider types each payer allows, and how a setting denial is reworked and fed back. Before we verify a single telehealth session for a new practice, we chart your setting denials by payer so we can see which payers' rules are actually catching you, and we build the grid against that, not against a generic template.
From there the grid becomes a living playbook rather than tribal knowledge in one coder's head. It records how each payer wants a telehealth setting coded, which modifiers apply, which provider types are eligible, and how the grid gets updated the quarter a payer changes its rule. It is written down, kept current, and owned by the team. When your specialist is out, a trained backup codes to the same grid the same way, so an eligible patient's claim never denies because one person was away.
That is the difference between reworking this month's setting denials and fixing the process for good, and it is what a dedicated eligibility and benefits verification partner actually buys you. A coder leaving used to mean the grid lived nowhere and setting denials started stacking up again. Under this model the verification keeps running, the grid stays, the backup steps in, and place of service stops being the thing that quietly denies your covered patients.
The Whole Thing in Four Sentences
An eligible patient still gets telehealth claims denied for place of service because telehealth coverage is a service-and-setting rule, POS 02 versus 10, provider type, and code category, and the plan-level eligibility response does not carry any of it. Trusting eligibility alone, billing every home visit the same way across payers, or rebilling without changing the setting all fail the same way. The fix is to verify by code and location, build and maintain a per-payer telehealth grid, code every claim to it, and rework the denials back into it. A behavioral health 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 denying eligible telehealth patients? Start with a Two-Week Free Trial: your real telehealth setting denials, a dedicated specialist verifying by code and location and building your per-payer grid, 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 verifying telehealth benefits by service code and patient location and maintaining your per-payer place-of-service grid, single-site behavioral health practice
5+ remote specialists running telehealth benefit verification and grid upkeep across a multi-provider group or several therapy sites
10+ remote specialists, multi-location behavioral health network, MSO, or PE-backed platform verifying telehealth setting rules across many payers and providers
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.
Clear Your Telehealth Setting Denials This Month
You have seen the whole method. The trial lets you test it on your own denial queue, with a per-payer grid your team can look up every day.
Start My Two-Week Free TrialWant Us to Stop Denying Eligible Telehealth Patients?
Tell us your situation and we will map your telehealth setting denials and the per-payer grid behind them. A team member will follow up with next steps.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- Centers for Medicare and Medicaid Services Place of Service Code Set. Federal reference defining POS 02 and POS 10 for telehealth and their application by setting. cms.gov
- American Medical Association Telehealth and Practice Management Resources. Physician-practice guidance on telehealth coding, place-of-service rules, and payer-by-payer administrative burden. ama-assn.org