Long Answer Fields

Note: This article applies to the new Form Step experience in Streamline.

Long Answer fields allow users to enter detailed, multi-line responses in your form.

They’re ideal for collecting open-ended information such as feedback, comments, explanations, or other extended text input.

Adding a Long Answer Field

1. In the form editor, click Add Field.
2. From the Basic Fields section, select Long Answer.
3. The field will appear on your form, ready for customization.

Customizing Field Properties

After adding the field, you can edit its properties directly within the form builder.

You can:

• Change the title of the field to match the information you’re collecting.
• Add placeholder text to show an example response or guide users on what to include.
• Include helper text below the field to provide additional context or instructions.

To the right of the field title, you’ll also find quick-access icons to manage visibility and behavior:

• Toggle Required on or off.
• Click the eye icon to hide or show the field.
• Click the lock icon to make the field read-only.
• Click the two boxes to duplicate the field.
• Click the trash can to delete it.

Field Settings

In the field settings panel on the top right, you’ll find additional options to control how the field behaves:

• Data Mapping Label: Add an internal label for data mapping or CSS targeting.
• Default Value: Pre-fill the field with default text or a prewritten example.
• Character Range: Set a minimum or maximum character limit for responses.

These options help ensure data consistency and give you more control over the user experience.

Tips for Using Long Answer Fields

• Use long answer fields for open-ended or detailed responses, such as “Describe your experience” or “Provide additional comments.”
• Keep placeholder text concise — it should guide users, not overwhelm them.
• Combine with character limits if you want to encourage concise responses while still allowing flexibility.
• For shorter input, consider using a Short Answer field instead.