Create an Automation

Create an Automation only after the Property, active Survey and Guest message templates are ready. You need Automation create/update permission, access to the Property and an account plan that includes Automations.

Complete the form

From the left sidebar, select Automations, then select the New automation button. The current form contains:

• Name — required operator-facing name.
• Property — required scope. Only accessible Properties appear.
• When should timing start? — required anchor: Booking created, Check-in or Check-out.
• Survey — required active Survey belonging to that Property.
• Send before, at, or after? — required direction. Before and After reveal How long? and Minutes, hours, or days; the offset is 0–365. At stores a zero-minute offset.
• Property local time — required HH:MM time used for Check-in/Check-out calendar anchors in the Property timezone.
• Only for stays of at least — required minimum of 1 and maximum of 30 nights.
• Delivery language — Use property language settings — Recommended, or an explicit override: Automatically choose for each guest with safe fallback, or Always send in a specific language selected from usable canonical or reviewed/published content.
• Send one reminder — optional. When selected, it schedules one reminder on the following day; no repeating series exists.
• Active — allows processing when all other gates pass.

The Live sending summary restates timing; review it before selecting the Save changes button. ELUNIA rejects an inactive/wrong-Property Survey, unusable specific language, invalid bounds, or an exact duplicate combination of Property, Survey, anchor, direction, offset and local time.

What happens after saving

Saving returns to the Automation list. The processor evaluates active rules periodically. If an existing Stay already qualifies and its calculated due time has passed, it can become due on the next run; saving does not guarantee an immediate send. Exactly-once stage keys prevent duplicate initial/reminder communications.

If the Property uses Manual sending, the rule remains operationally paused. If no active Survey is available, prepare one first. A rule does not update Stay status, activate a Survey, create missing templates, repair an email or override subscription restrictions.

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.