Inline form

An inline form is embedded directly in your page's own layout, like any other piece of content on the page — it's not a modal, and it doesn't float above anything. It's simply part of the page, visible to every visitor who scrolls to it, with nothing to click to open it.

Use cases

An always-visible feedback prompt anchored to one key page (checkout confirmation, your dashboard, a docs article) — feels like part of the page rather than an interruption.
Long-form content (articles, documentation) where readers can leave feedback whenever they want, at their own pace, without a popup breaking their flow.
Revealed only after a specific moment: inline forms support the same delay/click-trigger settings as popups (see Settings), so you can have one fade in only after a visitor scrolls to it or clicks something — without ever using a modal.

Configuration

Same step/field editor as every other type — add steps and fields from the survey editor, see Field types and Steps. Inline forms don't have any type-specific settings beyond that (no trigger button, no delay/trigger config — those only apply to popup forms, see Settings).

Publishing requirements

Publishing enforces the same baseline as every type: at least one step, at least one field per step, and every translated field/label filled in for each of the domain's locales.

One field should be flagged as the main evaluation question, and one as the main feedback text (used elsewhere in the app — see Responses — as the response's headline score and quoted comment). For an inline form, missing either one is only a non-blocking warning: the editor will nudge you, but you can still publish without them. Popup forms enforce both as hard errors instead — see Popup form.