White-LabelTelehealth forBranded Patient Portals

Link your storefront and patient portal to supported provider-network, payment, API, and webhook workflows. Licensed care teams retain clinical decisions.

Book a Program WalkthroughSee How It Works
Portal BrandingRole-Scoped AccessREST APILifecycle Webhooks
Program ActivityExample data
Preview
$14,280Revenue
White-LabelREST APIProductsPatientsAnalyticsIntake
portal.brandedjust now

Own the brand. Leave clinical operations to the care team.

Configure a patient experience under your name while provider networks handle intake review, visits, prescribing, and follow-up on the same platform.

Telehealth brand operations team reviewing branded telehealth launch plans
The Challenge & The Solution

ConnectingBrandOperationstoCareWorkflows

Telehealth programs combine brand, integration, operations, and clinical handoffs. Here is how the platform maps those responsibilities.

Build or connectan infrastructure decision

Clinical Infrastructure Has Many Parts

Provider recruitment, pharmacy operations, patient intake, and platform integrations are separate workstreams when a program is assembled independently.
  • Provider-network coordination
  • Pharmacy and fulfillment handoffs
  • Patient and operations workflows
Program-specificlicensing and entity setup

Licensing and Contracts Set the Program Scope

Licensing, privacy, pharmacy, and prescribing requirements vary by program, patient location, and entity.
  • Program and market availability
  • Contracted entity responsibilities
  • Clinical decision ownership
API + webhooksintegration surfaces

Integrations Need Clear Handoffs

Storefront, payment-session, patient, and lifecycle-event handoffs need mapped ownership and testing.
  • Storefront handoffs
  • Payment-session integration
  • Lifecycle-event mapping
How It Works

StorefrontandCare-TeamHandoffs

Five steps show storefront integration, payment and intake, clinical review, and available reporting, with an owner for each handoff.

Integration

Connect Your Storefront

Map your website or app to the GEN Health API, then validate credentials, supported flows, and event handoffs.

1
API Credentials ActiveExample data
Client key: active
Webhook URL: configured
Products: 12 synced
Ongoing

Patient Discovers & Purchases

Patients find your brand through your marketing channels and purchase telehealth products on your storefront.

2
New OrderExample data
Product: Weight Management
Payment: $199.00
Status: confirmed
Configured

Configured Handoffs Begin

Payment, intake, provider-network, and fulfillment milestones move through the workflows configured for the program.

3
Clinical PipelineExample data
Intake: completed
Provider: matched
Review: in progress
Clinical

Care Team Reviews the Patient

Affiliated clinicians review the patient and make clinical decisions within the program's licensed care workflow.

4
Review CompleteExample data
SOAP note: approved
Rx: submitted to pharmacy
Patient: notified
Reporting

Configured Fees Are Reported

When a contracted program includes affiliate fees, the admin dashboard reports configured fees on eligible completed activity.

5
Earnings UpdatedExample data
This month: $14,280
Transactions: 71
Margin: 42%
Platform Capabilities

EverythingabrandActuallyNeeds

The same client-side workflows we ship in product for telehealth brands — branding, demand, integrations, and operations, shown in sequence so owners and handoffs are clear.

01
Portal & brand

Client-Scoped Branding & Portal

Your brand on every patient touchpoint

As the brand, you control portal identity — logo, color palette, and display name independent of the provider network. Toggle logo virtual backgrounds for sync visits so every video call reinforces your brand.

Portal identity

Logo, colors, and display name scoped to your client

Branded patient experience

Patients see your brand from checkout through follow-up

Visit background policy

Enable the pre-configured logo background for provider video visits

Separated from network branding

Your portal look stays yours alongside the clinical network

Example data

MC
Your Marketing Brandportal.yourbrand.com
Live
Palette
Logo background on sync visitsOn

Client-scoped portal identity · independent of network chrome

02
Client API

API Keys & Integrations

Connect your storefronts and back office securely

Generate and manage Client API keys for external integrations. Create patients, orders, and payment sessions programmatically with server-side pricing resolution, scoped permissions, and audit-friendly access.

Client API key management

Issue and rotate keys from your admin settings

Patient & order automation

Onboard demand and create orders from your own systems

Payment sessions

Short-lived checkout sessions with resolved pricing

Scoped permissions

Least-privilege keys with operational traceability

Example data

Client API key
mk_live_••••8f3a
POST /v1/payment-sessions
{ "clientProductId": "cp_wl_", "patientId": "..." }
200pricing resolved · scoped to client
Audit trailRotate keysWebhook-ready
03
Products & intake

Catalog, Forms & Promotions

Configure what patients see and how they convert

Map purchased products to your portal with per-client categories. Decide which intake forms are public for lead gen versus signed-in for established patients. When enabled, run client-scoped coupon codes on eligible products only.

Form visibility rules

Public vs authenticated intake, tuned for acquisition vs care

Category & product layout

Organize offers for your specific marketing funnel

Coupon programs

Create and assign codes when coupon features are enabled for your client

Chart review triggers

