Every question in a step is a field of one of nine types. Add one via Add field in the step editor; each type has its own config options grouped into up to five tabs — Meta, Label, Config, Validations, Options — only the tabs a given type actually needs are shown.
A single numeric score from 1 to max (default 5), shown as stars or icons the visitor taps.
max — the top of the scale (e.g. 5 for a star rating, 10 for a finer scale).This is the type most surveys flag as their main evaluation question (Meta tab).
A row of numbered buttons from min to max (defaults to 1–10).
For the classic 0–10 NPS scale, set min to 0 explicitly — it isn't the default.
min, max — the button range.Multiple-choice, multiple-select — respondents can pick any number of the options you define.
Multiple-choice, single-select — same Options tab as checkbox group, but only one answer at a time.
A draggable slider between min and max (defaults to 0–100), with optional end labels.
min, max, minText, maxText.A dropdown with the options you define.
Free-text response.
This is the type most surveys flag as their main feedback-text question (Meta tab).
A single-line free-text field — for short answers like a name, email, phone number, or link,
where a multi-line textarea would look wrong. The Input type config sets the native input
type (text, email, number, tel, or url), which shapes the keyboard/autofill hints a
visitor's browser or phone gives them for that field.
Input type — text, email, number, tel, or url.A content/instructional block, not a question — the visitor just reads it. Use it to add context, instructions, or a thank-you note between real questions. Nothing is captured or submitted for this field type.
**bold**, *italic*,
~~strikethrough~~, ++underline++, and line breaks — plus a toolbar above the Label field for
applying them without typing the markers by hand, and for inserting an icon at the cursor.Rich text fields have a Meta tab (name/comment/field key, same as every other type) but skip the main evaluation/feedback checkboxes — see below — and have no Config, Validations, or Options tab: there's no answer to validate or configure.
Every answer field can be marked required, and free-text fields (textarea, text input) can additionally demand a valid email address.
Ticking either one reveals a text box underneath it: the message the visitor reads when that check stops them. It arrives already filled in, in every language the domain uses, so you can leave it alone and visitors still get a sensible message in their own language. Overwrite it whenever the default is too blunt for your survey — "We need your email to send the discount code" tells someone far more than "Field is required".
The message is a translated field like any other, so switch language with the selector above it to word it differently per language. It can also vary based on a previous answer (a conditional value), the same conditional mechanism used elsewhere in the editor — most surveys never need this and can leave the single default.
Every scoring/answer field type has a Meta tab controlling whether it's the survey's main evaluation question or main feedback-text question — each survey needs exactly one of each. Popup surveys are blocked from publishing without both; inline and on-site surveys only get a non-blocking warning — see Form types for the full breakdown per type. Rich text is the one exception: since it captures no answer, it can never be flagged as either, so those two checkboxes never appear for it.