Example demo workflow — not a real customer, and not a guaranteed result. This walkthrough uses an invented salon to show how Saponly would work in practice. Your results depend on your salon, your data, and your clients.
Most of a salon's inbound WhatsApp is a small set of repeating questions — prices, hours, availability, booking. In this example we walk through how a salon could let an AI receptionist handle the bulk of them while the owner stays in control of every booking.
The example salon
Glow Beauty Salon, Dubai (illustrative). A small team: three stylists, a focused menu of hair, keratin, and facials. Like most salons, they get most of their inquiries on WhatsApp and Instagram, all day, every day.
The problem
The same questions, over and over:
- "How much is keratin?"
- "Are you open Friday?"
- "Can I book with Sara tomorrow?"
Replies come late when the team is with clients, some messages get missed at night, and the occasional no-show leaves a chair empty.
The setup
Glow Beauty loads the basics into Saponly once:
- Services & prices — haircut, keratin (with a length-based range), hydra facial.
- Staff — three stylists mapped to the services they do.
- Working hours & holidays — including the Friday afternoon question.
- FAQs — parking, walk-ins, cancellation policy.
What the customer sees
A client messages the salon's normal WhatsApp number:
Client: How much is keratin?Saponly: Keratin at Glow Beauty is AED 600-1,200 depending on hair length, about 3 hours. Want me to check available times? 💛
Client: Are you open Friday?Saponly: Yes - Friday we're open 10:00-20:00. Would you like a slot?
Client: Can I book with Sara tomorrow?Saponly: Sara has tomorrow 2:00 PM open for keratin. Shall I send a request to the salon to confirm?Client: Yes please.Saponly: Booking request sent! The salon will confirm shortly. ✨
What Saponly did
- Answered the price and hours from the salon's real data — no guessing.
- Checked real availability for Sara before proposing a time.
- Captured a booking request and sent it to the owner — it did not auto-confirm.
- Queued reminders for once the owner approves.
- Would hand off to the team if the client asked something sensitive or unusual.
In this example, the repetitive questions are handled without the team typing a thing, while the booking still waits for a human yes. How much of *your* inbound is repetitive is something only your own chat history can tell you — we do not have a measured figure to quote, and we will not invent one.
The owner benefit (in this example)
- Far fewer repeat replies to type.
- Faster responses, even when every chair is full.
- No auto-confirm risk — every booking is approved by a person.
- Reminders that help cut no-shows.
Try it on your salon
This was an example. The honest way to know if it helps *your* salon is to see it on your own services. Watch the demo, see who Saponly is built for, or read what an AI receptionist actually is.
Disclaimer: example demo workflow, not a guaranteed result. Saponly does not claim existing customers or outcomes that haven't happened.