Operational occupancy context
A view of changing room-use patterns, material differences from configured expectations and context alongside other monitored signals.
StayControl combines available network observations with room-condition signals to provide a privacy-sensitive occupancy estimate, giving hospitality teams useful context for review without identifying guests.
Occupancy monitoring is often expected to produce a precise number. StayControl instead interprets several available signals to show patterns and material differences that may warrant review.
A view of changing room-use patterns, material differences from configured expectations and context alongside other monitored signals.
It does not identify who entered or stayed overnight, prove a rule violation or establish fire-code compliance.
StayControl uses no cameras or facial recognition and does not identify guests from the occupancy estimate. The estimate describes room-use context, not a named person's movements.
StayControl combines available router/IP observations with noise, temperature and humidity readings, then applies contextual correction to produce an occupancy estimate.
Available router/IP observations
Room sound context
Room temperature
Relative humidity
No single input determines the estimate on its own.
Operational context for review
Occupancy estimation depends on useful router/IP visibility in the property's network environment. What is available can vary by router and setup, so monitoring availability and update timing can differ between properties.
Compare the occupancy estimate with what the operation expects, then decide whether a material difference deserves review.
Configured operating context and, where supported, relevant reservation or stay data can help the team understand what it expects at that point in the stay.
Not proof of a violation
StayControl provides an occupancy estimate based on the signals available in the room and network environment.
Reservation data may add context where a supported provider exposes the relevant fields and the setup has the required permissions. A PMS guest count or booking record is not live proof of physical presence, does not establish who is in the room, and a mismatch is not proof of unauthorized guests.
The occupancy estimate remains elevated relative to the property's configured expectations, giving the team a reason to review the stay and room context.
The observed estimate looks different from the context expected for that stage of the stay. The difference is a prompt to investigate, not a conclusion.
Occupancy context can be reviewed alongside an elevated noise condition or another available StayControl signal. One signal does not turn the other into proof.
A property manager can review occupancy context across rooms or properties without installing cameras or claiming to identify individual guests.
StayControl provides the occupancy estimate and can alert the team when configured conditions are met. The team can review the available history before deciding whether any follow-up is needed.
Review the estimate, history and other available room signals before deciding whether follow-up is warranted.
Use connected reservation context where available.
View integrationsStayAssist can contact the guest or team by voice or message, with optional waits, retries or rechecks where configured. It does not guarantee contact or resolution.
Explore StayAssistDifferent purposes. StayControl estimates occupancy context for operational review. StayEco uses radar presence for compatible AC automation. Neither provides an exact guest count.
How the estimate works, where reservation context fits and what the property needs for monitoring.
No. StayControl provides an occupancy estimate based on available network and room-condition signals. It is intended to show operational context and patterns, not a certified exact headcount.
No. StayControl estimates occupancy without cameras, facial recognition or individual guest identification. It does not say who is present or track a named person.
StayControl combines available router/IP observations with noise, temperature and humidity readings. The inputs are interpreted together and no single signal should be treated as a person count.
Yes, where a supported integration provides relevant reservation or stay data. Availability depends on the provider, API fields, permissions and setup. Booking information can add context, but it is not live proof of who is physically present.
A material or sustained difference can prompt the team to review the room, stay and other available monitoring context. It does not prove unauthorized occupancy, identity or a rule violation.
No. StayControl combines network and room-condition signals into operational occupancy context. StayEco uses radar presence for compatible AC automation. They serve different purposes, and neither is an exact guest counter.
StayControl needs mains power and Wi-Fi. Occupancy estimation also depends on useful router/IP visibility in the property's network environment, which varies by router and setup. Remote monitoring and review require platform connectivity, and update timing can vary between properties.
See how StayControl can help your team review room-use patterns, expected operating context and related monitoring signals without cameras or exact headcounts.