One customer can have many bookings without creating a new customer record each time.
The customer record stores the person or organization's main identity and relationship. Each booking stores its own dates, resources, status, price, participants, and other booking details. The records stay linked.
What Stays on the Customer Record?
The customer record can hold information that remains useful across more than one transaction, such as:
- Name and contact details.
- Organization or account relationship.
- Communication preferences.
- Membership or customer status when relevant.
- Links to related bookings, invoices, payments, requests, or other records.
See Customer Record for the core term.
What Stays on Each Booking?
Each booking needs its own details because each use can be different.
- Date and time.
- Room, space, service, or resource.
- Booking status.
- Price, deposit, or payment details.
- Guests or participants.
- Notes, requests, or special requirements for that booking.
Why Is Linking Better Than Duplicating the Customer?
If the same person is entered as a new customer every time, staff can end up with several versions of the same person, different contact details, and an incomplete history.
A linked model makes it easier to answer questions such as:
- What has this customer booked before?
- What bookings are coming next?
- Which payments or invoices belong to this relationship?
- How often does the customer return?
Salesforce supports relationships between records so one record can be connected to many related records without copying the same information into each one.
What If the Customer Is Not the Guest?
The records can still stay separate and connected. A company may be the customer paying for several bookings while different employees are the guests.
See Customer vs. Guest vs. Member for that distinction.
How Does Booking Ninjas Connect the Records?
Booking Ninjas is built on Salesforce and keeps bookings connected to other operational records. Its Booking Management area centralizes bookings, resources, availability, pricing, and operations.
The exact customer-to-booking structure should match the organization's business model rather than forcing every business into the same record design.
Sources and Further Reading
- Booking Ninjas: Booking Management — explains how bookings are kept with related resources, availability, pricing, and operational data.
- Salesforce Help: Object Relationships Overview — explains how Salesforce links records through relationships instead of duplicating the same data.