Before the visit
Make finding a time feel easy.
Services, available professionals, and chairs come together before your client confirms.
Chairside / A salon DOL example
More time
for people.
Less juggling.
The right stylist. A chair that’s ready. A client who feels expected.
Connect the booking, the welcome, and the next visit—with your services, your style, and your rules at the heart of it.
Fictional sandbox. No live booking, AI, voice, messages, or payments.
Curious what makes it work?Picture a connected studio: a booking reserves a stylist and chair, arrival reaches the front desk, and a return visit is proposed for client review. Enable JavaScript to lift the floor and follow the animated layers.
For the people behind the chair
Keep your personal touch.
Connect the rest of the day.
During the day
A calmer handoff. A warmer welcome.
Give the front desk and your team a shared view of who’s arrived and what happens next.
After the service
Keep the next visit in the picture.
Offer a return visit with clear choices. Your client stays in control; payments can connect later.
A salon. A barbershop. Your own way of working.
Discuss my studio DOL ↗Good hospitality, with a working foundation
The experience above.
The orchestration below.
That connection is a Digital Orchestration Layer—DOL for short. Follow a request, see where business rules apply, and explore what changes for each business. These walkthroughs illustrate the architecture; they are not live AI or voice sessions.
01 / A request in motion
From a client’s request
to the right action.
Choose an example, then run the flow or explore one step at a time. Watch what changes when a request passes—or fails—the scope check.
A client request moves through Core Intelligence, a typed capability, policy checks, and the business executor. A scoped event updates the relevant service screen, and a receipt returns the outcome. Enable JavaScript to explore the interactive walkthrough.
02 / Open up the operating model
The right information.
The right permissions.
Explore the nine salon and barbershop layers beneath the experience. Select a layer to see the information it works with and the change it can request.
Nine layers cover clients, services, staff and chairs, appointments, front desk, checkout and return, communications, evidence, and accessibility. Enable JavaScript to inspect each layer.
03 / One archetype. Your kind of studio.
Change the business.
Keep the shared foundation.
Choose a salon, a barbershop, or a shared studio. Its brand, services, resources, and operating model vary while the reusable Chairside foundation stays in place.
The shared Chairside archetype combines with a studio’s public bundle to create a separately scoped DOL instance. Enable JavaScript to compare the example venues.
The venue bundle supplies public knowledge and configuration. Private records, credentials, and operational authority belong inside the business-controlled runtime.
The underlying definition
What goes into your DOL.
Explore the 20 components in this example. Your build selects compatible services and defines the supported provider connections.
Inspect all 20 standard components
Business identityRequired
Public brand, hours, policies, and isolated instance identity.
business-identityService catalogRequired
Services, durations, prices, preparation, and staff eligibility.
service-catalogStaff & chairsRequired
Working hours, staff eligibility, chairs, and cleanup buffers.
staff-resourcesAppointmentsRequired
Availability, holds, confirmation, rescheduling, and cancellation.
bookingClient preferencesRequired
Minimum necessary, consented customer context; no clinical records.
client-contextFront desk & serviceRequired
Check-in, in-service, completion, and truthful status updates.
service-progressWalk-ins & waitlistSelectable
A local queue with explicit staff acceptance and no guaranteed appointment.
waitlistDeposits & checkoutSelectable
Optional provider binding. Quotes and simulated receipts are not charges.
paymentsReminders & rebookingSelectable
Consent-bound notification outbox and rebooking proposals; delivery requires a provider.
communicationsBusiness knowledgeRequired
Grounded service and policy answers from the public bundle.
business-knowledgeCore IntelligenceSelectable
Maps bounded text requests to typed proposals; cannot authorize actions.
core-intelligenceCore VoiceSelectable
Optional replaceable voice adapter with a complete text fallback.
core-voiceEvents & receiptsRequired
Scoped projections, duplicate protection, and attributable outcomes.
events-receiptsOwner operationsRequired
Inspect components, policy, operational state, and demo receipts.
administrationAccessibilityRequired
Required feature option: reduced motion, stronger contrast, larger text, and non-voice operation; baseline controls cannot be disabled.
accessibilityBooth / chair rentalSelectable
Optional relationship-scoped catalog and calendar ownership; production adapter not included.
booth-rentalRetail & inventorySelectable
Optional stock-aware retail contract; not activated in this sandbox.
inventoryVenue & professional ratingsSelectable
Separate ratings tied to an eligible completed visit. Local sample ratings only; real submissions require verified sign-in and policy checks.
ratingsGallery highlightsSelectable
Planned shared component: owner-curated, consented, accessible highlights. Upload and moderation portal not yet implemented.
gallery-highlightsTestimonials & private complaintsSelectable
Planned shared component: OAuth/OIDC sign-in before submission, private complaint routing, separate testimonial publication consent and approval.
customer-feedbackDefinition: salon.chairside@0.1.0.
Try the service surfaces
Step into Chairside Studio.
Book a fictional appointment, open the front desk, check in your client, complete the service, and inspect the same DOL’s receipts.
Generic sample business. State stays in this tab; no real customer data, booking provider, or payment channel.