A salon has one automatable problem worth money: the booking that arrives while every pair of hands in the building is busy. Colour takes two hours, and nobody stops mid-application to answer a phone. A chatbot answers instead — takes the service, the stylist preference and the date, and either books it or puts it in front of reception the moment there is a gap.
What does it actually handle?
- Bookings and rebookings, including at 21:00 when somebody finally looks at their diary.
- Price questions, answered from your own price list rather than guessed — cut, colour, balayage, treatments, and what a consultation costs.
- "How long will it take?", which is the question that decides whether somebody books at all.
- Stylist availability, when a client will only see one person.
- Reminders, on the schedule you set, which is where the no-show money actually is.
- The practical ones — parking, whether you take card, whether children are welcome, whether you do extensions.
Where is the money, really?
In two places, and it is worth being honest about which is bigger.
The first is the after-hours booking. Salons are busiest at exactly the hours their clients are free to phone, so the phone rings when nobody can answer it. Every one of those calls is somebody who wanted to give you money.
The second is the no-show. A two-hour colour slot that empties on the morning is very hard to refill, and the reminder that prevents it currently depends on somebody at the desk having a spare five minutes. A system does not have busy days. That is the whole difference — not cleverness, consistency.
| Now | With a chatbot | |
|---|---|---|
| Booking at 20:30 | Voicemail, or nothing | Answered and taken |
| Price question mid-service | Client waits or leaves | Answered from your list |
| Reminder before a colour slot | When somebody remembers | Every time, on schedule |
| A complaint about a colour | Person | Person — the bot hands over |
| Cost | Front-desk time | R299/month |
What does it cost a salon?
A single salon is a Starter build: R299 a month plus a R250 once-off setup fee — R549 at checkout, then R299 a month, cancellable at the end of any paid month. A multi-chair salon with several stylists' diaries and a treatment menu that needs logic usually lands on Intermediate at R649 a month.
If you want the bot writing directly into the diary rather than sending a request to reception, that is our booking system, which starts at R1 299 a month and handles reminders as part of the build.
What should a salon bot never do?
Two things. It must never promise a result — a colour correction is a judgement a stylist makes with the hair in front of her, and a bot that says "yes, we can take you from black to ash blonde in one session" creates an argument for somebody else to have. And it must never handle a complaint. Anything with a temperature goes to a person straight away, with the conversation attached so the client does not have to repeat it.
The salon phone rings hardest at exactly the hours nobody can pick it up. That is not a staffing problem — it is the shape of the business — and it is the one thing software genuinely fixes.
Is it worth it for a small salon?
Do the arithmetic with your own numbers rather than ours. Take the value of one colour appointment. If the monthly fee is less than that, the bot needs to save you one booking a month to break even. Most salons know roughly how many calls go unanswered on a Saturday; if that number is zero, keep your money.
Where we do this
The same build runs for businesses in Ekurhuleni, Witbank and Kimberley, and the city pages set out what changes locally — the languages, the trading hours and the sectors that dominate. Everything is deployed and supported remotely from Vanderbijlpark.