Skip to content
Vayra Platform

Patient experience

Your brand in front. Our infrastructure behind it.

The storefront, intake, portal and messaging your patients use, on your domain and in your visual identity, running on the same stack Vayra uses for its own practice.

What it does

  • Branded storefront

    Program pages, eligibility checks and checkout on your own domain. Your colours, type and voice. Patients never see Vayra unless you choose to show it.

  • No-code intake builder

    Build intake questionnaires with branching logic, required disclosures and contraindication screens. Version every change, so you can show which form a patient answered and when.

  • Async triage

    Completed intakes route to the right clinical queue with the answers already structured for review. Incomplete or ineligible submissions stop before they reach a clinician.

  • Patient portal

    Order status, shipment tracking, documents, care plan and billing in one signed-in place. Patients can update details without a support ticket.

  • Secure messaging

    Asynchronous messaging between patients and their care team, kept inside the clinical record rather than in a separate inbox.

  • Refills and renewals

    Patients request refills from the portal. Requests carry the history a clinician needs to approve or decline, and the decision flows straight to fulfillment.

From first visit to first shipment

  1. Step 1

    Discover

    A visitor lands on your program page and checks eligibility.

  2. Step 2

    Intake

    They complete your questionnaire. Required consents are captured and versioned.

  3. Step 3

    Review

    The intake joins an async queue for a licensed clinician to review.

  4. Step 4

    Decide

    The clinician approves, asks a follow-up question, requests a visit, or declines.

  5. Step 5

    Fulfill

    Approved prescriptions route to a partner pharmacy and the patient can track the order.

What you control, and what we operate

You control

  • Domain, brand and every word of marketing copy
  • Programs offered and how they are priced
  • Intake questions, within clinical review
  • The patient relationship and the patient list

Vayra operates

  • Hosting, security and uptime of the patient surfaces
  • Form versioning and consent capture
  • Routing into clinical review and fulfillment
  • Portal, messaging and notification delivery

Integration notes

Intake completions and order changes are emitted as events, so your own CRM or data warehouse can follow the patient journey without polling.

Payloads on this page are illustrative. The public partner API is planned for v1.1; see developers for what exists today.

Illustrative event: intake.completed
{
  "type": "intake.completed",
  "id": "evt_01J9ZK6Q",
  "created": "2026-10-27T15:04:05Z",
  "data": {
    "intakeId": "int_7d2c",
    "formVersion": 12,
    "program": "your-program-slug",
    "queue": "async-review"
  }
}

See the platform with your own use case

A 30 minute walkthrough of the dashboards, the clinical workflow and the fulfillment path, shaped around what you are building. No slides unless you ask for them.