Your spa may be losing opportunities before and after every appointment.
New customers need an answer and a clear path to booking. Existing customers need a reason and an easy opportunity to return. Discover how to address both parts of your spa's customer journey.
One coordinated front desk. Three ways to communicate.
Help customers get answers and find the right next step through voice, text, and email. With supported bilingual handling configured for your spa, AURA can help reduce repetitive enquiry work and make communication more accessible to a wider range of guests.
Not every enquiry is handled automatically, and not every language is supported. The language pair and channel behaviour are confirmed during onboarding — not assumed.
Which of these feels closest to your spa today?
Choose the scenario that sounds most like your day-to-day. Your selection updates the recommendation below — nothing leaves your browser.
AURA AI Front Desk — one coordinated front desk across voice, SMS, and email
A guest is interested in a massage, facial, scalp ritual, or sauna session. They want to know what's available and when they can book — but your team may be with another guest or mid-treatment. AURA is designed to handle routine incoming communication across three connected channels.
Three channels, one coherent process
- 1 · The customer's situation
- A guest calls while your therapist is with another guest. They want to know whether a facial is available on Friday and what your opening hours are.
- 2 · The response AURA is designed to provide
- AURA answers on your configured business number using approved service, hours, and policy information — and, where booking is supported, offers available Friday times.
- 3 · The business record or next action
- The guest's contact details, the call summary, and any appointment are captured through the configured process.
- 4 · What remains the staff's responsibility
- Your team stays with the guest in front of them. AURA transfers to a person only when the matter genuinely needs one.
Channel setup, permissions, exact behaviour, handover, and delivery must be validated before launch — not every channel or action is end-to-end tested.
The Front Desk booking journey
- What the customer experiences
- A guest interested in a massage, facial, scalp ritual, or sauna session calls your business number.
- What AURA does
- AURA answers the call on your configured business number.
- What the spa team sees or needs to do
- No one needs to pick up for a routine question — your team can stay with the guest in front of them.
Customers have an accessible way to ask routine questions across voice, SMS, and email
A structured process for handling incoming enquiries on every channel
A suitable booking path can reduce friction when a guest wants an appointment
Staff can focus on guests and tasks that genuinely need them
Human handover stays available for matters outside the system's role
A record of who reached out and what happened — instead of a missed call or unread thread
When a prospective guest can't get a timely answer or a clear booking path, the spa may not get the chance to convert that interest into an appointment. Not every unanswered enquiry is a lost booking — but a structured response gives more of them a chance.
Booking compatibility and the correct booking method are determined during onboarding — not assumed. Missed-call text-back, a separate after-hours routing system, voice payment collection, voice cancellation/rescheduling, staff text alerts, and universal booking integrations are not currently guaranteed features.
Make it easier for guests to communicate in their preferred supported language.
A guest may call or message in Spanish rather than English. AURA can be configured to handle the approved language pair using your approved service information and policies — so routine enquiries become more accessible without depending on a bilingual employee being free at that moment. Requests needing human judgement, or outside the configured scope, still go to the team.
- The language pair and behaviour are confirmed during onboarding.
- Voice, SMS, and email language behaviour are validated independently.
- No perfect translation, all-language coverage, or unlimited multilingual support is claimed.
- Approved service names, prices, and policies are preserved consistently in both languages.
If the guest confirms, AURA creates the appointment through the configured booking process and sends any confirmations the agreed workflow includes.
Example uses a massage availability question. Confirm the actual English/Spanish language settings and approved configuration before claiming a channel has passed testing — and don't alter the live receptionist prompt or language settings as part of this website task.
Spa Customer Retention System — build a structured process for appropriate repeat-visit opportunities
A guest has completed a treatment. You'd welcome them again — but the next step may depend on staff remembering to follow up, finding the right time, and locating the correct booking link.
The intended Retention flow
An appointment outcome is reliably recorded — the trigger everything depends on.
The system checks customer information, eligibility, communication preferences, and agreed rules.
The configured workflow determines which follow-up is appropriate.
An eligible guest may receive an approved review, rebooking, or lifecycle message.
Responses are handled by the configured assistant or the right member of staff.
Stop conditions, opt-outs, duplicate prevention, and records govern whether communication continues.
Three example journeys
Select a journey to see what it requires and how it behaves.
Journey 1 — Review invitation
Invite an eligible guest to leave a review at the right destination and time.
- Required outcome
- A completed, recorded appointment.
- Approved destination
- The review platform or link you've approved — the real client-specific link is needed before activation.
- Timing
- An agreed window after the visit — not immediate, not weeks later.
- Eligibility
- Only guests whose appointment outcome and preferences qualify.
- Message
- An approved, short invitation the guest can act on or ignore.
- Replies
- Handled by the configured assistant or the right staff member; opt-outs respected.
A more consistent follow-up process
Fewer follow-up tasks left entirely to memory
Clearer visibility of customer status and agreed next actions
An easier route for interested guests to consider another appointment
A defined process for eligibility, message timing, exclusions, and opt-outs
Stop conditions and duplicate prevention govern whether communication continues
Without a structured follow-up process, some suitable opportunities to reconnect with existing customers may simply remain unnoticed. This doesn't promise a specific repeat-booking rate or guaranteed revenue — it gives suitable opportunities a chance to be seen.
Retention requires reliable appointment outcomes, accessible customer data, consent, valid links, and successful testing. Appointment outcome marking may remain a staff responsibility unless the booking integration reliably supplies it. Some retention workflows are untested, incomplete, or dependent on staff actions.
Two different offers with distinct responsibilities
Front Desk helps the customer take the next step. Retention helps the spa create an appropriate next step after the visit.
When does it help?
When someone contacts the spa and wants answers or a booking
After a recorded appointment or another agreed lifecycle trigger
Main objective
Make enquiry handling and booking assistance more structured
Make appropriate post-visit follow-up more consistent
Customer experience
An answer, a booking path, or human handover
A relevant follow-up, rebooking opportunity, or appropriate next step
What starts it?
An incoming call or supported configured interaction
Reliable customer and appointment data plus agreed eligibility rules
What does the spa provide?
Approved business information, booking setup, number and transfer details
Customer and appointment records, consent, approved links, and follow-up rules
What remains human-led?
Exceptions, complaints, judgement, and staff handover
Appointment outcome maintenance where required, replies needing judgement, and exceptions
One system for the first conversation. Another for what happens next.
Voice, SMS, and Email AI help the business manage incoming customer communication when appropriately configured. The Retention System handles separate, agreed post-visit or customer-lifecycle workflows. Shared records and configuration may connect these processes when correctly set up — but a booking or follow-up outcome still depends on the underlying calendar, data, consent, configured workflows, and staff responsibilities.
Appointment
The visit happens. Shared customer and appointment records connect what Front Desk captured to what Retention acts on — provided they're correctly configured.
- Voice, SMS, and Email AI help manage incoming communication across channels
- Retention addresses the consistency of appropriate customer follow-up
- Together they support a more connected journey from first interest to possible repeat business
- Shared customer records and agreed workflows can reduce unnecessary duplication — if correctly configured
- Staff continue to handle matters requiring human judgement
What this combination does not mean
- It does not guarantee bookings, eliminate the need for staff, or make incomplete appointment data reliable on its own.
- You don't need Retention to use the Front Desk — and not every business requires the combined offering. Each system stands on its own agreed scope.
How much time does your team spend answering the same questions?
These everyday front-desk tasks repeat across phone, SMS, and email. Spread across three channels, they interrupt other guest-facing work and can quietly create an inbox backlog.
Answering repeated service and pricing questions
Responding to basic booking enquiries
Repeating opening hours and cancellation policies
Reviewing incoming text conversations
Working through routine email enquiries
Collecting information before a staff member can take over
Manually tracking questions that need a follow-up
How AURA is designed to reduce repetitive work
- Handles appropriate interactions with your approved information across voice, SMS, and email
- Helps customers find a booking path instead of leaving a question unanswered
- Routes suitable exceptions to the team instead of letting them pile up
- Keeps a record of what was asked and what was offered
What it doesn't do
AURA doesn't eliminate every one of these tasks, and not every interaction is automated. Complex questions, judgement, exceptions, and sensitive matters still need a person — the goal is fewer repetitive interruptions, not no staff at all.
Estimate the booking opportunity your current process may be leaving unaddressed.
Rough estimates are fine. These are illustrative planning scenarios — not audited losses, industry benchmarks, profit estimates, or promises of additional revenue. Nothing leaves your browser.
Module A — Front Desk opportunity
Potentially recoverable pre-booking enquiries
Your assumption for planning — not a benchmark or expected systems result.
$0/mo
Assumes the spa has available capacity and a valid booking process. AURA doesn't guarantee that the selected percentage will convert, and this doesn't imply a missed-call text-back feature exists.
Module B — Retention opportunity
Eligible existing customers with no future appointment
Your assumption for planning — not a benchmark or expected systems result.
$0/mo
Outcomes depend on data quality, appointment-status accuracy, customer preferences and consent, appropriate timing, usable booking links, and tested workflows. Don't imply these customers would all otherwise be permanently lost.
Combined illustrative monthly booking-value opportunity
The sum of the two scenario values — valid only when the two customer groups are distinct.
The first group is potentially recoverable pre-booking enquiries. The second is eligible existing customers with no future appointment. Don't include the same customer opportunity in both groups.
These are illustrative scenarios based on your assumptions, not audited losses, profit estimates, forecasts, or guaranteed results. Actual performance depends on service fit, capacity, implementation, data quality, customer behaviour, and the workflows agreed and tested for your business.
A practical six-step path — in plain language
No jargon, no surprises. Here's how a spa goes from "we think we're losing opportunities" to a tested, agreed solution.
- 1
Understand the business
Confirm the problem, service type, operational needs, and readiness before anything is configured.
- 2
Gather the right information
Approved services, prices, hours, policies, booking details, customer records where relevant, links, and consent requirements.
- 3
Design the customer journey
Define the actions, messaging, handovers, eligibility rules, and who's responsible for each step.
- 4
Configure the agreed solution
Prepare the applicable receptionist, calendar approach, CRM foundation, and the relevant workflows.
- 5
Test and approve
Test booking scenarios, messages, handover, opt-outs, stop rules, and any other dependencies before activation.
- 6
Launch and maintain
Agree who keeps information accurate and which monitoring, maintenance, and improvements are included.
Transparent about what's charged — without invented numbers
We won't display fabricated prices here. The written proposal is where exact figures, inclusions, and exclusions belong — agreed before any work begins.
One-time implementation fee
Covers the agreed, client-specific initial setup deliverables — scoped to your spa's services, booking setup, and configuration.
Monthly recurring fee
Covers only the ongoing services included in the agreement — nothing assumed, nothing hidden.
Shared foundation, charged once
Foundation work shared by both systems is charged once — not duplicated simply because you add the second service later.
Additional costs, disclosed and agreed
Any applicable messaging, usage, third-party platform, additional integration, or custom-work charges are disclosed and agreed where relevant — never added silently. The written proposal itemises implementation fees, recurring fees, inclusions, exclusions, and any additional costs.
- Approved business information and receptionist configuration
- Booking method and compatibility confirmed during onboarding
- Number and human-transfer setup
- Customer and appointment record foundations
- Eligibility, timing, and opt-out rules
- Approved links and follow-up workflows, tested before activation
Review-request ownership and the exact commercial packaging of confirmations and reminders remain explicitly subject to the final approved offer definition. We don't invent entitlements, guarantees, or prices — we agree them in writing.
Start with the part of the journey that needs attention most.
You don't have to do everything at once. Pick the part that's costing you the most today — we'll design the rest around it.
What to discuss with Zeppelynn AI
There's no sign-up form here on purpose. When you're ready, talk with us about: which scenario fits your spa, what customer and appointment records you already have, your current booking method, what consent and communication preferences you track, and which follow-ups you'd want tested before activation. We'll turn that into a written proposal with itemised fees, inclusions, and exclusions.