How to Add Telemedicine to Your Medspa Website. A no-code guide for 2026.

Why medspas are adding telemedicine in 2026

In 2026, a medspa website without a telehealth layer is a medspa website that can't legally sell most of what's on its menu. Botox, GLP-1s, peptides, IV cocktails with prescription additives, hormone therapy, ED meds, Rx hair-loss protocols — every one of those requires a Good Faith Exam by a licensed provider before fulfillment, and patients buying online have come to expect that exam to happen on the same site they checked out on. Bouncing them to a separate scheduling tool, a phone call, or an in-person visit kills the conversion and creates a paper trail that doesn't exist where regulators expect to find it.

Two motivations show up on every conversation we have with a clinic owner adding telehealth to their site, and they sit on opposite sides of the same coin. The first is conversion. Patients who add a GLP-1 program or a Botox pre-pay to their cart are ready to spend; bouncing them to "we'll call you to schedule a consult" is where the funnel collapses. The second is the regulator. Every state expects a documented patient-specific evaluation by a licensed prescriber before a prescription product is dispensed or an Rx-involved procedure is performed — what that evaluation looks like, and which providers can perform it, varies state to state. That's the layer most clinic builders defer until something breaks.

The good news for clinics that don't have a developer on payroll: none of the three viable approaches require you to write code. They differ wildly on cost, time-to-launch, and how much of the medical-compliance lift you take on yourself. The rest of this guide is a clear-eyed comparison so you can pick the right one, plus a step-by-step for the version most medspas land on.

The three approaches, compared

There are three ways clinics actually add telehealth to a site they already own. They look very different in cost and labor:

1. Custom development. Hire a team (or an agency) to build a bespoke booking + video + provider-routing + documentation system. You own the IP, you own every problem. Expect $40K–$120K upfront and a $3K–$8K/month maintenance line, plus a medical director on retainer.
2. SaaS scheduling tool. Drop a Calendly, Acuity, or SimplePractice embed on your site to book a separate visit with your own provider. Fastest install. Doesn't actually do the GFE — it schedules one — and doesn't generate signed compliance documentation, route to state-matched providers, or integrate with your store.
3. Embedded GFE widget with a managed provider network. Install a plugin, plug into a managed clinical network that handles the exam itself. The compliance side is the vendor's problem; the booking, exam, prescription, and documentation all happen inside your existing checkout. Per-exam pricing, no upfront build.

For a medspa that's already selling Rx products on a WordPress + WooCommerce stack, the third option is almost always the right answer. The first option makes sense for a national tele-aesthetics brand building proprietary IP. The middle option — a SaaS scheduler with no GFE component — is the most common compliance trap, because it looks like the telehealth piece is solved when it isn't.

What to actually look for in a telemedicine widget

The category is crowded enough now that the marketing pages all sound identical. Five criteria separate the widgets that hold up under a state-board inquiry from the ones that don't:

1. Real HIPAA compliance, with a signed BAA. A Business Associate Agreement is the legal contract that makes a vendor accountable for the PHI they touch. "HIPAA-friendly," "HIPAA-aligned," or "encrypted" — without a BAA in writing — is marketing language, not compliance.
2. A managed provider network with verifiable state coverage. Ask which states their network operates in, and which they don't. National-sounding tools that quietly exclude 10–15 states are common; verify before you commit. Quidget's network operates in 48 (every state except Alabama and Mississippi).
3. LegitScript Certification — or the equivalent merchant credential. Stripe, Square, and the major medspa-adjacent processors flag uncredentialed Rx-product sales and freeze accounts when enforcement letters arrive. LegitScript is the certification your merchant processor wants to see.
4. White-label or your-brand presentation. The patient should feel like they're still on your clinic's site through the entire exam, not a marketing detour into a vendor brand. Domain control matters here too.
5. Documentation that lands in your store, not theirs. The signed GFE has to attach to the order/chart your fulfillment team works from. A widget that traps the documentation in a portal you have to log into separately is a workflow tax forever.

Step-by-step: adding Quidget in under 30 minutes

The Quidget install is built for clinics that want to self-serve. There's no white-glove implementation team, no 6-week onboarding, no kickoff call required. Over 80% of clinics that run the install themselves get to a live first exam on their first attempt — most in under thirty minutes of focused work.

The single most common stuck point is step 2 — configuring the treatment menu — because that's the first time most clinic owners are asked to enumerate exactly which Rx products they sell and under what protocol. The interface is checkbox-driven, but the homework on your own product catalog is what takes the time. If you have a current price list and your medical director on call, it's the fastest path through.

