Bookings · Booking Desk
Give every customer engagement a controlled commercial state.
A booking is hard to trust when confirmation, advances, balances and cancellations live in separate records.
This is a capability inside Lightning Pharos, not a separate product.
Create or confirm a dated customer booking.
01 · What ships
The complete working surface.
Dated customer engagements with a controlled commercial state.
- 01
CRM-linked bookings with inquiry, confirmed, completed, and cancelled states
- 02
Fees, advances, balances, refunds, and block dates held on the booking
- 03
Availability checks with refusal when the requested period is already booked
- 04
The booking stays attached to the customer record and its commercial history
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Create or confirm a dated customer booking.
- 02 / 03
Governed event
Pharos refuses a conflicting period and records the fee, advance and balance.
- 03 / 03
Connected result
Completion, cancellation and refund history stay with the same CRM-linked booking.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
Bookings does not yet provide a service catalogue, staff qualification or assignment, shift-based capacity, a time-slot engine, or a no-show state.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.