End-to-end demoClient + spaHermes packet handoff

Watch a client concern become a clinic-ready lead and a spa operating action.

This guided cockpit shows the whole loop: intake, visual demo, event-safe plan, clinic match, quote request, Operator Lite inbox, setup-driven reply, and quote comparison.

Step 1 of 10: Clinic setup creates the operating rules

Spa setup

Presenter Mode

Use this during a sales call to focus the room on the client side, the spa side, or the full handoff.

Audience View

Switch views without changing the underlying step.

Current presenter focusClient, Hermes, and Spa

Speaker Notes

Talk track for the active step.

Spa setup

Start by removing the integration objection. This works with the spa's current booking link and inbox.
The setup packet is the operating contract: services, prices, providers, guardrails, products, and tone.

Shareable demo script

1. Clinic setup creates the operating rules
Phase: Spa setup
Client: Spa is ready to route a better lead.
Hermes: OperatorLiteGeneratedSetup
Spa: Setup packet saved.
Talk track: Start by removing the integration objection. This works with the spa's current booking link and inbox. The setup packet is the operating contract: services, prices, providers, guardrails, products, and tone.

2. Client starts with a concern
Phase: Consumer intake
Client: Selects Under-eyes and describes dark/hollow/tired appearance.
Hermes: ConcernProfile
Spa: Concern graph captured.
Talk track: The consumer value is clarity. The spa value is structured intent before the first staff reply. This is not a directory click; it is a qualified consult packet forming in real time.

3. Demo face avoids upload friction
Phase: Visual triage
Client: Chooses demo model instead of uploading his own face.
Hermes: VisualSimulationSession
Spa: Visual pattern organized.
Talk track: The demo-face option lowers friction for users who will not upload their own photo. Keep the language conservative: appearance signals only, not diagnosis.

4. Event timing changes the recommendation
Phase: Safety logic
Client: Selects date in 2 days and conservative preferences.
Hermes: EventContext + PreferenceProfile
Spa: Downtime rules applied.
Talk track: This is a trust moment. The product recommends not making the client worse before a date. The clinic benefits because the lead arrives with safety constraints and realistic expectations.

5. Plan splits now vs later
Phase: Treatment plan
Client: Reviews immediate event-safe plan and longer-term options.
Hermes: Plan
Spa: Plan packet created.
Talk track: The plan separates immediate event prep from the long-term treatment path. The consult questions reduce back-and-forth and help staff route to the right provider.

6. Matched clinic is chosen
Phase: Clinic match
Client: Chooses a clinic aligned with no-filler/no-Botox preferences.
Hermes: ClinicTransparencyScore
Spa: Clinic match scored.
Talk track: The match logic is explainable, not sponsored-looking. For a spa, this means better-fit leads, not just more low-context traffic.

7. Client sends quote/message
Phase: Handoff
Client: Sends quote request into Operator Lite.
Hermes: OperatorLiteActionLead
Spa: Lead lands in Lite inbox.
Talk track: This is the handoff moment. The client action becomes an Operator Lite lead. No integration is required; staff can copy into whatever tool they already use.

8. Operator Lite generates the manual action
Phase: Spa action
Client: Awaiting clinic response.
Hermes: OperatorLiteReplyTemplate
Spa: Copy reply, quote range, or booking link.
Talk track: The setup rules now drive the operational response. This turns a med spa's service menu into a lightweight sales assistant without touching backend systems.

9. Spa replies without integration
Phase: Response
Client: Understands what to do now and what to defer.
Hermes: MessageLog
Spa: Manual response sent.
Talk track: This is the wedge product: useful immediately, then integrations can come later only where needed. The spa can respond faster while preserving clinician judgment and safety boundaries.

10. Quote comparison closes the loop
Phase: Decision support
Client: Compares by safety, timing, fit, transparency, and value.
Hermes: ClinicQuoteResponse
Spa: Follow-up and product stack queued.
Talk track: Close by showing that this is not just lead capture. It supports follow-up, product attach, and long-term treatment conversion. The business case is safer conversion, better-qualified consults, and more revenue from existing workflows.

Potential Client

Before the client arrives

what client sees

No consumer account is required yet.
The clinic provides only public workflow details.
No CRM, calendar, EHR, payment, or phone integration is needed.

Client actionSpa is ready to route a better lead.

Open related screen

Hermes Handoff

Structured packet moving across the system.

OperatorLiteGeneratedSetupClinic setup creates the operating rules

100/100 readiness
Use the clinic's existing booking link (https://lumen-demo.example/book/under-eye-consult). Ask leads to add "Spa Lite packet" in notes so staff can match the consult context manually.
Route near-event, low-downtime leads to LED + hydration facial or consult-only guidance before procedures.

Client inputSpa action

Spa / Operator Lite

Spa operator layer

what spa gets

Booking link, price ranges, provider routing, product brands, and escalation rules are converted into operating rules.
Reply templates and quote rows are generated.
The spa keeps its existing backend.

Operator actionSetup packet saved.

Open Operator Lite

Value Summary

Close the demo by making the business case explicit.

no integration required

For the clientClarity before booking

The user understands causes, timing risk, treatment tradeoffs, clinic fit, and what to ask before spending money.

For the spaHigher-intent lead packet

The clinic receives concern details, exclusions, timing, budget, product context, and a copy-ready next action.

For the businessNo-integration wedge

The spa can start with booking links, inbox copy, manual quote ranges, and follow-ups before any CRM, calendar, EHR, or payment work.

Action Log

Each step creates or updates a structured operating object.

1 events