Salons don't lose regulars in one dramatic moment — a six-week client stretches to nine, then to a lapse nobody logged. The diary shows the result two months later as a quiet week. This is the run a salon hands Datify first, shown with sample numbers from a four-chair archetype.
The situation
The salon knows its regulars by name, but nobody has time to notice that a name is overdue — noticing is exactly the kind of always-on attention a human front desk can't spare and software can.
The ask is delicate: a lapsed regular should get a warm nudge from the salon, not a campaign blast.
The instruction, verbatim
“Invite back anyone overdue their usual visit. Their usual stylist, real slots, no discounts unless I approve one.”
One sentence, typed by the owner, with the rules already standing:
The plan it came back with
Each invitation named the client's usual stylist and offered their usual day where the diary allowed it. The owner read every draft in the plan — then approved the lot in one tap.
What actually happened
Thirty-one regulars back on the books, most into the exact quiet week the owner was dreading. No discounts were needed, so none were offered — the rule held because it's enforced in code, not remembered under pressure.
What changed
The overdue check now runs weekly: the moment a regular drifts past their window, they're on the next plan. The quiet week stopped being a surprise because the drift is answered while it's still one client, not a trend.
Sector story: the workflow above is the real product loop; the figures are representative sample numbers, not a named client's results.
One instruction, a plan read before it ran, and a ledger that never rounds up. 31 regulars rebooked — and the same loop runs again next month without being asked twice.