Managing Customer Records

Modified on Mon, 27 Apr at 2:38 PM

Every booking is attached to a customer record. The customer record is the single place where all of a person's bookings, payments, vouchers, notes, and history live. This guide covers finding, editing, and merging customer records.

Finding a customer

Go to Customers from the main menu. The list shows every customer at your tenant; filter it with the search box at the top — matches by name, email, or phone.

Customers list page showing the search box and a table with name, email, phone, last booking, and total spend columns

Click a customer's name to open their record.

The customer record

The profile shows everything Booking Phoenix knows about the customer:

  • Contact details — name, email, phone, address.
  • Bookings — full history, most recent first.
  • Payments — all charges, refunds, and saved cards.
  • Vouchers — issued to or redeemed by them.
  • Notes & alerts — internal notes from staff (see Customer Alerts and Notes).
  • Survey responses — if surveys are enabled.
  • Audit log — every change made to the record, by whom.

Customer record page with the left-side info panel (name, email, phone) and the main tabs for Bookings, Payments, Vouchers, Notes

Editing customer details

  1. Click Edit on the customer record.
  2. Update any fields — name, email, phone, address, marketing consent.
  3. Click Save.

The change is recorded in the audit log, so you can see who updated what and when. All linked bookings continue to reference this customer — you don't need to update them individually.

Duplicate customers

Duplicates happen: a customer books once as "john.smith@gmail.com" and again as "John.Smith@gmail.com", or uses two different email addresses. Each creates a separate record, which splits their booking history.

Booking Phoenix flags likely duplicates at the top of the customers list. Click through to review — matches are based on similar name + phone, or shared email prefix.

Merging customers

When you've identified two records that belong to the same person:

  1. Open the record you want to keep (usually the one with more history).
  2. Click Merge.
  3. Search for and select the duplicate record.
  4. Review the comparison screen — bookings, payments, and vouchers from both sides will move to the kept record.
  5. Click Confirm Merge.

Merge customers screen showing two columns side-by-side with the source and destination records, and counts of bookings/payments/vouchers that will be moved

The duplicate record is deactivated (not deleted) and all its data is reassigned. This is a one-way operation — you cannot un-merge, so double-check before confirming.

Deactivating a customer

If a customer asks to be removed from your system or you have a clear reason to block them from booking, click Deactivate on their record. They can no longer log in, receive marketing emails, or book through the widget using that email. Their historical data stays intact for reporting and compliance.

Marketing consent

The record has a marketing consent toggle reflecting whether the customer has agreed to receive promotional emails. This is set at booking time by a checkbox on the widget and can be updated from the customer record. When a customer unsubscribes from a marketing email, the toggle updates automatically.

Consent state affects which customers appear in marketing exports — only opted-in customers are included. Transactional emails (booking confirmations, reminders) are always sent regardless.

Data export (GDPR / privacy requests)

When a customer asks for a copy of their data or requests deletion, use the export/delete actions on the customer record. Export bundles everything into a downloadable file; delete anonymises the record (we can't physically delete booking history without breaking reports, but we scrub personal details).

Both actions are logged. Keep a copy of the request email in case you need to audit the action later.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article