One treatment journey, from intake to the six-month recall

The business

A skincare and esthetics studio in Solana Beach, California. A small team, a treatment room calendar, and an owner who was doing the admin between clients.

This is one of more than fifty projects, an example of the work rather than the whole book.

The starting condition

Appointments were taken and confirmed manually. Intake was paper, or a form somebody had to read before the client arrived. Allergies and conditions lived in that paperwork, which meant the provider’s safety check depended on someone having read the right sheet at the right moment. Aftercare was given verbally and forgotten by the time it mattered. Clients who should have come back at three months came back when they happened to think of it.

The pieces were all software, and none of it spoke to the rest. Booking, payment, intake and the client record each lived in their own tool, and the owner was the integration: reading one, typing into another, remembering what the gap between them had dropped. That holds until she is busy, away, or interrupted between clients.

What was built

Intake, once, per client, and carried. A custom intake form is attached to the client rather than to a single visit, so what the studio learns about someone on their first appointment is still there on their fifth. New answers update the record instead of starting a second version of the same person.

An allergy and condition alert for the provider. The safety-relevant answers from intake are pulled out and shown to the treatment provider as an alert at the point of treatment, not buried in a form somebody would have to go and find. This is the part of the build that matters most and looks smallest: the information already existed, and the work was putting it in front of the right person at the moment they can act on it.

Pre-treatment messages, specific to the treatment booked. The client is told what to do and what to avoid before a particular appointment, on a schedule that fits that treatment rather than a generic reminder. A client who needs to stop a product a week before hears about it a week before.

Confirmation and the chase. Booking confirmations go out automatically, and appointments that stay unconfirmed are chased rather than left to discover themselves on the day. No-shows and cancellations have a defined path instead of an awkward phone call.

Post-treatment guidance, timed to the recovery. Aftercare arrives when the client needs it, in writing, treatment by treatment. The studio stops repeating instructions that were given verbally at the door and the client stops guessing on day three.

Recall at two, three and six months. Treatment-specific reminders bring people back on the schedule the treatment calls for, not when the calendar looks quiet.

Synced with the studio’s booking and payment system, so the record it already ran on stayed the system of record and nobody had to keep two calendars in step.

What this changed

The owner stopped being the thing that connected the steps. Every step above used to be a thing she carried: remembering the allergy, remembering the aftercare, remembering who was due. The build did not add a service she was not already providing. It moved that work out of one person’s memory and into a journey that runs whether or not she is between clients that day.

The pillars this touched

Systems defined the journey and who owns each step, Automation & AI carried the approved messages, and Customer Continuity owns the recall that brings people back.