Pain Point, Solved 4.9 ★★★★★ Google Rating

When Does a Telehealth Therapy Claim Need POS 02 Versus POS 10, and Which Payers Still Want Modifier 95?

All Pain Points

Ask AI about this page

A telehealth therapy claim needs POS 10 when the patient is at home and POS 02 when the patient is at another site like a clinic or facility, because those two codes usually pay at different rates, and modifier 95 applies to synchronous audio-video sessions while audio-only sessions need modifier 93 instead. On top of that, Medicare largely keys off the correct place of service while many commercial payers still want modifier 95 appended, so the same session can be coded three different acceptable ways depending on whose card the patient carries. The denials and underpayments are not a coding-skill problem; they are a rules-matrix problem, made worse because POS 02 versus 10 hinges on where the patient sat, a fact intake rarely captures. The fix has four moves: capture the patient’s location at the session so POS is real, maintain the payer-specific telehealth rules so each claim matches the plan, match modifier to modality so audio-only never goes out as audio-video, and scrub every telehealth claim against all three before it submits. We run those moves inside the systems you already use, so the batch stops coming back on Friday. The table of contents maps the whole method; the moves after it are the detail.

How to Stop Telehealth POS and Modifier Denials in a Therapy Group
Key Pain Points and Discussions by Providers
Why This Keeps Happening
The Solution
How We Permanently Fix the Process
The Whole Thing in Four Sentences
Frequently Asked Questions
Where the Claims on This Page Come From

How to Stop Telehealth POS and Modifier Denials in a Therapy Group

The goal is a telehealth claim that matches the payer’s rule and the way the session was actually delivered, the first time, so Friday stops being rework day. Here is what does that, move by move.

1. Capture Where the Patient Actually Sat

The whole POS problem starts at intake. POS 02 versus 10 turns on where the patient was during the session, home or another site, and if intake never records it, the biller is guessing at coding time. The first move is to capture the patient’s location as part of scheduling or the session note, every time, so the place of service on the claim reflects reality instead of a default. You cannot code POS correctly from a field that was never filled in, and a guess is what a payer underpays.

2. Maintain the Payer-Specific Telehealth Rules

There is no single telehealth rule, so pretending there is one is what breaks the batch. Medicare largely keys off the correct place of service, while many commercial payers still want modifier 95 appended, and audio-only rules differ again. Maintaining a live grid of which payer wants which POS, which modifier, and at what rate, kept current as plans change their policies, is what lets each claim match the plan it is going to. When the rule is written down per payer, the claim stops being a guess and starts being a match.

3. Match the Modifier to the Modality, Every Time

Modifier 95 is for synchronous audio-video sessions. An audio-only session needs modifier 93, and sending an audio-only check-in out with 95 is a denial waiting to happen. The move is to tie the modifier to how the session was actually delivered, video or audio-only, so the code on the claim tells the truth about the visit. When modality drives the modifier automatically instead of everything defaulting to 95, the audio-only denials that used to pile up stop arriving.

4. Scrub Every Telehealth Claim Before It Submits

The denials and underpayments happen because the POS, the modifier, and the payer rule are checked after the remit comes back, not before the claim goes out. The move is a scrub that matches place of service, modifier, session modality, and the specific payer’s telehealth policy on every claim before submission. When a claim that does not match the plan’s rule gets caught and corrected up front, the Friday rework batch shrinks to almost nothing, because the errors never became remits in the first place.

5. Hand Telehealth Billing to a Dedicated Team

Groups that stop losing Fridays to telehealth rework do it by handing the rules and the scrubbing to a dedicated team: remote specialists who maintain the payer grid, match POS and modifier to the real session, and scrub every claim before it submits, live in 1 to 2 weeks. The biller goes back to working real exceptions instead of reworking the whole batch, a trained backup covers every gap, and the telehealth denials stop being the thing that eats the end of every week. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We bill every telehealth session POS 02 with modifier 95 because that is what we set up on day one. Then one payer underpays every home visit that should have been POS 10, and I only find out when I reconcile the remits a month later.” – billing lead, teletherapy group practice

