Telehealth billing has a funny way of looking simple right up until the first round of EOBs lands in employees’ inboxes. That’s when the “$0 virtual care” promise collides with deductible applications, out-of-network surprises, and support tickets that end up on HR’s desk.
Most write-ups about telehealth billing zoom in on CPT codes and modifiers. Those details matter, but they’re rarely the real reason telehealth gets expensive or messy. The problem I see most often is more structural: the claim goes down the wrong pipe. When the routing is wrong, everything downstream-member experience, plan spend, and compliance-gets harder than it needs to be.
If you want telehealth to be a true “used-first” front door to care (and not just another vendor), you have to design billing like a benefits system, not a coding exercise.
The question nobody asks early enough: who is supposed to pay?
Before you worry about POS 02 versus POS 10, start with a basic operational decision: where should this telehealth encounter be paid from? In employer-sponsored benefits, there are a few common payment paths, and each one behaves differently.
1) Major medical (carrier/TPA) claims
In this model, telehealth is billed like a standard professional claim and adjudicates through the medical plan.
- Why employers choose it: it fits existing workflows, plays nicely with standard claim operations, and is easy to report on.
- Where it breaks: the visit may hit the deductible, price higher than expected (especially under parity rules), or inflate claim volume in ways that matter at renewal (for fully insured plans).
2) Vendor-paid telehealth (PEPM + “$0 visit”)
Here, the employer pays a per-employee-per-month fee and the vendor is intended to deliver low-friction access with little to no member cost-share.
- Why employers choose it: predictable cost and a better “just use it” employee experience.
- Where it breaks: visits accidentally route to major medical anyway, providers may not align with the plan’s network rules, and employees end up confused when “free” in the app doesn’t look free on the EOB.
3) Direct-pay or alternative pricing approaches
Some telehealth strategies avoid traditional claim adjudication altogether. This can work well, but it demands more operational discipline to avoid member disruption.
- Why employers choose it: it can be efficient and reduce claims friction.
- Where it breaks: if member protections aren’t engineered, you risk surprise billing scenarios and a heavier administrative load.
“$0 telehealth” isn’t a slogan-it’s plan design
Employers often market $0 telehealth, but then leave the underlying plan mechanics unchanged. The result is predictable: the plan adjudicates the visit like any other office visit, and employees feel misled.
To make $0 telehealth real, you need explicit decisions (and consistent configuration) around the levers that actually drive what members pay.
- Deductible: is telehealth first-dollar, or does it apply to the deductible?
- Out-of-pocket maximum: do telehealth amounts accumulate toward the OOP max?
- HDHP/HSA considerations: if you sponsor HDHPs, “free” care can have knock-on effects for HSA eligibility. Treat this as a design decision to validate with your plan advisor and counsel.
- Tele-mental health parity: operational limitations (access, utilization management, reimbursement) can create parity risk if tele-mental health is materially more restrictive than medical/surgical care.
The practical point: your SPD, your TPA configuration, and your vendor contract have to tell the same story. If they don’t, employees will find the mismatch fast-and they’ll believe the paperwork.
Stop treating POS 02 vs POS 10 like trivia
Place-of-service codes and modifiers aren’t just compliance checkboxes. In many payer systems, they influence pricing logic, edits, and review workflows. That means a small change in vendor workflow-like defaulting to POS 10-can shift unit costs without anyone noticing until spend reporting catches up.
If you want predictable telehealth costs, lock down these items operationally:
- Which POS codes are allowed for which telehealth services
- Which modifiers are required (and when)
- Whether telehealth is priced at parity with in-person care or on a defined telehealth schedule
- How exceptions are handled (and who owns the cleanup)
The hidden cost isn’t the visit-it’s what happens after
Telehealth rarely ends with the video call. It often triggers labs, imaging, prescriptions, referrals, and follow-up care. If those downstream steps aren’t aligned, you can “save” on the telehealth visit and still lose the economics through leakage and duplication.
A better way to evaluate telehealth is to treat it like the start of a mini-episode. Measure:
Telehealth visit cost + 30/60/90-day downstream allowed spend
Then make sure your telehealth solution can actually close the loop.
- Closed-loop referrals: referrals that land in-network with minimal friction
- Preferred lab routing: especially important for self-funded plans trying to control unit cost
- Pharmacy alignment: eRx routing that supports your pharmacy strategy and improves adherence
- Documentation quality: adequate records for claims integrity, audits, and appeals
Compliance: telehealth billing touches more than people think
Telehealth sits at the intersection of operations and regulation. When something goes wrong, it’s rarely “just a vendor issue,” because the employer is still responsible for the plan’s administration and communications.
- ERISA: if employees are told telehealth is $0 and it frequently adjudicates otherwise, you can end up with a pattern of complaints and appeals that signals weak plan administration.
- HIPAA: telehealth multiplies data-sharing touchpoints across vendors (TPA, PBM, navigation, eligibility, care management). You want a clear data flow map, BAAs where needed, and minimum-necessary access built into operations.
- ACA preventive services: not every telehealth encounter is preventive. Misclassification drives cost-share errors and avoidable member friction.
- MHPAEA: parity risk often shows up in real-world access and management practices, not just in formal written policy.
A practical blueprint for telehealth billing that actually works
If you want telehealth to function as “used-first” care-simple for employees and financially rational for the plan-treat billing as a systems design project. Here’s a sequence that works in the real world.
- Choose your routing architecture. Decide whether telehealth is claim-based through the TPA/carrier, vendor-paid outside claims, or a hybrid.
- Write down the plan intent in plain English. Define what “$0 telehealth” means: deductible waived or not, what services are included, and how accumulators behave.
- Configure adjudication to match intent. Align POS/modifier rules, network status, fee schedules, edits, and exception handling.
- Engineer downstream closure. Build in-network referral workflows, preferred lab pathways, and pharmacy alignment so telehealth doesn’t create avoidable leakage.
- Make employee communications match EOB reality. Don’t market what adjudication can’t deliver. Confusion is the fastest way to kill adoption.
- Measure the right outcomes. Track episode-level cost impact and member friction (tickets, appeals), not just telehealth utilization.
The takeaway
Telehealth billing isn’t primarily a coding problem anymore. It’s a benefit design and claims orchestration problem. When you route encounters intentionally, align plan documents with adjudication, and close the downstream loop, telehealth becomes what employers hoped for in the first place: low-friction care that employees will actually use before small issues turn into expensive claims.
If you’re building toward a “used-first” model, the cleanest next step is to document your telehealth payment policy (one page is enough), then validate that your plan documents, TPA settings, and vendor workflows all match it. That single exercise usually uncovers 80% of the issues before employees ever see them.