Overview

Not every step in a questionnaire is a question. From View Questionnaire, use Content to add a content row: a text message, a tap-to-continue button, an image-upload prompt, or a link into another questionnaire.

Content rows appear in the step list with type letter T (text/message-style steps) or A (questionnaire header / branch). Real questions use Q and are added with Question instead—see the question and response types reference.

After you add a content row, click it to open the batch content editor for Pre-Validation, optional post actions, Stage, and extra text fields. Members only see updates after you Publish the parent questionnaire.

Add content dialog

Opened from Content on the questionnaire step list.

FieldWhat to enterEffect after you click Add
Content type Pick what kind of step this is—usually Message for text or buttons, or QuestionnaireHeader to branch into another questionnaire. See the content type table. Sets how the row is stored and how the member app interprets the step after publish.
Text Required for Message and Other types. The member-facing wording (multiline). Use your brand's tone; you can refine it later in the batch content editor. Saved as the step text. In chat-style flows the server may emit it as a Lora text message when the member reaches this step.
Mobile form (Message) Shown only for message-style types. Pick Message, Button, or Images. See the mobile form table. Controls whether the member sees plain text, a single continue button, or an image-upload control.
Batch Name Required when content type is QuestionnaireHeader. Choose the target questionnaire from the list (by display name). Stores the linked questionnaire's internal name. After publish, slide-style and some chat flows can insert that questionnaire's steps at this point when pre-validation passes.

Cancel closes without saving. Add creates the row and refreshes the step list.

Content type

The first dropdown in the add content dialog and on the batch content editor.

Option in AdminStep list letterPlain meaningWhen to chooseMember effect (after publish)
Message T A non-question step: text, a continue button, or an image prompt (depending on mobile form). Instructions, transitions, "tap to continue", or photo upload steps between questions. In Lora chat, the server emits a text-style chat message for this step (subject to pre-validation). Slide/wizard flows read the published JSON and render the step with the chosen mobile form.
Question Q A full question step (same as adding via Question). Normally you add questions with the question dialog instead. This type exists for legacy rows and server-created links. Member must answer before the flow continues; opens the question editor when clicked in Admin.
Other T Alternate content bucket (rare in new setups). Only when your team lead confirms an existing flow uses this type—prefer Message for new content. Not emitted in the standard Lora chat server loop; may appear only in published batch JSON for specific brands.
QuestionnaireHeader A A branch point into another questionnaire by name. Embed a sub-questionnaire inside a parent flow (for example a specialized block after a gate question). After publish, the member app can load the linked questionnaire's published steps inline when pre-validation on this row passes. The target questionnaire must exist and be published separately.
AI message T Agent-generated Lora text — wording is decided at runtime by a configured agent. Personalized instructions or dynamic copy where static text is not enough. Configure agent + optional special instructions in the batch content editor (not in the add dialog). At runtime the agent evaluates whether to show a message and what text to emit in the chat thread. Members see ordinary Lora bubbles — not Admin labels.

Mobile form

The Message dropdown (Admin labels: Message, Button, Images).

Only applies to Message and Other content types—not to QuestionnaireHeader rows.

Option in AdminWhat the member seesWhen to use
Message Plain text in the chat thread or slide body—no special control beyond reading and scrolling. Short explanations, welcome lines, or narrative between questions.
Button The main text appears with a single continue button under it in Lora chat or slide flows. Tapping the button advances the flow—nothing is saved as a questionnaire answer. "Got it", "Continue", consent lines, or transitions where you only need acknowledgment before the next step.
Images An image upload control—the member picks or takes a photo; the app treats the step like a built-in photo question (file picker) even though you added it as content. Mid-flow photo or document capture without creating a separate Q question row.
Continue button under message text in Lora chat
Waiting for screenshot. Capture: a content step with mobile form Button—message text plus one continue button in Lora chat or slides.
Image upload step in a questionnaire flow
Waiting for screenshot. Capture: a content step with mobile form Images—photo picker mid-questionnaire.

