A Zeppelynn AI Product·How AURA WorksSee how AURA works
Discover how AURA supports your spa's front desk, helps customers arrange appointments, and keeps your team informed through configured communication channels.
A guided visual presentation you can understand in a few minutes. Your exact call flow, booking arrangements, and message wording are agreed and reviewed during your spa's setup.
The cast
ConfiguredSpa owner
Defines the experience
AURA
Virtual front-desk concierge
Receptionist
Answers & routes calls
Business team
Stays informed & follows up
AURA sits between your guest and your team — configured from what you approve, and designed to route out-of-scope requests to a person according to the agreed escalation rules.
A virtual front desk, configured around your spa
AURA is Zeppelynn AI's virtual front-desk concierge for spas and wellness businesses. This walkthrough shows how it's prepared for a spa, what a caller experiences, what your team sees, and how customer communication fits into the complete journey.
How AURA is prepared for a spa
An eight-stage setup, from first hello to go-live. Each stage shows what happens, who's responsible, and what you gain. Tap any stage to expand the detail.
A clear, shared understanding of how AURA fits your front desk.
- We walk through AURA's intended role: a helpful first point of contact for routine enquiries, bookings, and message routing.
- You share your goals — what a great front-desk moment looks like for your guests and your team.
- Nothing changes yet. This is a conversation to confirm scope before any setup begins.
Confidence that AURA stays inside the lines you set, and hands sensitive questions to your team.
- We list the everyday, non-clinical services AURA may describe — treatments, durations, availability, policies.
- We mark the boundary: questions about medical suitability, symptoms, or anything clinical are directed to human review according to the agreed safety and escalation rules.
- You decide where AURA should stop and ask, rather than guess.
A single, organized snapshot of how your spa operates — the foundation AURA is built from.
- Business details: name, location, hours, and contact points.
- Services, prices, durations, packages, and membership terms.
- Policies: cancellations, rescheduling, no-shows, and how exceptions are handled.
- Scheduling: calendars, availability windows, and booking preferences.
- Contacts: who a request should reach when a person is needed.
- Messaging preferences: what customers can be told, and how.
A guardrail: spas that touch clinical care are never silently switched on — they're reviewed first.
- The onboarding form asks whether the business offers clinical or medical services.
- A 'yes' or 'unsure' answer triggers manual review rather than continuing automatically through the full onboarding flow.
- This is a real branch in the process, not a formality — submission of the onboarding form does not activate the live receptionist.
AURA answers from your spa's information — not its own assumptions about wellness.
- We structure your approved content into the guidance AURA references when it responds.
- Prices, durations, packages, and membership terms reflect what you've actually agreed to offer.
- Policies and FAQs shape how AURA phrases answers and where it pauses for a person.
Routing that mirrors how your front desk actually answers and books.
- The receptionist configuration — how calls are answered and routed — is set up on its own.
- Calendar connection and the booking approach (when and how AURA can book) are configured here.
- Human transfer and escalation paths are defined so out-of-scope or person-specific requests reach someone.
- This is a distinct step from the onboarding form: the form captures information; this step wires up the behavior.
Customers get a clear thread; your team gets a clear paper trail — each through its own channel.
- Customer-facing confirmation and reminder texts are configured for the customer SMS channel.
- Separately, the team's channels are configured: a post-call summary email, an in-app booking notification, and human-handover tasks where the text/email assistant requires a person.
- Staff-facing SMS is not confirmed in the current configuration. Where shown, it's labeled an optional future or client-specific setup — not active behavior.
You sign off on the experience your guests will actually have before it's switched on.
- We test the configured experience end to end against agreed scenarios.
- You review it and approve the wording, routing, and notifications that matter to your spa.
- Activation happens after the necessary checks and your approval — not the moment the form is submitted.
- After go-live, ongoing improvement is a subsequent process: we review and refine as your spa evolves.
What happens when a customer contacts the spa
AURA greets the caller, identifies the need, and routes the request down the right configured path. Explore each branch to see the decision, the caller's next step, your team's role, and the business benefit.
- 1Customer calls or contacts the spa
- 2AURA greets the customer
- 3AURA identifies what the customer needs
- 4The request follows the appropriate configured path
- 5The customer receives the next appropriate response, where supported
- 6The business team receives relevant information through its configured channels
- 7The request reaches a booking, a human handoff, or another appropriate outcome
Service question
AURA responds using your approved spa information where available; questions outside scope go to a human.
Is this within the approved knowledge AURA was configured with?
A clear, on-brand answer — or, if it's outside scope, a warm handoff to your team rather than a guess.
Receives the out-of-scope questions AURA was not configured to answer.
Consistent answers from your approved information — no improvisation.
One customer. Two connected experiences.
A single call moves through two lanes at once — what the customer feels on the left, and what your team sees on the right. Shared events are linked where they actually overlap.
The customer calls AURA.
The call is logged.
They ask about a service.
—
AURA responds with approved information.
—
They request an appointment.
—
They receive confirmation and reminder messages, where configured — by Customer SMS.
The booking can appear on the calendar, with an in-app booking notification for the configured team member.
They receive post-visit or rebooking communication, where configured.
—
They're referred to a person when needed.
Human handover can create a task when the text/email assistant requires a person. A post-call summary email is configured for admins and a designated address.
—
Staff review call records and handle any follow-up that needs a human.
Channels, kept distinct
- Customer SMS
- Customer-facing email assistant
- Spa-team summary email
- In-app booking notification
- Human-handover task
Each is a separate channel — never combined into one generic "notification," and never shown as an email, in-app alert, or task as an SMS.
How communication can feel to a customer
These are design examples — not the saved AURA workflow templates. Final wording depends on your spa's configuration. No real SMS or email is sent by this walkthrough.
Every example below is labelled Illustrative — final wording depends on the spa's configuration. Review requests are described as a feature requiring the spa's own verified review link and approval; the demo review-request placeholder is not shown as a working link.
Customer SMS
ConfiguredA booking confirmation, sent by Customer SMS. Final wording depends on the spa's configuration.
A pre-visit reminder on the Customer SMS channel.
A post-visit thank-you, where configured.
Customer-facing email assistant
UnverifiedThe email assistant can reply by email from the demo sender identity. Any sample email response is illustrative — actual saved email behavior must not be assumed without verification.
What your team sees, and what to do next
The channels your team may use to stay on top of enquiries — each labelled by its verification status, so you know what's confirmed and what still needs testing.
Customer SMS
Customer-facing confirmation and reminder texts. Wording, consent, and registration are agreed per spa.
Customer-facingCustomer-facing email assistant
A separate channel. The assistant can reply by email from the demo sender identity; exact behavior must be verified per setup.
Customer-facingSpa-team summary email
Post-call summary email, configured for administrators and a designated address. Delivery is not yet confirmed.
Team-facingIn-app booking notification
A booking can surface on the calendar with an in-app notification for the configured team member.
Team-facingHuman-handover task
When the text/email assistant needs a person, a task can be created for the relevant scenario — not fully tested.
Team-facingStaff SMS
Optional staff SMS — not confirmed in the current configuration. A client-specific setup that would require configuration and testing.
Team-facingWhat a team member should do next
These are illustrative previews and prompts — not screenshots of real CRM notes, delivered messages, or staff texts.
What AURA adds to your front desk
Practical, honest benefits — no guaranteed revenue, no zero-missed-calls claims, and no promise that every message is delivered.
A more consistent first point of contact
A more consistent, on-brand first point of contact during configured coverage.
Answers from your approved services & policies
AURA references what you've actually agreed to offer, rather than generic wellness chatter.
Appointment handling that follows your setup
Booking, availability, and consent rules reflect your configuration — not assumptions.
Clearer communication around reservations
Confirmations and reminders on the customer's channel; a paper trail on yours.
Visibility into enquiries
The configured business channels give your team a view of what's coming in.
Human involvement where it belongs
Questions outside AURA's approved scope reach a person, not a guess.
Optional post-visit & membership messaging
Follow-up, rebooking, and membership communication, where you've configured it.
What we don't claim
No guaranteed bookings, zero missed calls, perfect accuracy, or guaranteed SMS delivery. AURA is a configured assistant — it improves consistency and visibility, and routes the rest to your team.
What Zeppelynn and your spa decide together
The actual receptionist experience is configured for each business. One demo configuration does not prove that all client-specific routing or data separation is already implemented.
Service menu, prices & durations
Treatments, packages, and membership terms.
Business hours & booking availability
When you're open and when you take bookings.
Booking mode & calendar
How and when AURA may place a booking.
Transfer number & backup contact
Where a person-specific request should go.
Policies & escalation boundaries
What's approved, and where AURA stops.
Customer SMS wording, consent & registration
What customers can be told, and how you stay compliant.
Review link & rebooking rules
Your own verified review link and rebooking terms.
Team notification recipients & channels
Who hears about what, and on which channel.
Email sender identity
The address customers see on replies.
Test scenarios & client approval
What we'll verify together before going live.
AURA is tuned to each spa's services, hours, policies, and people. A single demo shows the shape of the experience — not a guarantee that every client's routing and data separation is already in place. Those are agreed and verified per business.