Every question in a step is a field. Add field in the step editor opens a catalog of field types grouped into Popular, More and Content, with a search box above them; hovering a tile shows a live preview and what that type is good for, clicking one takes you to its settings. Each type's options are grouped into up to five tabs — Meta, Label, Config, Validations, Options — and only the tabs a type actually needs are shown. Change type in the same dialog swaps a field for another type — see Changing a field's type.
Some catalog tiles are presets of one underlying type: Short text, Email, Phone, Number and Website are all the text input with a different input type picked for you.
The welcome and thank-you screens aren't fields and have no tile: switch the welcome screen on under Settings, and write the text of both screens in Form copy.
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);
Icon and Size — the shape and size of the icons.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) — the classic NPS layout. (Called
"Matrix" in earlier versions; the grid of rows and columns is now the separate Matrix
type below.)
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, an email address, a phone number, a
number or a link, where a multi-line textarea would look wrong. Input type on the Config tab
decides what kind of answer it takes: it sets the keyboard a phone shows and what the browser offers
to autofill, and every type except Text also checks the answer's format.
Input type — one of:
https://example.com. A visitor who types just example.com gets https:// added when they
leave the field.The Phone tile is a text input with Input type set to Phone. The visitor gets a country picker —
a flag and a calling code in front of the number — and the number is grouped the way that country
writes it as they type. They can change the country in the picker, or type or paste a number starting
with + and the country follows it. A number too short or too long for the chosen country isn't
accepted.
Default country — the country the picker starts on, shown only while Input type is
Phone. Left on Visitor's country (automatic), the widget picks one from the survey's language and
the visitor's browser settings. The example above does exactly that, so it starts on the country
your own browser suggests.The answer is saved with its calling code, like +44 7400 123456, however the visitor typed it.
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.
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.
A binary question, drawn as two buttons, thumbs up/down, or a tick and a cross.
Style — buttons, thumbs or tick/cross; optional custom Yes/No labels.A calendar date, using the visitor's own browser date picker.
Earliest date / Latest date — an optional allowed range.Two dates, a start and an end — for a stay, a booking or an availability window. Both use the visitor's own browser date picker, and the end picker doesn't offer days before the chosen start.
Earliest date / Latest date — an optional allowed range, applied to both dates.A visitor picks both dates or neither: one date on its own is never accepted, even when the field isn't required, and the end can't be earlier than the start. The response shows the two dates as one range.
A single checkbox with your agreement text beside it. The text is the field's label, written in the
same editor as a rich text block, so it can link to your terms or privacy policy:
select the words, press Insert link in the toolbar and enter the address, which has to start with
http:// or https://. Leave Link text empty and the address itself becomes the text. With the
cursor inside a link, Edit link and Remove link change or remove it. Marking the field
required means the box has to be ticked, not merely seen.
A square bracket can't sit inside a link's text or right before a link — it would break the link when the survey is saved — so the editor doesn't accept that edit and tells you why.
A grid: your rows down the side, your columns along the top, and one answer per row — a single
column, several columns, or a short text, depending on the Answers per row setting.
Answers per row — one answer, several answers, or free text.Rows with two opposite poles, each rated on a numeric scale between them.
min, max — the scale between the poles (defaults to 1–7).Options the visitor sorts into their order of preference — by dragging, or with the up/down buttons on each row (the keyboard and touch route).
Options the visitor sorts into groups, then orders within each group. Every option starts in a "not placed yet" pool; a row can be dragged into a group or moved with its own selector.
A number per option, and the widget insists they add up to your Total — a running total under
the rows shows the visitor where they stand.
Total, and whether to show the running total.A star rating for each of several items — the same icons, size and maximum as a single rating, once per row.
max, Icon, Size — as for rating.Name, email, phone, company and a message in one block. Choose which of the six sub-fields to ask for and which of them are required; each can carry its own label, or use the built-in wording in the visitor's language. An enabled email sub-field is format-checked on its own, and the phone sub-field gets the same country picker as a phone field, starting on the visitor's own country.
A drawing pad. The visitor signs with a finger or a mouse; the answer is the signature as an image, shown on the response detail page.
A heading with an optional description that splits a long step into parts. Like rich text it is content, not a question — nothing is collected for it, and it never appears among a response's answers.
Section isn't offered in the Add field catalog for now. Sections already in a survey keep working and can still be edited.
Types built on a list — the choices of a single choice, multiple choice, dropdown, ranking or constant sum, a matrix's rows and columns, a group rank's groups, a bipolar matrix's pole pairs — edit it on the Options tab. Each list has its own heading and its own button: Add option, Add row, Add column or Add group; Remove next to an entry deletes it. A new entry arrives numbered ("Option 4", "Row 3") in every language of the domain, and a new bipolar row arrives with a pair of example poles (Slow / Fast, Complicated / Simple, Unfriendly / Friendly) for you to replace.
Change type, next to the field's current type at the top of the field dialog, takes you back to the catalog. Picking a type there starts the field over as that type: its own starter question, options and validation rules replace what you had, so it's quickest to settle the type before writing the question. Opened the catalog by mistake? Back to settings returns to the field as it was.
On a field that's already saved, one thing is kept: its field key, so the responses it has already collected stay attached to it. The main evaluation or main feedback flag goes to the new type if that type can take it and no other field has it.
Every answer field can be marked required. Some types also check the answer itself, with nothing to switch on: an email, website, number or phone input checks its format (see Text input), and a date range needs both dates in the right order. Of those checks, only the email one has a message you can edit here. For a few types "required" means something more specific: a consent box has to be ticked, a matrix needs every row answered, a constant sum has to add up to its total, and a contact form checks each sub-field you marked required on its own.
A field saved earlier with the old Must be a valid email check turned on still shows that checkbox, so you can switch it off; new fields don't offer it.
Ticking required reveals a text box underneath it (the email check shows its box all the time): 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 field has a Meta tab with a name, a comment and a field key. The name and comment are for you only — visitors never see them, and the name is how the field is listed in its step. Leave the name empty and the field is named after its question when you save it.
A rating, opinion scale or slider also gets Use as the main evaluation, and a long or single-line text field gets Use as the main feedback. A survey has exactly one of each: tick the box on a second field and a warning names the field that has it now, and saving moves it over. Popup surveys are blocked from publishing without both; inline and on-site surveys only get a non-blocking warning — see Form types for the breakdown per type, and Steps for how the flags are assigned. Rich text and Section capture no answer, so those two checkboxes never appear for them.