Clients in chat want prices, masters, free slots, and a booking. The front desk cannot answer around the clock.
The salon CRM is still the only source of truth, and it has no open API. The bot still works with that CRM: it consults, sells, and books without inventing slots outside the journal.

The pain we close
Messages arrive at night and on weekends. While a person catches up, the client has already left for another salon. You cannot plug the usual salon software in through an official API: there is none. You need a digital receptionist in chat that looks at the same CRM the staff uses.
Who it is for
Beauty salons with online booking and masters. Clients in VK and MAX chats. A staff member who joins only when the bot escalates a hard case.
How it works
In chat the bot consults, answers about services and price, suggests add-ons, and takes the client to book, reschedule, or cancel. Schedule and booking facts are checked against the CRM journal. Hard questions go to a human. The client can also get the salon’s official booking link.

Under the hood
With no open API, slots and bookings use a staff session in the CRM cabinet and its internal requests, plus the public service catalog. Roles are split: sales and admin talk via a language model; the booking itself is code without made-up slots. Live channels today: VK and MAX.
Result
Live VK and MAX bots on your own server. The client gets answers and a path to book; the salon keeps the schedule in its CRM even without an open API. The CRM brand and salon names stay off this portfolio page.
