Stay statuses and repeat stays

Stay status is a factual operational value, not a prediction based only on dates.

The four statuses

• Upcoming means the visit has not been checked in. It can appear in Arriving today or Arriving soon according to Arrival.
• Checked in means the Guest is currently treated as in house. It appears in Currently in house and, according to Departure, in Departing today, Departing soon or Departure passed.
• Checked out means the visit is complete. It leaves the active operational groups and may satisfy a checkout-anchored Automation.
• Cancelled means the visit will not proceed. It is excluded from active arrival/departure work and should not be used as a substitute for deleting incorrect test data.

From the left sidebar, select Stays, select the relevant Stay and then select the Edit Stay button to make a truthful change. Dates do not silently update status. If a Checked in Stay has a past Departure, either mark it Checked out if the Guest left or extend Departure. ELUNIA never makes that decision automatically.

Automations and authority

Automation eligibility uses the saved status, dates and configured anchor. Marking a Stay Checked out after its checkout-based timing is due can make it immediately eligible for evaluation. This does not bypass contact, Survey, entitlement, suppression or exactly-once checks.

For a Stay backed by an external reservation, an active connection and active mapping make the provider authoritative. Correct it at the provider. When the connection or mapping is inactive or disconnected, manual ELUNIA lifecycle assistance applies again.

Record a repeat Stay

From the left sidebar, select Guests, search for and select the known Guest, then select the control to add a Stay. Each visit remains a separate Stay in Guest Journey, with its own dates, status, Unit, invitations and feedback.

ELUNIA does not infer identity from names, phone numbers or similar details. Confirm the person before attaching a repeat Stay. If uncertain, preserve separate canonical records rather than merging histories unsafely.

If operational groups look wrong, check the Property timezone, saved dates and status. If a provider-managed value returns after an edit, verify the integration state and correct the authoritative source.