Form Fields

Conductly's form designer offers a variety of field types to collect exactly the information you need. This page covers every available field type, its configuration options, and how CRM field mapping works.

Field Types

Short Answer (Text)

A single-line text input for brief responses.

Use for: Names, short descriptions, simple questions

Paragraph (Textarea)

A multi-line text area for longer responses.

Use for: Comments, detailed descriptions, open-ended questions

Number

A numeric input that only accepts numbers.

Use for: Age, years of experience, quantities

Date

A date picker field. Respondents see a calendar picker, and the input is validated as a valid date. The stored value is a standard date string (YYYY-MM-DD).

Use for: Date of birth, trial lesson preferred date, start date

Dropdown (Select)

A dropdown menu where the respondent selects one option from a list.

Use for: Instrument selection, experience level, how they heard about your school

Dropdown fields offer two option sources:

• Input Options -- Define your own custom list of choices
• Values from Conductly -- Pull options directly from your Conductly data (currently supports Instructors and Instruments)

tip

Using "Values from Conductly" for instrument and instructor dropdowns keeps your form options automatically in sync with your school's data. When you add a new instrument or instructor in Conductly, it will appear in your form dropdown automatically.

Multiple Choice (Radio)

A set of radio buttons where the respondent selects exactly one option.

Use for: Yes/no questions, preference selection, single-choice questions

Checkboxes

A set of checkboxes where the respondent can select one or more options.

Use for: Multi-select questions like "Which days work best for lessons?" or "Select all instruments of interest"

Section Header with Description

A non-input field that displays a header and rich text description. Use this to break your form into logical sections and provide instructions or context.

Use for: Section breaks, instructions, explanatory text between groups of questions

note

Section headers are display-only and do not collect any data. They are purely for organizing your form and providing context to the respondent.

Policy with Yes/No (Text with Acknowledgment)

Displays a block of rich text (such as a policy or terms) followed by a confirmation checkbox. The respondent must acknowledge the text to proceed.

Use for: Terms acceptance, policy agreements, liability waivers, photo release consent

This field type has two parts:

• Body Text -- The rich text content (your policy, terms, or information) displayed using a rich text editor
• Confirmation Text -- The label for the acknowledgment checkbox (e.g., "I have read and agree to the above policy")

Default Sections

In addition to individual fields, Conductly provides pre-built sections that bundle commonly needed fields together:

Family Information

A role-adaptive section that collects core family data. It starts with a single required question -- "I am a" with two choices, Student or Parent or Guardian -- and the rest of the section adapts to the answer.

If the respondent chooses Student, the form asks for their Age first:

• 13 or older -- Student Name, Student Email, Student Gender (Male, Female, Non-binary, Prefer not to disclose), Student Birthdate, Primary Phone, Street Address, Apartment/Suite (optional), City, State/Province, and Zip/Postal Code
• Under 13 -- only Age and Parent's Email are collected, so your follow-up goes to the parent

If the respondent chooses Parent or Guardian, the form collects:

• Guardian Name, Guardian Email, Primary Phone, and address fields (Street Address, Apartment/Suite, City, State/Province, Zip/Postal Code)
• A Student Information subsection with Student Name, Student Gender, and Student Birthdate

Names are collected as single Name fields (not separate first/last fields), and the section does not include an instrument question -- add a Dropdown field with "Values from Conductly" → Instruments if you want to ask about instruments.

Because this section always captures an email address, adding it satisfies the form's required Email mapping automatically. See Creating Forms.

note

The Family Information section's fields are fixed -- there are no per-form toggles to show or hide individual fields within it.

Additional Contact 1 Information / Additional Contact 2 Information

Two separate sections, each providing Name, Relationship, Phone, and Email fields for an extra contact person -- useful for emergency contacts or co-parents.

Communication Preferences

A single required question: "Would you like to receive text messages?" Respondents choose between "Yes, I'd like to receive text messages" and "No, I prefer not to receive text messages." Use it to capture SMS opt-in consent.

Field Properties

Every field (except section headers) can be configured with these properties:

Property	Description
Label	The question text displayed to the respondent (required)
Field Type	The type of input (text, checkbox, dropdown, etc.)
Make field required	When checked, the respondent must fill in this field to submit the form

:::note Form validation is currently limited to the Required flag Conductly does not support per-field validation rules like minimum/maximum length, numeric ranges, regex patterns, or conditional logic (show field A only when field B is X). If you need these, you'll need to validate submissions manually or post-process them in your workflow. Let us know if validation rules are important for your school — we may add them in a future release. :::

For fields with options (dropdown, radio, checkboxes):

Property	Description
Options	The list of choices available to the respondent
Option Type	Whether options are custom input or pulled from Conductly data (dropdowns only)

Managing Options

For dropdown, radio, and checkbox fields:

• Click Add option to add a new choice
• Click on an option's text to edit its label
• Click the x button next to an option to remove it
• Options are displayed in the order they appear in the editor

CRM Field Mapping

CRM field mapping is one of the most powerful features of Conductly's forms. It lets you connect form fields to specific database fields in Conductly, so when a form is submitted, the data is automatically imported into the correct student or guardian record.

How It Works

Each field in your form can be mapped to:

1. Entity -- Whether the data belongs to a Student or Guardian record
2. Field -- Which specific field on that record to populate

Available Field Mappings

Conductly Field	Description
First Name	First name of the student or guardian
Last Name	Last name of the student or guardian
Email	Email address
Phone	Phone number
Date of Birth	Student's date of birth
Street	Street address line 1
Apartment, Suite, etc.	Street address line 2
City	City
State	State or province
Zip	Postal/zip code

In addition to these built-in fields, any custom field your school has added for Students or Guardians (Settings > Custom Fields) also appears in the mapping list for the matching entity.

Setting Up a Mapping

1. When creating or editing a field, find the Map to Entity dropdown
2. Select either Student or Guardian
3. In the Field Mapping dropdown, select the corresponding Conductly field -- built-in or custom
4. Save the field

info

CRM field mapping is optional for most fields. Fields without mappings will still collect data -- it just will not be automatically imported into a student or guardian record. You can always view the raw response data regardless of mapping.

The one exception is Email: every form must have at least one field mapped to Email (or include the Family Information section, which captures email automatically). The form cannot be saved otherwise. See Creating Forms.

:::note Mapping to a custom field When a question is mapped to a custom field, its Field Type and Options lock to match that field automatically -- a Dropdown custom field's choices become the question's choices, for example. This keeps every answer valid for the field it feeds. To change the type or choices, edit the underlying field in Settings > Custom Fields instead of the form. A later form submission overwrites an earlier answer in the same custom field, so a family correcting a previous answer on a new submission takes effect. :::

Example Mapping

For a registration form, you might set up mappings like this:

Form Field Label	Entity	Conductly Field
"Parent/Guardian First Name"	Guardian	First Name
"Parent/Guardian Last Name"	Guardian	Last Name
"Parent/Guardian Email"	Guardian	Email
"Student First Name"	Student	First Name
"Student Last Name"	Student	Last Name
"Student Date of Birth"	Student	Date of Birth

When a family submits this form, Conductly will automatically create a guardian record and a student record with the provided information.