Front desk
Search reservations, prepare check-in, preview checkout, and surface arrival risks.
- Reservation search
- Check-in preview
- Checkout confirmation
The vault plan separates the assistant into PMS domains. Each domain receives only the tool catalog it should see, so the agent can reason with context without crossing into unrelated workflows.
Search reservations, prepare check-in, preview checkout, and surface arrival risks.
Work with room types, room creation, room status changes, and room blocks.
Read folios and prepare payment, refund, void, reversal, and adjustment flows.
Read guest profile context, timeline state, restrictions, and identity/KYC readiness.
Support user invites, role checks, and permission validation inside the hotel scope.
Read OTA snapshots, prepare queues, request approval, execute, and verify changes.

The agent layer detects the user language, preserves room numbers and domain values, normalizes the request into a canonical PMS intent, and answers back in the user's language.
The model can request a tool, but tenant scope, permission, validation, idempotency, execution, and audit stay in Safari.
Agent cards must match the active workflow, so an add-room flow cannot leak unrelated reservation cards.
Agent changes are judged with fixtures, smoke gates, trace signals, and policy regressions rather than prompt feel.
The active plan moves Safari Agent from a helpful chat surface into a durable PMS runtime with language context, domain tools, approval gates, verification, and evals.
Session, state, planner, tool policy, and workspace output.
Cards and payloads stay tied to the active workflow.
Inventory, front desk, billing, guest, admin, and integrations.
Regression fixtures for language, scope, writes, PII, and UI cards.
Ask for an operation, review the prepared plan, approve sensitive work, and keep the resulting trace visible to the hotel team.