“The audio-only check-ins are the ones that keep bouncing. They go out with modifier 95 like everything else, and that payer wants 93 for audio-only, so it denies every time and I rework it after the fact.” – medical biller, behavioral health group

“Intake never records where the patient actually was during the session, so at coding time I am guessing whether it is POS 02 or POS 10. Half my POS denials trace straight back to a field nobody filled in.” – billing manager, group therapy practice

“Every payer wants something slightly different. Medicare cares about the place of service, this commercial plan still wants modifier 95, and I am keeping the whole matrix in my head. Friday is the day I pay for whatever I got wrong.” – revenue cycle coordinator, behavioral health practice

“I spend the end of every week reworking last month’s telehealth batch. It is not one big error, it is a hundred small mismatches between how we coded and what each payer actually wanted, and they only show up on the remit.” – billing specialist, teletherapy practice

Our Answer

Here is what we actually do. A dedicated remote specialist maintains a live grid of each payer’s telehealth rules, which place of service, which modifier, and at what rate, and captures where the patient actually sat so POS 02 versus 10 is real, not a default. They match the modifier to the modality, so audio-only sessions carry modifier 93 and audio-video carry 95 where the payer wants it, and they scrub every telehealth claim against place of service, modifier, modality, and the specific payer’s policy before it submits. The mismatches that used to surface on the remit get caught before the claim goes out. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside your billing and EHR systems, with AI drafting the first-pass scrub and a human verifying every claim. This is our medical billing support paired with an AI-first workflow, in one paragraph.

Why This Keeps Happening

If the coding is not the problem, why do the telehealth claims keep bouncing? Because there is no single telehealth rule to code to. Medicare largely keys off the correct place of service, POS 10 for a patient at home and POS 02 for a patient at another site, and those two codes generally pay at different rates, while many commercial payers still want modifier 95 appended on top of the place of service. The same audio-video therapy session can be coded three defensible ways depending on the payer, so a group that bills every session identically is guaranteed to be wrong for some of them.

The audio-only sessions are a second, separate trap. Modifier 95 describes a synchronous audio-video visit, and an audio-only session needs modifier 93 instead, so a check-in delivered by phone but billed with 95 misrepresents the visit and denies. When a group defaults everything to POS 02 and modifier 95, the home-based sessions get underpaid and the audio-only sessions get denied, and neither error is visible until the remit comes back weeks later. Catching those mismatches before submission is exactly what a payer-specific behavioral health billing workflow is built to do.

And the root of the POS half of it is upstream of billing entirely. POS 02 versus 10 hinges on where the patient sat during the session, and intake rarely records that, so at coding time the biller is guessing from a field nobody filled in. The cost is not one dramatic denial; it is a hundred small mismatches, underpaid home visits and denied audio-only check-ins, that stack up into a Friday spent reworking last month’s batch instead of working new claims. Closing that gap is what an AI medical billing workflow with human oversight is built to do.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the underpayment you never notice. A denial is loud, it bounces and demands rework, so at least you know. A POS 02 session that should have been POS 10 does not deny; it just pays a little less than it should, quietly, on every home-based visit, and it keeps doing that until someone reconciles the remits line by line. Multiply a small underpayment by every telehealth session a busy group runs, month after month, and the money that walks out on the place-of-service default dwarfs the denials you actually rework. Unless someone matches POS to where the patient really sat before the claim goes out, the most expensive telehealth error is the one that never looks like an error at all.

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
Billed every telehealth session POS 02 with modifier 95	Home-based sessions underpaid at the facility rate and audio-only check-ins denied, month after month	One default applied to a matrix of payer rules
Fixed the denials as they came back on the remit	The mismatches were only visible weeks later, so Friday became permanent rework day	The biller, after the fact
Told intake to ask where the patient is, informally	Without it built into scheduling it got skipped, so POS stayed a guess at coding time	Whoever remembered to ask, when they remembered
Gave telehealth billing to a dedicated remote specialist	Payer grid maintained, POS matched to where the patient sat, modifier matched to modality, every claim scrubbed before it went out	Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on a telehealth batch? The specialist maintains a live grid of each payer’s telehealth policy, which place of service, which modifier, at what rate, and captures where the patient actually sat so POS 02 versus 10 reflects reality instead of a default. Every claim gets scrubbed against place of service, modifier, session modality, and the specific payer’s rule before it submits, so the home-based session carries POS 10 and the audio-only check-in carries modifier 93. Most telehealth denials and underpayments are a rules-matching problem, not a coding-skill problem, and that is exactly what dedicated medical billing support is built to solve before the remit ever comes back.

