Keep bookings, sales, installments, memberships, vouchers, wallet movements, forms, notifications, and check-ins tied to one client profile.
The client record should stay usable between visits
Client records the team can actually work from
Keep visit history, notes, purchases, balances, and important context in one profile that reception, specialists, and managers can open without guessing.
Why this matters
The client profile should be the operating hub, not a contact card
When bookings, balances, forms, check-ins, and notes are split across places, every repeat visit starts colder than it should. The team asks again about details it should already know.
Start a booking, sale, membership, form, or check-in from that same profile instead of changing context.
Keep imports, groups, duplicates, merging, export, and online-booking control inside the same client layer.
How the record should work
One profile the team can act from, not just look at
A useful client layer is not only searchable. It lets reception, specialists, and managers open one profile and continue the relationship from there.
- Open one client profile and see the flags, core details, recent stats, and tabs that already shape the next action.
- Use the same profile to review bookings, sales, installments, memberships, vouchers, wallet movements, forms, notifications, and check-ins.
- Move from that profile into a booking, sale, membership sale, voucher sale, manual form, or check-in without losing client context.
- Use import, groups, duplicate search, merging, blocking or restoring online booking, and export to keep the client base workable.
What this record needs
What makes the record useful in real work
A stronger record helps only when it stays practical for the people who have to open it in the middle of the workday.
Client profile, history, and balances
The profile keeps bookings, sales, installments, memberships, vouchers, wallet movements, notes, documents, and recent activity in one place.
Actions that start from the profile
Bookings, sales, membership sales, voucher sales, manual forms, and check-ins can all start from the same client record.
Groups, import, duplicates, and online-booking control
Groups, imports, exports, duplicate cleanup, merging, and block or restore actions keep the client base usable instead of messy.
What improves
Clearer continuity and less forgotten context
The gain is not a fuller profile for its own sake. It is a record that helps the business work with the same client more clearly over time.
Faster orientation before the visit
The team reaches the client with more of the right history, balance, and context already visible.
A more trustworthy client base
Duplicates, missing profiles, and scattered client lists become less of a daily problem.
A stronger base for repeat business
The client record supports the next visit instead of forcing the team to reconstruct it.
FAQ
What teams usually ask about client records
Is this just a contact list?
No. It is the operational client profile: history, bookings, sales, balances, forms, notes, and the actions the team needs between visits.
Does this also include imports, groups, and duplicates?
Yes. Import, export, client groups, duplicate search, and profile merging belong to the same client layer because data quality directly affects daily work.
Does this matter only for reception?
No. It matters for reception, specialists, and managers once the same client context should survive through the whole visit cycle.
Does this replace forms and memberships?
No. It connects to them. The client record is the hub, while forms and memberships solve their own operational problems.