Open your client list and search for a common first name. The odds are good you'll find the same person two or three times: once as "Jen", once as "Jennifer Tran", once as "Jen T" with a phone number from 2023.
It never feels urgent, because nothing breaks. But every duplicate splits someone's history in two, and the half you can't see is usually the half you need.
How the mess gets in
Different people, different habits. One receptionist types full names, another types first names, a third copies whatever the client wrote on the sign-in sheet.
No lookup before creating. It's faster to add a client than to search for one, so under pressure, people add.
Placeholders. "Walk-in", "Guest", "Unknown", "Mom" — typed into the name field because a booking needed a name and nobody had one. Those records quietly collect visits from dozens of different people.
Mishearings. Names taken over the phone are the least reliable data you hold. A noisy line turns "Joan" into "John", and a name spelled out once is rarely spelled out twice.
A name you weren't told is not a name
The mishearing problem is worse than it looks, and we have the embarrassing examples to prove it.
On one test call to Sonorch's own booking assistant, the caller's answer to "what service would you like?" was transcribed as "For Joe". The system took Joe as the caller's name and created a profile for "Joe" against their real phone number. On another, a caller interrupted with "actually, wait" — which the transcription heard as "Ashley Way" — and the profile was renamed.
Both are fixed: a name that arrives without being asked for now has to be confirmed out loud, and a profile can't be renamed without first reading back the name already on file. But the lesson applies to any desk, human or software: a name you inferred is not a name you have. If you didn't ask, and they didn't confirm, don't record it as fact.
The phone number is the key
Names get spelled differently, shortened, changed after a wedding, and misheard. A mobile number almost always belongs to one person and rarely changes.
That makes the phone number the right thing to match on. Before creating a client, search by number. If the number already exists, it's the same person, whatever name they gave today — update the name if they've corrected it, but don't make a second record.
The exceptions are real and worth knowing: couples sharing a landline, a parent booking a child under their own number, an office manager booking for colleagues. That's when a note on the booking — "booked by Mom" — beats creating a person called Mom.
Why it's worth an afternoon
Duplicates cost you in ways that never appear as a line item:
- Rebooking. "When was your last fill?" has the wrong answer if the last visit is on the other record.
- Preferences. The colour, the shape, the product they react to — noted once, on one of the copies.
- Marketing. The same person gets the birthday text three times, or the "we miss you" text while sitting in the chair.
- No-show rules. If you track no-shows to decide who needs a deposit, a client with three records has three clean slates.
Cleaning up without losing history
- Export the list and sort it by phone number. Duplicates cluster together.
- Merge, don't delete. Whatever your system calls it, you want the visit history and notes to follow into the record you keep. Deleting the spare copy throws its history away.
- Retire the placeholders. "Walk-in" and "Unknown" records have no single person to merge into — leave the old sales where they are and stop using those names from now on.
- Put one rule by the desk: search by phone before creating anyone new.
For a single location it's rarely more than an afternoon, and it makes every decision you base on client history a little more likely to be right.
If no-shows are the reason client records matter in your shop, cutting no-shows without deposits is the next read. In Sonorch, the phone and the register share one client list, keyed on the caller's number.