No visible step
The interface being reviewed shows no visible sending status, message, or step.
What this does not prove: that all conditions were met, or that no internal processing took place.
Start with survey activation, then check the appointment, delay, email address, and language. This sequence makes it easier to find where the send stopped.
For an automatic sending attempt to be processed, several conditions must be reviewed. This page distinguishes three situations: no visible sending step, a displayed status or message, and an email that was not received. The currently documented flow uses email and depends in particular on the feature being enabled, an appointment that meets the documented conditions and is considered completed, the configured delay, a usable address, and the language associated with the booking. A displayed status reports only the result visible at that step; it does not prove external delivery, opening, or a response.
Start by documenting what the interface and inbox actually allow you to observe. These three situations do not describe the same stage of the flow.
The interface being reviewed shows no visible sending status, message, or step.
What this does not prove: that all conditions were met, or that no internal processing took place.
A label or status is visible in the flow. Record its exact text and where it appears.
What this does not prove: that the message was accepted or delivered by external email services.
The expected email is not present in the inbox being checked despite the visible result or observed delay.
What this does not prove: that no processing attempt was made by the platform.
Review the available setting status in the flow being studied without assuming its name or location is identical for every account.
The documented flow depends on an appointment that meets the eligibility conditions and is considered completed.
Processing depends on the delay actually displayed in the configuration. The available values may vary by flow.
The currently documented flow uses email and the language associated with the booking. This page does not confirm SMS or a multichannel option.
A displayed status or message describes what the system reports at a visible step. Its meaning must be interpreted from the wording and context.
This flow helps organize the checks without promising that a single cause can always be identified from the interface.
The user distinguishes between no visible status, a displayed status, and non-receipt of the email.
Limit: identifying the symptom does not automatically reveal the cause of the behaviour.
The automatic sending setting is checked in the available options.
Limit: enabling it does not guarantee that all other conditions are met.
Apparent eligibility, completed status, and the displayed delay are reviewed.
Limit: these conditions do not prove immediate sending or successful delivery.
The usable address and associated language are reviewed in the available context.
Limit: the visible information may be incomplete or may not confirm deliverability.
The context and visible result are recorded to continue the checks or prepare a support request.
Limit: documenting the flow does not guarantee that the exact cause will be identified without further analysis.
Use the guides related to configuration, the sending flow, response experience, and preparing a support request.
Learn about documented features for preparing surveys, collecting responses, and reviewing available results.
View the pageExplore the guides devoted to survey configuration, sending, interpretation, and follow-up.
View the collectionLearn how to prepare and review questionnaire sections, response formats, and language variants.
Read the articleLearn about the documented conditions: activation, eligibility, delay, email address, and associated language.
Read the articleSpecify the page and flow, the sending-setting status, appointment status, displayed delay, associated language, partially masked email address, approximate date, time, and time zone, the exact status or message observed, and a sanitized screenshot if useful. Never send a password, authentication code, key, token, technical secret, or unnecessary personal information.