The part in-house billing struggles to hold is the matrix itself. One person keeping every payer’s telehealth rule in their head is how the mismatches happen, so the rules live in a written grid that is kept current as plans change their policies, and the modifier is tied to how the session was actually delivered rather than to habit. The biller stops reworking the whole batch on Friday and starts working only the real exceptions, because the hundred small mismatches never became remits in the first place.

Behind all of it, AI drafts the first-pass scrub and a credentialed human verifies. The workflow flags a claim whose POS, modifier, or modality does not match the payer’s rule; a person confirms the correction before it submits and owns any claim that needs judgment. Every security control that protects the patient and claim data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical and billing data through a claims workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team code your telehealth claims better than your own biller who knows your providers cold? Because maintaining a payer-by-payer telehealth grid and scrubbing every claim against it is their entire day, not the thing they squeeze in before Friday. The people working your claims are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US behavioral health billing and telehealth coding. They know when a payer keys off place of service versus wants modifier 95, when a session needs modifier 93, and how to catch a POS mismatch before it becomes a quiet underpayment. 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+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so the telehealth batch never sits because the one person who knows the payer grid is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; 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.

✓ What stops happening: What stops happening: the Friday spent reworking last month’s telehealth batch. Home-based sessions quietly underpaid at the facility rate because they went out POS 02. Audio-only check-ins denied because they carried modifier 95 instead of 93. The POS guessed at coding time from a field intake never filled in. The hundred small payer mismatches that only showed up weeks later on the remit.

2-Week Free Trial

Ready to Stop Reworking the Telehealth Batch?

Book A Strategy Call Request Information

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented telehealth billing workflow: which payer keys off place of service, which still wants modifier 95, which sessions need modifier 93, how POS 02 versus 10 is decided from where the patient sat, and the scrub that checks all of it before a claim submits, written down and applied the same way every time. Before we take a single claim for a new practice, we chart your telehealth denials and underpayments by payer, POS, and modifier so we can see where the money is actually leaking, and we build the grid against that, not a generic template.

From there the workflow becomes a living playbook rather than a matrix in one biller’s head. It records each payer’s telehealth rule, how modality maps to modifier, how location is captured at intake so POS is real, and the escalation path when a payer changes its policy mid-year. It is written down, kept current, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so the telehealth batch never falls behind because one person is off.

That is the difference between reworking this week’s telehealth denials and fixing the process for good, and it is what a dedicated AI medical billing partner actually buys you. A biller leaving used to mean the payer grid left with them and the mismatches came back. Under this model the workflow keeps running, the grid stays current, the backup steps in, and telehealth POS and modifier denials stop being the thing that eats the end of every week.

The Whole Thing in Four Sentences

A telehealth therapy claim needs POS 10 when the patient is at home and POS 02 when the patient is at another site, and those codes usually pay differently, while modifier 95 is for audio-video sessions and audio-only sessions need modifier 93. Medicare largely keys off place of service while many commercial payers still want modifier 95, so the same session can be coded three acceptable ways depending on the payer. Billing everything POS 02 with modifier 95, fixing denials after the remit, or asking intake informally to note location all fail the same way. The fix is capturing where the patient sat, maintaining the payer-specific rules, matching modifier to modality, and scrubbing every claim before it submits. A multi-provider behavioral health group runs exactly this model with us today, names withheld, no patient data shown.

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 reworking the telehealth batch? Try us risk free: two weeks, your real telehealth claims, dedicated specialists maintaining the payer grid and scrubbing every claim before it submits, 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.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single

