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

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.

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.

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 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 trained human reviewer 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 include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, 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+ 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 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 does not have to fall 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 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 reworking the telehealth batch? Start with a Two-Week Free Trial: 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.