Pulse9: Stay Pilot · Operator workflow
Pulse9: Stay Pilot aims to help lodging teams create more personal guest stays with less manual operational work. Today’s paid-pilot offer starts with guest inquiries, post-stay feedback, and operator-created property follow-up. The broader connected hospitality vision remains proposed or provider-dependent.
Current paid-pilot workflows
The inquiry inbox, feedback review, and property operations require an authorized workspace member and a subscription matched to provider-verified payment. Creating an account or workspace, or saving a property, does not grant paid access. These current workflows do not require a PMS connection.
Guest questions are saved to the selected property’s inbox. Authorized members of a paid workspace can review and export that property’s records, reply, and resolve or reopen inquiries. A reply status reflects whether the email service accepted the send; it does not confirm mailbox delivery.
A property share link collects a guest’s self-reported 1–5 rating and optional comment. The link does not verify a booking. Authorized workspace members can review saved responses and property trends, then create a manual housekeeping or maintenance work item from a response.
Operators can create and manage housekeeping or maintenance work items for the saved property. These are operator-created follow-ups, not automated dispatch or predictive maintenance.
Broader hospitality roadmap · planned
Planned AI guest-profile enrichment would use pre-arrival surveys and historical preferences to help teams prepare a more personal stay.
Future room templates are intended to cover lighting, temperature, wellness choices, and amenity options, subject to smart-room provider access and product capability.
AI housekeeping queues, predictive maintenance dispatching, and night-audit diagnostic reconciliation are planned workflows—not available automations today.
EcoPulse is planned to use real-time API tracking for energy, water, and carbon per room night, support ESG reports, and offer guest green-loyalty rewards after connected data is available.
PMS connectivity goal
Connected PMS workflows remain planned and provider-dependent. They require a real supported integration, provider approval, and authorization for the property; no PMS connection is verified for Stay Pilot. Listed PMS names are roadmap targets only. The roadmap has named Impala API and Channex.io as possible connector targets; neither is represented as a verified integration.
From setup to the monthly rhythm
Guest delivery and reporting are planned. Subscription checkout follows a separate, existing workspace flow; a verified subscription does not make unbuilt hotel workflows live.
Operator accounts, private workspaces, first-property onboarding, and monthly plan selection are available. The existing workspace checkout depends on provider readiness; paid access begins only after provider verification. PMS access is a separate dependency for connected workflows.
The planned guest journey would send a personalized portal 24 hours before check-in through WhatsApp Business API/Twilio SMS, with amenity selection, upsells, and check-in times.
A future automated, white-label PDF is intended for the hotel GM by email, covering direct revenue saved, energy/kWh saved, and efficiency hours gained. These are report topics, not measured results.
Choose a monthly plan, create an account and private workspace, and save a first property before attempting the existing workspace-specific hosted checkout. Payment readiness is unverified; paid access starts only after provider verification. If checkout cannot start, use signup or send an inquiry. PMS access is separate from today’s workflows.