Most e-commerce health brands run on asynchronous telehealth, whether or not they use the term. A patient completes an intake at 11:40 pm. A licensed provider reviews the case the next morning, asks one clarifying question, and sends the prescription to the pharmacy before lunch. No appointment, no waiting room, no video call.
This post covers how that model works in practice, which verticals it fits, where synchronous telemedicine still earns its higher cost, and what the platform underneath has to support either way. If you want the plain definition first, the asynchronous telehealth glossary entry covers it in a minute.
The two models, briefly
Synchronous telehealth is live. A patient and provider interact at the same time by video, phone, or real-time chat. Asynchronous telehealth is reviewed. The patient submits structured information, questionnaire answers, photos, history, and the provider evaluates it on their own schedule, usually within hours.
The distinction sounds academic until you price it. A synchronous visit consumes a scheduled block of provider time whether the case needed all of it or not. An asynchronous review consumes only the minutes the case actually requires. At volume, that difference decides your unit economics.
Conversion follows the same logic. E-commerce health traffic peaks at night and on weekends. An intake that finishes in ten minutes keeps the patient in the funnel; a scheduler that offers Thursday at 2 pm gives them three days to change their mind. Staffing changes shape too: providers work a review queue that flexes with volume instead of a calendar someone has to guess at in advance.
How an asynchronous visit actually runs
- Intake: the patient completes a structured questionnaire that branches by treatment category, state, and prior answers, uploads photos where the condition is visual, verifies identity, and signs consents. This step decides everything downstream. A thin form produces a case the provider cannot act on, which is why patient intake software quality is the first thing to evaluate in any async program.
- Provider review: the case lands in a queue. The provider reads the structured history, checks the photos, and either decides or asks for more.
- Clarification: when something is unclear, the provider messages the patient inside the platform. The patient answers on their own time. No one reschedules anything.
- Decision and prescription: if treatment is appropriate, the provider e-prescribes and documents the encounter. If it is not, the patient gets a clear explanation and, where it helps, a path to a live visit.
- Fulfillment and follow-up: the pharmacy ships, refill logic takes over, and check-ins collect the data the next review needs.
Each stage produces a record. That audit trail is the difference between an async program a regulator can read and one that lives in screenshots and inboxes.
Which verticals suit asynchronous care
Async works when the patient can supply everything the provider needs to decide. Three categories show up again and again.
Weight loss refills: the initial GLP-1 consult may need more depth, and in some states a live encounter, but months two through twelve are a questionnaire: current weight, side effects, dose tolerance. A patient on a stable titration schedule does not need a calendar slot to report that the medication is fine.
Hair loss: finasteride and minoxidil protocols are history-driven and stable. The questions rarely change, the answers rarely surprise, and a decent photo settles most of the rest.
Dermatology photo review: store-and-forward derm is the oldest async pattern in medicine. Acne, rosacea, and similar conditions carry their evidence in the image, and a provider can often review a well-shot photo set faster than a video call could get the lighting right.
The common thread is protocol-driven care with reliable history. The further a condition drifts from that, the harder async has to work.
Where synchronous telemedicine earns its cost
Live visits are expensive per encounter, and sometimes worth every dollar.
Behavioral health depends on conversation. Complex first visits, medication counseling with real tradeoffs, and rapport-sensitive conditions all benefit from a provider who can probe in real time. So does any case where live judgment reduces clinical risk.
The platform requirements shift with the model: scheduling, secure visit links, reminders, and documentation instead of review queues. Our guide to HIPAA-compliant scheduling software covers that layer.
The state rules nuance
Prescribing rules are set state by state, and they treat modality differently. Some states accept an asynchronous encounter as sufficient to establish the patient relationship for most treatment categories. Others expect a phone or video interaction first, at least for certain medications. The rules also change, and the category details matter more than any summary can capture.
The operational answer is structural, not legal: do not hard-code a single modality into your funnel. Build intake that branches by state and treatment category, keep a live-visit path ready for the states that expect one, and have counsel own the state-by-modality map. The expensive failure mode is launching async-only, discovering that a large state expects a call for your core product, and bolting scheduling onto the funnel under pressure.
Escalation keeps async safe
Every serious async program needs a defined exit from async. Red-flag answers, contradictory history, a photo that raises more questions than it answers: these cases should move to a live encounter through a designed path, not through a support ticket.
That is also why the sync-versus-async debate usually resolves into a hybrid. A patient starts asynchronously, escalates to a video visit, receives a prescription, completes follow-up messaging, and later lands in a remote patient monitoring workflow. If your platform treats those as separate products, your team inherits the integration work between them.
What the platform has to support
Whichever mix you run, evaluate the same list: intake quality and branching, provider review queues with audit trails, secure messaging, e-prescribing and pharmacy handoff, scheduling for the live path, and HIPAA-ready controls under a signed BAA. The HIPAA-compliant telehealth platforms guide walks through the compliance diligence behind each item.
How Remedora runs asynchronous care
Remedora is an all-in-one telehealth platform for e-commerce health brands, and its intake-to-prescription flow runs asynchronously with licensed provider review as the default. A patient lands on your storefront, completes branded intake (translated into Spanish and Brazilian Portuguese where your audience needs it), and the case routes to a provider network licensed in all 50 states plus Puerto Rico. The provider reviews, messages the patient when something needs clarifying, and e-prescribes. Pharmacy fulfillment (sterile and non-sterile, with shipping to Puerto Rico), payments, and support run on the same system, with HIPAA compliance under one signed BAA instead of a stack of vendor agreements. Pricing starts at $200 per month flat, and brands typically go live in hours, which makes it practical to test an async vertical before you commit real payroll to it.
If you are designing the care model from scratch, start with the care path and let the modality follow. How to launch a telehealth company covers that sequence, and the short version is this: pick the conditions you want to treat, map which steps genuinely need a live provider, and make sure the platform can run both modes without side-channel workarounds.
