Check sending readiness

Sending Readiness lists conditions ELUNIA can currently detect that may prevent or weaken survey sending. From the left sidebar, open the Feedback menu and select the Needs attention item. Then select the Sending readiness link. Alternatively, select the operational-warning card on Today.

The page evaluates every accessible Property separately and marks it Ready only when its detected issue list is empty. This is configuration readiness—not a promise that an email provider will accept or deliver a particular message.

Conditions currently checked

• Main contact missing: choose the person responsible for feedback workflow in Settings.
• Guest email missing: add a valid email to the affected Guest. Every Stay for a Guest without a valid email can contribute to the count, regardless of whether you plan to send that Stay immediately.
• Stale Stay: an Upcoming Stay has a past check-in date, or a Checked-in Stay has a past Property-local checkout date. Correct an ELUNIA-managed Stay; verify the source system for an integration-managed Stay.
• Recipient suppressed: an active delivery-suppression record matches a Guest email used by the Property’s Stays. Review the affected records before attempting contact.
• Automatic sending needs attention: Automatic mode has no active rule. Optional inactive rules alone are not warnings.
• Survey inactive: in Automatic mode, an active Automation points to a Survey that is not Active.
• Required content missing or outdated: required Survey translations and shared Guest Messages must contain usable, current content. Invitation messages are checked for sending; reminder messages are required only by a workflow with reminders enabled. Draft or unreviewed content also needs attention.
• Account or plan limitation: Automatic mode is selected but the current entitlement does not allow Automations.

Email, suppression and Stay-lifecycle diagnostics can include historical records. Language readiness uses all property guest preferences as described below. A clear page does not guarantee remote provider availability or delivery.

Manual and automatic sending

The Property’s sending method is configured in feedback workflow settings. Manual sending still needs an active Property, active Survey with questions, active invitation template and commercial outbound access for the first-use setup check. Automatic sending additionally needs the Automation entitlement and an active Automation attached to a usable Survey.

Guest and Stay eligibility is evaluated again when a communication is prepared. A clean Readiness page does not mean every Stay is eligible, that the message is already queued, or that a provider delivered it.

After sending, read the communication evidence on the Stay. Queued means accepted for processing, Sent means provider acceptance, and Delivered requires delivery evidence. Survey Opened and Completed are separate invitation events.

ELUNIA reports readiness problems but does not repair dates, unsuppress recipients, activate Surveys or Automations, or change the plan automatically.

Next: Create and send your first Survey or Today metrics and alerts.

Which guest languages need content?

ELUNIA detects every recorded Guest communication language within the Property, never nationality. Guests without stays or assigned rooms and stays at any past or future date are included. Sending eligibility and timing remain separate operational checks.

In preferred-language mode, known guest languages need ready content; unknown preferences need the configured fallback. Missing fallback is a blocker. Explicit property or workflow language choices determine the effective requirements. With no guests, expected languages or the configured default support planning.

Unchanged canonical defaults with maintained translations are Ready without AI Credits or mandatory tenant publication. Only missing or stale customized fields require translation/review. Optional translations outside the effective policy do not become requirements. Discovery never starts AI. Explicitly deferring translations advances setup only; it cannot unblock Go live.

An earlier completed response remains a historical first-feedback milestone. It does not prove that newly required languages or edited source content are ready today. Logo, accommodation Units and PMS are not universal readiness requirements.

Property language defaults and workflow exceptions

The Languages setup stage establishes the normal Property policy. New workflows normally select Use property language settings — Recommended. Existing explicit workflow choices remain exceptions until changed. The Sending stage shows the effective language and offers Use property settings to remove an exception. Saving Property policy never overwrites exceptions or starts AI.

Readiness follows each active workflow's effective language. Manual requests inherit the Property policy; a one-off choice affects only that request. Unknown preference without configured fallback needs attention. Existing properties without a reviewed policy retain their earlier delivery behavior. See Get your property ready.

In guided setup, Languages covers every feedback experience selected in Step 4, including its reminder before a rule is active. Sending saves a new account’s configuration for review; automatic sending starts only after explicit Go live in Step 7. Existing live rules keep their current behavior and require explicit changes.

Step 6 saves independent ON/OFF choices for each selected survey, including surveys in the same journey. Configured ON before activation says Will start when you Go live. OFF means manual sending. The Go-live summary groups these choices by journey; there are no conditional audience controls.