If a salon chain books clients in YCLIENTS, a booking system widely used by salons in Russia, while its client base and leads live in amoCRM, a popular Russian sales CRM, the CRM for the chain is best built around YCLIENTS rather than in place of it. Bookings, the till and staff payments stay where they are already set up, and the client system takes booking and visit data from YCLIENTS and builds one card per person. That is how we are doing it for a chain of cosmetology studios - the project is under NDA, so the chain is not named.
Where the duplicate clients come from
The picture in this chain is a common one. Bookings, the till and staff payments are in YCLIENTS. The client base, website leads and messages are in amoCRM. A lead comes in from the website, the booking is made by phone, a question is asked in a messenger. The same client ends up in two systems as two different people, and neither knows the whole story.
For example, the administrator sees in YCLIENTS that a client is booked for a peel on Thursday but does not see that a week ago she asked about a package in a chat. The manager in amoCRM sees the chat but does not know how many treatments are left on the package. The cosmetologist’s recommendations after a treatment sit in the card, and the end of a course is remembered only by chance.
So the first question we ask with a task like this is which program owns which data.
Who owns what: YCLIENTS, the CRM and messengers
We did not replace YCLIENTS. It is the salon’s working tool: bookings, the till and staff payments are set up there. We replaced amoCRM with a system of our own built for cosmetology. From there the rule is simple: each kind of data is entered in one place, and the other programs only read it.
| Data | Entered in | Visible in |
|---|---|---|
| Bookings, till, staff payments | YCLIENTS | YCLIENTS and the client card |
| Packages and what is left on them | YCLIENTS | The client card |
| Leads from the website, social media and messengers | Our system | One pipeline in our system |
| Cosmetologist’s recommendations, messages, calls | Our system | The client card |
Once this is written down, nobody has to argue about which phone number for a client is the right one.
How the YCLIENTS integration with the CRM works
YCLIENTS has an open REST API. Access needs a partner key, issued after registering in the YCLIENTS integrations marketplace, and for some methods a key for the salon’s user as well. Through the API you can get clients, bookings, visits and packages, and when an app is connected a list of addresses is set up where YCLIENTS sends notifications.
For a chain there is one important detail. The API has a separate “network clients” section: a method finds a client by phone number across the whole salon chain, not in one branch. So in our system records are matched by phone. A person who went to two different studios becomes one client with one history.
YCLIENTS returns the client list in pages of at most 200 rows and can sort it by first and last visit date, number of visits and amount spent. This comes in handy later, when we get to the old base.
What ends up in the card:
- Visits - from YCLIENTS, with treatments and staff.
- Packages - how many were bought and how many are left.
- The cosmetologist’s recommendations after a treatment.
- Messages from every channel, and calls.
- Leads from the website, social media and messengers - in one pipeline, not in separate sections.
Booking data reaches the card by itself. The administrator does not copy anything by hand, so a second version of the same client never appears.
Treatment rhythm and winning back lost clients
One card is not there just to keep the base tidy. For a chain, the main gain is repeat visits. Every treatment has a natural rhythm. Facial massage is done weekly as a course, peels as a course and by season, device treatments as a course and then once or twice a year. Before our system, only the administrator and the cosmetologist kept this rhythm in mind, and it often got lost.
We separated two different tasks.
A protocol is a rule for repeating a treatment going forward. It is set once per treatment, and then the system schedules the client’s reminder when the next visit is due.
Reactivation is a pass over the base built up over the years. A large base of past visits brings no repeat sales by itself: nobody was bringing back clients who had drifted away. This is where sorting by last visit date helps: you can see who has not been in for a long time and who finished a course and never came back. Each group gets its own win-back scenario.
The protocol works with people who visit now. Reactivation works with those who have already left. Mix them up, and a regular client gets a “we miss you” message while one who left gets an ordinary reminder about a treatment she stopped having long ago.
Phone integration with the CRM and messaging
The chain had one phone line for all its studios, and it was overloaded, especially in the evening.
The phone integration here works like this: on an incoming call the administrator sees the name, recent visits, package and upcoming booking before picking up. After the call the conversation can continue in WhatsApp or Telegram, and the messages land in the same card rather than on someone’s personal phone.
We deliberately do not put a voice robot on the first line at this stage. Data comes first, automatic replies later.
Loyalty cards in Apple Wallet and Google Wallet in this project run on the same platform as our own product Apex Loop and are linked to the client card and packages from the start.
If your setup looks similar - bookings in one program, clients in another - we build client systems and connect them to YCLIENTS.
What to prepare before the work starts
We start a task like this with a few questions. You can collect the answers in advance, and the conversation will be shorter.
- Which programs you use now. Booking, CRM, spreadsheets, telephony, the messengers clients write in.
- Which one stays the main one for bookings. Usually YCLIENTS: it stays as is, and everything else is connected to it.
- Where packages and courses live today. In the booking program, in a spreadsheet or only in the administrator’s head.
- Which treatments repeat and how often. This is the basis for protocols: weekly, as a course, by season, once or twice a year.
- How many years of base you have. This decides how big reactivation will be and which groups to start with.
Access to YCLIENTS for the integration is given by the salon itself: the user key is obtained by signing in with the salon’s account. Without this step no data reaches the CRM, so it is best done in the first days.
Frequently asked questions
Which CRM should a beauty salon choose if it already uses YCLIENTS?
One that takes booking and visit data from YCLIENTS instead of duplicating the booking calendar. Bookings, the till and staff payments stay in YCLIENTS, and the CRM handles leads, messages, calls and repeat visits.
Can YCLIENTS be integrated with amoCRM instead of building our own system?
It can be connected: YCLIENTS has an open REST API. But if an off-the-shelf CRM does not understand treatment courses, packages and repeat-visit rhythm, these still have to be tracked by hand, which is why in our project amoCRM was replaced with a system built for cosmetology.
Does YCLIENTS integrate with 1C?
1C is the most common accounting software in Russia. The YCLIENTS documentation lists data exchange with an automation and accounting program as one of the typical integration cases, and it works through the same API. What exactly to pass to accounting is decided when we go through the task.
How do you find one client who visited different salons in the chain?
By phone number: the YCLIENTS API has a method that searches for a client by phone across the whole salon chain. That is what one client card in our system is built on.
How much does a CRM for a salon chain cost and how long does it take?
CRM and accounting systems, integrations and loyalty cards start from 150 000 ₽, websites from 50 000 ₽. Any project takes from 1 month. The exact price depends on the task - we name it after going through it.
Who this fits
Chains of beauty salons, cosmetology, massage and medical clinics whose bookings live in YCLIENTS or a similar program while client work is scattered across a CRM, spreadsheets and messengers. Describe in the form below which programs you use now and where clients get lost - we will go through it and tell you what to keep and what to connect.







