Haven Intelligence

Haven Intelligence turns hotel records into sourced briefs, explanations, recommendations, and action proposals. It is approval-first: a model never checks in a guest, changes a room, alters a rate, posts a charge, creates a dispute, or mutates a financial record by itself.

Start a shift with the Command Brief

1. Open Haven Intelligence from the hotel navigation.
2. Select Refresh command brief. The application calculates arrivals, departures, dirty or blocked rooms, maintenance work, and open leakage alerts.
3. Read the freshness time, evidence count, provider, confidence, and warnings before acting.
4. Open source records from the operational module. Treat the brief as a prioritized guide, not a replacement for the room rack, reservation, folio, or task record.
5. Review proposed actions in the approval queue. Approval records your decision; the underlying action still follows its normal authorized workflow.

Ten integrated capabilities

Configure the provider

The platform-managed provider is used by default and consumes plan credits. Eligible hotels may enable BYOK. HavenSuite encrypts the hotel key and never displays it again.

Enable capabilities safely

1. As Hotel Owner, open the Governance tab.
2. Enable one feature for an internal or beta hotel. Keep it disabled for other hotels until its acceptance tests pass.
3. Room-condition vision requires a separate explicit opt-in. Enabling general AI does not enable vision.
4. Approve only hotel-authored knowledge documents that are accurate, current, and suitable for guests.
5. Review usage, failure warnings, feedback, and audit logs before expanding rollout.

Create a Guest Concierge link

1. Open an authenticated reservation and create its secure concierge link.
2. Send the link through the configured notification channel. WhatsApp, SMS, email, and QR carry the secure link; they do not host independent AI conversations.
3. The guest accepts the privacy notice. The session is scoped to that reservation and expires after 24 hours.
4. Information answers cite approved hotel context. Housekeeping, maintenance, or service requests show a separate confirmation action.
5. If the answer is uncertain or the guest asks for a person, use human handoff. The transcript remains available to staff.
6. Resending creates a new token and expires the old session.

Review room-condition vision

Vision is available only after Owner opt-in and only from private room-condition evidence. HavenSuite re-encodes images to JPEG, strips metadata, limits dimensions, stores a SHA-256 hash, and records exactly which processed evidence was included in a run.

Ask a report question

Ask questions such as “show arrivals and occupied rooms today” or “show room revenue this week.” HavenSuite normalizes the request into an allowlisted report, metrics, dimensions, filters, date range, grouping, sort, and visualization. The schema is permission checked, executed through application query services, and stored with the source snapshot. Model-generated SQL is never executed.

Review an action proposal

1. Open Review queue and inspect the feature, evidence, risk, arguments, and freshness.
2. Select Approve only if you have the required granular permission and the source records still support the proposal.
3. Approval does not silently mutate the hotel. Continue through the existing application action, such as room assignment, ticket creation, rate approval, or guest request handling.
4. Dismiss unsuitable proposals with a meaningful reason. Decisions remain attached to the run and audit log.

Queue, schedule, and retention

php artisan queue:work --sleep=3 --tries=3 --timeout=120
php artisan hotel:haven-briefs
php artisan hotel:haven-retention
php artisan schedule:list

Command briefs run at opening, shift change, and pre-night-audit times. Vision and other long tasks use unique queued jobs with retries. Retention expires guest sessions, deletes expired processed vision copies, and purges expired intelligence runs. Owners can export hotel intelligence records from Governance.

When intelligence is unavailable

• Read the unavailable or deterministic-fallback message; do not repeatedly submit the same action.
• Continue using Front Desk, Room Rack, Housekeeping, Maintenance, Rates, Folios, and Reports normally.
• Check feature policy, plan eligibility, remaining credits, queue worker, provider configuration, and network health.
• Never paste provider keys into support messages, screenshots, prompts, or documentation.
• Review the AI audit run for error class, latency, schema version, input hash, and provider without exposing secret or unnecessary guest data.

Privacy and security checklist

• Keep vision off until the Owner accepts the evidence-processing policy.
• Approve only guest-safe knowledge documents.
• Use named accounts and granular AI permissions.
• Review provider data retention and processing terms before production use.
• Use export and deletion tools to meet the hotel retention policy.
• Keep payment card details, identity document numbers, credentials, and unrelated PII out of prompts.

Operational rule: evidence first, recommendation second, authorization third, normal application service last.