Core product rules
Rules that must guide database design, UI, booking logic, payment, services, technology and AI records.
1. SSBookings is the platform engine
The public retail room-rental site is a separate customer-facing domain that lists only buildings and rooms that opt in.
2. One shared booking engine
Resident bookings, public paid bookings, room-panel bookings, AI email bookings, catering orders, video services, call conferencing and transcription records must link to the same booking engine and audit trail.
3. Meeting services are separate orders
Coffee, catering, room setup, IT help, cleaning and building services must be separate service orders linked to a booking, room, building, supplier and payment method.
4. Technology services are sellable add-ons
Video conferencing, Yealink MeetingBar use, phone conferencing, bridge numbers, recording, transcription and AI summaries must be sellable as add-ons, packages, tenant entitlements or managed service plans.
5. Transcripts and meeting records belong to the booking
Authorised booking users must be able to access recordings, transcripts, AI summaries, decisions and action items from the booking site, subject to permission, consent and retention rules.
6. Retail availability is rule based
Buildings and rooms must opt in. Rules include utilisation thresholds, such as only offering public rentals when utilisation is below 80%.
7. Template-driven mobile design
All pages must use shared layouts, shared components and shared CSS. The system must be fully usable on a phone, including camera-first room photo upload and tablet quick ordering.