How the connected system works
Five moments. One record. No invisible handoff.
The patient sees one understandable next step. The clinic sees one responsible action. MedSpaMedia keeps the shared context attached as the work changes hands.
- 01Attract
Turn one clear offer into the right first visit.
A prospective patient finds a useful page, ad, post, or printed offer.
- Responsible action
- Choose the offer, audience, destination, and owner before creative production begins.
- Completion proof
- Web, Meta, social, print, and event work keep the same offer context.
State boundaryOpen attractA click is not a lead; an offer is not active until its destination, conditions, and owner agree.
- 02Welcome
Collect only what changes the next handoff.
The patient shares contact details, goals, and required consent in a short clinic flow.
- Responsible action
- Front desk receives a confirmed record instead of retyping a form or guessing whether it saved.
- Completion proof
- The intake receipt, client, visit, and responsibility are created together.
State boundaryOpen welcomeA local form state is not saved. The patient sees confirmation only after the receipt exists.
- 03Prepare
Give the provider context without pretending to diagnose.
The patient arrives knowing who will review the information and what happens next.
- Responsible action
- The assigned provider sees only the visit they own, reviews the record, and completes the clinical handoff.
- Completion proof
- Provider review and patient-safe follow-up remain separate, explicit states.
State boundaryOpen prepareThe platform does not diagnose. Only the assigned provider reviews and completes the visit.
- 04Guide
Make the waiting room part of the visit, not background noise.
A silent, branded channel explains treatments and the clinic's current offer while the patient waits.
- Responsible action
- The owner chooses the lineup; VRAL produces one version; the clinic reviews a private proof before installation.
- Completion proof
- Draft, submitted, in production, review, revision, delivered, and installed never collapse into one fake success state.
State boundaryOpen guideSelected is not delivered. Delivered is not installed. Each transition keeps separate proof.
- 05Continue
End every interaction with a named next step.
The patient gets the next approved action, not an unexplained marketing sequence.
- Responsible action
- Owner, front desk, provider, and VRAL each see the next responsibility addressed to them.
- Completion proof
- Today Room keeps owner, due time, dependency, and completion proof attached to the source record.
State boundaryOpen continueQueued is not sent, booked, or paid. The next person and next system response remain explicit.