When somebody books a room, books a service, reserves a table or buys from your shop page online, they don't log in — they just type their name, phone number and email. So the system has to work out, on its own, whether this is somebody already in your customer list or a brand new person.
It decides on the phone number. Same number, same customer. Their new booking joins their existing record, so their history stays in one place instead of splitting across a new row every visit.
Before you start
Nothing to set up — this happens automatically on every online booking. It's worth knowing how it behaves, though, because it explains two things you will see in your customer list.
What the customer sees
As soon as they finish typing their phone number, a returning customer gets a small green note under the field:
👋 Welcome back, P… N… — we'll add this to your existing record (…0027). Not you? Check the number above.
Only initials and the last four digits are shown. That's deliberate: these pages are open to anybody on the internet, so a full name would let a stranger type numbers at random and read back your customer list. The initials are enough for the right person to recognise themselves and spot a mistyped number before they pay.
If the note doesn't appear, the number is new to you and a new customer record will be created.
The rules it follows
- The number is compared digit by digit, not character by character.
0816 932 0027,0816-932-0027and+234 816 932 0027are all treated as the same number. Someone typing their number a different way this time will not become a second customer. - One customer on that number → that customer. Their new booking, receipt and folio go onto their existing record.
- Several customers share that number → the name decides. Family phones and office lines are common. If the name they typed matches exactly one of the people on that number, it goes to that person.
- Several customers share the number and the name matches none of them → a NEW customer is created. The system will not guess. This is the important one, and the reason is in the next section.
Why it sometimes makes a duplicate on purpose
Rule 4 looks unhelpful — you asked for one customer and got a second. It's deliberate, and it's the safer of two bad outcomes:
- A duplicate customer is a tidy-up job. You merge or tidy the record when you notice it, and nothing was posted wrongly in the meantime.
- A booking attached to the wrong customer is an accounting problem. Their deposit receipt, their folio and their balance all land on a stranger who happens to share a phone line — and you may not find out until one of them disputes a bill.
So when the number genuinely doesn't identify one person, the system takes the tidy-up job rather than the accounting problem.
Tips
- Encourage staff to record phone numbers consistently when they create customers by hand. The matching copes with different spacing and country codes, but a wrong digit is a different person as far as it can tell.
- A shared phone number is worth splitting. If a husband and wife share a number and both book, give one of them their own number on their record — it will match cleanly from then on.
- The email is refreshed, the name is not. If a returning customer types a new email address, it replaces the old one so their confirmation reaches them. Their registered name is left alone — a hurried booking form shouldn't overwrite the name you have on file.
- A blank email doesn't wipe anything. Leaving the email field empty on a booking leaves whatever is already on the record.
Common problems
"I have two records for the same person." Most likely they booked with two different numbers, or their number appears on somebody else's record too (rule 4). Check both records' phone numbers — if they're the same digits, this was rule 4 protecting you from a mis-attached booking.
"The booking went onto the wrong customer." This happens when two people share a number and the name matched the other person's record. Correct the name or the number on the customer record so future bookings match cleanly, then move the transaction using the normal correction route for that document.
"The 'Welcome back' note didn't show for a customer I know is on file." Three usual reasons: they typed fewer than ten digits (nothing is looked up until then), the number on their record is different from the one they typed, or their number is on more than one record — in which case the note stays silent rather than naming the wrong person.
"A guest complains they were greeted with someone else's initials." Their number matches an existing record. Check that record: it's either a stale entry with the wrong number, or a genuinely shared line. Either way the guest should correct the number in the form before paying.