$399/ week

One dedicated remote specialist maintaining your telehealth billing rules and scrubbing claims before submission, single-location teletherapy or group practice

Clear Your Telehealth Denials This Month

You have seen the whole method. The pilot proves it on your own telehealth claims, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information or call directly: (800) 489-5877

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

When does a telehealth therapy claim need POS 02 versus POS 10?

POS 10 applies when the patient is at home during the session, and POS 02 applies when the patient is at another site such as a clinic or facility. The two codes generally pay at different rates, with the home-based POS 10 often paying the higher non-facility rate, so getting this right is real money. The catch is that it depends on where the patient actually sat, which intake has to capture, or the place of service on the claim ends up being a guess.

Which payers still want modifier 95 on a telehealth claim?

Many commercial payers still want modifier 95 appended to a synchronous audio-video telehealth session, while Medicare largely keys off the correct place of service instead. Because it varies by payer, the same audio-video session can be billed acceptably in more than one way, which is why maintaining a payer-by-payer grid of who wants which modifier is what keeps each claim matching the plan it goes to.

What modifier does an audio-only therapy session need?

An audio-only session needs modifier 93, not modifier 95. Modifier 95 describes a synchronous audio-video visit, so sending an audio-only check-in out with 95 misrepresents how the session was delivered and gets denied. Tying the modifier to the actual modality, video or audio-only, is what stops the audio-only denials that otherwise pile up.

Why do our telehealth claims underpay even when they do not deny?

Because a place-of-service mismatch usually underpays rather than denies. A home-based session billed POS 02 instead of POS 10 pays a little less at the facility rate, quietly, on every visit, and nothing bounces to tell you. It only surfaces when someone reconciles the remits line by line, which is why the underpayment leak often runs longer and costs more than the denials you actually rework.

How much does outsourced telehealth billing cost?

Staffingly charges a flat weekly rate per dedicated remote specialist, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of your collections. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.

Will AI be coding our telehealth claims?

No. AI drafts the first-pass scrub, flagging a claim whose place of service, modifier, or modality does not match the payer’s rule, and a credentialed human verifies every correction before the claim submits. The coding judgment stays with people. Automation removes the repetitive matching work so the specialist spends their time on the claims that need a person, not on rechecking the whole batch by hand.

Do we have to change our billing software or EHR?

No. Our specialists work inside the billing and EHR systems you already use, so there is no migration and no new platform for your staff to learn. They maintain the payer grid and scrub claims where your billing already happens, which is why a typical practice is live in 1 to 2 weeks rather than months.

How fast will we see fewer telehealth denials?

Usually within the first two weeks. Once a dedicated specialist is maintaining the payer grid, capturing where the patient sat, matching modifier to modality, and scrubbing every claim before it submits, the mismatches that used to surface on the remit start getting caught up front, and the Friday rework batch starts shrinking.

How does one flat weekly rate cover 45 hours every week?

Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

CMS Telehealth Billing and Place of Service Guidance. Federal guidance on telehealth place-of-service codes, modifiers, and coverage policy relevant to behavioral health claims. cms.gov
AMA CPT and Telehealth Coding Resources. Physician-practice guidance on CPT coding, telehealth modifiers, and place-of-service reporting for behavioral health services. ama-assn.org
MGMA Practice Operations and Coding Resources. Benchmarks and guidance on telehealth billing, claim scrubbing, and denial management for medical group and behavioral health practices. mgma.com
HFMA Revenue Cycle and Denials Management Resources. Guidance on claim edits, front-end scrubbing, and the revenue impact of coding and place-of-service mismatches. hfma.org
Physicians Practice Telehealth and Coding Operations. Practice-management guidance on telehealth coding, modifier use, and place-of-service reporting in behavioral health billing. physicianspractice.com