Updated 2026-08-11 · 5 min read
When a salon owner starts thinking about an AI assistant, the same two questions always come up. And they're exactly the right ones:
- Is it going to double-book my calendar?
- What happens when a client needs to speak to a person?
They aren't fussiness: they're the two failures that ruin an assistant. The first sits two clients in the same chair; the second leaves somebody talking to a machine that doesn't understand her, which is the fastest way to lose a long-standing client. Let's take both, with what you should demand of anybody — us included — and the specific test you can run in a demo.
Failure 1 · The calendar that double-books
The root of it is that a service isn't ONE duration. A colour is fifteen minutes of application, forty of processing while the colour develops, and twenty to finish. If the assistant books «colour = 75 minutes of chair occupied», it's blocking the stylist for the forty minutes she isn't touching anybody. That's the expensive, silent mistake: it doesn't look like a double booking, it looks like a calendar that doesn't stretch and a week that doesn't add up.
And then there's the noisy one, the real one: if the system saves «60 minutes» because that's the service's base duration, and that day the client has long hair and it takes ninety, the next appointment gets eaten. That's two people and one chair.
What to demand of anybody:
- That a service can be split into bands — work, wait, work — and that another quick client fits inside the wait. That's the difference between five and seven clients in a morning.
- That the same service can have different durations (short or long hair, with nail art) and that the assistant asks which one before booking, instead of getting it right by luck one time in three.
- That a first visit carries extra margin: nobody knows how long her hair will take the first time.
- And the one nobody asks for: that somebody raises a flag if an appointment comes out shorter than that service needs. Getting it right isn't enough; it has to show the day it gets it wrong.
How we solve it. ClaudIA's calendar works in bands: the colour's processing time stays free for another client and the stylist isn't left standing. Each service can have its variants with their own duration and price, and the assistant asks which one before booking. New clients get margin. And there's a watchdog that goes through the day's appointments and flags any that's shorter than the shortest band of its service — because a calendar that gets it wrong quietly is worse than one that gets it wrong loudly. We cover variable timings in detail in colour, highlights and timings that aren't fixed.
What you do have to do, and it's only fair to say so: write down the real timings of your services, band by band. Half an hour of work, once. If a provider doesn't ask you for them when you sign up, that isn't them being easier to set up: it's them booking blind.
Failure 2 · The conversation nobody picks up
The bot's bad name has a shape: the loop. The client asks something the assistant doesn't know, the assistant answers something else, the client rephrases it, and on until she gives up. What you lose there isn't a message: it's a client who won't write again.
What to demand of anybody:
- That when it doesn't know, it steps aside. No insisting, no repeating the menu, no improvising an answer.
- That the alert reaches you, on your phone, with who it is, her number and what she wanted. An alert sitting in a panel you'll open this evening isn't an alert: it's an archive.
- The question almost nobody asks: that when you step in, the assistant goes quiet in that chat. If it keeps writing while you write, the client gets two voices and trusts neither.
- And that it doesn't come back on its own. If you've taken that conversation, it's yours until you hand it back.
How we solve it. When ClaudIA can't resolve something — a complicated change of look, a complaint, anything that needs judgement — she steps aside and tells you on WhatsApp, with the name, the number and the reason. If you reply from your own phone, ClaudIA pauses herself in that chat and doesn't come back until you press «Reactivate». The conversation stays flagged in the panel so nobody skips it.
The demo test: ask it something it can't resolve and watch two things — whether the alert reaches your phone, and whether it goes quiet when you reply.
And the third failure, that almost nobody asks about
What happens when it breaks. Because all software breaks; the difference is whether you find out.
An assistant that falls over quietly is worse than no assistant: you think you're covering the phone and you aren't. The call comes in, nobody takes it, and you discover it a week later through a client who complains. Demand a log where you can see every call and every conversation with what actually happened, and alerts when something breaks. We have it because we needed it ourselves first.
If you take one thing away, make it this: don't ask what an assistant can do. Ask what it does when it doesn't know, and what it blocks in your calendar. Those two answers settle almost everything else.