Automation timing

Automation timing combines an anchor, direction, offset and Property-local time. From the left sidebar, select Automations, select the New automation or Edit button, and review the Live sending summary.

Anchors and directions

• Booking created uses the time the Stay record was created. It supports Before, At and After, although Before can calculate a time earlier than ELUNIA first knew the Stay.
• Check-in uses Arrival at Property local time.
• Check-out uses Departure at Property local time and requires a Checked out Stay before processing.
• Before subtracts the offset; At uses the anchor without an offset; After adds it.
• How long? accepts 0–365 and Minutes, hours, or days chooses the unit.

All calendar calculations use the Property timezone. “One day before Check-in at 11:00” means 11:00 on the previous local calendar day. “Two hours after Check-out” means two hours after the local Departure anchor. “After Check-in by 1 day” appears at the configured local time on the second day of the Stay, subject to minimum nights.

Execution time

ELUNIA evaluates Automations every five minutes. A rule calculated for 11:00 normally becomes eligible on the first successful run at or after 11:00; do not promise delivery at exactly 11:00. Queue and provider processing add separate time.

A due initial stage is not proof that a Communication was queued. Eligibility, templates, sending mode, entitlement and contact checks still apply. Editing timing affects future evaluation but does not rewrite existing occurrence timestamps or sent messages.

If timing looks wrong, confirm the Property timezone, Stay creation/Arrival/Departure values, status, direction, offset and minimum nights. A PMS synchronization changes canonical Stay facts; it does not execute the Automation itself.

Guided setup and pre-arrival

The three touchpoints are Pre-arrival, During the stay and After checkout. Pre-arrival rules use timing before check-in; reminder and delayed delivery remain subject to pre-arrival eligibility. New setup workflows inherit property language settings unless explicitly overridden; usable canonical content does not require a tenant publication. New-account Step 6 stages configuration; only explicit Go live activates planned rules. Existing live rules require explicit changes. Starter, including its trial, does not include Automations. See Prepare your property.