Survey languages

Choose the guest language, not the operator interface

Open Surveys → Edit → Languages. This workspace belongs to that survey; it is not Property Setup Step 5. Add another language and Preview guest content are at the top. The source language is shown separately from required communication languages. Saved optional/historical translations are available in their disclosure.

Recorded property guest preferences are discovered regardless of stay dates or assigned rooms. The property communication policy and explicit sending-rule overrides determine which content is required. Adding an optional translation or opening it here does not change that policy.

Read a language card

Ready means the applicable content is usable. Unchanged ELUNIA defaults can already be ready in the 24 supported guest languages without customer AI Credits or saved tenant translation rows. That is maintained availability, not evidence that your team published a translation.

Needs attention names the missing, outdated or unreviewed customized fields. It does not mean the entire survey must be translated again. For example, adding an invoice/receipt question can leave every unchanged default ready while only the new question and choices need work.

The complete experience includes applicable survey questions, Thank You text, invitation/reminder messages, configured privacy-purpose wording and the fixed guest interface. Sending, setup and Preview use this same distinction; saved Guest Messages alone are not a complete language list.

Resolve the exact missing items

1. Select the affected language card and inspect its listed source fields.
2. Choose Translate custom content with AI, or expand Review / edit manually.
3. Save a manual draft or explicitly approve publication; for AI, wait for the saved result and review each section.
4. Refresh readiness after publication and inspect any remaining blockers.
5. Open Preview guest content in that language. Fallback to source text is labeled and is not proof of a ready translation.

Changing source content can make affected custom translations stale while preserving their old text. Other languages outside current requirements remain optional. No AI starts on navigation, discovery or policy saving.

Other content and supported languages

Guest Messages are shared at property level. Follow their blocker action to edit the original/translation; do not replace an ambiguous original by guessing. Optional privacy-purpose text creates no requirement when empty. If configured, translate it through the Property's Manual privacy-purpose translations or approved preparation workflow.

Arabic, Hebrew, Simplified Chinese, Japanese and Korean remain catalog preferences but are not fully supported guest-delivery languages in this release. ELUNIA preserves those preferences and explains configured supported fallback delivery; missing fallback needs attention. Operator interface languages are independent.

In setup, Continue saves language policy and rechecks it. Finish translations later records a deferral without approving anything or unblocking Go live. See Manual translations, AI translation, and Sending readiness.