Intake tied to orders flows into clinical review when configured

Example data

Intake & catalogClient scope
Lead form (public)
Signed-in intake
SUMMER24Eligible products only
−15%
04
Reports

Tenant-Scoped Analytics

Measure demand, conversion, and revenue — not someone else’s

Access reports and rollups hard-bound to your clientId: onboarding conversion, product demand, visit mix, billing visibility, and prescription turnaround at the milestones your team needs — without crossing tenant lines.

Marketing & ops KPIs

Funnels, demand, and engagement for your patient base only

Visit & product mix

See how async vs sync and product lines perform

Billing & usage summaries

Review invoices for clinical reviews and platform usage

Exports for leadership

Download tenant-scoped data for internal analysis

Example data

Reports · tenant scopeclientId locked
Conversion64%
Affiliate rev.$42k

Export CSV · onboarding, visits, billing visibility

05
Operations

Patients, Staff & Coordination

Run the demand side while clinical stays in-network

Client Admins bulk-upload and oversee patients, create Client Staff for day-to-day coordination, and book visits on behalf of patients when appropriate. Staff track forms, orders, and patient messaging — all strictly scoped to your organization.

Bulk onboarding

Upload patient lists and monitor onboarding status

Client Staff roles

Operational accounts for coordination without full admin keys

Visit scheduling support

Initiate booking workflows for your own patients

Form & message coverage

Support intake completion and patient inquiries operationally

Example data

PatientsBulk import
Alex R.Forms pending
CS
Jordan K.Visit booked
CS
Book visits · Messages · Orders
The Operating Model

Map the Workflow Before Launch

Brand

Client-scoped portal

API

Storefront connections

Roles

Separated access

Events

Webhook lifecycle

Independent Build & Configured Platform

Where implementation responsibilities sit

Independent buildConfigured platform
Clinical Infrastructure
Source components separately
Use configured platform workflows
Integration Scope
Build custom handoffs
Use supported API and webhooks
Responsibility Model
Define each vendor boundary
Map roles, contracts, and care entities
Clinical Staff
Recruit and manage directly
Work with an affiliated provider network
Why Telehealth Brands Choose GEN

For Brand and Operations Teams

Separate brand operations from clinical decisions.

Client teams manage brand and acquisition workflows while licensed providers and affiliated care entities own clinical decisions within each configured program.
  • Client roles exclude clinical decision-making
  • Provider-network responsibilities vary by program
  • Fees and payment routing follow contracted configuration

Set portal, email, and domain branding

Custom logos, colors, fonts, and domain. Patients see your identity from checkout through follow-up communications.
  • Configurable portal branding
  • Branded email communications
  • Custom domain support

Use the REST API and webhooks for storefront handoffs

Documented REST endpoints, scoped permissions, and lifecycle webhooks support configured client integrations.
  • Documented REST endpoints
  • Lifecycle event webhooks
  • Client integration documentation

Tenant-scoped reporting for operational review

Review available revenue, conversion, patient-acquisition, and product activity with built-in dashboards and exportable reports.
  • Revenue and conversion tracking
  • Patient acquisition analytics
  • Exportable report data

Add products and markets after required setup

Confirm affiliated entities, provider coverage, vendor accounts, integrations, testing, and approvals before opening a product or market.
  • Multi-product catalog support
  • Bulk patient onboarding
  • Market availability by program and network

Give operations staff non-clinical tools

Create Client Staff accounts for daily operations. Your team can coordinate patients, review forms, and track orders without clinical access.
  • Client Staff account management
  • Patient coordination tools
  • Order lifecycle tracking
Developer Experience

API-First Integration

Review a payment-session example and the supported lifecycle events available through webhooks.

create-payment-session.ts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
 
Lifecycle Webhooks
Example events
order.createdNew order placed through your storefront
1s ago
payment.completedPayment successfully processed
4s ago
review.approvedProvider approves clinical review
7s ago
prescription.shippedMedication shipped to patient
10s ago
prescription.deliveredMedication delivered to patient
13s ago
visit.completedVideo visit successfully concluded
16s ago
Secure API KeysScoped PermissionsAudit TrailsBranded Docs

FAQ

Questions we'd ask too.

Your team should understand the model, the integration, and day-one operations before you route patients through GEN.

Showing 12 of 12 questions

Ready to Connect Your Telehealth Brand?

Connect your storefront, configure your brand, and map responsibilities with the affiliated care entities for your program.

Book a Program WalkthroughRead the white-label guide
Configurable BrandingRole-Scoped Access
What happens next
1

Provision access

API keys, webhooks, and a sandbox for your marketing and eng teams

2

Connect the storefront

Use API keys, payment sessions, and webhooks for supported handoffs

3

Configure patient branding

Set the domain, logo, colors, catalog, and patient paths

4

Review program reporting

Use tenant-scoped operational and billing reports available to your role

Launch timing varies by scope and prerequisites

Illustrative operating scenario

Campaign traffic enters the branded product and patient flow.

A discovery call can confirm which workflows, entities, and prerequisites apply to your program.