Salons, spas, beauty lounges and clinics run on relationships. A returning client expects the team to remember her usual stylist, the colour formula from last time, the allergy she mentioned once, and the package she paid for in advance. When that knowledge lives in a notebook, a shared phone and the memory of one receptionist, things slip: double bookings, forgotten preferences, packages nobody can track.
A CRM, a client relationship management system, is meant to fix that. But most generic CRMs are built for sales teams chasing deals, not for a front desk juggling appointments, rooms and staff. Here is what a CRM for this kind of business actually needs, based on building a custom CRM for Enchanté by Remy Daher in 2025 and on the booking and scheduling work behind my other projects.
Start from the front desk
The person who uses the system most is at the reception desk, often with a client in front of her and the phone ringing. Everything should be designed around three questions she answers dozens of times a day:
- Who is this client, and what do we know about her?
- When can we fit her in, and with whom?
- What does she owe, and what has she already paid for?
If the system answers those three questions in a few seconds, the team will use it. If it takes several screens, they will go back to the notebook.
Client profiles
The profile is the heart of the system:
- Name, phone number (the main way clients are found), and preferred language.
- Visit history: date, services, staff member, notes.
- Treatment details: formulas, products used, settings, before and after notes.
- Allergies, sensitivities and any flags the team must see before starting.
- Preferences: favourite staff member, usual times, communication preferences.
- Packages, prepaid balances and outstanding amounts.
Search must work by phone number, partial name and in both Arabic and English spellings, because clients are entered by different people in different ways. Merging duplicate profiles should be easy, because duplicates will happen.
For clinics, some of this information is sensitive. Access should be limited by role, every view and change should be logged, and the data should be protected and backed up properly. See web app security basics.
Appointments and scheduling
Scheduling in a salon or clinic is more complex than a simple calendar:
- Services have durations, and some have gaps: colour processing time, for example, during which the stylist can start another client.
- Staff have skills. Not everyone performs every service.
- Resources are limited. Rooms, chairs and machines can only be used by one client at a time.
- Working hours vary by staff member and by day, with breaks and days off.
A good scheduler shows the day by staff member, makes free slots obvious, and refuses bookings that conflict on staff or resources. Drag and drop to move an appointment saves a lot of time. The same availability logic powers online booking if you add it later, which I discuss in booking apps for service businesses.
Reminders and no-shows
No-shows hurt small businesses directly. Automated reminders by SMS, WhatsApp or email, a day before and a few hours before, are one of the highest-value features. Let clients confirm or ask to reschedule, and record who did not show up so the team can decide on deposits for repeat cases.
Keep the messages short, in the client's preferred language, and editable by the business without a developer.
Packages, memberships and prepaid sessions
Many salons and clinics sell bundles: ten sessions of a treatment, a monthly membership, a gift card. The system must:
- Track how many sessions are left, and deduct them automatically when an appointment is completed.
- Handle expiry dates if the business uses them.
- Show the balance on the client profile and at checkout.
- Keep an audit trail, because disputes about remaining sessions are common.
This is one of the areas where generic tools often fall short and spreadsheets become error-prone quickly.
Checkout and payments
At the end of a visit, the system should produce a clear summary: services, products sold, packages used, discounts, amount due. Record how the client paid, whether cash, card, transfer or a digital wallet, and keep it simple for the team. For the options available to businesses in Lebanon, see accepting payments in your app or website.
Staff and commissions
Many salons pay staff partly on commission. If so, the CRM should calculate it from completed services and product sales, by staff member and period, with rules the owner can adjust. Even without commissions, seeing how busy each staff member is helps with planning.
Reports that the owner actually reads
Keep reporting focused:
- Revenue by day, week and month, by service and by staff member.
- New versus returning clients.
- Clients who have not visited in a while, for a follow-up message.
- Package sales and remaining balances.
- No-show rates.
An export to a spreadsheet covers the rest at first. See what your admin panel needs for the general principles.
Marketing, carefully
A CRM makes it possible to message clients about offers, birthdays or seasonal services. Use it with care: send only to clients who agreed to receive messages, keep it relevant, and make it easy to opt out. A few well-targeted messages beat frequent broadcasts that get the business muted.
Off-the-shelf or custom?
There are many salon and clinic software products. For a business with a standard workflow, one of them may be the right choice. Try a few with real scenarios from your week before deciding.
A custom CRM makes sense when:
- Your workflow does not fit the software: special packages, multiple branches with shared clients, unusual scheduling rules.
- You need Arabic and English done properly, for clients and staff. See bilingual Arabic and English apps.
- You want to connect it to your own booking app or website.
- You want to own your data and not depend on a vendor's pricing or roadmap.
A custom system costs more upfront, so the decision should be based on how much the mismatch is costing you today in time, errors and lost clients.
How I approach a custom CRM
- Shadow the front desk for a day to see the real workflow.
- Agree on the core: profiles, scheduling, checkout, packages, reminders.
- Import existing data from spreadsheets or the old system, cleaned and deduplicated.
- Launch with the team, train them, and adjust quickly based on their feedback.
- Add the rest once the core is used daily: reports, marketing, online booking.
The first version should be small and solid. See how to scope the first version.
Common mistakes
- Choosing software from a demo without testing it on a busy day's real scenarios.
- No search by phone number.
- Packages tracked outside the system.
- Too many required fields, so the team skips the system.
- No backups, or backups nobody has restored.
If your salon, spa or clinic is outgrowing its notebook or its current software, see my work, read about me, and get in touch.