Async vs sync visits: which one your category actually needs
Requiring a video visit where one is not needed is the most expensive avoidable decision in a telehealth funnel. Skipping one where it is required is a compliance failure.
Key takeaways
- Async means a provider reviews a submitted intake and decides without a live encounter. It is the workhorse model of direct-to-consumer telehealth.
- Async removes scheduling, no-shows and provider idle time, which is why it converts far better.
- Several states require a synchronous visit before an initial prescription, and controlled substances commonly require one regardless.
- Testosterone is the clearest example: DEA Schedule III, so a live visit and baseline labs come before the first fill.
- The requirement should be enforced by intake routing on the patient's state, not by staff knowledge.
What each one is
A synchronous visit is a real-time video consultation between patient and clinician. An asynchronous review, sometimes called store-and-forward, is a clinician assessing a structured intake the patient submitted earlier and issuing a decision without the two ever being online together.
Both are legitimate telehealth. They differ in cost to deliver, in conversion, and in where they are legally sufficient.
Why async converts so much better
Every synchronous requirement inserts a scheduling step into the funnel. The patient has to find a slot, remember it, and be somewhere they can take a video call. Each of those is a drop-off point, and the no-show rate on free consultations in consumer health is significant.
Async removes all of it. The patient completes an intake when they are already motivated, and the decision comes back on the provider's schedule. There is no calendar, no idle provider time, and no dependency on the patient being available at a particular moment.
For a brand paying for its own traffic, that difference compounds directly into cost per acquired patient.
Where a synchronous visit is required
Two things force a live visit, and they are independent of each other.
The first is state law. A number of states require a synchronous encounter before an initial prescription, regardless of the medication. Which states these are changes, which is exactly why this belongs in routing logic rather than in a team member's memory.
The second is the medication. Controlled substances carry their own requirements. Testosterone, as a DEA Schedule III substance, is the common case in this category: a live visit after baseline labs and before the first prescription is the norm.
How this maps onto categories
Most direct-to-consumer categories can run asynchronously in most states, with a synchronous pathway triggered by state or by clinical complexity.
| Category | Standard pathway | What forces sync |
|---|---|---|
| Weight management (GLP-1) | Async review | State rules requiring an initial live visit |
| Testosterone (TRT) | Synchronous | DEA Schedule III, plus baseline labs |
| Enclomiphene | Async with labs | Not a controlled substance |
| Menopause (HRT) | Async review | State rules, or clinical complexity |
| Sexual health | Async review | State rules only |
| Hair loss | Async with photos | Rarely anything |
| Peptides | Async with sync option | State rules, protocol dependent |
Build it as routing, not as policy
The mistake is documenting the rule and relying on people to follow it. The requirement varies by state and changes over time, and volume makes manual application unreliable exactly when it matters most.
The right implementation encodes the rule inside the intake, so a patient in a state that will not permit an async initial prescription is screened at that point rather than discovered later. Your team never has to know the map, and the map can be updated centrally when the rules change.
Both pathways, chosen by the intake rather than by your team
PharmaBro runs asynchronously across every category except testosterone, where Schedule III status brings a live-visit requirement. The intake encodes state eligibility, so a patient who cannot lawfully be served on an async pathway is screened at that point rather than booked into something we do not offer.
That means one workflow rather than a separate operating procedure per state, and it means the constraint is enforced structurally instead of depending on someone remembering.
Conclusion
Async is the default for good reason: it converts better, costs less to deliver, and is legally sufficient for most categories in most states.
The discipline is knowing precisely where it is not sufficient, and encoding that in the intake rather than in a policy document. Requiring video everywhere is expensive. Requiring it nowhere is a compliance problem. Routing by state and category is the only version that is both.
Frequently asked questions
Is asynchronous telehealth legal?
In most states for most non-controlled therapies, yes. Several states require a synchronous visit before an initial prescription, and controlled substances have additional requirements. The rules vary and change, so routing by patient state is safer than a fixed policy.
Which categories can run fully async?
Hair loss and sexual health are the closest to fully asynchronous in practice. Weight management, menopause and most peptide protocols run async in most states with a sync pathway where required. Testosterone is the clear exception because of DEA scheduling.
Does async mean no provider actually reviews the case?
No, and any platform where it means that has a serious problem. Async means the review is not simultaneous, not that it is absent. A clinician licensed in the patient's state reviews the intake and can approve, request clarification, or decline.
Priya RaghunathanHead of Compliance Operations
Handles LegitScript, HIPAA posture, MSO structuring and state coverage. Writes the parts of this blog that operators wish someone had told them before they signed.