Customer records
Formulas, allergies, visit history and spend in one record — so the stylist who did not do the last colour still knows what happened.
The problem
The stylist who mixed last time is off today. The formula was written on the back of a card, or not at all. The client is asked to describe a colour they cannot name, and everyone hopes.
A colour that does not match the last one
An allergy discovered during the patch test, not before it
No idea whether a regular is worth a retention call
In practice
Capabilities
Record the mix, developer, timing and result against the visit, not the person. Anyone picking up that client next has the same information the last stylist had.
Allergies, sensitivities and patch-test dates sit at the top of the record and follow the customer onto the ticket, where the person holding the bowl will actually see them.
Visit frequency, lifetime spend, retail attach and the last service — enough to tell a regular from someone drifting away, without building a segmentation engine.
Marketing consent is a dated record with a source, not a checkbox someone remembers ticking. Withdrawing it is equally recorded, and equally dated.
0
Record the whole floor reads from
0
Formulas stored in a stylist’s memory
0%
Of consent changes dated and sourced
0
Safety fields surfaced on every ticket
The flow
Create the record at the door with the essentials — name, contact, and any safety notes.
The formula, timing and result are recorded against the line as the work happens.
Whoever takes the chair opens the history and starts from what worked, not from a description.
The last-seen date makes it obvious who is worth a call before they become someone else’s regular.
Questions
Anyone with the customer read permission for that branch. Safety notes are deliberately visible to the whole floor — a formula is useless if the person holding the bowl cannot read it.
Keep reading
Set up in an afternoon. Cancel whenever.