Marigold StudioAppointment LabDemo · nothing sent

Fictional concept demonstration

Marigold Studio

A calmer pathfrom question to appointment.

Booking, rescheduling, approved FAQs, service recommendations, no-show prevention, staff handoff, and one operator view - with every customer action disabled.

01

Assessment

Standardize the booking promise before automating it.

The synthetic case assumes fragmented requests, inconsistent service selection, late changes, and manual reminders. Every number below is an assumption with a validation method.

01

Choose

Client selects a goal and service

02

Check

Rules show synthetic availability and preparation

03

Hold

A browser-only slot is placed in the review queue

04

Review

Staff checks exceptions and recommendation fit

05

Confirm

The demo records a local confirmation - nothing is sent

06

Prevent

A reminder plan and reschedule path stay visible

Opportunity scorecard

Value, burden, risk, and readiness.

A-01

Structured self-booking

93
A-02

Reschedule guardrails

83
A-05

No-show reminder plan

77
A-03

Approved-source FAQ

70
A-04

Service recommendation aid

60
A-06

Autonomous exception approval

33

Assumption ledger

Prove the baseline first.

A-01

Monthly appointment requests

70–110

Count all channels for 30 days

A-02

Manual coordination

8–14 min/request

Time a 30-request sample

A-03

No-show or late-change share

6%–14%

Reconcile completed and changed sessions

A-04

Contribution per retained session

$70–$140

Owner supplies invoice less variable cost

A-05

Recoverable sessions

1–4/month

Compare a controlled pilot to baseline

02

Interactive prototype

Customer clarity on the left. Staff authority on the right.

All state disappears on refresh. Network actions are not implemented.

BOOKING ASSIST / BROWSER ONLYNo live connection
1. Describe the goal
Suggested service · 90% confidencePersonal Color Session

introductory guided session fits the stated goal

2. Choose a service and synthetic slot
3. Prepare a local review record

No synthetic appointments yet.

Approved-source FAQ

Answer from four entries, or stop.

No open-web lookup and no invented policy.

Ask a question to test retrieval and handoff.

Editable ROI assumptions

A range to test, not a return to promise.

Labor value plus retained contribution, less monthly software and support cost. Revenue is not attributed until the baseline and control are credible.

ILLUSTRATIVE MONTHLY MODEL

Labor capacity value

$246

Retained contribution

$210

Monthly cost

-$145

Illustrative net

$311
Annualized: $3,737 · validate every input

Risk analysis

The hardest failures are promises and data, not buttons.

High

Availability promise

Never confirm a real slot outside the system of record

Medium

Poor recommendation fit

Show reasoning and route exceptions to staff

High

Sensitive notes

Collect only ordinary scheduling needs; prohibit health details

High

Reminder consent

Use vendor-supported consent, quiet hours, and opt-out controls

Medium

Calendar drift

Reconcile and stop booking if sync health is uncertain

03

Implementation plan

Twelve weeks from evidence to client-controlled handoff.

01 · BaselineWeeks 1–2

Map channels, policies, exceptions, staff ownership, consent, and 30 days of request data.

02 · ConfigureWeeks 3–4

Trial one scheduling system with services, duration, buffers, rescheduling, reminders, roles, and export.

03 · PilotWeeks 5–8

Open one controlled channel; review recommendations and exceptions; keep manual fallback ready.

04 · HandoffWeeks 9–12

Acceptance test, train staff, audit permissions, test disable/export, and hold a 30-day review.