All tutorials

Azimea Academy · Full walkthrough

Page flows: question, confirmation and participation policy

Start with an NPS model, refine the question and completion page, and review the account-specific address. Compare saving, previewing and publishing, including the limits of once-per-contact invitations.

5:57Audio: EnglishCaptions: English

What you will see

  • Start with an NPS model, refine the question and completion page, and review the account-specific address.
  • Compare saving, previewing and publishing, including the limits of once-per-contact invitations.

Transcript

A page flow continues the conversation after someone follows an email.

We will start from a feedback model, refine its question and confirmation page, then review its address and access policy.

Previewing the experience and publishing it are separate steps with different effects.

The template library offers ready-made structures for common questions.

We will use the recommendation model as an editable starting point.

Its layout gives us a complete response experience to refine, rather than requiring every label and confirmation message to be

assembled from a blank page.

The page title and description explain why someone is being asked for feedback.

We will make the introduction specific to this demonstration and keep the wording brief.

A clear introduction helps the person understand the purpose of the question before choosing an answer.

The page address combines a fixed account identifier with an editable path.

The account portion keeps the company's public addresses distinct, while the path makes the particular flow recognizable.

We will use a concise name and save it through the application, which checks for conflicting addresses.

The recommendation question uses a zero through ten scale. We will refine the question and the explanations at its ends, keeping the

meaning of the low and high scores clear. The wording should ask one understandable question, rather than combining several different

ideas into the same rating.

Required answer controls whether the person can continue without responding to this question.

We will compare the setting and keep this rating required. Use that choice deliberately.

Necessary answers can support the flow, while unnecessary requirements can make a short feedback request harder to complete.

The confirmation page appears after a successful submission. It deserves its own wording and layout review.

We will thank the person clearly, so the final screen confirms that the response was received rather than looking like another

unanswered question in the flow.

The access policy determines who can complete the published flow.

Once per contact uses a personal invitation generated from an email feedback destination.

A forwarded invitation can be used by its holder, so it limits completion without independently proving who is holding the link.

Saving keeps our current design as a draft. The public experience uses the published version, so saving alone does not apply the new

access policy or page content to visitors. This gives us a chance to review the changes before updating the live flow.

Preview lets us inspect the flow without recording a real response.

We will review its presentation, then use browser back to return to the designer.

This is also a useful place to compare a phone layout before relying on the published experience.

Publishing makes the reviewed content and access policy active. Review both together.

A polished form can still have the wrong participation rules. Updating the published design does not reset invitations that have

already been completed, so republishing is not a way to invite another response from the same contact.

The publication menu provides access to the public page and its address.

Our flow now requires a personal invitation for completion. Select it as an email feedback destination to create the appropriate

recipient links, rather than treating a copied general address as an unrestricted invitation.

The flow now has a clear introduction, a defined response scale, a confirmation page, and an explicit participation policy.

Review these as one experience before using it in an email. The feedback component lesson explains how to connect the published flow to

the answers inside a message.