Set up your property in 7 steps

After registration, verify your email and open Welcome to ELUNIA. You are preparing one property: the place whose guests, surveys and sending rules belong together. Have its contact details, timezone and at least one survey experience in mind. A logo, room inventory and PMS connection are optional.

Use Continue to save or confirm the current step. Merely opening a step or Preview never confirms it. You can leave and resume from Today → Continue setup. After completion, use Settings → Property setup to review the same settings.

Open the Help dropdown in the top bar and choose Help Center at any point, including before creating your Business. When available, Help for this page opens this setup guide. Private Support Tickets requires active Business access.

Step 1 — Property

Enter the property name and business/contact information shown in the form. Choose the actual property type so recommendations fit your accommodation. Check the timezone carefully: stay dates and local sending schedules use it. Choose the primary contact where offered. Optional phone/logo fields can be completed later.

Select Continue after checking the details. In a new registration this creates the property and selected trial together. It does not send surveys. To correct details later, reopen Property; changes to branding or privacy text shown to guests can require another survey review.

Step 2 — Rooms & units

Add the places guests stay: rooms, villas, apartments or studios. Enter a name and type in the single-unit form, or select Add multiple for a numbered range. Search the list before adding duplicates. Names sort naturally: R1, R2, R9, R10.

You may explicitly defer units if you do not need them yet. A stay can exist without a unit, and the stay form can offer adding one later. A PMS connection is not required. View integrations explains available capabilities; Apaleo currently imports room-name text, not your ELUNIA Unit inventory.

Continue after adding units or choosing the offered deferral. Read any history warning before deleting a unit already used by a stay.

Step 3 — Guests & stays

Choose Add manually, Import CSV, or Connect your PMS. A Guest records a person and their communication preference; a Stay records one visit and the dates used for survey timing. For manual entry, add the guest first, then their stay. Returning visitors can have several stays on the same property guest record.

Select the guest, check-in and check-out, and optionally a room/unit. A new manual Upcoming stay cannot start before today in the property's timezone; checkout cannot precede check-in. Historical records and imports have their own rules. A date passing does not automatically check a guest out.

Record the preferred communication language accurately. A flag is only a language label, not nationality. A guest with a stay years away—or with no stay yet—still contributes their recorded language to discovery.

CSV import first previews the rows and errors before confirmation. The PMS entry opens the Integrations catalog; it does not connect or import automatically. Continue after adding/importing a stay, or explicitly choose I'll add guests and stays later. Selecting an acquisition method alone does not complete the step.

Step 4 — Surveys

The permanent columns are Pre-arrival, During the stay, and After checkout. Use the ＋ Add survey button in each column. A journey can contain multiple surveys; adding another keeps the existing selections. You need at least one selected survey, not all three journeys. The same survey cannot be selected twice in a journey.

Use Choose from templates to browse recommendations, filtering by journey. Alternatively use Create my own survey. A template must fit the intended touchpoint. On each selected survey, open Review & accept survey, inspect the focused preview and select Accept this survey. Previewing alone is not acceptance.

Customize opens editing. A change to reviewed guest-visible content—including applicable published translations or Thank You text—can make that survey require review again. Unchanged surveys retain their reviews. Each added survey needs its own review. Adding or removing a sibling does not change an unchanged survey’s acceptance.

Remove from setup removes the selection, not the survey or its history. Choose explicitly what happens to every connected sending rule: keep it or stop future sending. A rule kept active can continue independently. Archive, stop sending and permanent delete are separate actions. See Survey lifecycle before removing a used survey.

On the Surveys page, legacy surveys under Needs journey assignment remain accessible but fill no journey slot. Assign journey offers only the three journeys above and does not create a duplicate or activate sending.

The separate Public reviews section offers optional setup. It opens the existing property Review Destinations. These links appear after completed surveys regardless of score, across the property—not just the selected After-checkout survey. You can leave them unconfigured. Continue once every selected survey is accepted.

Step 5 — Languages

Choose each guest's preferred language or one language for everyone, and a fallback for unknown or unsupported preferences. Continue saves these choices and checks readiness again; there is no separate Save prerequisite. Explicit language overrides on sending rules remain exceptions to property policy.

ELUNIA detects all recorded property guest languages without a stay-date horizon. Expected languages help planning before guests exist. Unchanged maintained ELUNIA content may already be Ready without tenant AI work. Adding an optional translation does not make it a property requirement.

For customized content, each affected card identifies the exact missing or outdated fields. For example, Português may need only your invoice/receipt question while the unchanged default questions remain ready. Use Translate custom content with AI or expand Review / edit manually there. Manual survey fields can be saved as drafts or explicitly approved and published. Message/privacy blockers offer their relevant editing paths.

AI starts only after an explicit request. A queued request is waiting; Check status reads progress and does not start another translation. After generation, review and approve the prepared sections. Published content remains in use until replacement approval. Insufficient usable credits show an error on the affected card; work rejected before execution creates no charge.

Finish translations later lets you proceed with a deferral. It does not make untranslated content ready or unblock Go live. See Manual translations and AI translation.

Step 6 — Sending

Choose Send manually or Send automatically. Automatic sending depends on your plan, including the plan selected for a trial. If unavailable, choose manual or use Upgrade plan. A verified successful upgrade provides a return to Sending; returning from checkout alone is not proof of activation.

For eligible new setup only, automatic sending may be suggested before you have confirmed a preference. This is a proposed configuration, not an active rule. Existing confirmed or live settings are preserved.

Review each selected survey's schedule: Pre-arrival is before check-in, During the stay is relative to the visit, and After checkout is after departure. Inspect minimum nights, reminders and the communication language. Inherited language follows property policy; an explicit rule override remains visible. Removing a rule from the planned automatic selection does not erase its history.

For a new account, Continue saves the configuration for Step 7 without enabling it. Edits to established live rules are real operational changes: read the confirmation and timing warnings first. See Automation timing.

Step 7 — Review & Go live

Read the selected surveys grouped under each journey. Each survey shows its own manual or automatic sending choice and, when automatic, its timing. A matching-stay count is informational, not an audience configuration or a promise of immediate delivery. Optional Public reviews offers Set up public reviews or Manage review destinations, with a return to Step 7. Missing setup confirmations and operational blockers appear with actions; resolve the affected item rather than restarting setup.

The actionable readiness list links to the affected language/content work. Review each changed field and refresh readiness when publication is complete. Deferred translations, an unavailable automatic-sending entitlement, or an unreviewed selected survey still block activation.

Select Go live only when you intend to activate. ELUNIA rechecks readiness, activates the selected surveys and planned automatic rules, and leaves manual experiences manual. Opening Step 7 or Preview does none of this. Activation does not guarantee immediate delivery: guest eligibility and schedules still apply.

After Go live

The success summary shows the activated experiences, languages and sending modes. First-activation celebration does not replay on refresh or later visits. You can reopen the activation summary from completed setup.

Use Today for operational warnings, Feedback for issues needing follow-up, Survey Responses for submitted answers, and Insights for trends. Inspect Automations before changing future schedules. Reopen Settings → Property setup deliberately whenever you need to review configuration; navigation does not reset activation or first-response history.

Independent sending choices

In Step 6 — Sending, select Send automatically to configure individual survey switches. Each survey has its own ON/OFF choice and Edit schedule button. ON before activation says Will start when you Go live; a saved, active rule says Active. OFF means Send manually. Use Continue to save. No switch silently enables sibling surveys. Setup does not offer conditional audience rules.

Remove from setup affects only the chosen survey; other surveys in the same journey remain selected. Draft/Active is a lifecycle state, separate from review acceptance and selection.