Add your first Guest and Stay

A Guest represents the person. A Stay represents one visit by that person at one Property. Keep them separate: a returning guest should normally keep one Guest record and gain another Stay.

Add the Guest

From the left sidebar, select the Guests menu. Then select the Add guest button. Open the Property field, choose an accessible Property and enter the required first and last name. Email, phone, preferred communication language, country and internal notes are optional.

Add a valid email before sending a survey email. The property communication policy and explicit workflow overrides determine delivery requirements. In preferred-language mode, unknown preferences require the configured fallback; a missing known-language translation requires attention rather than an assumed English fallback. Marketing permission is an advanced record for promotional contact and does not control ordinary survey or stay-related messages. ELUNIA does not run marketing campaigns from this setting.

After saving, the Guest page opens. Users other than viewers can usually create or edit Guest data; access remains limited to their Business and assigned Properties.

Add the Stay

From the Guest page or Stays, choose Add Stay and select the Guest. The Stay automatically belongs to that Guest’s Property.

• Room / accommodation unit is optional and must be an active Unit in the same Property.
• Check-in and Check-out are required; checkout cannot be before check-in.
• Status is required: Upcoming, Checked in, Checked out or Cancelled.
• Source, Reference and Notes are optional. Source describes where the reservation information came from. Reference can hold the identifier your team uses to find it.

Example: create guest Sofia Martin for Seaside House, then add a Stay in Unit 204 from 12 to 15 September with status Upcoming and the hotel’s booking reference. On arrival, a permitted operator changes the status to Checked in; after departure, the operator confirms Checked out.

Keep the lifecycle accurate

The Stays page groups Upcoming arrivals for today and the next three days, all Checked-in guests, departures for today and the next three days, and Checked-in stays whose Property-local departure date has passed. A Stay can appear in more than one relevant group, such as In house and Departing today.

For a manual or ELUNIA-managed Stay, review the record and either extend an incorrect departure date or confirm checkout. ELUNIA never changes the status merely because a date passed. The optional departure reminder is one staff summary for eligible manual stays, not a guest message.

If a Stay is backed by an active integration connection and active Property mapping, it is integration-managed. Its provider remains authoritative for dates and status; ELUNIA shows the contradiction but must not silently override it. Source or Reference text alone does not make a Stay integration-managed.

Accurate checkout matters because post-stay sending depends on canonical Stay state. ELUNIA does not infer arrival, departure, Unit or reservation identity from incomplete information.

Next: Create and send your first Survey.

New manual Upcoming stays must start today or later in the property timezone. Past dates are disabled/rejected for that creation path. This does not prevent historical/imported stays or rewrite existing dates.