PRIVATE OPERATIONS / BOOKINGS
THE CONTROL
ROOM.
Private booking inbox for the PHANTOM team. A request is not a confirmed reservation until a staff member has checked venue capacity and contacted the guest.
AUTHENTICATION REQUIRED
Operator access
Enter the server-side PHANTOM_ADMIN_TOKEN. It is held in this page's memory only and is not written to browser storage.
Incoming requests
Operations health
A read-only diagnostic snapshot. Paths and secret values are intentionally omitted. Backups on this server do not replace off-host disaster-recovery copies.
Unlock the console to inspect runtime health.
Session availability
Inspect how the configured timetable and active request holds affect available capacity. Only confirmed reservations and fresh request holds are counted; this panel does not alter the operating schedule.
Select a date to inspect time slots.
Booking calendar
A week-at-a-glance view of active and historical records. Guest contact details are intentionally excluded. Select an entry to find it in the request register.
Unlock the console to load the booking calendar.
Recent activity
Records creation, status changes and deletions without guest names, contact details or IP addresses.
Unlock the console to load recent activity.
Notification delivery
Booking acknowledgements, confirmations, cancellations and reschedules are queued transactionally. Configure a trusted HTTPS relay for email + SMS, or Resend for direct email delivery; phone notifications stay queued without an SMS relay.
Unlock the console to load the notification outbox.
Privacy note: this panel displays personal contact information submitted for booking requests. Give access only to authorized staff, protect the server and backups, and define a retention/deletion process before launch. Booking records are stored in a local SQLite database, notification events in the same database, and audit events in a separate JSONL file. This is a single-server deployment model, not a serverless/shared multi-instance data architecture.