One record per person, everything that happened to them attached to it, and a login so they can look it up without calling you.
Salyntra keeps one record per client: contact details, birthday, tags, preferences, who referred them, and every appointment, payment and loyalty movement attached to it. Staff add notes and photos to that record as they work. Clients get their own login to see their history, their points balance and their upcoming visits, and to correct their own details — which is the part that stops your front desk being the only route to information the client already owns.
Enough to recognise somebody and to serve them the way they were served last time.
Two phone numbers rather than one, because the same person often signs up on a mobile and books on a landline — and the duplicate-merge flow needs to see both before it can safely join the records.
Onto a notes timeline on the client, added by whichever staff member wrote them, kept in date order rather than overwriting one another. A formula from March is still there in September when the client asks for "the same as last time".
Notes are per-branch. If you run more than one location and share a client list between them, the shared record does NOT share its notes: what your Lekki stylist wrote about a client stays with Lekki. That is deliberate, and it is enforced by the way notes are stored rather than by a setting someone can get wrong.
Yes, by CSV — clients, and also past appointments, products, sales and expenses.
Every import is recorded as a batch you can roll back. That matters more than it sounds: the reason people put off migrating is not the import, it is the fear of a bad import they cannot undo. If the column mapping was wrong, you reverse the batch and try again.
Sign in and answer their own questions, rather than ringing the salon to ask them.
No. The public booking page takes a walk-in or a first-time client with no account at all, and a barbershop can take a booking with no name attached to it.
The portal is for the clients who want it. A record exists either way — the account is a way into a record that is already there, not a precondition for having one.
Everyone at the same branch sees the same notes on a client. Across branches they differ: notes carry the branch that wrote them, so sharing a client list between locations shares the person and their loyalty balance, not what each location privately recorded about them.
You get duplicates, which is why every import is a reversible batch — roll the second one back. Salyntra also has a merge flow for duplicates that arrive the ordinary way, where somebody books under a second phone number.
A client can correct their details from the portal. Deletion goes through the salon, because the salon is the data controller for its own client list — see the privacy policy for what deletion actually removes and what is kept for tax purposes.
A public page your clients can book from, and a calendar your front desk can actually work in.
PaymentsBank transfer is a first-class payment method here, not an afterthought bolted on beside cards.
Payroll & commissionEvery appointment already knows who performed it and what it earned. Payroll should not need re-entering.
InventoryBack-bar product leaves the shelf during services, not at the till. Your stock count should know that.
Live chatEvery conversation about a booking, a colour or a change of plan in one place, next to the client record it belongs to.
LoyaltyPoints, tiers and bonuses, with caps and expiry so the liability does not quietly outgrow the salon.
ReportsWhere the money came from, which stylists are carrying the week, who has stopped coming back, and what is sitting on the shelf.
Multi-branchSwitch between branches without signing out, decide whether they share a client list, and move stock between them.
Thirty days, every feature, no card. Import your clients and services and judge it against how you actually work.