WorkspaceManagement
Back to all workspaces03 · Management
Guests and arrivals with context
Stay context brings together holder, source and status to prepare an arrival with the information at hand.
Local demo with fictional data. No real bookings, payments, messages or synchronisation.
- Decision
- Check the minimum information before welcoming a guest without duplicating it across tools.
- Result in view
- The team distinguishes a received enquiry from an in-house stay.
What you can inspect
Enough context to understand the decision.
- 01
Lead guest and companions
- 02
Contact details
- 03
Source of the stay
- 04
Status of each guest
How the context moves
How your team would use it.
- 01
The enquiry keeps its context
- 02
The table shows only the needed fields
- 03
The team checks the status
- 04
The arrival keeps its context
Contract and boundary
What you can try today.
Visible in the demoFictitious visual representation; it does not imply live activation.
Observable evidence: Read-only fictitious table with two sample guests, source and status.
Boundary: It creates no profile, reports no traveller, stores no visitor data and sends no communication.
- Guests and arrivals
Related responsibility
Check who must review this screen.
The page shows local evidence; the guide explains the decision, owner and boundary before activation.
Your next step
Open the exact Terrava view or assess the starting plan.
Explore the workspace or find the plan that fits your way of working.