The Form column on the step list shows these Admin labels for content rows (for example "Message", "Button", "Images").

Slide-only layouts: Some brands also use special mobile-form values for branded start/end slides (for example side-arrow intro pages). Those still appear as T rows; prefer the three options above unless your brand lead points you to a custom layout.

Batch content editor

Click a T or A row to open fields beyond the add dialog.

Field / sectionWhat to enterEffect
Content type Same options as the add dialog. Auto-saves on change. Switching type may show or hide text vs questionnaire picker fields.
Text Member-facing copy for message-style rows. Updates the stored translation key for this step's language.
Mobile form Message, Button, or Images. Changes how the published step renders in the member app (see table above).
Additional Info Optional secondary line of text shown under the main message on certain slide layouts. Shown as supporting copy on certain start-page layouts in slide flows when your brand uses them.
Linked questionnaire Pick target questionnaire when type is QuestionnaireHeader. Stores linked questionnaire name for inline branch after publish.
AI message — agent General-code agent (AI message type only). Runtime agent decides whether to emit Lora text on this step.
AI message — special instructions Optional multiline prompt (AI message type only). Extra context passed to the agent for this step.
Stage Optional number—same meaning as on question rows. On chat-style onboarding, groups steps into the same progress segment (dots at the top of Lora chat). See view questionnaire — Stage column.
Skip allowed Toggle on message / other / AI message rows. Member may skip without completing the step.
Marks batch complete Toggle on message / other rows. Completes the whole questionnaire when the member passes this step.
Pre-Validation Eligibility rules for showing this step. If rules fail, the step may be hidden in the member flow (same engine as questions and groups). See pre-validation guide.
Post actions What the app should do after the member passes this step (for example navigate to a screen). Used on slide and chat controllers when the member completes or taps through the step.
Batch Content Status Draft, Published (active after parent publish), or Deactivated. Deactivated steps are skipped in published flows.

Type letters on the step list

Quick reference for the Type column—letters match what Admin shows today.

LetterMeansOpens when you click the row
Q Question step Question editor
T Text / message-style content (Message or Other type) Batch content editor
A Questionnaire header / branch (QuestionnaireHeader type) Batch content editor (pick linked questionnaire)

How chat questionnaires deliver content

What the server does after publish for On Boarding Chat, Home Lora Chat, and related chat types.

When a member reaches a step in a chat-style questionnaire, the Lora pipeline evaluates Pre-Validation first. If rules pass:

Content typeServer behaviorMember sees
Message verified — Saved as a Lora text message. Hidden flag set when pre-validation fails. Plain text, continue button, or image upload depending on mobile form.
Question (legacy row on content type) verified — Saved as a Lora question message; flow waits for an answer before continuing. Same as a normal Q question row—prefer adding questions via Question instead.
QuestionnaireHeader verified — When rules pass, the member app loads the linked questionnaire's published steps inline at this point. Sub-flow from another batch name; target questionnaire must be published separately.
Other verified — Not emitted in the standard Lora continue loop. May exist only in published JSON for legacy brands—prefer Message for new content.

Slide questionnaires (On Boarding Slides) do not use this server loop—they read published JSON in the member slide pager. Break The Ice posts the first message into match chat then stops the full step loop.

Members only see updates after you Publish the parent questionnaire. Editing a T or A row auto-saves from the batch content editor.

Other Questions in communications

How Other Questions questionnaire type connects to the Chat channel on communication templates.

Other Questions is not a journey members open from the app menu. Instead:

  1. Create questions under a questionnaire whose type is Other Questions.
  2. On a communication template, open the Chat channel and add chat sequence rows.
  3. Pick individual questions from the Other Questions pool when building that sequence.
  4. Publish the communication (and translations/screens if your brand bundles them).

Members see only the questions you embedded in that comm—typically after a trigger event fires and pre-validation passes. This is separate from home Lora chat questionnaires. See Communications guide and questionnaire types — Other Questions.