Guest access & grounded AI
App-less QR/web entry, approved hotel answers and structured service-request creation.
PILOT CORE
FOUNDING HOTEL PROGRAM
Put the operating loop on a real hotel shift.
A founding pilot is a controlled deployment built to prove how guest intent becomes approved answers or accountable hotel work—before a broad rollout.
PILOT SCOPE
The operating core, configured as one system.
A pilot is implementation work, not a temporary login. Each included workflow is modeled around the property and evaluated with the people expected to use it.
Routing & ownership
Department routing, My Work and accountable acceptance through completion.
PILOT CORE
SLA & escalation
Property service targets, overdue visibility and configured escalation paths.
PILOT CORE
Tasks & checklists
Recurring standards and one-off operational work with attributable execution.
PILOT CORE
Ask OPHOZ
Staff guidance grounded only in published property procedures and policy.
PILOT CORE
Shift continuity
Unresolved requests, tasks, incidents and follow-ups carried into handoff.
PILOT CORE
Management visibility
Operational state, history and launch diagnostics available to authorized leaders.
PILOT CORE
Employee app foundation
Private Android and iOS testing during implementation, subject to real-device acceptance.
ACCEPTANCE REQUIRED
THE HOTEL PROVIDES
Property truth and operating decisions.
- An accountable implementation owner and department leads
- Approved policies, procedures, property facts and guest boundaries
- Real routing, escalation, service-target and shift expectations
- Staff participants and supported test devices for acceptance
OPHOZ CONFIGURES
The system around the hotel.
- Property, room, team, permission and service configuration
- Approved knowledge, guest entry and request-routing paths
- Staff operating views, tasks, handoffs, alerts and diagnostics
- Controlled scenarios, issue resolution and launch-readiness review
IMPLEMENTATION
Four gates between software and guest rollout.
The hotel sees what is configured, what has been evaluated and what still needs external activation or physical-device proof.
Model the property
Configure identity, rooms, departments, routing, service targets and approved hotel knowledge.
Prepare the team
Invite staff, map permissions, define alert preferences and rehearse ownership expectations.
Evaluate the loop
Run guest questions, requests, tasks, SLA, escalation, handoff and device-specific scenarios.
Decide what is ready
Resolve launch blockers and expand guest access only after the hotel accepts the configured workflow.
COMMERCIAL TRUTH
Every capability carries its real release state.
The pilot does not turn an unprovisioned provider or untested device path into a production claim.
- CORE PLATFORMGuest-to-staff operating workflows are available for controlled property configuration and acceptance.
- NATIVE APPSStore distribution, production signing and physical-device push/deep-link acceptance remain release requirements.
- VERIFIED SMSEmployee SMS backup requires separate provider setup and verified enrollment before use.
- VOICEOPHOZ Voice is a separate private pilot requiring telephony provisioning and real-number acceptance testing.
- INTEGRATIONSPMS, CRS, OTA, payments, check-in and enterprise SSO are not represented as connected without a tested property integration.
BOOK A PILOT
Tell us where the operation needs control.
Share the property and the pressure point. OPHOZ will review operating fit before proposing scope or timing.
01 · We review the hotel and operating need02 · We discuss scope, dependencies and pilot fit03 · A written configuration and acceptance plan follows