Online Booking for Studios, Salons and Cafés: Where Requests Get Lost and How to Win Them Back
September 23, 2026
In short. Studios, salons, cafés and small hotels lose revenue not for lack of demand but between channels: a request arrives at night in WhatsApp, a slot is sold twice, a client does not show up, payments are reconciled by hand, a regular is not recognised. A booking system closes these gaps when bookings account for real resources, send visit reminders, accept Kaspi payments and keep the client's history.
Five places where revenue leaks
| Stage | Loss | What fixes it |
|---|---|---|
| Request | Nobody answers at night | An AI assistant in WhatsApp and Instagram replies around the clock |
| Booking | Double bookings and idle rooms | Booking that accounts for rooms, equipment and staff |
| Visit | The client does not show up | Reminders before the visit |
| Payment | Manual reconciliation | Kaspi Pay and payment tracking in the same system |
| Return | A regular client is not recognised | A CRM with visit history, bonuses and loyalty tiers |
Booking by resource, not just by time
A slot is not only a time but a specific room, equipment and specialist. If the system knows the second room is taken and the right specialist is on leave, the slot cannot be sold twice. That is how Envy works — a platform for managing photo, video and podcast studios created by the 105 team.
AI assistants in messengers: the value and the limit
- It can: answer frequent questions from the knowledge base, understand voice messages and photos of receipts, remind clients of visits and collect reviews.
- It should not: promise what is not in the knowledge base or argue with clients — difficult cases go to an operator in a shared inbox.
One dashboard for every branch
When bookings, the till, shifts, payroll and analytics live in one system, the owner sees occupancy and revenue for each branch without spreadsheets. In Envy these are separate modules: a loyalty CRM, finance and payroll, equipment tracking, a POS for the studio café and branch analytics.
Where to start
- Review — 1–2 weeks. Request channels, resources, how bookings are handled today and where clients drop off.
- Prototype — 2–4 weeks. Booking for one branch with reminders and payment.
- Connect the rest — CRM, till, shifts, AI assistant — in iterations.
Sources
This material was prepared with AI from the sources listed above. Spotted an inaccuracy? Write to info@105.kz.