Calls, reservations, payments and administrator actions share the same security boundaries.
This document explains to hotel managers and technical teams how calls are verified, reservation actions are isolated by hotel, access is restricted and critical actions are recorded.
Security foundation
Incoming calls are verified at the source, linked to the correct hotel by phone number and deduplicated. User access is restricted by hotel membership, role and action permission.
Hotel-level data isolation
Call, guest, reservation, payment, assistant configuration and audit records are isolated by hotel. Users can access only data permitted by their property membership and role.
Call data flow
Call summaries, transcripts and cost data arrive through verified connections. Duplicate external notifications and repeated reservation submissions are blocked by idempotency controls.
Access management
Two-factor authentication is mandatory for platform administrators and optional for hotel managers. Reservation, finance, telephony and assistant settings are controlled by separate role permissions.
Security control points
Call event processing
Auditable workflowThe security whitepaper reflects the product design
This architecture supports security claims with auditable product behavior.