How the customer list is built
Pro only. Every unique email or phone that has ever booked lands as a customer row.
The customer list is a Pro feature. On Starter, bookings still work, but we do not build a persistent customer profile.
What creates a customer row
- A public booking with an email address.
- A walk-in you added to the calendar with an email or phone.
- A row imported from another platform.
We de-duplicate on email, falling back to phone when there is no email. Two bookings with the same email = one customer row.
What is on a customer row
| Field | Source |
|---|---|
| Name | The most recent booking |
| Original booking | |
| Phone | Original booking |
| Total visits | Count of completed bookings |
| Last visit | Most recent completed booking date |
| No-shows | Count of no_show bookings |
| Notes | You add them by hand |
| Tags | You add them by hand |
Two figures that depend on you
Visits counts completed bookings and no-shows counts no_show ones — so both are only as accurate as your habit of closing bookings out at the end of the day. A week of appointments left sitting at confirmed counts as neither. See Booking statuses explained.
How a walk-in becomes a regular
A walk-in entered with just a name creates a booking and no customer row, because there is nothing to match the next visit against. The same person with a phone number becomes a record that their second visit attaches to, and from then on you have their history.
That is the whole argument for asking at the desk.
What is not there
- Spend total. We do not track cash paid in-shop; only deposits taken through Booked are ever seen.
- Product purchases.
- Marketing consent. SMS consent is tracked separately, and it is global rather than per shop.