If step 2 stalls, our team will hop on a 15-minute setup call and walk through it with you. That's not a sales call — most clinics are already past the decision by the time they ask for help.

Platform compatibility: WordPress, Squarespace, Shopify, Wix

Quidget is built for WordPress + WooCommerce specifically, because that's the stack the majority of medspa e-commerce sites already run on — Woo is the most-used cart for Rx-adjacent commerce because it gives you control over checkout fields, fulfillment rules, and HIPAA-relevant data handling. If you're already on WP/Woo, the install is the 30-minute path above.

For sites on other platforms, the supported pattern is to run the booking flow on a Quidget-powered WordPress subdomain (typically book.yourclinic.com) and link to it from the main site. The patient experience is the same — your branding, your domain, your colors — but the install lives separately from your marketing site:

• Squarespace. Run Quidget on a subdomain, add a "Book your exam" button on your main site that hands off to it. The pattern works without disrupting your Squarespace content.
• Shopify. Same subdomain approach. Some Shopify clinics also run Woo as a separate Rx storefront just for prescription products, keeping cosmetic and Rx commerce on different stacks.
• Wix. Same subdomain approach. Wix doesn't expose enough checkout customization to do this natively even with a custom build.
• Custom-coded sites (React, Next.js, etc.). The subdomain pattern works, and engineering-led clinics sometimes prefer it because it isolates the regulated workflow into a separately auditable surface.

Roughly 30% of the clinics on Quidget today are non-WordPress sites running the subdomain pattern. It's not the marketing-page default, but it's a well-trodden install path.

Pricing & ROI math

The numbers most "add telehealth" posts skip — what does this actually cost compared to what it replaces?

• An in-person GFE provider on retainer. A part-time NP or MD covering GFEs for a working medspa typically costs $80–$200/hour, and a clinic running ~30 routine GFEs a week needs roughly 5–8 hours of provider time on top of treatment coverage. That's $20K–$80K/year in provider salary just for the GFE step.
• A custom-built telehealth stack. The realistic build budget is $40K–$120K upfront for a working v1, plus $3K–$8K/month in maintenance, plus a medical director on retainer separately. Most builds don't reach feature parity with a managed widget for the first 12 months.
• A managed GFE widget like Quidget. Per-exam pricing, no upfront install fee. A clinic running 30 exams a week generally lands at a fraction of in-person retainer cost — and a fraction of build-and-maintain cost — because you only pay when an exam actually happens.

The free 30-day trial is sized for this exact comparison: run your real volume through the widget for a month, compare your real cost-per-exam against your current line items, and make the call from your own numbers instead of a sales-deck projection.

The compliance checklist

Whatever approach you pick, these seven items have to be true at the end of it. Print them out and walk down the list with whichever vendor you're evaluating.

1. Synchronous, real-time GFE performed by a state-licensed provider before any Rx product ships or any Rx-involved treatment is administered.
2. Signed BAA on file with every vendor in the chain that touches PHI — including the widget, the video provider, the EMR, and any scheduling layer.
3. LegitScript Certification (or the merchant-credentialing equivalent your processor requires) on the entity selling the Rx products.
4. State coverage that matches every state you ship to or operate in. Patients in uncovered states need to be flagged at checkout, not after the fact.
5. Documentation retention for the window your state requires — typically 7–10 years for medical records, longer in some jurisdictions.
6. Medical director of record if your state requires one. A widget can cover the exam itself; it can't replace a named MD on file at the board.
7. An audit trail linking the order, the patient record, the GFE encounter, the prescription, and the fulfillment event — readable in one place, not assembled across systems on demand.

Next steps

Three concrete paths depending on where you're starting from:

1. If you're already on WordPress + WooCommerce — start the free 30-day trial and run the 5-step install. Most clinics get to a live first exam on their first attempt.
2. If you're on Squarespace, Shopify, or Wix — book a 15-min demo and we'll walk through the subdomain pattern with your specific site. We've onboarded over a hundred non-WP clinics this way.
3. If you're still figuring out whether telehealth is the right move at all — the GFE pillar guide walks through what regulators actually expect, with no commitment and no sales pitch. Come back here when you're ready.

The shorter version of all of it: adding telehealth to a medspa site in 2026 is no longer a six-month engineering project — it's a Tuesday-afternoon plugin install, with the compliance work handled by people whose only job is the compliance work. The clinics that figure that out first are the ones still selling injectables online in 2027.